Wireless telephone system including voice over IP and POTS
Claim Score by NHIP
Abstract
A telephone capable of placing or receiving calls over the PSTN or a packet network. The telephone can store multiple telephone numbers for each potential called party along with preferences that govern the order of selecting telephone numbers to service any given outgoing call. Some or all of the telephone numbers can be associated with a presence service. Presence indicators stored in the telephone are dynamically updated via the packet network connection and are used as part of the telephone number selection algorithm. The preferred embodiment is a wireless system having a base station and a remote device.

Term
Term ended
Expired 23 September 2023, 3 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
12 claims: 3 independent, 9 dependent
- 1A method for telephone call connecting using a base station and a mobile device, the base station having a first connection to a circuit switched telephone network and a second connection to a packet network and storing one or more telephone numbers associated with each of a plurality of potential called parties and a preference order in which to call the telephone numbers for the potential called parties having more than one telephone number associated therewith, the mobile device adapted for communicating speech to the base station using a wireless protocol and storing names for potential called parties, the method comprising:selecting, at the base station when one of the stored names is selected for calling at the mobile device, either the first connection or the second connection to service a call from the mobile device based on the stored preference order a route preference associated with the selected stored name, further comprising selecting the first connection when a first telephone number in the preference order is associated with the circuit switched telephone said route preference so dictates use of a circuit switched network and the second connection when the first telephone number is associated with the packet network said route preference so dictates use of a packet switched network .
- 10A method for calling a telephone number associated with a selected name from a telephone system base station, based on a preference order associated with the selected name, comprising:storing one or more telephone numbers associated with each of a plurality of potential called parties and a preference order in which to call the telephone numbers for the potential called parties having more than one telephone number associated therewith, and selecting, at the base station when one of the stored names is selected for calling at a mobile device, either a first connection to a circuit switched telephone network or a second connection to a packet network to service a call from the mobile device based on the stored preference order a preferred route associated with the selected stored name, wherein selecting either a first connection or a second connection selects the first connection when a first telephone number in the preference order is associated with the circuit switched telephone and the second connection when the first telephone number is associated with the packet network said preferred route dictates use of a circuit switched network and said second connection when said preferred route dictates use of a packet switched network .
- 12Broadest claimClaim Score 50, average(NHIP)A telephone system for placing a call to a telephone number associated with a selected name, said telephone system comprising:a handset, said handset being associated with a base station, said handset having a plurality of names therein, said plurality of names being received at said handset from said base station, said handset being constructed to transmit at least information about said selected name to said base station to initiate said placing of said call, said selected name being one of said plurality of names;said base station comprising, a first connection to a packet network, a second connection to a circuit switched network, a third connection to said handset through which said base station receives said selected name from said handset, and a stored route preference through which said base station determines whether to place said call as a VOIP call using said first connection to a packet network or as a POTS call using said second connection to a circuit switched network, said stored route preference being associated with at least said selected name.
Independent claims3
28 paragraphs in 5 sections, as filed
BACKGROUND OF THE INVENTION
TECHNICAL FIELD
The invention relates to a wireless telephone handset and an intelligent base station that connects a call either to the public switched telephone network (PSTN) or to a packet network using Voice over IP (VoIP) based on a per call selection algorithm.
At the present time, it is becoming commonplace for users to communicate via speech using packet networks in lieu of the standard public switched telephone network. Voice over IP (Internet Protocol) is typically used to provide this capability. Users can select from a variety of products including wired VoIP desk sets and wireless systems that use both proprietary protocols between a handset and a base station, as well as the wireless LAN 802.11 protocols. Of course, users can also select from any number of wireless telephones that connect to the PSTN. However, if one wishes to avail him or herself with access to both types of networks, one must acquire a separate system for each, one for VoIP gateway dialing and the other for wireless traditional PSTN dialing, and manually select which system to use on any given telephone call.
SUMMARY OF THE INVENTION
The invention addresses the problems by providing a telephone system that in a first respect is capable of placing or receiving calls over the PSTN or a packet network. The preferred embodiment for packet communications is via the TCP/IP protocol. In a second aspect of the invention, the telephone system has the capability of storing multiple telephone numbers for each potential called party along with preferences that govern the order of selecting telephone numbers to service any given outgoing call. Some or all of the telephone numbers can be associated with a presence service. Cell phone operators already have the ability to collect and distribute presence indicators. Other telephones that are associated with computers can be associated with presence services at the present time. All telephones will no doubt have this capability at some time in the future. For the telephone numbers that are associated with a presence service, presence indicators stored in the telephone system are dynamically updated via the packet network connection and are used as part of the telephone number selection algorithm.
In the preferred embodiment, the telephone system is a wireless system comprising a base station and a handheld mobile device such as a wireless telephone handset or Personal Data Assistant (PDA) equipped with a microphone and speaker. A user of the telephone system configures the system over a Local Area Network (LAN) using a browser at a workstation. The mobile device or the base station could also be equipped as well to perform configuration using either a keypad or voice recognition technology. Configuration includes among other things adding names and telephone numbers to a database in the telephone system. Configuration also includes the selection of a preference algorithm to control the order in which telephone numbers are dialed to attempt connection with a called party and whether any given call is routed first over the packet network or the PSTN. The selection of PSTN or VOIP can be based on many algorithms. In the preferred embodiment, the user can configure the selection of routing by time of day or area code. Certainly, these preference algorithms are intended as examples and not to be limiting. The dynamically adjusted presence indicators, of course, play a large role in the selection of telephone numbers.
BRIEF DESCRIPTION OF THE DRAWINGS
<figref idref="DRAWINGS">FIG. 1</figref> shows block diagram of a wireless system, including a handset or handheld with a display and an intelligent base station, for practicing the invention;
<figref idref="DRAWINGS">FIG. 2</figref> shows an illustrative block diagram of the intelligent base station;
<figref idref="DRAWINGS">FIG. 3</figref> shows an illustrative block diagram of the handset or handheld of the wireless system;
<figref idref="DRAWINGS">FIG. 4</figref> shows a screen image of a configuration menu that is displayed on a networked computer in a preferred embodiment of the system, or secondarily on a display of the handset or handheld;
<figref idref="DRAWINGS">FIG. 5</figref> shows a computer display of a called party names list stored in the base station;
<figref idref="DRAWINGS">FIG. 6</figref> shows a computer display image of a presence table stored in the base station and associated with potential called parties;
<figref idref="DRAWINGS">FIG. 7</figref> shows an computer display image of a time-of-day routing preference table stored in the base station and used to select routing of a call over VoIP or POTS telephone lines;
<figref idref="DRAWINGS">FIG. 8</figref> shows an alternative routing preference table bases on area code rather than time-of-day; and
<figref idref="DRAWINGS">FIG. 9</figref> shows a functional flowchart of the steps that are performed in the course of placing a telephone call from the mobile handset or handheld.
DETAILED DESCRIPTION
<figref idref="DRAWINGS">FIG. 1</figref> shows a wireless mobile telephone handset <b>100</b> that communicates with a base station <b>102</b> using well-known wireless protocols. The base station has two ports for communicating with called parties. A first port <b>104</b> is a standard telephone connection for communicating with the public switched telephone network (PSTN) for POTS (Plain Old Telephone Service) telephone service. The second port <b>106</b> is a standard data connection for communicating with a data network, such as the Internet for telephone communication using Voice over IP (VoIP). In the preferred embodiment, the packet network connection <b>106</b> from the base station is connected to an internet <b>114</b> using a router <b>112</b> that is attached to a LAN <b>108</b>. LAN <b>108</b> also connects to a computer <b>110</b> and base station <b>102</b>. The base system is configured over the LAN <b>108</b> using a browser, such as Microsoft Internet Explorer, that is executed in a computer <b>110</b> attached to the base station <b>102</b> via the LAN <b>108</b>. This technique of configuring network devices is well known and used typically to configure routers, bridges, etc. The packet connection <b>106</b> is also used to receive presence indications associated with potential called parties at designated telephone numbers, as will be explained below. These presence indications arrive from the internet <b>114</b> and are forwarded to base station <b>102</b> via LAN <b>108</b>.
<figref idref="DRAWINGS">FIG. 2</figref> shows an illustrative block diagram of the base station <b>102</b>. It is equipped with an antenna <b>200</b> to communicate wirelessly with the handheld device <b>100</b>. The antenna <b>200</b> is connected to a transmitter/receiver <b>202</b> over which digital data is transmitted between the handheld <b>100</b> and the base station <b>102</b> using wireless telephony protocols. The base station is controlled by a CPU (central processing unit) <b>204</b>. CPU <b>204</b> is controlled by a firmware program and operating system embedded in firmware memory <b>206</b>. CPU <b>204</b> also communicates with other portions of the base station via a data bus <b>222</b>. The base station can also be equipped with a keypad <b>208</b>. microphone and speaker (not shown) for additional convenience and functionality.
A switch <b>210</b> controls whether the base station communicates with the PSTN or with a data network. In the VoIP state, switch <b>210</b> connects the transmitter/receiver <b>202</b> to packet interface <b>212</b>. Packet interface <b>212</b> performs the functions necessary to packetize data from the handheld <b>100</b> and send it to TCP/IP stack <b>214</b>; for incoming data from the packet network via connector <b>216</b>, packet interface <b>212</b> de-packetizes the data and sends it to the transmitter/receiver <b>202</b>.
When switch <b>210</b> is in the POTS state, it connects the transmitter/receiver <b>202</b> to a POTS interface <b>218</b>, which is conventional well-known apparatus in commercial use today for PSTN communication via the POTS connector <b>220</b>.
The wireless system can be an analog system or a digital system. The fundamental technology for either type of system, including the transmitter/receiver <b>202</b> and the POTS and packet interfaces is commercially available in chip sets. Conexant, Inc., for example, is a leading manufacturer of wireless telephony digital and analog chips as well as technology for voice over IP.
A name list <b>224</b> is maintained in a random-access memory of the base station; the names list contains the names of people that can be called using the list, along with the information necessary to complete the calls. Also in random-access memory is a presence table <b>226</b> that contains information regarding the instant presence at specified telephones or devices of people in the names list <b>224</b>. The name list and presence table are discussed in more detail below. One or more instant messaging (IM) clients <b>228</b> are also present in the memory of the base station to maintain the dynamic state of the presence table. The IM clients receive presence information from the Internet via the network connector <b>216</b>. The IM clients are loaded into the base station using the computer <b>110</b> and the LAN <b>108</b> connection to the base station.
<figref idref="DRAWINGS">FIG. 3</figref> contains a block diagram of the handheld <b>100</b>. An antenna <b>300</b> communicates with base station <b>102</b> and connects to a transmitter/receiver <b>302</b> of the handheld. Like the base station, the handheld <b>100</b> also contains a CPU <b>304</b> controlled by a firmware program and operating system <b>306</b>. CPU <b>304</b> communicates with other equipment in the handheld via a data bus <b>322</b>. A keypad <b>308</b> allows the entry of telephone numbers if that mode of operation is desired by a caller. The handheld also contains a names list <b>324</b> in its random-access memory, but unlike the names list <b>224</b> in the base station, names list <b>324</b> contains only the names in the identical format as stored in the base station names list. Whenever the base station names list <b>224</b> is edited, when the user is completed and saves the table, the names only portion of the table is transmitted to the handheld and stored in its names list. When a caller activates the handheld names list <b>324</b>, its contents are displayed on display <b>326</b>. The caller can navigate through the list using buttons on the keypad or, with today's technology; a voice recognition chip can easily be used to allow a caller to verbally navigate the names list. The handheld also contains other equipment that is standard in wireless mobile units, illustrated here as <b>310</b>, that connects to a microphone <b>312</b> and speaker <b>314</b>.
The operation of the system is now described. <figref idref="DRAWINGS">FIG. 4</figref> shows a sample menu of configuration services that is displayed to a user at computer <b>110</b> of FIG. <b>1</b>. This sample menu contains links for editing the name list, and for configuring time-of-day or area code preferences, and for setting the number of rings that determine when the system abandons a number as unanswered. As mentioned, the preferred way of configuring the base station is by using a browser such as the Microsoft Internet Explorer, although many other modes are possible and contemplated within the scope of the invention. The operating system contained in firmware <b>206</b> of the base station contains a server to communicate with the browser software at the computer <b>110</b>. Name list <b>224</b> in the base station is edited by displaying its contents at the browser.
<figref idref="DRAWINGS">FIG. 5</figref> shows an illustrative screen that is displayed at computer <b>110</b> for name entry, display and editing. Each entry of the name list contains a Name field <b>500</b>, a Number field <b>502</b>, a Preferred field <b>504</b>, a Cell field <b>506</b>, an Instant Message (IM) field <b>508</b>, and an instant messaging ID field <b>510</b>. In each entry, the name field <b>500</b> contains a person's name in any way that the user wishes to identify the person. The Number field <b>502</b> contains a telephone number associated with that person. As shown in the first four entries of the name list of <figref idref="DRAWINGS">FIG. 5</figref>, John Doe has at least four telephone numbers at which he might be reached. If “JD” in the fifth entry refers to the same John Doe, then he has five numbers entered into this list. The Preferred field <b>504</b> contains a flag that indicates a preference for a particular number. The Cellular field <b>506</b> contains a flag that identifies a number as belonging to a cell phone. The IM field <b>508</b> contains an identification of an instant messaging client if there is such a client associated with the particular telephone number. Each such client corresponds to an instance of IM client <b>228</b> in FIG. <b>2</b>. There are presently a number of possible IM services, such as offered by Lotus Sametime, ICQ, Yahoo, AOL and Microsoft's MSN. Some of these services are free and require only a registration via the World-Wide-Web. In <figref idref="DRAWINGS">FIG. 5</figref>, John Doe has registered with three such services; AOL Instant Messaging (AIM), Yahoo and Sametime. Each service is associated with a different telephone number, and each requires a different IM client loaded as an instance of IM Client <b>228</b>. Each service has a different format for a user identification and the user identification is placed in the ID field <b>510</b> of FIG. <b>5</b>. For example, John Doe's ID for AIM is “JOHNDOE”. On the other hand, Sametime uses an internet e-mail address as the user ID. John Doe's e-mail address is jd@us.ibm.com. New entries are created by positioning the cursor in the desired field of the row <b>512</b> at the bottom of the screen and typing in the contents of the field. This is a data entry technique that is used by many database programs, such as Microsoft Access for example. The same entry technique is used for the tables shown in <figref idref="DRAWINGS">FIGS. 6</figref>, <b>7</b> and <b>8</b> as well.
For each entry in the names list (FIG. <b>5</b>), there is a corresponding entry in the Presence Table, as shown in FIG. <b>6</b>. The names are shown in <figref idref="DRAWINGS">FIG. 6</figref>, but that is primarily for clarity here; only a number field is actually required in the preferred embodiment. The P (presence) field <b>604</b> contains a flag that is set or reset dynamically as a person associated with an IM service logs into and off of the service. A “Y” indicates that a person is logged in at the number associated with the IM service. A “N” indicates that the person is not logged-in; an empty field means that the telephone number is not associated with an IM service. Each presence service generates a presence or non-presence message, along with a telephone number, as its registered members log on and off of a service, and these messages are transmitted in real-time to interested people. Such messages are received over the Internet by an IM Client <b>228</b> and communicated to the appropriate entry in the presence table identified by the received number. This is conventional service at this time that differs in operation somewhat with the different services, but RFCs 2778 and 2779 have been proposed by the Internet Engineering Task Force to attempt to establish an operational standard.
The user can establish preferences for the routing of calls. Obviously, there are many alternative ways of defining user preferences. Two alternative preferences arc taught here for illustrative purposes, a time-of-day (TOD) preference, and an area code (AC) preference. A user selects which service he or she wishes by means of the browser menu in FIG. <b>4</b>. If a user selects TOD preferences, the TOD preferences table in <figref idref="DRAWINGS">FIG. 7</figref> is displayed by the browser. By way of example, each entry of this table contains a start time field <b>700</b>, an end time field <b>702</b>, a primary field <b>704</b> and a secondary field <b>706</b>. The start and end fields of an entry define an interval of time in which the preferred call routing is specified by the primary field <b>704</b>. If a call is unsuccessful via the preferred route (VoIP or POTS), and if there is a secondary entry, then the call is re-tried via the secondary route. If mere is no entry in the secondary field, this means the user never wants to use that routing in the defined time interval. If a routing field contains a “DC” (don't care) entry, then a call is placed in the associated time interval by the base station making arbitrary selection as to primary and secondary routing.
If the user prefers to route calls according to area code, then the user configures the table shown in <figref idref="DRAWINGS">FIG. 8</figref>, using the menu of FIG. <b>4</b>. Each entry of the AC table has an AC field <b>800</b> that contains a desired area code. The primary field <b>804</b> and the secondary field <b>806</b> arc used in the same way as described above for TOD preferences.
<figref idref="DRAWINGS">FIG. 9</figref> contains an illustrative functional flowchart of actions performed to place a telephone call. At step <b>900</b>, a user activates the name list <b>324</b> stored in the handheld <b>100</b> and navigates to the name of the person he or she wishes to call. The user then initiates the call by depressing a CALL key or equivalent. As a result, the selected name is transmitted to the base station <b>102</b> at step <b>902</b>. The selected name is received at the base station at step <b>904</b> and used to search for an entry in the name list <b>224</b> of the base station. If the selected name is “John Doe” for example, a preferred name entry is found at the second John Doe entry at telephone number 919-530-4354, as indicated by the Y in the Preferred field <b>504</b>. This particular number is not associated with a cellular phone, as indicated by the N in the Cellular field <b>506</b>. However, field <b>508</b> indicates that this phone is associated with the AOL IM service AIM. The base station therefore, interrogates the second entry of the Presence table in <figref idref="DRAWINGS">FIG. 6</figref> to determine if John Doe is present at this telephone location. Field <b>604</b> of the presence table indicates that John Doe is present at number 919-530-4354. Therefore, the base station places a call to the preferred number 919-530-4354 for John Doe. If the Presence table had indicated that John Doe was not present (N in field <b>604</b>) at the preferred number, the base station would then look for an entry for John Doe in the Presence table for which the presence indicator <b>604</b> is set. Failing that, the base station would lastly look for a presence entry that is null (neither Y nor N). Such a null state means that there is no presence service associated with the corresponding telephone number. The base station would therefore dial this number last, and of course there may be plural such telephone numbers that might be dialed in sequence until John Doe is located or the list of possible numbers is exhausted. If it is assumed that the Y entry for John Doe in the presence field <b>604</b> were in fact a N, then base station <b>102</b> would select the number 919-260-1231 from the first entry, because that's the only number at which John Doe might be present.
After a number has been selected at step <b>904</b>, step <b>906</b> interrogates a preference table to determine the routing (VoIP or POTS) of the call. If the user has selected time-of-day (TOD) routing, the TOD table in <figref idref="DRAWINGS">FIG. 7</figref> is interrogated. Assuming that it is 10 AM in the morning for example, the TOD table indicates (field <b>704</b>) that VoIP is the primary routing choice. The base station controls switch <b>210</b> to select the VoIP path to TCP/IP connector <b>216</b> and the call is then placed in a conventional VoIP fashion at step <b>910</b>. If that call fails for any reason, or if the call is unanswered after a specified number of rings (see <figref idref="DRAWINGS">FIG. 4 and 912</figref> in FIG. <b>9</b>), or if the caller initiates a disconnect from the keypad <b>208</b>, the base station continues to step <b>914</b> and examines the secondary routing field <b>706</b> of <figref idref="DRAWINGS">FIG. 7</figref> for a secondary routing (POTS in this example). If a secondary routing is specified, then the base station re-tries the call at <b>914</b> using the secondary preference. If the user has not specified a secondary routing preference, as at field <b>706</b> of the second TOD entry (5 PM to 11 PM), then the base station will not re-try the call to this particular number. At <b>916</b>, the base station returns to step <b>904</b> to search for another telephone number to try. Eventually, a call will be successful (which is not shown in <figref idref="DRAWINGS">FIG. 9</figref>) or all possibilities will have been exhausted. The preferred embodiment in the latter case displays an appropriate no answer message on the display <b>326</b>, as illustrated at <b>920</b> of <figref idref="DRAWINGS">FIG. 9</figref>, if the call is ultimately unsuccessful.
Artisans in the field of the invention will realize that there are many variations within the spirit and scope of the preferred embodiment. It is the intent of the inventors to encompass these variations to the extent possible according to the state of the relevant art and the law.
Contents5
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2008222294A1 | Cited by | United States of America | Pre-grant |
| US2002029142A1 | Cites | United States of America | Applicant |
| US2002075306A1 | Cites | United States of America | Applicant |
| US2003013442A1 | Cites | United States of America | Applicant |
| US2003040310A1 | Cites | United States of America | Applicant |
| US2003144030A1 | Cites | United States of America | Applicant |
| US2003176180A1 | Cites | United States of America | Applicant |
| US2004009787A1 | Cites | United States of America | Applicant |
| US2004052245A1 | Cites | United States of America | Applicant |
| US2005043044A1 | Cites | United States of America | Applicant |
| US2005096024A1 | Cites | United States of America | Applicant |
| US2005119016A1 | Cites | United States of America | Applicant |
| US2005124386A1 | Cites | United States of America | Applicant |
| US2005239470A1 | Cites | United States of America | Applicant |
| US2006079223A1 | Cites | United States of America | Applicant |
| US2006160565A1 | Cites | United States of America | Applicant |
| US2007280252A1 | Cites | United States of America | Applicant |
| US2008003952A1 | Cites | United States of America | Applicant |
| US2008279175A1 | Cites | United States of America | Applicant |
| US2009238147A1 | Cites | United States of America | Applicant |
| US5036531A | Cites | United States of America | Applicant |
| US5533019A | Cites | United States of America | Applicant |
| US5588039A | Cites | United States of America | Applicant |
| US5590174A | Cites | United States of America | Applicant |
| US5590398A | Cites | United States of America | Applicant |
| US5594777A | Cites | United States of America | Applicant |
| US5910946A | Cites | United States of America | Applicant |
| US5933774A | Cites | United States of America | Applicant |
| US6115598A | Cites | United States of America | Applicant |
| US6131043A | Cites | United States of America | Applicant |
| US6134235A | Cites | United States of America | Search report |
| US6205135B1 | Cites | United States of America | Applicant |
| US6222829B1 | Cites | United States of America | Applicant |
| US6295457B1 | Cites | United States of America | Applicant |
| US6351464B1 | Cites | United States of America | Applicant |
| US6456616B1 | Cites | United States of America | Applicant |
| US6539225B1 | Cites | United States of America | Applicant |
| US6556821B1 | Cites | United States of America | Applicant |
| US6584317B2 | Cites | United States of America | Applicant |
| US6597686B1 | Cites | United States of America | Search report |
| US6600925B1 | Cites | United States of America | Applicant |
| US6731629B1 | Cites | United States of America | Applicant |
| US6865391B1 | Cites | United States of America | Applicant |
| US6879833B2 | Cites | United States of America | Applicant |
| US6889045B2 | Cites | United States of America | Applicant |
| US6928067B1 | Cites | United States of America | Applicant |
| US6957060B1 | Cites | United States of America | Applicant |
| US7024198B2 | Cites | United States of America | Applicant |
| US7047012B1 | Cites | United States of America | Applicant |
| US7058415B2 | Cites | United States of America | Applicant |
| US7089011B1 | Cites | United States of America | Applicant |
| US7092712B2 | Cites | United States of America | Applicant |
| US7139577B1 | Cites | United States of America | Applicant |
| US7209457B1 | Cites | United States of America | Applicant |
| US7336948B1 | Cites | United States of America | Applicant |
| US7447217B2 | Cites | United States of America | Applicant |
| US7450939B2 | Cites | United States of America | Applicant |
| US7492758B2 | Cites | United States of America | Applicant |
| US20020029142A1 | Cites | United States of America | Third party observation |
| US20020075306A1 | Cites | United States of America | Third party observation |
| US20030013442A1 | Cites | United States of America | Third party observation |
| US20030040310A1 | Cites | United States of America | Third party observation |
| US20030144030A1 | Cites | United States of America | Third party observation |
| US20030176180A1 | Cites | United States of America | Third party observation |
| US20040009787A1 | Cites | United States of America | Third party observation |
| US20040052245A1 | Cites | United States of America | Third party observation |
| US20050043044A1 | Cites | United States of America | Third party observation |
| US20050096024A1 | Cites | United States of America | Third party observation |
| US20050119016A1 | Cites | United States of America | Third party observation |
| US20050124386A1 | Cites | United States of America | Third party observation |
| US20050239470A1 | Cites | United States of America | Third party observation |
| US20060079223A1 | Cites | United States of America | Third party observation |
| US20060160565A1 | Cites | United States of America | Third party observation |
| US20070280252A1 | Cites | United States of America | Third party observation |
| US20080003952A1 | Cites | United States of America | Third party observation |
| US20080279175A1 | Cites | United States of America | Third party observation |
| US20090238147A1 | Cites | United States of America | Third party observation |
29 members in 12 offices
Priority claims10
| Document | Office | Kind | Date |
|---|---|---|---|
| 66931403 | United States of America | A | |
| 66931403 | United States of America | A | |
| 25895308 | United States of America | A | |
| 25895308 | United States of America | A | |
| 57483909 | United States of America | A | |
| 10669314 | – | – | – |
| 12258953 | – | – | – |
| US20030669314 | – | – | – |
| US20080258953 | – | – | – |
| US20090574839 | – | – | – |
Members29
| Document | Office | Kind | |
|---|---|---|---|
| US2005063361A1 | United States of America | A1 | |
| US2005064894A1 | United States of America | A1 | |
| CA2535300A1 | Canada | A1 | |
| CA2693755A1 | Canada | A1 | |
| WO2005029889A1 | World Intellectual Property Organization (WIPO) | A1 | |
| MXPA06001945A | Mexico | A | |
| EP1668936A1 | European Patent Office (EPO) | A1 | |
| IL174501D0 | Israel | D0 | |
| CN1846452A | China | A | |
| BRPI0414703A | Brazil | A | |
| KR20060126905A | Republic of Korea | A | |
| EP1668936B1 | European Patent Office (EPO) | B1 | |
| AT377916T | Austria | T | |
| ATE377916T1 | Austria | T1 | |
| JP2007534206A | Japan | A | |
| DE602004009948D1 | Germany | D1 | |
| EP1668936B9 | European Patent Office (EPO) | B9 | |
| DE602004009948T2 | Germany | T2 | |
| US2009040968A1 | United States of America | A1 | |
| US7492758B2 | United States of America | B2 | |
| US7590106B2 | United States of America | B2 | |
| KR100940977B1 | Republic of Korea | B1 | |
| US7710946B2 | United States of America | B2 | |
| CN1846452B | China | B | |
| IL174501A | Israel | A | |
| JP4608493B2 | Japan | B2 | |
| USRE42271EThis record | United States of America | E | |
| CA2535300C | Canada | C | |
| CA2693755C | Canada | C |
47 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Receipt into PubsR1021 | R1021 | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Post CardPST_CRD | PST_CRD | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Oath or Declaration Filed (Including Supplemental)C602 | C602 | |
| Response after Non-Final ActionA... | A... | |
| Mail Post CardPST_CRD | PST_CRD | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Notice of Reissue Published in Official GazetteNRE. | NRE. | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Preliminary AmendmentA.PE | A.PE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
5 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS |
Numbers
- Publication
- RE042271
- Publication, DOCDB
- RE42271
- Publication, EPODOC
- USRE42271E
- Application
- 12574839
- Application, DOCDB
- 57483909
- Application, EPODOC
- US20090574839
Titles
- English
- Wireless telephone system including voice over IP and POTS
Classification
- CPC, 7
- H04M7/0057
- H04L51/043
- H04M1/2535
- H04M1/72502
- H04M7/0012
- H04W8/18
- H04W84/16
- IPC, 8
- H04L12 66
- H04B1 38
- H04M1 00
- H04M1 253
- H04M1 72502
- H04M3 44
- H04W84 16
- H04W92 14
- USPC, 10
- 370353000
- 370401000
- 379201020
- 379216010
- 379355020
- 379355030
- 379355040
- 455414100
- 455552100
- 455561000