Wireless telephone system including voice over ip and pots
Abstract
This record has no abstract on file.
Term
Term ended
Expired 14 September 2024, 2 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
24 claims: 19 independent, 5 dependent
- 1回線交換電話ネットワークへの第1接続とパケット交換ネットワークへの第2接続とを有する基地局と、無線プロトコルを用いて音声を前記基地局に通信するためのモバイル・デバイスと、を含む電話システムであって、前記基地局が、前記モバイル・デバイスのユーザにより選択可能な1つ又はそれ以上のエンティティの識別を格納する装置と、各エンティティに関連付けられた1つ又はそれ以上の電話番号を格納する装置と、前記パケット交換ネットワークを介して、格納された電話番号に各々が関連付けられた1つ又はそれ以上の存在インジケータを受信する装置と、前記受信した存在インジケータを格納するメモリと、該モバイル・デバイスのユーザによるエンティティの選択に応答して、前記選択されたエンティティに関連付けられた前記存在インジケータの状態に基づいて、ダイヤルする電話番号を選択し、前記選択された番号をダイヤルする装置と、該選択された番号に関連付けられたユーザの優先性に応じて、呼び出しを前記回線交換ネットワーク又は前記パケット交換ネットワークにルーティングする装置と、を含む電話システム。
- 2前記基地局が、所定の選択アルゴリズムに基づいて、前記第1接続又は前記第2接続のいずれかを選択して、前記モバイル・デバイスからの呼び出しをルーティングする装置をさらに含む、 請求項1 に記載の電話システム。
- 3前記基地局が、時刻に基づいてユーザのルーティング優先性を格納するメモリをさらに含む、請求項 1又は2 のいずれか1項に記載の電話システム。
- 4前記基地局が、前記選択された番号のエリア・コードに基づいて、ユーザのルーティング優先性を格納するメモリをさらに含む、請求項1 乃至3 のいずれか1項に記載の電話システム。
- 5前記選択する装置がスイッチをさらに含み、前記基地局の装置が、さらに、前記スイッチの第1ポートと第2コネクタとの間にパケット・インターフェース及びプロトコル・スタックを含み、該スイッチの第2ポートと第1コネクタとの間に電話インターフェースを含む、請求項 1乃至4のいずれか1項 に記載の電話システム。
- 6プログラムされた命令の制御下にあり、前記スイッチを制御して、前記所定の選択アルゴリズムに基づいて、前記パケット・インターフェース又は前記電話インターフェースのいずれかを選択し、呼び出し対してサービスする中央演算処理装置をさらに含む、請求項 5 に記載の電話システム。
- 7前記パケット・インターフェースが、前記モバイル・デバイスからの信号を前記第2接続に接続された前記プロトコル・スタックと互換性のあるデジタル・パケットに変換するための手段を含む、請求項 5 又は請求項 6 に記載の電話システム。
- 8前記パケット・インターフェースが、前記プロトコル・スタックから受信したパケットを、前記モバイル・デバイスに送信する信号に変換するための手段を含む、請求項 5 又は請求項 6 に記載の電話システム。
- 9前記電話インターフェースが、前記モバイル・デバイスからの信号を前記第1コネクタに送信するアナログ信号に変換するための手段を含む、請求項 5 又は請求項 6 に記載の電話システム。
- 10前記電話インターフェースが、前記第1コネクタからのアナログ信号を前記モバイル・デバイスに送信する信号に変換するための手段を含む、請求項 5 又は請求項 6 に記載の電話システム。
- 11前記モバイル・デバイスが、a)前記エンティティの前記名前を格納するメモリと、b)ユーザが、ダイヤルするエンティティを選択することを可能にするための手段と、c)選択されたエンティティの名前を前記基地局に送信するための手段と、を含む、 請求項1乃至10 のいずれか1項に記載の電話システム。
- 12応答されなかった電話の呼び出しに応答して、付加的な番号が着呼エンティティに格納されたかどうかを判断して、このような付加的な電話番号に対して呼び出しを再試行する装置をさらに含む、 請求項1乃至11 のいずれか1項に記載の電話システム。
- 13前記プロトコル・スタックがTCP/IPスタックである、 請求項1乃至12 のいずれか1項に記載の電話システム。
- 14前記モバイル・デバイスが、該モバイル・デバイスのユーザにより選択された識別を前記基地局に送信する装置を含み、該基地局が、エンティティを呼び出すための識別に関連付けられた1つ又はそれ以上のネットワーク・アドレスを格納し、ネットワーク・アドレスに関連付けられたエンティティ存在インジケータに照会して、前記ユーザが、そのネットワーク・アドレスに位置しているかどうかを判断する装置を含む、請求項 1乃至13 のいずれか1項に記載の電話システム。
- 15前記識別は、前記ユーザの名前 である請求項 14 に記載の 電話 システム。
- 16前記識別は、前記ユーザの会社名 である請求項 14 に記載の 電話 システム。
- 17回線交換電話ネットワークへの第1接続とパケット交換ネットワークへの第2接続とを有する基地局と、無線プロトコルを用いて前記基地局に音声を通信するためのモバイル・デバイスと、を含む電話システムを制御するための方法であって、前記基地局が、前記モバイル・デバイスのユーザにより選択可能な1つ又はそれ以上のエンティティの識別を格納するステップと、各エンティティに関連付けられた1つ又はそれ以上の電話番号を格納するステップと、前記パケット交換ネットワークを介して、格納された電話番号に各々が関連付けられた1つ又はそれ以上の存在インジケータを受信するステップと、前記受信した存在インジケータを格納するステップと、該モバイル・デバイスのユーザによるエンティティの選択に応答して、前記選択されたエンティティに関連付けられた前記存在インジケータの状態に基づいて、ダイヤルする電話番号を選択するステップと、該選択された番号に関連付けられたユーザの優先性に応じて、呼び出しをルーティングするステップと、を含む方法。
- 18前記ルーティングするステップは、選択的に、回線交換ネットワーク上で呼び出しを 行うか 、又は、前記パケット交換ネットワーク上で呼び出しを 行う ステップ である 、請求項 17 に記載の方法。
- 19電話番号を格納する前記ステップが、前記基地局において、エンティティの前記識別、前記エンティティ及び前記存在インジケータに関連付けられた電話番号を格納するステップと、前記モバイル・デバイスにおいて、前記エンティティの名前を格納するステップと、をさらに含む、請求項 17 又は請求項 18 に記載の方法。
- 20前記モバイル・デバイスのユーザがダイヤルするエンティティを選択することを可能にするステップと、前記選択されたエンティティの名前を前記基地局に送信するステップと、をさらに含む、請求項 19 に記載の方法。
- 21時刻に基づいてユーザのルーティング優先性を格納するステップをさらに含む、請求項 17乃至20 のいずれか1項に記載の方法。
- 22前記選択された番号のエリア・コードに基づいて、ユーザのルーティング優先性を格納するステップをさらに含む、請求項 17乃至21の いずれか1項に記載の方法。
- 23応答されなかった電話の呼び出しに応答して、付加的な番号が着呼エンティティに格納されたかどうかを判断するステップと、このような付加的な電話番号に対して呼び出しを再試行するステップと、をさらに含む、請求項 17乃至22 のいずれか1項に記載の方法。
- 24コンピュータ制御式電話にロードされて実行されたとき、前記電話システムが、請求項 17乃至23 のいずれか1項に記載の方法を遂行するように制御するコンピュータ・ソフトウェア・プログラムを格納するコンピュータ格納媒体。
Independent claims24
21 paragraphs, as filed
The present invention is an intelligent base station that connects calls to either a public switched telephone network (PSTN) or a packet network using voice over IP (VoIP) based on a radiotelephone handset and a call unit selection algorithm. Regarding.
Nowadays, it is not uncommon for users to communicate by voice using packet networks instead of standard public exchange telephone networks. Voice over IP (Internet Protocol) typically provides this functionality. Users can choose from a variety of products, including wired VoIP desk sets and wireless systems that use both the proprietary protocol between the handset and the base station and the wireless LAN 802.11 protocol. Of course, the user can also choose from any number of radiotelephones that connect to the PSTN. However, if the user wants to access both types of networks, one for VoIP gateway dialing and another for wireless traditional PSTN dialing, and so on. You have to get it and artificially choose which system to use for any given phone call.
<p> An object of the present invention is to provide a radiotelephone system including voice over IP and POTS.</p>
<p> The present invention addresses these issues in a first aspect by providing a telephone system capable of making or receiving calls over a PSTN or packet network. A preferred embodiment for packet communication is via the TCP / IP protocol. In a second aspect of the invention, the telephone system has a priority that governs the order in which multiple telephone numbers are selected for each of the potential callers to service a given call. It has a function to store with. Some or all of the phone numbers can be associated with existing services. Mobile phone operators have the ability to collect and disperse presence indicators in advance. Other phones associated with the computer can be associated with existing services at this time. All phones will surely have this feature sometime in the future. In the phone number associated with the presence service, the presence indicator stored in the phone system is dynamically updated over the packet network connection and used as part of the phone number selection algorithm.</p><p> In a preferred embodiment, the telephone system is a wireless system that includes a base station and a handheld mobile device such as a radiotelephone handset or personal portable information terminal (PDA) equipped with a microphone and speakers. Users of the telephone system use a browser on their workstation to build the system on a local area network (LAN). The mobile device or base station may also be prepared to carry out the build using either a keypad or voice recognition technology. This construction specifically involves adding names and telephone numbers to a database within the telephone system. This construction also controls the order of telephone numbers dialed to attempt to connect to the called party, and whether the given call is first routed over the packet network or over the PSTN. Includes selecting a priority algorithm to control what is done. The choice of PSTN or VOIP can be based on a number of algorithms. In a preferred embodiment, the user can construct a routing choice by time or area code. Of course, these priority algorithms are exemplary and are not intended to be limiting. The dynamically adjusted presence indicator, of course, plays a major role in phone number selection.</p>
FIG. 1 shows a wireless mobile phone handset 100 that communicates with base station 102 using a well-known wireless protocol. The base station has two ports for communicating with the called party. Port 1 104 is a standard telephone connection that communicates with the Public Switched Telephone Network (PSTN) for POTS (Plain Old Telephone Service) telephone services. The second port 106 is a standard data connection that communicates with a data network such as the Internet for telephone communication using voice over IP (VoIP). In a preferred embodiment, the packet network communication 106 from the base station is connected to the Internet 114 using a router 112 attached to LAN 108. LAN108 also connects computer 110 to base station 102. The basic system is built on LAN108 using a browser such as Microsoft Internet Explorer running on computer 110 attached to base station 102 by LAN108. This technique for building network devices is well known and is typically used to build routers, bridges, and so on. The packet connection 106 is further used to receive an presence indication associated with a potential caller with a designated telephone number, as described below. These presence indications arrive from the Internet 114 and are transferred to the base station 102 via the LAN 108.
FIG. 2 shows an exemplary block diagram of base station 102. It is equipped with an antenna 200 for wireless communication with the handheld device 100. Antenna 200 is connected to transmitter / receiver 202, on which digital data is transmitted between the handheld device 100 and base station 102 using the wireless telephony protocol. The base station is controlled by a CPU (Central Processing Unit) 204. The CPU 204 is controlled by a firmware program and an operating system embedded in the firmware memory 206. The CPU 204 also communicates with other parts of the base station via the data bus 222. The base station can also be equipped with a keypad 208, a microphone and a speaker (not shown) for additional convenience and functionality.
The switch 210 controls whether the base station communicates with the PSTN or with the data network. In the VoIP state, switch 210 connects transmitter / receiver 202 to packet interface 212. The packet interface 212 performs the functions necessary to packetize the data from the handheld device 100 and send it to the TCP / IP stack 214, and for the data coming in from the packet network through the connector 216, The packet interface 212 unpackets the data and sends it to the transmitter / receiver 202.
When the switch 210 is in the POTS state, connect the transmitter / receiver 202 to the POTS interface 218, which is the usual well-known device commercially used in PSTN communication via the POTS connector 220 today. ..
The wireless system may be an analog system or a digital system. The basic technology for any type of system, including transmitter / receiver 202 and POTS interfaces, and for packet interfaces, is commercially available as a chipset. For example, Conexant, Inc., is a leading manufacturer of wireless telephony digital and analog chips, as well as voice-over IP technology.
Name list 224 is kept in the base station's random access memory, and this name list contains the names of people who can be called using the list, along with the information needed to complete the call. In addition, there is an existence table 226 in the random access memory that contains information about whether the person in the name list 224 is present on the specified phone or device at that time. The name list and existence table are described in more detail below. One or more instant message (IM) clients 228 also reside in the base station's memory to maintain the dynamic state of the existence table. The IM client receives the existence information from the Internet via the network connector 216. The IM client is loaded into the base station using the computer 110 and the LAN108 connection to the base station.
FIG. 3 includes a block diagram of the handheld device 100. The antenna 300 communicates with the base station 102 and connects to the transmitter / receiver 302 of the handheld device. Like a base station, the handheld device 100 also includes a CPU 304 controlled by a firmware program and operating system 306. The CPU 304 communicates with other devices in the handheld device via the data bus 322. The keypad 308 allows the caller to enter a telephone number if the mode of operation is desired. The handheld device also includes a name list 324 in its random access memory, but unlike the name list 224 in a base station, this name list 324 is stored in the base station's name list. Contains only names in the same format. Whenever the base station name list 224 is edited, if the user completes the table and saves this table, the name of only part of the table is sent to the handheld device and into that name list. Stored. If the caller activates the handheld device name list 324, its content is displayed on display 326. The caller can search the list using a button on the keypad, or use today's technology voice recognition chips to allow the caller to search the name list by voice. Is easy. The handheld device further includes other devices that connect to the microphone 312 and speaker 314, which are standard in the radio slave station, referred to here as 310.
The operation of the system will be described here. FIG. 4 shows a sample menu of build services displayed to the user on the computer 110 of FIG. This sample menu determines when a link to edit a name list, a link to build a date / time or area code priority, and when the system aborts a number as unresponsive. Includes a link to set the number of rings. As mentioned above, the preferred method for constructing a base station is by using a browser such as Microsoft Internet Explorer, but many other modes are also possible and within the scope of the present invention. is assumed. Microsoft Internet Explorer is a trademark of Microsoft Corporation in the United States, other countries, or both. The operating system included in base station firmware 206 includes a server for communicating with browser software on computer 110. The name list 224 at the base station is edited by displaying its contents in a browser.
FIG. 5 shows an exemplary screen displayed on the computer 110 for name entry, display, and editing. Each entry in the name list includes a name field 500, a number field 502, a preferred field 504, a cell field 506, an instant message (IM) field 508, and an instant messaging ID field 510. In each input field, the name field 500 includes the name of a person in any form in which the user attempts to identify the person. Number field 502 includes a telephone number associated with that person. John Doe has at least four phone numbers that he can connect to, as shown in the first four input fields in the name list in Figure 5. John with the same "JD" in the fifth input item If he points to Doe, he has entered five numbers in this list. Priority field 504 includes a flag indicating priority for a particular number. Cellular field 506 includes a flag that identifies a number belonging to the mobile phone. If the client currently sending the message is associated with a particular phone number, IM field 508 includes the identification of that client. Each such client corresponds to the example of IM client 228 in FIG. Currently, there are a number of possible IM services such as Lotus Sametime , ICQ , Yahoo , AOL , and Microsoft's MSN . (Lotus and Sametime are trademarks of IBM Corporation in the United States, other countries, or both.) Some of these services are free and only require registration through the World Wide Web. In Figure 5, John Doe is AOL Instant. You are registered with three such services: Messaging (AIM), Yahoo (trademark), and Sametime (trademark).
Each service is associated with a different phone number, each of which requires a different IM client to be loaded, as in the IM client 228 example. Each service has a different format for user identification, and this user identification is located in the ID field 510 of FIG. For example, John Doe's ID for AIM is "JOHN DOE". Sametime, on the other hand, uses an Internet email address as the user ID. John Doe's email address is jd@us.ibm.com. A new input item is created by placing the cursor in the desired field in column 512 at the bottom of the screen and entering in the content of that field. This is a data entry technique used by many database programs, such as Microsoft Access. The same input technique is used for the tables shown in FIGS. 6, 7, and 8.
For each input item in the name list (Fig. 5), there is a corresponding input item in the existence table shown in Fig. 6. The name is shown in FIG. 6, mainly for the sake of clarity here, and in fact, in the preferred embodiment, only the number field is needed. The P (existence) field 604 includes a flag that is dynamically set or reset when a person associated with the IM service logs in and off the service. An "Y" indicates that a person has logged in with the number associated with the IM service. An "N" indicates that the person is not logged in, and an empty field means that the phone number is not associated with the IM service. Each existing service, along with a phone number, generates existing or non-existent messages when registered members log on and off the service, and these messages are sent to interested people in real time. Such a message is received by the IM client 228 on the Internet and communicated to the appropriate input item in the presence table identified by the received number. This is a normal service at this time and is somewhat different in operation from different services, but RFCs 2778 and 2779 have been proposed by the Internet Engineering Task Force to establish operating standards. ..
The user can establish a priority for routing the call. It is clear that there are many alternative ways to define user priorities. Here, for exemplary purposes, two alternative priorities are taught: time (TOD) priority and area code (AC) priority. The user selects which service he / she wants from the browser menu in FIG. When the user selects TOD priority, the TOD priority table in FIG. 7 is displayed by the browser. As an example, each input item in this table includes a start time field 700, an end time field 702, a primary field 704, and a secondary field 706. The start and end fields of the input fields define the time interval for which priority call routing is specified by primary field 704. If the call by the preferred route (VoIP or POTS) fails, and if there is a secondary input item, the call will be retried by the secondary route. If there is no input field in the secondary field, this means that the user never wants to use that routing at the defined time interval. If the routing field contains a "DC" (unspecified) input field, the base station makes a call at the associated time interval to make arbitrary choices for primary and secondary routing.
If the user prefers to route the call by area code, the user builds the table shown in Figure 8 using the menu in Figure 4. Each input item in the AC table has an AC field 800 containing the desired area code. The primary field 804 and the secondary field 806 are used in the same manner as described above for TOD priority.
FIG. 9 includes a functional flowchart of an exemplary operation performed on a telephone call. In step 900, the user activates the name list 324 stored in the handheld device 100 and performs the procedure up to the name of the person who wants the call. The user then initiates the call by pressing down on the CALL key or its equivalent. As a result, in step 902, the selected name is transmitted to base station 102. The selected name is received at the base station in step 904 and is used to search for input items in the base station's name list 224. For example, if the selected name is "John Doe", then the preferred name entry is the second John at phone number 919-530-4354, as indicated by Y in the preferred field 504. Found in Doe input fields. This particular number is not associated with a mobile phone, as indicated by the N in Cellular Field 506. However, field 508 indicates that this phone is associated with AOM's IM service, AIM. Therefore, the base station queries the second input field of the presence table in FIG. 6 to determine if John Doe is present at this telephone location. Field 604 in the existence table indicates that John Doe exists at numbers 919-530-4354. Therefore, the base station applies to John Doe for a call with priority number 919-530-4354. If the presence table indicates that John Doe does not exist at the priority number (field 604 is N), then the base station is John in the presence table where the presence indicator 604 is set. Find the input item for Doe. If this fails, the base station finally looks for a null (neither Y nor N) existence input. Such a null state means that there is no existing service associated with the corresponding phone number. Therefore, the base station will dial this number last, but of course, until John Doe is searched, or until there is no list of possible numbers, such phone numbers will be dialed in sequence. There can be more than one. If it is assumed that the Y input field for John Doe in the existence field 604 was actually N, then base station 102 is the first number because John Doe is the only number that may exist. Select the number 919-260-1231 from the input items.
After the number is selected in step 904, step 906 queries the priority table to determine the routing of the call (VoIP or POTS). If the user chooses time (TOD) routing, it queries the TOD table in Figure 7. For example, assuming 10 am AM, the TOD table shows that VoIP is the primary routing choice. The base station controls switch 210 to select a VoIP route to TCP / IP, and then in step 910 the call is made in the normal VoIP format. If this call fails for any reason, or if the call is not answered after the specified number of rings (see 912 in Figures 4 and 9), or the caller is keypad 208. If the disconnect is initiated from, the base station proceeds to step 914 and examines the secondary routing field 706 in FIG. 7 for secondary routing (POTS in this example). If secondary routing is specified, the base station retries the call at 914 with secondary priority. If the user does not specify a secondary routing priority in field 706 of the secondary TOD input field (5PM to 11PM), the base station will not retry the call to this particular number. At 916, the base station returns to step 904 and searches for another phone number to try. Eventually, the call will either succeed (not shown in Figure 9), or all possibilities will disappear. A preferred embodiment in the latter case is to display a suitable unanswered message on display 326 if the call ultimately fails, as shown in 920 of FIG.
Those skilled in the art of the present invention will appreciate that there are numerous modifications within the spirit and scope of the preferred embodiments. It is the inventor's intent to include these modifications to the extent possible by state of the art and law.
<figref num="1">A block diagram of a wireless system including a handset or handheld device with a display and an intelligent base station for carrying out the present invention is shown.</figref><figref num="2">An exemplary block diagram of an intelligent base station is shown.</figref><figref num="3">An exemplary block diagram of a wireless system handset or handheld device is shown.</figref><figref num="4">Shown is a screen image of a build menu displayed on a networked computer in a preferred embodiment of the system and secondarily on the display of a handset or handheld device.</figref><figref num="5">Shows the computer display of the called party's name list stored in the base station.</figref><figref num="6">Shows a computer display image of the presence table stored in the base station and associated with a potential caller.</figref><figref num="7">Shows a computer display image of a time routing priority table stored within a base station and used to select routing for calls over VoIP or POTS telephone lines.</figref><figref num="8">Shows an alternative routing priority table based on area code rather than time of day .</figref><figref num="9">Shows the steps in the functional flow chart performed in the process of making a phone call from a portable handset or handheld device.</figref>
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| US6295457B1 | Cites | United States of America |
| US20020075306A1 | Cites | United States of America |
| US6205135B1 | Cites | United States of America |
| US6351464B1 | Cites | United States of America |
29 members in 12 offices
Priority claims14
| Document | Office | Kind | Date |
|---|---|---|---|
| 10669314 | United States of America | – | |
| 10669578 | United States of America | – | |
| 66931403 | United States of America | A | |
| 66931403 | United States of America | A | |
| 66957803 | United States of America | A | |
| 66957803 | United States of America | A | |
| 2004052161 | European Patent Office (EPO) | W | |
| 2004052161 | European Patent Office (EPO) | W | |
| 2003669314 | – | – | – |
| 2003669578 | – | – | – |
| 2004052161 | – | – | – |
| US20030669314 | – | – | – |
| US20030669578 | – | – | – |
| WO2004EP52161 | – | – | – |
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 | |
| JP4608493B2This record | Japan | B2 | |
| USRE42271E | United States of America | E | |
| CA2535300C | Canada | C | |
| CA2693755C | Canada | C |
30 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Notification of acceptance of power of attorneyJAPANESE INTERMEDIATE CODE: R3D02RD02 | RD02 | |
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Written notification of registration of transferJAPANESE INTERMEDIATE CODE: R350R350 | R350 | |
| Written request for registration of change of nameJAPANESE INTERMEDIATE CODE: R313533S533 | S533 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Notification of acceptance of power of attorneyJAPANESE INTERMEDIATE CODE: R3D02RD02 | RD02 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Written notification of registration of transferJAPANESE INTERMEDIATE CODE: R350R350 | R350 | |
| Request for registration of non-exclusive licenceJAPANESE INTERMEDIATE CODE: R315201S202 | S202 | |
| Request for registration of non-exclusive licenceJAPANESE INTERMEDIATE CODE: R315201S202 | S202 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Written notification of registration of transferJAPANESE INTERMEDIATE CODE: R350R350 | R350 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Request for change of ownership or part of ownershipJAPANESE INTERMEDIATE CODE: R313113S111 | S111 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 4608493
- Publication, DOCDB
- 4608493
- Publication, EPODOC
- JP4608493B
- Application
- 2006527401
- Application, DOCDB
- 2006527401
- Application, EPODOC
- JP20060527401
Titles2
- Japanese
- ボイス・オーバーIP及びPOTSを含む無線電話システム
- English
- Radiotelephone system including voice over IP and POTS
Classification
- CPC, 15
- H04W4/16
- H04W92/02
- H04M1/2535
- H04M1/271
- H04M1/2745
- H04M1/72502
- H04W8/18
- H04W84/16
- H04W92/14
- H04M1/27485
- H04M1/27453
- H04M1/72436
- H04M1/72451
- H04B7/00
- H04M1/725
- IPC, 13
- H04M11 00
- H04M3 42
- H04M1 253
- H04M1 2745
- H04M1 27453
- H04M1 27485
- H04M1 72436
- H04M1 72451
- H04M1 72502
- H04W4 16
- H04W8 18
- H04W84 16
- H04W92 14