A wireless communications device is disclosed. The wireless communications device is configured to support a call over a cellular network or an IP network to a remote communications device. The wireless communications device is further configured to handoff the call between the cellular network and the IP network. An Interworking Function (IWF) is configured to maintain a call between a wireless communications device and a communications device as the wireless communications device is handed off between a cellular network and an IP network.
|
34. A network entity, comprising:
a processor configured to maintain a call between a wireless communications device and a communications device as the wireless communications device is handed off between a first network that uses a first access technology and a second network that uses a second access technology, wherein the processor is further configured to provide a three-way conference call functionality, the processor further being configured to support the handoff of the wireless device by sending a caller identification message that directs the wireless communications device to answer a page while currently engaged in the existing call and conferencing into the existing call over one of the networks while the wireless communications device is connected through the other network.
40. A processor for a network entity configured to:
support handing off a wireless device between a first network that uses a first access technology and a second network that uses a second access technology;
maintain a call between a wireless communications device and a communications device as the wireless communications device is handed off between the first network and the second network; and
provide three way conference call functionality, wherein the processor is further configured to support the handoff of the wireless device by sending a caller identification message that directs the wireless communications device to answer a page while currently engaged in the existing call and conferencing into the existing call over one of the networks while the wireless communications device is connected through the other network.
43. A method of supporting communications from a network entity, comprising:
supporting handing off a wireless device between a first network that uses a first access technology and a second network that uses a second access technology;
maintaining a call between a wireless communications device and a communications device as the wireless communications device is handed off between the first network and the second network; and
providing three way conference call functionality, wherein the supporting the handoff of the wireless device further comprises sending a caller identification message that directs the wireless communications device to answer a page while currently engaged in the existing call and conferencing into the existing call over one of the networks while the wireless communications device is connected through the other network.
46. A non-transitory computer-readable storage media containing a set of instructions which, when executed by a processor at a network entity, cause the network entity to:
support handing off a wireless device between a first network that uses a first access technology and a second network that uses a second access technology;
maintain a call between a wireless communications device and a communications device as the wireless communications device is handed off between the first network and the second network; and
provide three way conference call functionality, wherein the supporting the handoff of the wireless device further comprises sending a caller identification message that directs the wireless communications device to answer a page while currently engaged in the existing call and conferencing into the existing call over one of the networks while the wireless communications device is connected through the other network.
49. A method of communicating from a wireless communications device, comprising:
supporting a call over a first network that uses a first access technology or a second network that uses a second access technology to a remote communications device; and
responsive to a request to handoff from the first network to the second network, handing off the call by establishing a connection to the second network to support the call with the remote communications device, answering a page in response to a caller identification message from a network entity that directs the wireless communications device to answer the page while currently engaged in the call over the first network, conferencing the wireless communications device into the call over the second network, and terminating a connection to the first network that was previously supporting the call with the remote communications device;
wherein the handoff of the call from the first network to the second network is transparent to a user on the call.
37. A network entity, comprising:
means for supporting handing off a wireless device between a first network that uses a first access technology and a second network that uses a second access technology; and
means for maintaining a call between a wireless communications device and a communications device as the wireless communications device is handed off between the first network and the second network, wherein the means for maintaining further comprise means for providing three way conference call functionality to maintain the call between the wireless communications device and the communications device as the wireless communications device is handed off between the first network and the second network, the three way conferencing means being configured to support the handoff of the wireless device by sending a caller identification message that directs the wireless communications device to answer a page while currently engaged in the existing call and conferencing into the existing call over one of the networks while the wireless communications device is connected through the other network.
21. A processor, configured to:
support a call involving a wireless communications device over a first network that uses a first access technology or a second network that uses a second access technology with a remote communications device; and
handoff the call from the first network to the second network by establishing a connection to the second network to support the call with the remote communications device, answering a page in response to a caller identification message from a network entity that directs the wireless communications device to answer the page while currently engaged in the call over the first network, conferencing the wireless communications device into the call over the second network, and terminating a connection to the first network that was previously supporting the call with the remote communications device;
wherein the connection to the second network is established in response to signaling from the network entity supporting a connection between the wireless and remote communication devices over the first network, the signaling from the network entity configured by the network entity to request that the processor establish the connection;
wherein the handoff of the call from the first network to the second network is transparent to a user on the call.
14. A wireless communications device, comprising:
means for supporting a call over a first network that uses a first access technology or a second network that uses a second access technology with a remote communications device; and
means for handing off the call from the first network to the second network by establishing a connection to the second network to support the call with the remote communications device, answering a page in response to a caller identification message from a network entity that directs the wireless communications device to answer the page while currently engaged in the call over the first network, conferencing the wireless communications device into the call over the second network, and terminating a connection to the first network that was previously supporting the call with the remote communications device;
wherein the connection to the second network is established in response to signaling from the network entity supporting a connection between the wireless and remote communication devices over the first network, the signaling from the network entity configured by the network entity to request that the processor establish the connection;
wherein the handoff of the call from the first network to the second network is transparent to a user on the call.
8. A method of communicating from a wireless communications device, comprising:
supporting a call over a first network that uses a first access technology or a second network that uses a second access technology with a remote communications device; and
handing off the call from the first network to the second network by establishing a connection to the second network to support the call with the remote communications device, answering a page in response to a caller identification message from a network entity that directs the wireless communications device to answer the page while currently engaged in the call over the first network, conferencing the wireless communications device into the call over the second network, and terminating a connection to the first network that was previously supporting the call with the remote communications device;
wherein the connection to the second network is established in response to signaling from the network entity supporting a connection between the wireless and remote communication devices over the first network, the signaling from the network entity configured by the network entity to request that the wireless communications device establish the connection;
wherein the handoff of the call from the first network to the second network is transparent to a user on the call.
28. A non-transitory computer-readable storage media containing a set of instructions for a processor to:
support a call involving a wireless communications device over a first network that uses a first access technology or a second network that uses a second access technology with a remote communications device; and
handoff the call from the first network to the second network by establishing a connection to the second network to support the call with the remote communications device, answering a page in response to a caller identification message from a network entity that directs the wireless communications device to answer the page while currently engaged in the call over the first network, conferencing the wireless communications device into the call over the second network, and terminating a connection to the first network that was previously supporting the call with the remote communications device;
wherein the connection to the second network is established in response to signaling from the network entity supporting a connection between the wireless and remote communication devices over the first network, the signaling from the network entity configured by the network entity to request that the processor establish the connection;
wherein the handoff of the call from the first network to the second network is transparent to a user on the call.
1. A wireless communications device, comprising:
a processor configured to support a call over a first network that uses a first access technology or a second network that uses a second access technology with a remote communications device, the processor being further configured to handoff the call between the first network and the second network in a way that is transparent to a user of the wireless communications device;
wherein the processor is further configured to handoff the call from the first network to the second network by establishing a connection to the second network to support the call with the remote communications device, answering a page in response to a caller identification message from a network entity that directs the wireless communications device to answer the page while currently engaged in the call over the first network, conferencing the wireless communications device into the call over the second network, and terminating a connection to the first network that was previously supporting the call with the remote communications device; and
wherein the processor is further configured to establish the connection to the second network in response to signaling from the network entity supporting a connection between the wireless communications device and the remote communications device over the first network, the signaling from the network entity configured by the network entity to request that the processor establish the connection.
2. The wireless communications device of
3. The wireless communications device of
4. The wireless communications device of
5. The wireless communications device of
6. The wireless communications device of
7. The wireless communications device of
9. The method of
10. The method of
11. The method of
12. The method of
13. The method of
15. The wireless communications device of
16. The wireless communications device of
17. The wireless communications device of
18. The wireless communications device of
19. The wireless communications device of
20. The wireless communications device of
22. The processor of
23. The processor of
24. The processor of
25. The processor of
26. The processor of
27. The processor of
29. The non-transitory computer readable storage media of
30. The non-transitory computer readable storage media of
31. The non-transitory computer readable storage media of
32. The non-transitory computer readable storage media of
33. The non-transitory computer readable storage media of
35. The network entity of
36. The network entity of
38. The network entity of
39. The network entity of
41. The processor of
42. The processor of
44. The method of
45. The method of
47. The non-transitory computer readable storage media of
48. The non-transitory computer readable storage media of
50. The method of
51. The method of
52. The wireless communications device of
|
This application claims the benefit of the filing date of U.S. provisional application having Ser. No. 60/676,083, filed on Apr. 28, 2005 and entitled “IP to Wireless Handoff,” the contents of which is incorporated herein by reference.
1. Field
The present disclosure relates generally to communications, and more particularly, to wireless handoffs between multiple wireless networks.
2. Background
The demand for mobile access to information has led to the development of an ever increasing number of wireless networks. Associated with each wireless network is a wireless communications standard that allows two wireless devices that support the standard to freely communicate over the network. CDMA2000 1x is just one example of a wireless communications standard that provides wide area telephony and data services. Promulgated by the Third Generation Partnership Project 2 (3GPP2), CDMA2000 1x is a wireless communications standard based on Code Division Multiple Access (CDMA) technology. CDMA is a technology that allows multiple users to share a common communications medium using spread-spectrum processing.
In addition to CDMA2000 1x, many other wireless communication standards exist today. By way of example, CDMA2000 1xEV-DO is a wireless communications standard optimized for data transmission using CDMA technology. Global System for Mobile Communications (GSM) is another wireless communications standard which is commonly employed in Europe. Unlike CDMA2000 1x and CDMA 1xEV-DO, GSM uses narrowband Time Division Multiple Access (TDMA) to support wireless telephony and data services. Enhanced Data for GSM Evolution (EDGE) is a further development of the GSM protocol designed to handle high speed data transmission. Some other wireless communication standards include General Packet Radio Service (GPRS) which supports high speed data services with data rates suitable for e-mail and web browsing applications and Universal Mobile Communications System (UMTS) which can deliver broadband voice and data for audio and video applications.
These wireless communication standards are generally used over cellular networks. The term “cellular network” is intended to cover any wireless network in which the service area is broken up into cellular regions, without regard to the type of service provided. Thus, a cellular network as used herein would includes any cellular topology that provides cellular services, Personal Communications Services (PCS), or any other type of services. Moreover, the cellular network may be based on any suitable wireless communications standard incorporating one or more multiple access technologies, including by way of example, CDMA, Wideband CDMA (WCDMA), Direct Sequence CDMA (DS-CDMA), TDMA, Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or the like.
As the demand for wireless access to information continues to increase, wireless communication devices are evolving to support integrated voice, data, and streaming media while providing seamless network coverage between cellular and Internet-Protocol (IP) networks. These IP networks may be accessed by a wireless device through one or more access points (APs) residing in a wireless Local Area Network (LAN). Typically, multiple wireless LANs will be distributed throughout the cellular network. These LANs may use any suitable wireless data networking protocol, including by way of example, WiFi, WiMax, Bluetooth, HomeRF, Ultra-WideBand (UWB), or the like.
The existence of wireless LANs in cellular networks provides a unique opportunity to increase user capacity by extending cellular communications to the infrastructure of the IP network. Under certain circumstances, cost savings may be realized by routing communications over the IP network. However, the commercial viability of this approach depends largely on the ability to maintain active calls across these networks.
A wireless communications device is disclosed. The wireless communications device is configured to support a call over a cellular network or an IP network to a remote communications device. The wireless communications device is further configured to handoff the call between the cellular network and the IP network. An Interworking Function (IWF) is configured to maintain a call between a wireless communications device and a communications device as the wireless communications device is handed off between a cellular network and an IP network.
It is understood that other embodiments of the present invention will become readily apparent to those skilled in the art from the following detailed description, wherein it is shown and described only various embodiments of the invention by way of illustration. As will be realized, the invention is capable of other and different embodiments and its several details are capable of modification in various other respects, all without departing from the spirit and scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.
Various aspects of a wireless communications system are illustrated by way of example, and not by way of limitation, in the accompanying drawings, wherein:
The detailed description set forth below in connection with the appended drawings is intended as a description of various embodiments of the invention and is not intended to represent the only embodiments in which the invention may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the invention. However, it will be apparent to those skilled in the art that the invention may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the invention.
In the following detailed description, various techniques will be described in connection with a wireless device traveling through a cellular network with one or more wireless LANs dispersed throughout the cellular coverage region. While such techniques may be well suited for these applications, those skilled in the art will readily appreciate that these techniques can be extended to wireless devices capable of accessing various combinations of multiple networks. By way of example, these techniques may be applied to a wireless device capable of switching between a CDMA2000 1x network and a GSM network. Accordingly, any reference to a wireless device capable of communicating with a cellular or IP network is intended only to illustrate various aspects of the present invention, with the understanding that these aspects have a wide range of applications.
The cellular network 102 is also shown with a wireless LAN 114 in the cell 104, but may have any number of wireless LANs located in the cell 104 or anywhere else in the network 102. The wireless LAN 114 may use any suitable wireless data networking protocol, including by way of example, WiFi, WiMax, Bluetooth, HomeRF, Ultra-WideBand (UWB), or the like. The wireless LAN 114 includes an AP 116 that allows the wireless device 100 to connect to an IP network 118. An Interworking Function (IWF) 120 provides the wireless device 100 with wireless access to a Public Switched Telephone Network (PSTN) 112 for Voice over IP (VoIP) and other communications. The IWF 120 may use a Session Initiation Protocol (SIP), or some other suitable protocol, to establish, maintain and terminate calls with wireless devices over the IP network 118.
The wireless device 100 may be any communications device capable of wireless telephony and/or data communications, including by way of example, a wireless telephone, a personal digital assistant (PDA), a laptop computer, a modem, a game console, or the like. The wireless device 100 is capable of maintaining a call with a remote communications device, such as a landline 126, across the cellular and IP networks 102, 118, respectively. In one embodiment, the wireless device 100 has a cellular phone number and an IP phone number, which allows the landline phone 126 (or other remote communications device) to access the wireless device 100 over the cellular network 102 or the IP network 118.
A media gateway 122 is shown in communication with the MSC 110 and the IWF 120. The wireless device's cellular and IP phone numbers are provisioned in the media gateway when the cellular user subscribes to wireless LAN services. In a manner to be described in greater detail later, these phone numbers are used by the media gateway 122 to facilitate the handoff of the wireless device 100 between the cellular network 102 and the IP network 118 during an active call. The media gateway 122 can be a separate entity as shown in
As the wireless device 100 travels into the coverage region of the wireless LAN 114, it detects a beacon signal from the AP 116. Using the beacon signal, the wireless device 100 establishes a wireless link with the AP 116 to gain access to the IP network 118. Once this occurs, the IWF 120 can connect the wireless device 100 through the PSTN 112 to the landline phone 126 to support a call. By way of example, when a user on the landline phone 126 dials the wireless device's IP phone number, the call is routed by the PSTN 112 to the IWF 120. The IWF 120 then signals the wireless device 100 using a page to establish an end-to-end connection between the wireless device 100 and the landline phone 126 to support the call over the IP network 118.
Once a call is established over the IP network 112 between the wireless device 100 and the landline phone 126, the media gateway 122 begins monitoring the quality of service over the IP network 112. Alternatively, another entity in the communications system may perform this function and report the results back to the media gateway 122. In any event, when the quality of service drops below a certain level, the media gateway 122 may determine that the wireless device 100 has traveled outside the coverage region of the wireless LAN 114 and initiate a handoff of the call to the cellular network 102.
The manner in which the quality of service may be monitored by the media gateway 122 may vary depending upon the specific application, the performance parameters, the overall design constraints, and other factors that might be relevant to the design of a communications system. In one embodiment of the media gateway 122, the quality of service for VoIP communications can be determined by monitoring the arrival of voice packets at the IWF 120. Since most vocoders employed in wireless devices generate a continuous flow of packets, the disruption of that continuous flow can provide a fairly good indicator that the wireless device 104 has traveled beyond the coverage region of the wireless LAN 114. In another embodiment of the media gateway 122, the quality of service for VoIP communications may be determined by monitoring the delay, jitter, and/or packet loss over the IP network 118. In this embodiment, the media gateway 122 may initiate a handoff to the cellular network 102, even if the wireless device 100 is within the coverage region of the wireless LAN 118, if the quality of the network connection is poor due to excessive delay, jitter, and/or lost packets.
The handoff of a call between the wireless device 100 and the landline phone 126 from the IP network 118 to the cellular network 102 may be initiated by the media gateway 122 by sending a handoff request to the IWF 120. In response to the handoff request, the IWF 120 may coordinate a soft handoff by providing certain functionality that emulates a three-way conference call. In particular, soft handoff is performed by conferencing in the wireless device 100 over the cellular network 102 into the existing call and then disconnecting the wireless device 100 over the IP network 118 from the call. Once the wireless device 100 is conferenced into the call over the cellular network 102, the IWF 120 suppress traffic over the cellular network 102 until the wireless device 100 is disconnected from the call over the IP network 118.
The IWF 120 coordinates a soft handoff by retrieving the cellular phone number for the wireless device 120 from the media gateway 122 and using it to signal the wireless device 100 over the cellular network 102. When the IWF 120 signals the wireless device 100 by dialing the wireless device's cellular number, which causes the PSTN 112 set up a connection between the IWF 120 and the MSC 110. The MSC 110 then prompts the BSC 106 to send signaling messages to the BTS 108 to page the wireless device 100. A SMS message may also be sent by the IWF 120 to the wireless device 100 to direct the wireless device 100 to answer the page even though it is currently engaged in another call over the IP network 118, and to answer the page in a way that is transparent to the user to ensure a seamless transition between networks. Alternatively, the IWF 120 can use caller ID or some other method to indicate to the wireless device 100 that the page should be answered in a similar way. In any event, the wireless device 100 establishes the appropriate traffic and control channels with the BTS 108 in response to the page, which enables the IWF 120 to conference the wireless device 100 into the call through the cellular network 102. Once this connection is established, the IWF 118 can complete the handoff by terminating the connection with the wireless device 100 over the IP network 118. When the handoff is complete, traffic between the landline phone 126 and the MSC 110 is routed through the IWF 120.
In another embodiment of the IWF 120, a hard handoff of the call to the cellular network 102 may be performed. A hard handoff begins exactly like a soft handoff, with the IWF 120 retrieving the cellular phone number for the wireless device 100 from the media gateway 122 and using it to call the wireless device 100 on the cellular network 102. But, the primary difference is that the IWF 120 terminates the connection between the landline phone 126 and the wireless device 100 over the IP network 118 immediately, thus resulting in a brief disconnect until the landline phone 126 is connected through the cellular network to the wireless device 100. Once connected, all traffic between the landline phone 126 and the wireless device 100 over the cellular network 102 are routed through the IWF 120. Again, the call from the IWF 120 to the wireless device 100 through the cellular network 102 should be transparent to the user to create a seamless transition between networks.
Alternatively, the wireless device 100 may be responsible for coordinating the handoff of the call to the cellular network 102. In this alternative embodiment, the handoff is initiated by the media gateway 122 by signaling a handoff request to the wireless device 100 over the IP network 118. In response, the wireless device 100 establishes traffic and control channels with the BTS 108 and then uses the IWF's phone number to establish a connection with the IWF 120 over the cellular network 102. The phone number for the IWF 120 may be provided to the wireless device 100 when the call over the IP network 118 is set-up. In the case of a soft handoff, the connection between the landline phone 126 and wireless device 100 over the IP network 118 is terminated after the wireless device is conferenced into the call over the cellular network 102. In the case of a hard handoff, the connection between the landline phone 126 and the wireless device 100 over the IP network 118 may be terminated before the connection between the two is made through the cellular network 102.
In the various embodiments of the communications system described thus far, the media gateway 122 initiates the handoff when the quality of service over the IP network 118 drops below a certain level. In an alternative embodiment, the wireless device 100 may initiate the handoff. In this embodiment, the wireless device 100 determines the quality of the wireless link by monitoring one or more parameters, including by way of example, the signal strength, bit error rate, carrier-to-interference ratio, etc. When the wireless device 100 determines that the quality of the wireless link is unacceptable, it signals the IWF 120 by sending a handoff request over the IP network 118. In response, the IWF 120 connects the wireless device 100 through the cellular network 102 to the existing call in any way described above, or in any other suitable way.
An active call between the landline phone 126 and the wireless device 100 can also be handed off from the cellular network 102 to the IP network 118. In this example, a call may be initially placed to the wireless device 100 by dialing the wireless device's cellular number on the landline phone 126. The call is routed by the PSTN 112 to the MSC 110, which prompts the BSC 106 to send signaling messages to the BTS 108 to page the wireless device 100. The wireless device 100 establishes the appropriate traffic and control channels with the BTS 108, and the MSC 110 connects the call between the wireless device 100 and the landline phone 126.
As the wireless device 100 travels into the coverage region of the wireless LAN 114, it detects the beacon signal from the AP 116. Using the beacon signal, the wireless device 100 establishes a wireless link with the AP 116 to gain access to the IP network 118. Once this occurs, the wireless device 100 uses the phone number for the MSC 110 that it received during the set-up of the call over the cellular network 102 to establish a connection with the MSC 110 over the IP network 118.
Alternatively, the wireless device 100 may signal a handoff request to the MSC 110 over the cellular network 102 once a wireless link is established with the AP 116. In response, the MSC 110 retrieves the wireless device's IP phone number provisioned in the media gateway 122 and uses it to call the wireless device 100 over the IP network 118. The IWF 120 then connects the wireless device 100 over the IP network 118 to the MSC 110. Appropriate SMS messaging, caller ID, or other methods may be used to seamless handoff the wireless device to the IP network 118. Depending upon whether a hard or soft handoff is performed, the connection between the landline phone 126 and the wireless device 100 through the cellular network 102 is terminated either before or after the connection between the two is made over the IP network 118.
In one embodiment of the MSC 110, the connection through the cellular network between the wireless device 100 and the MSC 110 is not terminated until the media gateway 122 determines that the quality of service over the IP network 118 is acceptable. In this embodiment, the wireless device 100 remains connected to the MSC 110 through both the cellular network 102 and the IP network 118 while the media gateway 122 determines the quality of service. In VoIP communications, by way of example, the media gateway may monitor disruptions in the continuous flow of packets and/or delay, jitter and lost packets over the IP network 118. When the quality of service reaches an acceptable level, the media gateway 122 signals the MSC 110 to release the connection between the landline phone 126 and the wireless device through the cellular network 102. Once this occurs, traffic between the landline phone 126 and the wireless device 100 over the IP network is routed through the MSC 110.
When a call is routed over the IP network 118, the IWF 200 begins monitoring the quality of service over the IP network 118. When the quality of service drops below a certain level, the IWF 200 may initiate a handoff to the cellular network 102, either because the wireless device has traveled outside the coverage region of the wireless LAN 118 or the quality of service has become unacceptable. In any event, the quality of service may be monitored in any number of ways as described in more detail in connection with
The IWF 200 initiates a handoff of a call from the IP network 118 to the cellular network 102 by prompting the BSC 106 to send signaling messages to the BTS 108 to page the wireless device 100. A SMS message, caller ID, or some other method may be used to direct the wireless device 100 to answer the page even though it is currently engaged in another call over the IP network 118, and to answer the page in a way that is transparent to the user to ensure a seamless transition between networks. In response to the page, the wireless device 100 establishes the appropriate traffic and control channels with the BTS 108, which enables the IWF 200 to connect the wireless device 100 through the cellular network 102 to the current call between the landline phone 126 and the wireless device 100 over the IP network 118. Depending upon whether a hard or soft handoff is performed, the connection between the landline phone 126 and the wireless device 100 through the cellular network 102 is terminated either before or after the connection between the two is made over the IP network 118.
Alternatively, the IWF 200 may initiate the handoff by signaling to the wireless device 100 over the IP network 118. In response to the signaling, the wireless device 100 establishes traffic and control channels with the BTS 108 and then establishes a connection with the IWF 200 over the cellular network 102. In the case of a soft handoff, the connection between the landline phone 126 and wireless device 100 over the IP network 118 is terminated after the connection between the two is made through the cellular network 102. In the case of a hard handoff, the connection between the landline phone 126 and the wireless device 100 over the IP network 118 may be terminated before the connection between the two is made through the cellular network 102.
In an alternative embodiment of the communications system shown in
An active call between the landline phone 126 and the wireless device 100 can also be handed off from the cellular network 102 to the IP network 118. In this example, the wireless device 100 may be connected to the landline phone 126 over the cellular network 102 when the wireless device 100 travels into the coverage region of the wireless LAN 114. The wireless device 100 then establishes a wireless link with the AP 116 to gain access to the IP network 118. The wireless device 100 can then be connected to the landline phone 126 by the IWF 200 over the IP network 118. Depending upon whether a hard or soft handoff is performed, the connection between the landline phone 126 and the wireless device 100 through the cellular network 102 is terminated either before or after the connection between the two is made over the IP network 118.
In one embodiment of the IWF 200, the connection through the cellular network 102 between the wireless device 100 and the landline phone 126 is not terminated until the IWF 200 determines that the quality of service over the IP network 118 is acceptable. In this embodiment, the wireless device 100 remains connected to the landline phone 126 through both the cellular network 102 and the IP network 118 while the IWF 200 determines the quality of service of the IP network. In VoIP communications, by way of example, the IWF 200 monitors disruptions in the continuous flow of packets and/or jitter, delay and lost packets over the IP network 118. When the quality of service reaches an acceptable level, the IWF 200 terminates the connection between the wireless device 100 and the landline phone 126 over the cellular network 102.
The wireless device 100 is also shown with a processor 308 coupled to both transceivers 302, 304, however, a separate processor may be used for each transceiver in alternative embodiments of the wireless device 100. The processor 308 may be implemented with hardware, firmware, software, or any combination thereof. By way of example, the processor 308 may include a microprocessor (not shown). The microprocessor may be used to support software applications that, among other things, (1) control and manage access to the cellular and IP networks, and (2) interface the processor 308 to the keypad 310, display, 312, and other user interfaces (not shown). The processor 308 may also include a digital signal processor (DSP) (not shown) with an embedded software layer that supports various signal processing functions, such as spread-spectrum processing in the case of CDMA applications. The DSP may also perform vocoder functions to support telephony applications. The processor 308 may include computer-readable media implemented with one or more storage devices accessible by the microprocessor, DSP, and various other hardware components of the processor 308. The computer-readable media may also encompass a carrier wave that encodes a data signal. The manner in which the processor 308 is implemented will depend on the particular application and the design constraints imposed on the overall system. Those skilled in the art will readily recognize the interchangeability of hardware, firmware, and software configurations under these circumstances, and how best to implement the described functionality for each particular application.
The various illustrative logical blocks, modules, circuits, elements, and/or components described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic component, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing components, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The methods or algorithms described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
The previous description is provided to enable any person skilled in the art to practice the various embodiments described herein. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments. Thus, the claims are not intended to be limited to the embodiments shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.”
Agrawal, Avneesh, Jalali, Ahmad, Jain, Nikhil, Bergan, Charles A.
Patent | Priority | Assignee | Title |
10028144, | Jan 28 2009 | Headwater Research LLC | Security techniques for device assisted services |
10057141, | Jan 28 2009 | Headwater Research LLC | Proxy system and method for adaptive ambient services |
10057775, | Jan 28 2009 | Headwater Research LLC | Virtualized policy and charging system |
10064033, | Jan 28 2009 | Headwater Research LLC | Device group partitions and settlement platform |
10064055, | Jan 28 2009 | Headwater Research LLC | Security, fraud detection, and fraud mitigation in device-assisted services systems |
10070305, | Jan 28 2009 | Headwater Research LLC | Device assisted services install |
10080250, | Jan 28 2009 | Headwater Research LLC | Enterprise access control and accounting allocation for access networks |
10165447, | Jan 28 2009 | Headwater Research LLC | Network service plan design |
10171681, | Jan 28 2009 | Headwater Research LLC | Service design center for device assisted services |
10171988, | Jan 28 2009 | Headwater Research LLC | Adapting network policies based on device service processor configuration |
10171990, | Jan 28 2009 | Headwater Research LLC | Service selection set publishing to device agent with on-device service selection |
10171995, | Mar 14 2013 | Headwater Research LLC | Automated credential porting for mobile devices |
10200541, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with divided user space/kernel space traffic policy system |
10237146, | Jan 28 2009 | Headwater Research LLC | Adaptive ambient services |
10237757, | Jan 28 2009 | Headwater Research LLC | System and method for wireless network offloading |
10237773, | Jan 28 2009 | Headwater Research LLC | Device-assisted services for protecting network capacity |
10248996, | Jan 28 2009 | Headwater Research LLC | Method for operating a wireless end-user device mobile payment agent |
10264138, | Jan 28 2009 | Headwater Research LLC | Mobile device and service management |
10320990, | Jan 28 2009 | Headwater Research LLC | Device assisted CDR creation, aggregation, mediation and billing |
10321320, | Jan 28 2009 | Headwater Research LLC | Wireless network buffered message system |
10326675, | Jan 28 2009 | Headwater Research LLC | Flow tagging for service policy implementation |
10326800, | Jan 28 2009 | Headwater Research LLC | Wireless network service interfaces |
10462627, | Jan 28 2009 | Headwater Research LLC | Service plan design, user interfaces, application programming interfaces, and device management |
10492102, | Jan 28 2009 | Headwater Research LLC | Intermediate networking devices |
10506666, | May 01 2018 | INTERMETRO COMMUNICATIONS, INC | Multiple active network wireless device |
10536983, | Jan 28 2009 | Headwater Research LLC | Enterprise access control and accounting allocation for access networks |
10582375, | Jan 28 2009 | Headwater Research LLC | Device assisted services install |
10681179, | Jan 28 2009 | Headwater Research LLC | Enhanced curfew and protection associated with a device group |
10694385, | Jan 28 2009 | Headwater Research LLC | Security techniques for device assisted services |
10715342, | Jan 28 2009 | Headwater Research LLC | Managing service user discovery and service launch object placement on a device |
10716006, | Jan 28 2009 | Headwater Research LLC | End user device that secures an association of application to service policy with an application certificate check |
10749700, | Jan 28 2009 | Headwater Research LLC | Device-assisted services for protecting network capacity |
10771980, | Jan 28 2009 | Headwater Research LLC | Communications device with secure data path processing agents |
10779177, | Jan 28 2009 | Headwater Research LLC | Device group partitions and settlement platform |
10783581, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device providing ambient or sponsored services |
10791471, | Jan 28 2009 | Headwater Research LLC | System and method for wireless network offloading |
10798252, | Jan 28 2009 | Headwater Research LLC | System and method for providing user notifications |
10798254, | Jan 28 2009 | Headwater Research LLC | Service design center for device assisted services |
10798558, | Jan 28 2009 | Headwater Research LLC | Adapting network policies based on device service processor configuration |
10803518, | Mar 15 2013 | Headwater Research LLC | Virtualized policy and charging system |
10834577, | Jan 28 2009 | Headwater Research LLC | Service offer set publishing to device agent with on-device service selection |
10834583, | Mar 14 2013 | Headwater Research LLC | Automated credential porting for mobile devices |
10841839, | Jan 28 2009 | Headwater Research LLC | Security, fraud detection, and fraud mitigation in device-assisted services systems |
10848330, | Jan 28 2009 | Headwater Research LLC | Device-assisted services for protecting network capacity |
10855559, | Jan 28 2009 | Headwater Research LLC | Adaptive ambient services |
10869199, | Jan 28 2009 | Headwater Research LLC | Network service plan design |
10985977, | Jan 28 2009 | Headwater Research LLC | Quality of service for device assisted services |
11013064, | May 01 2018 | InterMetro Communications, Inc. | Multiple active network wireless device |
11039020, | Jan 28 2009 | Headwater Research LLC | Mobile device and service management |
11096055, | Jan 28 2009 | Headwater Research LLC | Automated device provisioning and activation |
11134102, | Jan 28 2009 | Headwater Research LLC | Verifiable device assisted service usage monitoring with reporting, synchronization, and notification |
11190427, | Jan 28 2009 | Headwater Research LLC | Flow tagging for service policy implementation |
11190545, | Jan 28 2009 | Headwater Research LLC | Wireless network service interfaces |
11190645, | Jan 28 2009 | Headwater Research LLC | Device assisted CDR creation, aggregation, mediation and billing |
11218854, | Jan 28 2009 | Headwater Research LLC | Service plan design, user interfaces, application programming interfaces, and device management |
11219074, | Jan 28 2009 | Headwater Research LLC | Enterprise access control and accounting allocation for access networks |
11228617, | Jan 28 2009 | Headwater Research LLC | Automated device provisioning and activation |
11337059, | Jan 28 2009 | Headwater Research LLC | Device assisted services install |
11363496, | Jan 28 2009 | Headwater Research LLC | Intermediate networking devices |
11405224, | Jan 28 2009 | Headwater Research LLC | Device-assisted services for protecting network capacity |
11405429, | Jan 28 2009 | Headwater Research LLC | Security techniques for device assisted services |
11412366, | Mar 02 2009 | Headwater Research LLC | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
11425580, | Jan 28 2009 | Headwater Research LLC | System and method for wireless network offloading |
11477246, | Jan 28 2009 | Headwater Research LLC | Network service plan design |
11494837, | Mar 15 2013 | Headwater Research LLC | Virtualized policy and charging system |
11516301, | Jan 28 2009 | Headwater Research LLC | Enhanced curfew and protection associated with a device group |
11533642, | Jan 28 2009 | Headwater Research LLC | Device group partitions and settlement platform |
11538106, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device providing ambient or sponsored services |
11563592, | Jan 28 2009 | Headwater Research LLC | Managing service user discovery and service launch object placement on a device |
11570309, | Jan 28 2009 | Headwater Research LLC | Service design center for device assisted services |
11582593, | Jan 28 2009 | HEAD WATER RESEARCH LLC | Adapting network policies based on device service processor configuration |
11589216, | Jan 28 2009 | Headwater Research LLC | Service selection set publishing to device agent with on-device service selection |
11665186, | Jan 28 2009 | Headwater Research LLC | Communications device with secure data path processing agents |
11665592, | Jan 28 2009 | Headwater Research LLC | Security, fraud detection, and fraud mitigation in device-assisted services systems |
11743717, | Mar 14 2013 | Headwater Research LLC | Automated credential porting for mobile devices |
11750477, | Jan 28 2009 | Headwater Research LLC | Adaptive ambient services |
11757943, | Jan 28 2009 | Headwater Research LLC | Automated device provisioning and activation |
11812515, | May 01 2018 | INTERMETRO COMMUNICATIONS, INC | Multiple active network wireless device using a shadow number |
11923995, | Jan 28 2009 | Headwater Research LLC | Device-assisted services for protecting network capacity |
11966464, | Jan 28 2009 | Headwater Research LLC | Security techniques for device assisted services |
11968234, | Jan 28 2009 | Headwater Research LLC | Wireless network service interfaces |
11973804, | Jan 28 2009 | Headwater Research LLC | Network service plan design |
11985155, | Jan 28 2009 | Headwater Research LLC | Communications device with secure data path processing agents |
8948025, | Jan 28 2009 | Headwater Research LLC | Remotely configurable device agent for packet routing |
9014026, | Jan 28 2009 | Headwater Research LLC | Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy |
9026079, | Jan 28 2009 | Headwater Research LLC | Wireless network service interfaces |
9037127, | Jan 28 2009 | Headwater Research LLC | Device agent for remote user configuration of wireless network access |
9059913, | Jan 28 2009 | Headwater Partners I, LLC | Techniques for attribution of device data traffic to initiating end-user application |
9094311, | Jan 28 2009 | Headwater Research LLC | Techniques for attribution of mobile device data traffic to initiating end-user application |
9137701, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with differentiated network access for background and foreground device applications |
9137739, | Jan 28 2009 | Headwater Research LLC | Network based service policy implementation with network neutrality and user privacy |
9143976, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with differentiated network access and access status for background and foreground device applications |
9154428, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with differentiated network access selectively applied to different applications |
9154826, | Apr 06 2011 | HEADWATER PARTNERS II, LLC | Distributing content and service launch objects to mobile devices |
9173104, | Jan 28 2009 | Headwater Research LLC | Mobile device with device agents to detect a disallowed access to a requested mobile data service and guide a multi-carrier selection and activation sequence |
9179308, | Jan 28 2009 | Headwater Research LLC | Network tools for analysis, design, testing, and production of services |
9179315, | Jan 28 2009 | Headwater Research LLC | Mobile device with data service monitoring, categorization, and display for different applications and networks |
9179316, | Jan 28 2009 | Headwater Research LLC | Mobile device with user controls and policy agent to control application access to device location data |
9179359, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with differentiated network access status for different device applications |
9198042, | Jan 28 2009 | Headwater Research LLC | Security techniques for device assisted services |
9198074, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with differential traffic control policy list and applying foreground classification to roaming wireless data service |
9198075, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems |
9198076, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with power-control-state-based wireless network access policy for background applications |
9198117, | Jan 28 2009 | Headwater Research LLC | Network system with common secure wireless message service serving multiple applications on multiple wireless devices |
9204282, | Jan 28 2009 | Headwater Research LLC | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
9204374, | Jan 28 2009 | Headwater Research LLC | Multicarrier over-the-air cellular network activation server |
9215159, | Jan 28 2009 | Headwater Research LLC | Data usage monitoring for media data services used by applications |
9215613, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with differential traffic control policy list having limited user control |
9220027, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with policy-based controls for WWAN network usage and modem state changes requested by specific applications |
9225797, | Jan 28 2009 | Headwater Research LLC | System for providing an adaptive wireless ambient service to a mobile device |
9232403, | Jan 28 2009 | Headwater Research LLC | Mobile device with common secure wireless message service serving multiple applications |
9247450, | Jan 28 2009 | Headwater Research LLC | Quality of service for device assisted services |
9253663, | Jan 28 2009 | Headwater Research LLC | Controlling mobile device communications on a roaming network based on device state |
9258735, | Jan 28 2009 | Headwater Research LLC | Device-assisted services for protecting network capacity |
9270559, | Jan 28 2009 | Headwater Research LLC | Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow |
9271184, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with per-application data limit and traffic control policy list limiting background application traffic |
9277433, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with policy-based aggregation of network activity requested by applications |
9277445, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with differential traffic control policy list and applying foreground classification to wireless data service |
9319913, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with secure network-provided differential traffic control policy list |
9351193, | Jan 28 2009 | Headwater Research LLC | Intermediate networking devices |
9386121, | Jan 28 2009 | Headwater Research LLC | Method for providing an adaptive wireless ambient service to a mobile device |
9386165, | Jan 28 2009 | Headwater Research LLC | System and method for providing user notifications |
9392462, | Jan 28 2009 | Headwater Research LLC | Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy |
9491199, | Jan 28 2009 | Headwater Research LLC | Security, fraud detection, and fraud mitigation in device-assisted services systems |
9491564, | Jan 28 2009 | Headwater Research LLC | Mobile device and method with secure network messaging for authorized components |
9521578, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with application program interface to allow applications to access application-specific aspects of a wireless network access policy |
9532161, | Jan 28 2009 | Headwater Research LLC | Wireless device with application data flow tagging and network stack-implemented network access policy |
9532261, | Jan 28 2009 | Headwater Research LLC | System and method for wireless network offloading |
9544397, | Jan 28 2009 | Headwater Research LLC | Proxy server for providing an adaptive wireless ambient service to a mobile device |
9557889, | Jan 28 2009 | Headwater Research LLC | Service plan design, user interfaces, application programming interfaces, and device management |
9565543, | Jan 28 2009 | Headwater Research LLC | Device group partitions and settlement platform |
9565707, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with wireless data attribution to multiple personas |
9571559, | Jan 28 2009 | Headwater Research LLC | Enhanced curfew and protection associated with a device group |
9572019, | Jan 28 2009 | Headwater Research LLC | Service selection set published to device agent with on-device service selection |
9578182, | Jan 28 2009 | Headwater Research LLC | Mobile device and service management |
9591474, | Mar 02 2009 | Headwater Research LLC | Adapting network policies based on device service processor configuration |
9609459, | Jan 28 2009 | Headwater Research LLC | Network tools for analysis, design, testing, and production of services |
9609510, | Mar 14 2013 | Headwater Research LLC | Automated credential porting for mobile devices |
9609544, | Jan 28 2009 | Headwater Research LLC | Device-assisted services for protecting network capacity |
9615192, | Jan 28 2009 | Headwater Research LLC | Message link server with plural message delivery triggers |
9641957, | Jan 28 2009 | Headwater Research LLC | Automated device provisioning and activation |
9647918, | Jan 28 2009 | Headwater Research LLC | Mobile device and method attributing media services network usage to requesting application |
9674731, | Jan 28 2009 | Headwater Research LLC | Wireless device applying different background data traffic policies to different device applications |
9705771, | Jan 28 2009 | Headwater Research LLC | Attribution of mobile device data traffic to end-user application based on socket flows |
9706061, | Jan 28 2009 | Headwater Research LLC | Service design center for device assisted services |
9749898, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems |
9749899, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with network traffic API to indicate unavailability of roaming wireless connection to background applications |
9755842, | Jan 28 2009 | Headwater Research LLC | Managing service user discovery and service launch object placement on a device |
9769207, | Jan 28 2009 | Headwater Research LLC | Wireless network service interfaces |
9819808, | Jan 28 2009 | Headwater Research LLC | Hierarchical service policies for creating service usage data records for a wireless end-user device |
9858559, | Jan 28 2009 | Headwater Research LLC | Network service plan design |
9866642, | Jan 28 2009 | Headwater Research LLC | Wireless end-user device with wireless modem power state control policy for background applications |
9942796, | Jan 28 2009 | Headwater Research LLC | Quality of service for device assisted services |
9954975, | Jan 28 2009 | Headwater Research LLC | Enhanced curfew and protection associated with a device group |
9955332, | Jan 28 2009 | Headwater Research LLC | Method for child wireless device activation to subscriber account of a master wireless device |
9973930, | Jan 28 2009 | Headwater Research LLC | End user device that secures an association of application to service policy with an application certificate check |
9980146, | Jan 28 2009 | Headwater Research LLC | Communications device with secure data path processing agents |
Patent | Priority | Assignee | Title |
6473413, | Jun 22 1999 | Institute For Information Industry | Method for inter-IP-domain roaming across wireless networks |
6725044, | Aug 15 2002 | Thomson Licensing S.A.; THOMSON LICENSING S A | Technique seamless handoff of a mobile terminal user from a wireless telephony network to a wireless LAN |
6888803, | Dec 22 1998 | BlackBerry Limited | System, method, and computer program product for connectivity of wireless base station to PSTN via an IP data network |
6996079, | May 11 1998 | Nokia Technologies Oy | Handover and interworking in radio system |
7039027, | Dec 28 2000 | Symbol Technologies, LLC | Automatic and seamless vertical roaming between wireless local area network (WLAN) and wireless wide area network (WWAN) while maintaining an active voice or streaming data connection: systems, methods and program products |
7149524, | Feb 03 2000 | Orange | System and method for controlling handover |
7245917, | Sep 08 2003 | Research Foundation of the State University of New York | System and method for IP handoff |
7400886, | Jan 09 2004 | UNIFY GMBH & CO KG; UNIFY PATENTE GMBH & CO KG | Call hand-over in a wireless local area network |
7734909, | Sep 29 2003 | ARLINGTON TECHNOLOGIES, LLC | Using voice over IP or instant messaging to connect to customer products |
20020142761, | |||
20030119490, | |||
20030134638, | |||
20040137902, | |||
20040146021, | |||
20040179666, | |||
20050013421, | |||
20050096024, | |||
20060209882, | |||
20060239277, | |||
EP1182900, | |||
EP1392077, | |||
JP2005080197, | |||
WO72536, | |||
WO2005002267, | |||
WO3090013, | |||
WO2004068768, | |||
WO2004082219, | |||
WO2005006570, | |||
WO9959364, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Apr 28 2006 | Qualcomm Incorporated | (assignment on the face of the patent) | / | |||
Jun 06 2006 | BERGAN, CHARLES A | QUALCOMM INCORPORATED A DELAWARE CORPORATION | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 017837 | /0780 | |
Jun 08 2006 | JALALI, AHMAD | QUALCOMM INCORPORATED A DELAWARE CORPORATION | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 017837 | /0780 | |
Jun 12 2006 | AGRAWAL, AVNEESH | QUALCOMM INCORPORATED A DELAWARE CORPORATION | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 017837 | /0780 | |
Jun 20 2006 | JAIN, NIKHIL | QUALCOMM INCORPORATED A DELAWARE CORPORATION | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 017837 | /0780 |
Date | Maintenance Fee Events |
Jan 17 2018 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Jan 13 2022 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Aug 19 2017 | 4 years fee payment window open |
Feb 19 2018 | 6 months grace period start (w surcharge) |
Aug 19 2018 | patent expiry (for year 4) |
Aug 19 2020 | 2 years to revive unintentionally abandoned end. (for year 4) |
Aug 19 2021 | 8 years fee payment window open |
Feb 19 2022 | 6 months grace period start (w surcharge) |
Aug 19 2022 | patent expiry (for year 8) |
Aug 19 2024 | 2 years to revive unintentionally abandoned end. (for year 8) |
Aug 19 2025 | 12 years fee payment window open |
Feb 19 2026 | 6 months grace period start (w surcharge) |
Aug 19 2026 | patent expiry (for year 12) |
Aug 19 2028 | 2 years to revive unintentionally abandoned end. (for year 12) |