Method of enabling communication with a wireless communication device
Claim Score by NHIP
Abstract
A method of enabling communication with a wireless communication device is described. The method comprises steps of storing a unique identifier of the wireless communication device in a memory of a second wireless communication device; providing the unique identifier of the wireless communication device from the second wireless communication device to a wireless communication network; and communicating with the wireless communication device based upon its dynamic address.

Term
Term ended
Projected expiry passed 25 February 2024, 2.6 years ago.
- Priority and filed
- Published
- Projected expiry
- Today
35 claims: 3 independent, 32 dependent
- 1A method of enabling communication with a wireless communication device, said method comprising the steps of:assigning a dynamic address to said wireless communication device when said wireless communication device registers with a wireless communication network;storing a unique identifier of said wireless communication device in a memory of a second communication device;providing said unique identifier of said wireless communication device from said second communication device to a server;and communicating with said wireless communication device based upon said dynamic address assigned to said wireless communication device.
- 15A method of enabling communication with a wireless communication device, said method comprising the steps of:storing a unique identifier of said wireless communication device coupled to a vehicle in a memory of a second wireless communication device;providing said unique identifier of said wireless communication device coupled to a vehicle from said second wireless communication device to a wireless communication network;and communicating with said wireless communication device coupled to a vehicle based upon a dynamic address associated with said wireless communication device coupled to a vehicle.
- 25Broadest claimClaim Score 77, broad(NHIP)A method of enabling communication with a wireless communication device, said method comprising the steps of:storing a unique identifier of said wireless communication device in a memory of a second wireless communication device coupled to a vehicle;providing said unique identifier of said wireless communication device stored in said second wireless communication device to a wireless communication network;and enabling communication to said wireless communication device based upon a dynamic address associated with said wireless communication device.
Independent claims3
47 paragraphs in 4 sections, as filed
FIELD OF THE INVENTION
[0001] The present invention relates to wireless communication devices, and more particularly to a method for enabling communication with a wireless communication device.
BACKGROUND OF THE INVENTION
[0002] As wireless communication networks continue to evolve, new applications for data and new channels for providing data to individuals continue to be developed. One recent application for data can be found in the area of telematics. Telematics is a term generally related to the provisioning of data and/or services to vehicles. As the needs of users of vehicles and the capabilities of telematics systems continue to evolve, the uses for sending packet data have also increased.
[0003] Further, wireless devices are being developed to receive data via a packet switched network using static or dynamic IP addressing. For example, new telematics systems and other wireless communication devices, such as cellular telephones and personal digital assistants having wireless capability, are being designed with packet data capabilities. Further, the majority of network operators are beginning to deploy dynamic IP addressing schemes for these devices.
[0004] However, unlike conventional circuit switch networks which can easily locate a wireless communication device, a wireless communication device which is assigned a dynamic address, such as a dynamic internet protocol (IP) address, may not be located except by the network that assigned the dynamic IP address. If a wireless communication device is assigned a dynamic IP address, it would only be possible to communicate with the wireless communication device if the current dynamic IP address of the wireless communication device is known.
[0005] Accordingly, there is a need for a method for communicating with a wireless communication device having a dynamic IP address.
DESCRIPTION OF THE DRAWINGS
[0006]FIG. 1 is a system level diagram of a wireless communication network for implementing a method of the present invention;
[0007]FIG. 2 is a system level diagram of an alternate embodiment of a wireless communication network for implementing a method of the present invention;
[0008]FIG. 3 is a system level diagram of a further alternate embodiment of a wireless communication network for implementing a method of the present invention;
[0009]FIG. 4 is a block diagram of a central server according to the present invention;
[0010]FIG. 5 is a block diagram of a wireless communication device according to the present invention;
[0011]FIG. 6 is a flow chart showing a method for enabling communication with a wireless communication device from a vehicle according to the present invention;
[0012]FIG. 7 is a flow chart showing a method for enabling communication with a wireless communication device coupled to a vehicle according to the present invention;
[0013]FIG. 8 is a method for enabling communication between a communication device and a wireless communication device coupled to a vehicle according to the present invention;
[0014]FIG. 9 is a flow chart showing a method for enabling communication with a wireless communication device according to an alternate embodiment of the present invention;
[0015]FIG. 10 is a method for storing information for contacting a wireless communication device according to the present invention; and
[0016]FIG. 11 is a flow chart showing a method for enabling communication with a wireless communication device having a mobile tagging feature according to the present invention.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] Turning first to FIG. 1, a system level diagram of a network for enabling communication with a wireless communication device according to the present invention is shown. In particular, a communication network <b>100</b> preferably comprises a communication device <b>102</b> which is adapted to communicate with a communication network <b>104</b> by way of a communication link <b>106</b>. The communication device <b>102</b> could be a wireless communication device, such as a cellular telephone, a pager, or a personal digital assistant (PDA) having wireless capability, or a conventional wire line device, such as a conventional telephone or a computer connected to a wire line network. Similarly, the communication network <b>104</b> could be any type of communication network, such as a circuit switched network. In particular, it could be a land line communication network or a wireless communication network, both of which are well known in the art. A data connection <b>108</b> enables communication between the communication network <b>104</b> and a wireless carrier <b>110</b>. The data connection <b>108</b> could be any type of data connection, such as circuit switched, paging, SMS, packet data, etc.
[0018] A second communication link <b>112</b> enables communication to a second wireless communication device <b>114</b>. The second wireless communication device <b>114</b> is preferably a telemetics communication unit installed in a vehicle. Most current telematics systems include a wireless communication device embedded within the vehicle for accessing the telematics service provider. For example, conventional telematics units include a cellular telephone transceiver to enable communication between the vehicle and a call center associated with telematics service for the vehicle. The vehicle could have a handset coupled to the wireless communication device, and/or include hands free functionality within the vehicle. Alternatively, a portable phone operated by the user could be coupled to a “cradle” which enables communication between the portable device and the wireless communication device of the telematics system. The cradle could enable synchronization between the portable and the wireless communication device of the vehicle. Preferably, the wireless carrier <b>110</b> enables the transmission of packet data to the second wireless communication device <b>114</b>.
[0019] As will be described in more detail with respect to the remaining figures, the methods of the present disclosure enable the location of and transfer of data to a communication device having a temporary or dynamic address, such as a dynamic IP address, for locating the device. Also, while separate communication networks are shown, the data connection <b>108</b> could be between elements of a single communication network. Also, communication device <b>102</b> and wireless communication device <b>114</b> could be any type of communication device having a temporary or changing IP address, with at least one device in the network having a dynamic address. Finally, both one directional and two directional communication for providing packet data information could be employed between two devices. That is, in any case where packet data is transmitted in one direction, it is envisioned that data could also be transmitted in the opposite direction.
[0020] Turning now to FIG. 2, a system level diagram for enabling communication with a wireless communication device according to an alternate embodiment of the present invention is shown. In particular, the communication system <b>200</b> of FIG. 2 further includes a central server <b>202</b>. The central server could be, for example, a telematics service provider having conventional call center capability operated by employees, or voice recognition (VR) systems, as is well known in the art. The central server preferably communicates with the communication network <b>104</b> by way of a data connection <b>204</b>, and with the wireless carrier <b>110</b> by way of a data connection <b>206</b>. The central server <b>202</b> preferably includes a memory for storing address information, a unique identifier, the registration status or other information associated with one or more communication devices, such as a dynamic IP address for a wireless communication device.
[0021] Although separate communication networks (i.e. communication network <b>104</b> and wireless carrier <b>110</b>) are shown, a communication network could be employed with the central server <b>202</b> communicating with various elements of the communication network. Similarly, although only two wireless communication devices are shown, multiple communication devices, whether associated with wired or wireless network, could be employed.
[0022] As will be described in more detail in reference to the remaining figures, only one of the communication devices <b>102</b> or <b>114</b> may be required to communicate directly with the central server <b>202</b>. That is, one of the communication devices <b>102</b> or <b>114</b> may receive the necessary dynamic address for the other communication device by way of either the data connection <b>204</b> or the data connection <b>206</b>, and communicate directly with the other communication device by way of the data connection <b>108</b> using the dynamic address received from the central server <b>202</b>. Finally, although the central server <b>202</b> is shown separate from any communication network, the central server <b>202</b> could be employed in a communication network or by a service provider associated with a communication network.
[0023] Turning now to FIG. 3, a communication system for enabling communication with a wireless communication device according to an alternate embodiment of the present invention is shown. In particular, an Internet Service Provider (ISP) <b>302</b> enables communication with the wireless communication device <b>114</b> by way of a data connection <b>304</b>. A user of a terminal <b>306</b> is coupled to the ISP <b>302</b> by way of a communication link <b>308</b>. The terminal <b>306</b> could be any type of communication device, including wired communication devices or wireless communication devices coupled to the ISP <b>302</b>. For example, the terminal <b>306</b> could be a cellular telephone, pager, PDA or laptop having wireless capability, or a wired device, such as a computer or other device capable of communicating with the ISP <b>302</b>.
[0024] As will be described in more detail in reference to the remaining figures, the Internet service provider <b>302</b> could enable the transfer of information from the terminal <b>306</b> to the wireless communication device <b>114</b> by a packet data connection, or the wireless communication <b>114</b> could communicate with the terminal <b>306</b> by way of the Internet service provider <b>302</b> to receive an address, such as a dynamic IP address, to contact a separate communication device.
[0025] Turning now to FIG. 4, a block diagram of a central server <b>400</b>, such as the central server <b>202</b>, is shown. In particular, a network interface <b>402</b> enables communication with a communication network, such as communication network <b>104</b>, wireless carrier <b>110</b>, or Internet service provider <b>302</b>. The network interface <b>402</b> is coupled to a server <b>404</b>. A user data base <b>406</b> is also coupled to the server <b>404</b> and stores information related to users. For example, the user data base could comprise a memory for storing one or more temporary addresses, authentication information, a unique identifier, a registration status, or other information associated with one or more devices of a user.
[0026] Turning now to FIG. 5, a block diagram of a telematics communication system according to the present invention is shown. The telematics unit <b>502</b> preferably comprises a controller <b>504</b> having various input/output (I/O) ports for communicating with various components of the vehicle. For example, the controller <b>504</b> is coupled to a vehicle bus <b>506</b>, a power supply <b>510</b>, a man machine interface (MMI) <b>512</b>, and a crash sensor input <b>514</b>. The connection to the vehicle bus enables operations such as unlocking the door, sounding the horn, flashing the lights, etc. The controller <b>504</b> is also preferably coupled to various memory elements, such as a random access memory (RAM) <b>518</b> or a flash memory <b>520</b>. The telematics system <b>504</b> also preferably includes a global positioning system (GPS) unit <b>522</b> which provides the location of the vehicle, as is well known in the art. The controller <b>504</b> is also preferably coupled to an audio I/O <b>524</b> which preferably includes a hands free system for audio communication for a user of the vehicle by way of a wireless communication network, such as a cellular telephone network.
[0027] Finally, the telematics unit <b>502</b> could include a wireless local area network node <b>526</b> which is also coupled to the controller and enables communication between a WLAN enabled device such as a cellular telephone and the controller <b>504</b> by way of a WLAN communication means. Using a portable cellular telephone as the wireless communication device for the telematics unit eliminates the need for a separate cellular transceiver in the vehicle, thereby reducing cost of the telematics unit. A WLAN device could communicate with the WLAN enabled controller <b>504</b> by any WLAN protocol, such as Bluetooth, IEEE 802.11, IrdA, or any other WLAN application. However, the portable cellular telephone could communicate with the controller by any means known in the art.
[0028] Turning now to FIGS. <b>6</b>-<b>11</b>, methods are shown for enabling communication with a wireless communication device on the communication system shown in FIGS. <b>1</b>-<b>3</b> and/or using the devices in FIGS. <b>4</b>-<b>5</b>, or using other communication equipment. Referring first to FIG. 6, a flow chart shows a method for enabling communication with a wireless communication device from a vehicle. In particular, a unique identifier and/or authentication code of a wireless communication device is stored in a memory of a vehicle at a step <b>602</b>. The unique identifier of the mobile wireless communication device could be, for example, an electronic serial number (ESN) or an International Mobile Subscriber Identity (IMSI). Storing the unique identifier or other information prevents a driver from having to enter the information from the vehicle each time the wireless communication device is contacted.
[0029] The wireless communication device of the vehicle registers with a communication network, at which time it is assigned a dynamic IP address at a step <b>603</b>. The wireless device of the vehicle also registers with a central server at a step <b>604</b>. The central server could be reached by a static IP address or by a domain name system (DNS) service which is well known in the art. Accordingly, the vehicle can locate and register with a central server by its known IP address or domain name stored in the vehicle, when manufactured for example. The central server preferably authenticates the vehicle for access, or optionally includes a communication link which is encrypted. The dynamic IP address of the wireless communication device of the vehicle, and a unique identifier and/or authentication code of the wireless communication device to be called are provided to the central server at a step <b>606</b>. It is then possible for the wireless communication device of the vehicle to communicate with the wireless communication device to be called using a data communication link based upon the IP for the wireless communication device to be called stored in the central server at a step <b>608</b>. The central server preferably includes a look-up table having a dynamic address stored with unique identifier information and authentication codes for wireless communication devices. Further, whenever a device registers with a server, the server can use the stored IP address of the originating device communicating with it to send an acknowledgment or error code to the originating device.
[0030] The wireless communication device and/or the wireless communication device of the vehicle can then de-register at a step <b>610</b>. De-registration enables a communication system to provide faster feedback to a calling device. That is, if the called device is not on or within range of its communication system, the calling device can be informed immediately, rather than waiting for a predetermined time before the called device has failed to answer. In addition, the server can periodically poll the device to determine if the device is currently registered, such as the periodic location update function which is well known in GSM systems. The wireless communication device of the vehicle could communicate directly with called wireless communication device, as shown for example in the embodiment of FIG. 1, or could communicate through the central server as shown for example in the embodiment of FIG. 2. Although a central server is described, a server could be located within a given communication network or external to a communication network.
[0031] One practical application of the method of FIG. 6 could include a vehicle providing an alert to the wireless communication device that a vehicle's alarm has been activated. The wireless communication device of the vehicle could contact a server via a packet data connection. The vehicle could then transfer the ESN and the authentication code of the wireless communication device which it desires to call to the server. The wireless communication device of the vehicle could also transfer a message type and optional control/data for the called wireless communication device.
[0032] Upon successful authentication to the server, the server looks in its table for a ESN of the called wireless communication device and the corresponding current IP address associated with the ESN. If the ESN is located, the central server will contact the called wireless communication device based upon the stored current IP address and authenticate access to the mobile. If the authentication fails, an error code is preferably returned to the vehicle using the dynamic IP of the wireless communication device of the vehicle.
[0033] Upon successful authentication to the called wireless communication device, the central server will then transfer control/data information to the called wireless communication device. The called wireless communication device will then process the message and perform the indicated operation. If the authentication is unsuccessful, an error code will be sent back to the wireless communication device of the vehicle. Optionally, the called wireless communication device can send back to the server a status message or acknowledgment, such as a message indicating that the control/data information was successfully received by the called wireless communication device.
[0034] Alternatively, the vehicle could contact the mobile directly, rather than through a central server. The wireless communication device of the vehicle preferably contacts a central server via a packet data connection, and transfers the ESN of the wireless communication device that it is trying to contact, and any authentication code, message type or optional control/data. If the authentication fails, an error code is preferably returned to the vehicle. However, upon successful authentication to the central server, the central server looks in its table for a corresponding ESN and the IP address or addresses associated with that ESN. When a match is found, the central server provides the IP address to the wireless communication device of the vehicle. The wireless communication device of the vehicle then contacts the wireless communication device directly via the IP address provided by the server.
[0035] In particular, the wireless communication device of the vehicle then contacts the wireless communication device and attempts to authenticate using the authentication code for the wireless communication device stored in a memory of the vehicle, such as in a non-volatile memory associated with the wireless communication device of the vehicle. Upon successful authentication, the wireless communication device of the vehicle then transfers the control/data information and optionally its dynamic IP address to the called wireless communication device. The called wireless communication device then processes the message and performs the indicated operation, as necessary. If the authentication is unsuccessful, however, an error code will be sent back to the vehicle. The wireless communication device could also transfer a status message or acknowledgment based upon the dynamic IP address of the wireless communication device of the vehicle.
[0036] Turning now to FIG. 7, a flow chart shows a method for enabling communication with a wireless communication device in a vehicle. In particular, a unique identifier and/or authentication code of a wireless communication device of a vehicle is stored in a calling communication device at a step <b>702</b>. A wireless communication device registers with a wireless communication network at which time it is assigned a dynamic IP address at a step <b>703</b>. The calling communication device then registers with the central server at a step <b>704</b>. The dynamic IP address of the calling communication device, and authentication and a unique identifier of the wireless communication device of the vehicle are provided by the calling communication device to the central server at a step <b>706</b>. The unique identifier of the wireless communication device of the vehicle could be, for example, the vehicle identification number (VIN) or an ESN of the wireless communication device of the vehicle. It is then possible for the calling communication device to communicate with the wireless communication device of the vehicle based upon the current IP address for the vehicle's wireless communication device stored in the central server at a step <b>708</b>. The calling communication device and/or the wireless communication device of the vehicle can then de-register at a step <b>710</b>.
[0037] Although the method of FIG. 7 finds particular application in contacting a wireless communication device integrated in a vehicle, such as a telemetics unit, the method of FIG. 7 can be employed to contact any wireless communication device having a dynamic identifier, such as a dynamic IP address. Similarly, the wireless communication device could be contacted by any type of device, such as another wireless communication device, or a fixed communication device or other terminal, such as a computer.
[0038] One practical application for the method of FIG. 7 is the control of the vehicle by sending a command from a device to a wireless communication device of the vehicle using a packet data connection. For example, the calling communication device could contact a server via a packet data connection. The device could transfer the VIN, an authentication code, message type and optional control/data for the vehicle it is trying to contact. If the authentication to the server is successful, the server determines whether it has an IP address for the corresponding VIN provided by the calling communication device. If the server has a current IP address, the server will contact the vehicle via the IP address and authenticate access to the vehicle. Upon successful authentication to the vehicle, the central server will transfer the control/data information to the vehicle. The vehicle will then process the message and perform the indicated operation. For example, the message could include a command to start the vehicle, deactivate an alarm, or perform some other function of the vehicle. If the authentication to the mobile is unsuccessful, an error code will be sent back to the wireless communication device via the server. Finally, the vehicle could optionally transfer a status message or acknowledgment if the command was successful.
[0039] Alternatively, the central server could provide the current IP address of the wireless communication device of the vehicle to the calling wireless communication device, enabling the calling wireless communication device to attempt to contact the vehicle directly. For example, the calling wireless communication device could then transfer information via a packet data connection, such as transferring an MP3 file to the vehicle. Such a transfer would reduce the load on the central server in cases where large amounts of data is to be transferred.
[0040] Turning now to FIG. 8, a flow chart shows a method for enabling communication between a wireless communication device and a vehicle having an integrated wireless communication device. If two devices in a communication network attempt to communicate with each other, the central server can enable communication between the two devices using a packet data connection. The devices register with their respective communication networks at a step <b>801</b>, at which time they are provided dynamic IP addresses. Unique identifiers and/or authentication codes for a wireless communication device and an integrated wireless communication device in a vehicle are received at a central server at a step <b>802</b>. The dynamic IP addresses, unique identifiers and authentication codes are stored with current IP addresses for the respective devices at the central server at a step <b>804</b>. A unique identifier and authentication code for one of the devices (the called device) is received at the server at a step <b>806</b>. The central server then enables communication with the called device based upon a stored IP address for that device at a step <b>808</b>. That is, the server provides the current IP address of the device to the calling device, or simply communicates directly with the called device. The called device may optionally respond to the server or the calling device at a step <b>810</b>, thereby enabling bidirectional communication between the two devices. That is, the called device could respond to the server, or could respond directly to the calling device if the dynamic IP address of the calling device is provided to the called device by the server.
[0041] Turning now to FIG. 9, a flow chart shows a method for enabling communication with a wireless communication device according to the present invention. In particular, a vehicle is provide with an wireless communication device at a step <b>902</b>. For example, such a device could be a telematics communications unit which could operate on a cellular system as is well known in the art. Unique identifiers and/or authentication codes and associated IP addresses are stored on the central server at a step <b>904</b>. This information could include identifiers and codes for the wireless communication device of the vehicle, or other wireless communication devices which may be associated with a user of the vehicle.
[0042] It is then determined whether a request to communicate with a wireless communication device is received at the central server at a step <b>906</b>. If a request is received, the IP address or addresses of the called wireless communication device is then determined from the stored information at a step <b>908</b>. It is then determined whether the IP address of the called device should be sent to the calling device at a step <b>910</b>. If not, the central server contacts the called device directly. Alternatively, the calling device accesses the called device by way of the IP address of the called device provided from the central server at a step <b>914</b>.
[0043] It is then determined whether the call is successful. If the connection is not successful, the calling device will try another designated IP address at a step <b>918</b>. If the call is successful, the calling device will transfer control/data information to the device at a step <b>920</b>. Finally, it is then determined whether other devices are to be contacted at a step <b>922</b>. For example, a user of a wireless communication device may have a list of devices which should be contacted for particular messages. If other devices are to be provided with the control/data information, then another designated IP address will be contacted at step <b>918</b>.
[0044] Turning now to FIG. 10, a flow chart shows a method for storing authentication codes and/or unique identifiers and associated IP addresses on a central server as shown at step <b>904</b> of FIG. 9. In particular, IP addresses associated with a device are stored on a central server at a step <b>1002</b>. As set forth above, the user could set preferences to contact various devices. Such preferences could include the order to contact devices, desire to contact certain devices for certain messages, the desire to continue to contact additional devices even if a device is reached, etc. It is then determined whether a user has a preference to contact multiple devices at a step <b>1004</b>. If the user has a preference, the user designates the order of the devices to contact at a step <b>1006</b>. The user may also designate whether the devices should be contacted until one device acknowledges receiving the message, or whether all devices should be contacted. If the user does not have a preference regarding contacting multiple devices, the devices are preferably contacted based upon default or some other criteria at a step <b>1008</b>. For example, the devices could be contacted based upon the most frequently used devices, such as based upon the amount of time it is registered with the network, or some other criteria.
[0045] Turning now to FIG. 11, a method for enabling communication with a wireless communication device having a tagging feature is shown. The tagging feature would generally enable tracking of a user of a wireless communication device. The arrival of various location services and the requirement by government agencies to provide location information will enable convenient features for wireless communication devices, as well as other wireless devices such as telemetics units installed in vehicles.
[0046] In particular, a tagging feature on a wireless communication is set at a step <b>1102</b>. The tagging feature setting is provided to a central server at a step <b>1104</b>. A communication device, such as another mobile wireless communication device, requests the location of a second wireless communication device at a step <b>1106</b>. It is then determined whether the tagging feature of the second wireless communication device is set to provide location information at a step <b>1108</b>. If the tagging feature of the second wireless communication device is set to provide location information, the central server provides the location information related to the second wireless communication device to the first wireless communication device. The information could be sent directly to the requesting device using an IP address of the requesting device at a step <b>1110</b>. Alternatively, location information could be provided from the server to the second wireless communication device. However, if the tagging feature of the second wireless communication device is not set to provide location information, access to the location information is denied at a step <b>1112</b>.
[0047] It can therefore be appreciated that a new and novel method for enabling communication with a wireless communication device has been described. It will be appreciated by those skilled in the art that, given the teaching herein, numerous alternatives and equivalent will be seen to exist which incorporate the disclosed invention. As a result, the invention is not to be limited by the foregoing exemplary embodiments, but only by the following claims.
Contents4
10 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2013054820A1 | Cited by | United States of America | Pre-grant |
| US2010110944A1 | Cited by | United States of America | Pre-grant |
| DE102006011829B4 | Cited by | Germany | Search report |
| US2009259349A1 | Cited by | United States of America | Pre-grant |
| US2011039533A1 | Cited by | United States of America | Pre-grant |
| US9092311B2 | Cited by | United States of America | Applicant |
| US2017286960A1 | Cited by | United States of America | Search report |
| US2017286960A1 | Cited by | United States of America | Search report |
| US8331923B2 | Cited by | United States of America | Search report |
| US2005197174A1 | Cited by | United States of America | Pre-grant |
| US9977426B2 | Cited by | United States of America | Search report |
| US2011014898A1 | Cited by | United States of America | Pre-grant |
| US7568616B2 | Cited by | United States of America | Search report |
| US8677019B2 | Cited by | United States of America | Search report |
| US7623875B2 | Cited by | United States of America | Search report |
| US2017286960A1 | Cited by | United States of America | Search report |
| US2007247288A1 | Cited by | United States of America | Pre-grant |
| US2009012675A1 | Cited by | United States of America | Pre-grant |
| US2006101026A1 | Cited by | United States of America | Pre-grant |
| US10755279B2 | Cited by | United States of America | Search report |
| US2009070488A1 | Cited by | United States of America | Pre-grant |
| US2015156058A1 | Cited by | United States of America | Pre-grant |
| DE102007051157B4 | Cited by | Germany | Search report |
| US2018061155A1 | Cited by | United States of America | Search report |
| US2005256615A1 | Cited by | United States of America | Pre-grant |
| US7917603B2 | Cited by | United States of America | Search report |
| US9886813B2 | Cited by | United States of America | Search report |
| US7548744B2 | Cited by | United States of America | Search report |
| US2005001028A1 | Cited by | United States of America | Pre-grant |
| US2016140788A1 | Cited by | United States of America | Search report |
| US2006233133A1 | Cited by | United States of America | Pre-grant |
| US8330593B2 | Cited by | United States of America | Applicant |
| US7292848B2 | Cited by | United States of America | Search report |
| US8594624B2 | Cited by | United States of America | Applicant |
| US2015312392A1 | Cited by | United States of America | Pre-grant |
| US10332328B2 | Cited by | United States of America | Search report |
| US2008242227A1 | Cited by | United States of America | Pre-grant |
| US2015156058A1 | Cited by | United States of America | Search report |
| US2017286960A1 | Cited by | United States of America | Pre-grant |
| US2004023647A1 | Cited by | United States of America | Pre-grant |
| US2013006479A1 | Cited by | United States of America | Pre-grant |
| WO2007024188A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2016140788A1 | Cited by | United States of America | Pre-grant |
| US2015156058A1 | Cited by | United States of America | Search report |
| US2005136892A1 | Cited by | United States of America | Pre-grant |
| DE102004055293B4 | Cited by | Germany | Search report |
| US10659287B2 | Cited by | United States of America | Search report |
| US8843110B2 | Cited by | United States of America | Applicant |
| US2005273505A1 | Cited by | United States of America | Pre-grant |
| US7672666B2 | Cited by | United States of America | Search report |
| US8103256B2 | Cited by | United States of America | Search report |
| US7831697B2 | Cited by | United States of America | Search report |
| WO2008099484A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| DE102006056693B4 | Cited by | Germany | Search report |
| US2004203691A1 | Cited by | United States of America | Pre-grant |
| DE102006011829A1 | Cited by | Germany | Search report |
| US2006223582A1 | Cited by | United States of America | Pre-grant |
| US2007130469A1 | Cited by | United States of America | Pre-grant |
| US9756669B2 | Cited by | United States of America | Search report |
| US8160547B2 | Cited by | United States of America | Search report |
| US2009275311A1 | Cited by | United States of America | Pre-grant |
| US7006819B2 | Cited by | United States of America | Search report |
| US7266435B2 | Cited by | United States of America | Search report |
| EP1938561A4 | Cited by | European Patent Office (EPO) | Examiner |
| US7805612B2 | Cited by | United States of America | Search report |
| US2008102854A1 | Cited by | United States of America | Pre-grant |
| US2014258457A1 | Cited by | United States of America | Pre-grant |
| US8219710B2 | Cited by | United States of America | Search report |
| US2008254805A1 | Cited by | United States of America | Pre-grant |
| US9883017B2 | Cited by | United States of America | Search report |
| US2001022784A1 | Cites | United States of America | Pre-grant |
| US2002001303A1 | Cites | United States of America | Pre-grant |
| US2003034882A1 | Cites | United States of America | Pre-grant |
| US2003072450A1 | Cites | United States of America | Pre-grant |
| US4821309A | Cites | United States of America | Pre-grant |
| US6115611A | Cites | United States of America | Pre-grant |
| US6230012B1 | Cites | United States of America | Pre-grant |
| US6407988B1 | Cites | United States of America | Pre-grant |
| US6429773B1 | Cites | United States of America | Pre-grant |
| US6578085B1 | Cites | United States of America | Pre-grant |
| US6625135B1 | Cites | United States of America | Pre-grant |
| US6751452B1 | Cites | United States of America | Pre-grant |
| US6751475B1 | Cites | United States of America | Pre-grant |
| US6842762B2 | Cites | United States of America | Pre-grant |
6 members in 6 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 466901 | United States of America | A | |
| US20010004669 | – | – | – |
Members6
| Document | Office | Kind | |
|---|---|---|---|
| US2003103482A1 | United States of America | A1 | |
| WO03049408A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU2002346555A1 | Australia | A1 | |
| CN1524372A | China | A | |
| EP1459497A1 | European Patent Office (EPO) | A1 | |
| JP2005512408A | Japan | A |
46 transactions on the USPTO file
Abandoned after 2 non-final rejections and 2 final rejections.
- Non-final rejections
- 2
- Final rejections
- 2
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | |
|---|---|
| Mail Abandonment for Failure to Respond to Office ActionAbandoned | |
| Aband. for Failure to Respond to O. A. | |
| Case Docketed to Examiner in GAU | |
| Mail Final Rejection (PTOL - 326)Final rejection | |
| Final RejectionFinal rejection | |
| Date Forwarded to Examiner | |
| Response after Non-Final Action | |
| Request for Extension of Time - Granted | |
| Mail Non-Final RejectionNon-final rejection | |
| Non-Final RejectionNon-final rejection | |
| Date Forwarded to Examiner | |
| Response after Final Action | |
| Mail Final Rejection (PTOL - 326)Final rejection | |
| Final RejectionFinal rejection | |
| Case Docketed to Examiner in GAU | |
| Date Forwarded to Examiner | |
| Response after Non-Final Action | |
| Request for Extension of Time - Granted | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Mail Non-Final RejectionNon-final rejection | |
| Mail Miscellaneous Communication to Applicant | |
| Non-Final RejectionNon-final rejection | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Miscellaneous Communication to Applicant - No Action Count | |
| Date Forwarded to Examiner | |
| Withdrawal of Notice of AllowanceAllowed | |
| Workflow - File Sent to Contractor | |
| Mail Notice of AllowanceAllowed | |
| Notice of Allowance Data Verification CompletedAllowed | |
| Case Docketed to Examiner in GAU | |
| IFW TSS Processing by Tech Center Complete | |
| Correspondence Address Change | |
| Reference capture on IDS | |
| Information Disclosure Statement (IDS) Filed | |
| Information Disclosure Statement (IDS) Filed | |
| Case Docketed to Examiner in GAU | |
| Application Dispatched from OIPE | |
| Application Is Now Complete | |
| Additional Application Filing Fees | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the Applic | |
| Notice Mailed--Application Incomplete--Filing Date Assigned | |
| IFW Scan & PACR Auto Security Review | |
| Initial Exam Team nn |
2 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: application discontinuationABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTIONSTCB | STCB | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 2003103482
- Publication, EPODOC
- US2003103482
- Application
- 10004669
- Application, DOCDB
- 466901
- Application, EPODOC
- US20010004669
Titles
- English
- Method of enabling communication with a wireless communication device
Patent term adjustment
- A delay
- +813 daysthe office missed an examination deadline
- Net adjustment
- 813 days
Classification
- CPC, 7
- H04L67/34
- H04W8/26
- H04W80/04
- H04L61/50
- H04L61/00
- H04L67/52
- H04L9/40
- IPC, 6
- H04L12 28
- H04L29 06
- H04L29 08
- H04L29 12
- H04W8 26
- H04W80 04
- USPC, 2
- 370338000
- 370349000