Signaling schemes allowing discovery of network devices capable of operating in multiple network modes

Information

  • Patent Grant
  • 9380401
  • Patent Number
    9,380,401
  • Date Filed
    Wednesday, January 19, 2011
    13 years ago
  • Date Issued
    Tuesday, June 28, 2016
    8 years ago
Abstract
A network device includes a receiving module and a detecting module. The receiving module is configured to receive a beacon transmitted by a remote device operating in one of a plurality of network modes, or a probe response transmitted by the remote device in response to a probe request transmitted by the network device. The beacon or the probe response includes an information element indicating that the remote device is capable of operating in the plurality of network modes. The plurality of network modes includes an ad-hoc mode, an infrastructure mode, a mesh mode, and a WiFi direct peer-to-peer mode. The detecting module is configured to detect the remote device as capable of operating in the plurality of network modes based on the information element.
Description
FIELD

The present disclosure relates generally to wireless networks and more particularly to signaling schemes allowing discovery of network devices capable of operating in multiple network modes.


BACKGROUND

The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.


Referring now to FIGS. 1A-1D, different types of wireless networks are shown. The networks shown in FIGS. 1A-1C comply with one or more 802.11 standards developed by Institute of Electrical and Electronics Engineers (IEEE). The network shown in FIG. 1D complies with a WiFi Direct peer-to-peer (P2P) standard developed by the WiFi Alliance.


In FIG. 1A, an infrastructure network 10 includes an access point (AP) 12 and a plurality of client stations STA-114-1, . . . , and STA-n 14-n (collectively STAs 14). The AP 12 and the STAs 14 form a basic service set (BSS) having a BSS identifier (BSSID). The AP 12 transmits beacons to the STAs 14, where each beacon includes the BSSID. Each STA 14 communicates with the AP 12 using the BSSID. A plurality of interconnected BSSs is called an extended service set (ESS).


In FIG. 1B, an ad-hoc network 20 includes, for example, three client stations STA-122-1, STA-222-2, and STA-322-3 (collectively STAs 22). Although three STAs 22 are shown, the ad-hoc network 20 can include more or less than three STAs 22. The STAs 22 form an independent BSS (IBSS) having a BSSID. Each STA 22 can communicate with any of the other STAs 22 without an AP. Each STA 22 listens for a beacon and can transmit a beacon if none of the other STAs 22 transmits a beacon. The beacon includes the BSSID.


In FIG. 1C, a mesh network 30 includes network devices device-132-1, device-232-2, . . . , and device-n 32-n (collectively devices 32). Each device 32 has a unique ID and can transmit beacons that include the unique ID.


In FIG. 1D, a WiFi direct peer-to-peer (P2P) network 40 includes network devices that communicate without an AP. The network devices use signaling mechanisms of the infrastructure network 10. Each network device is capable of operating as an AP or a STA. When two network devices (e.g., AP/STA 42-1 and 42-2) discover each other, the two network devices negotiate a mode of operation. One network device (e.g., AP/STA 42-1) can operate as a group owner, which is essentially an AP, while the other network device (e.g., AP/STA 42-2) can operate as a STA, or vice versa.


SUMMARY

A network device includes a receiving module and a detecting module. The receiving module is configured to receive a beacon transmitted by a remote device operating in one of a plurality of network modes, or a probe response transmitted by the remote device in response to a probe request transmitted by the network device. The beacon or the probe response includes an information element indicating that the remote device is capable of operating in the plurality of network modes. The plurality of network modes includes an ad-hoc mode, an infrastructure mode, a mesh mode, and a WiFi direct peer-to-peer mode. The detecting module is configured to detect the remote device as capable of operating in the plurality of network modes based on the information element.


A network device includes a receiving module and a response generating module. The receiving module is configured to receive a probe request transmitted by a remote device. The response generating module is configured to generate a probe response. The probe response includes an information element indicating that the network device is capable of operating in a plurality of network modes. The plurality of network modes includes an ad-hoc mode, an infrastructure mode, a mesh mode, and a WiFi direct peer-to-peer mode.


A method for a network device includes receiving (i) a beacon transmitted by a remote device operating in one of a plurality of network modes or (ii) a probe response transmitted by the remote device in response to a probe request transmitted by the network device. The beacon or the probe response includes an information element indicating that the remote device is capable of operating in the plurality of network modes. The plurality of network modes includes an ad-hoc mode, an infrastructure mode, a mesh mode, and a WiFi direct peer-to-peer mode. The method further includes detecting the remote device as capable of operating in the plurality of network modes based on the information element.


A method for a network device includes receiving a probe request transmitted by a remote device, and generating a probe response. The probe response includes an information element indicating that the network device is capable of operating in a plurality of network modes. The plurality of network modes includes an ad-hoc mode, an infrastructure mode, a mesh mode, and a WiFi direct peer-to-peer mode.


Further areas of applicability of the present disclosure will become apparent from the detailed description, the claims and the drawings. The detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the disclosure.





BRIEF DESCRIPTION OF DRAWINGS

The present disclosure will become more fully understood from the detailed description and the accompanying drawings, wherein:



FIGS. 1A-1D depict different types of wireless networks;



FIG. 2A is a functional block diagram of a wireless network device;



FIG. 2B is a functional block diagram of a system for discovering wireless network devices capable of operating in multiple network modes; and



FIGS. 3A and 3B depict flowcharts of methods for discovering wireless network devices capable of operating in multiple network modes.





DESCRIPTION

The following description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. For purposes of clarity, the same reference numbers will be used in the drawings to identify similar elements. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A or B or C), using a non-exclusive logical OR. It should be understood that steps within a method may be executed in different order without altering the principles of the present disclosure.


As used herein, the term module may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC); an electronic circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor (shared, dedicated, or group) that executes code; other suitable components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip. The term module may include memory (shared, dedicated, or group) that stores code executed by the processor.


The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, and/or objects. The term shared, as used above, means that some or all code from multiple modules may be executed using a single (shared) processor. In addition, some or all code from multiple modules may be stored by a single (shared) memory. The term group, as used above, means that some or all code from a single module may be executed using a group of processors. In addition, some or all code from a single module may be stored using a group of memories.


The apparatuses and methods described herein may be implemented by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions that are stored on a non-transitory tangible computer readable medium. The computer programs may also include stored data. Non-limiting examples of the non-transitory tangible computer readable medium are nonvolatile memory, magnetic storage, and optical storage.


A network device can discover another network device on a channel by scanning the channel. Scanning can be passive and/or active. In passive scanning, a network device can discover other network devices when the network device receives beacons or probe requests from the other network devices. In active scanning, the network device transmits probe requests and can discover other network devices based on probe responses received from the other network devices.


Beacons, probe requests, and/or probe responses transmitted by a network device include an information element (IE) that indicates a mode of operation of the network device. The mode of operation of the network device typically depends on the type of network in which the network device communicates and is referred to as a network mode. For example, if the network device communicates in an ad-hoc network, the IE includes a bit indicating that the network device operates in an ad-hoc network mode or simply ad-hoc mode. Similarly, if the network device communicates in an infrastructure network, the IE includes a bit indicating that the network device operates in an infrastructure network mode or simply infrastructure mode.


In passive scanning, a first network device can discover a second network device if the IE received from the second network device indicates that the second network device operates in the same network mode as the first network device. In active scanning, when a first network device receives a probe request transmitted by a second network device, the first network device transmits a probe response if the first network device operates in the same network mode as the second network device. The second network device discovers the first network device based on the probe response received from the first network device.


According to IEEE 802.11 specifications, a network device capable of operating in multiple network modes is forced to indicate only one network mode in a probe response. The indicated network mode typically depends on the type of network in which the network device operates. Accordingly, a network device capable of operating in multiple network modes cannot indicate in a probe response the ability of the network device to operate in multiple network modes. Consequently, the network device cannot be discovered by network devices operating in a network mode other than the network mode indicated by the network device in the probe response.


The present disclosure relates to generating a probe response that allows a network device capable of operating in multiple network modes to be discovered by a scanning network device as a generic network device. A generic network device is a network device capable of operating in more than one network mode. Specifically, the network device can transmit a probe response that includes a new information element (IE). The new IE indicates that the network device can optionally operate in multiple network modes. Accordingly, when the scanning network device receives the probe response, the scanning network device can discover the network device as a generic network device. After discovery, the scanning network device and the discovered network device can select one of the multiple network modes and communicate using the selected network mode.


Thus, a network device can be discovered by other network devices regardless of the mode of operation of the network device and regardless of the modes of operation of the other network devices. Further, the discovered network device can negotiate with the scanning network device and select a suitable network mode of operation after discovery.


Two examples of discovering a network device according to the present disclosure are presented below. In a first example, a first network device operating in a WiFi direct peer-to-peer (P2P) mode transmits a probe request. A second network device is capable of operating in the WiFi direct P2P mode and another network mode (e.g., the ad-hoc mode). The second network device receives the probe request and transmits a probe response. The probe response includes a new IE, which indicates that the second network device can operate in the WiFi direct P2P mode and optionally in the ad-hoc mode, for example. Accordingly, the first network device discovers the second network device as being capable of operating in the WiFi direct P2P mode and optionally in the ad-hoc mode (i.e., as a generic network device). Subsequently, the first network device associates with the second network device using the WiFi direct P2P mode.


Unlike a conventional probe response, the probe response generated by the second network device does not include an independent basic service set (IBSS) bit to indicate that the second network device is capable of operating only in the ad-hoc mode, for example. Instead, the probe response includes the new IE, which indicates that the second network device can optionally operate in the ad-hoc mode in addition to being able to operate in the WiFi direct P2P mode.


Further, if the first network device is also capable of operating in the ad-hoc mode, the first network device and the second network device can negotiate a mode of operation during a setup process that follows the discovery of the second network device. During the setup process, the first network device and the second network device determine whether to operate in the WiFi direct P2P mode or the ad-hoc mode.


Thus, the second network device is not forced to indicate in the probe response that the second network device can operate only in a single network mode (e.g., the ad-hoc mode), which can preclude the first network device from discovering the second network device. Additionally, other modes of operation of the second network device (e.g., the WiFi direct P2P mode) are not foreclosed from utilization. Rather, the second network device can utilize any of the multiple network modes after being discovered by the first network device.


In a second example, a first network device operates in the ad-hoc mode in an ad-hoc network. Additionally, the first network device is capable of operating in other network modes (e.g., the infrastructure mode). The beacons transmitted by the first network device include the new IE. Specifically, the beacons do not include an IBSS bit to indicate that the first network device is operating in the ad-hoc mode. Instead, the beacons include the new IE, which indicates that the first network device can optionally operate in the infrastructure mode in addition to being able to operate in the ad-hoc mode.


Accordingly, a second network device that is not associated with the ad-hoc network can discover the first network device as a generic network device based on the beacons received from the first network device. After discovering the first network device, the second network device can communicate with the first network device using the ad-hoc mode or the infrastructure mode depending on the mode in which the second network device can operate.


Additionally, the first network device can attempt to discover other network devices external to the ad-hoc network by transmitting probe requests. The probe requests do not include the IBSS bit. Instead, the probe requests include the new IE, which indicates that the first network device can optionally operate in the infrastructure mode, for example, in addition to being able to operate in the ad-hoc mode.


When the second network device receives one of the probe requests, the second network device can transmit a probe response that includes an IE, which indicates that the second network device can operate in one or more network modes. On receiving the probe response, the first network device can discover the second network device as a generic network device based on the IE in the probe response. After discovering the second network device, the first network device and the second network device can select a suitable network mode and communicate using the selected network mode.


Referring now to FIGS. 2A and 2B, a network device 100 according to the present disclosure is shown. In FIG. 2A, the network device 100 includes an antenna 102, a physical layer (PHY) module 104, a media access control (MAC) module 106, and a processing module 108. The PHY module 104 transmits and receives data via the antenna 102. The MAC module 106 controls access of the network device 100 to the medium (e.g., air) via the antenna 102. The processing module 108 processes data transmitted and received by the network device 100 through the medium.


A remote network device (hereinafter remote device) 110 can communicate with the network device 100 via an antenna 112. While not shown, the remote device 110 can also include a PHY module, a MAC module, and a processing module similar to the network device 100. Further, although the network device 100 and the remote device 110 are shown to include a single antenna, the network device 100 and the remote device 110 can include multiple antennas.


In FIG. 2B, the network device 100 includes a system for discovering network devices capable of operating in multiple network modes according to the present disclosure. The system includes a receiving module 120, a transmit module 122, a detecting module 124, a negotiation module 126, an association module 128, and a response generating module 130.


For example only, the system can be implemented in the MAC module 106 of the network device 100 as shown. Alternatively, the system can be included in the PHY module 104 of the network device 100. In some implementations, the system can be implemented partly in the PHY module 104 and partly in the MAC module 106. While not shown, the discovery system can be similarly implemented in the remote device 110.


The receiving module 120 can receive a beacon transmitted by the remote device 110 operating in one of a plurality of network modes. Alternatively, the receiving module 120 can receive a probe response transmitted by the remote device 110 in response to a probe request transmitted by the network device 100 operating in one of a plurality of network modes. The network device 100 can transmit the probe request via the transmit module 122.


The beacon or the probe response received from the remote device 110 includes an information element (IE) according to the present disclosure. The IE indicates that the remote device 110 is capable of operating in a plurality of network modes. The plurality of network modes includes the ad-hoc mode, the infrastructure mode, a mesh mode, and a WiFi direct peer-to-peer mode.


The detecting module 124 processes the information element received from the remote device 110 and discovers the remote device 110 as a generic network device. Specifically, the detecting module 124 detects the remote device 110 as being capable of operating in the plurality of network modes based on the information element.


After the discovery of the remote device 110 is completed, the negotiation module 126 negotiates one of the network modes for communicating with the remote device 110. The association module 128 associates the network device 100 with the remote device 110 using the negotiated network mode. Subsequently, the network device 100 and the remote device 110 communicate using the negotiated network mode.


Alternatively, the receiving module 120 can receive a probe request transmitted by the remote device 110. The response generating module 130 generates a probe response on receiving the probe request from the remote device 110. The probe response includes an information element (IE) according to the present disclosure. The IE indicates that the network device 100 is capable of operating in a plurality of network modes. The plurality of network modes includes the ad-hoc mode, the infrastructure mode, the mesh mode, and the WiFi direct peer-to-peer mode. The transmit module 122 transmits the probe response.


The remote device 110 receives the probe response transmitted by the network device 100. The remote device 110 discovers the network device 100 as being capable of operating in the plurality of network modes (i.e., as a generic network device) based on the information element in the probe response.


After discovering the network device 100, the remote device 110 negotiates one of the network modes for communicating with the network device 100. The remote device 110 associates with the network device 100 using the negotiated network mode. Subsequently, the network device 100 and the remote device 110 communicate using the negotiated network mode.


Referring now to FIGS. 3A and 3B, methods 150 and 170 for discovering network devices capable of operating in multiple network modes according to the present disclosure are shown. The network device 100 (or the remote device 110) can implement the methods 150 and 170 as follows.


In FIG. 3A, control begins at 152. At 154, control determines if a beacon or a probe response is received by a network device from a remote device. Control waits until a beacon or a probe response is received by the network device. At 156, if a beacon or a probe response is received by the network device, control discovers the remote device as a generic network device based on the information element included in the beacon or the probe response received from the remote device. The information element indicates that the remote device is capable of operating in multiple network modes.


At 158, control negotiates a mode of operation with the remote device. At 160, control associates the network device with the remote device using the negotiated mode, and the network device communicates with the remote device using the negotiated mode. Control ends at 162.


In FIG. 3B, control begins at 172. At 174, control determines if a probe request is received by a network device from a remote device. Control waits until a probe request is received by the network device. At 176, if a probe request is received by the network device, control transmits a probe response from the network device to the remote device. The probe response includes an information element indicating that the network device is capable of operating in multiple network modes.


At 178, control determines if the remote device discovered the network device and is negotiating a mode of operation with the network device. Control ends at 184 if the remote device fails to discover the network device, or if the remote device determines not to associate with the network device.


At 180, if the remote device discovers the network device, and if the remote device decides to associate with the network device, control negotiates a mode of operation with the remote device. At 182, control associates the network device with the remote device using the negotiated mode, and the network device communicates with the remote device using the negotiated mode. Control ends at 184.


The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims.

Claims
  • 1. A network device comprising: a receiving module configured to receive a beacon transmitted from a remote device, wherein the remote device is operating in an ad-hoc mode, and wherein the beacon includes an information element indicating that the remote device is capable of operating in each of (i) the ad-hoc mode, wherein while operating in the ad-hoc mode, the network device and the remote device are configured to communicate with each other directly without having to communicate with each other via an access point; and(ii) an infrastructure mode, wherein while operating in the infrastructure mode, the network device and the remote device are configured to indirectly communicate with each other via an access point; anda processor configured to detect, based on the information element contained in the beacon transmitted from the remote device, that the remote device is capable of operating in each of the ad-hoc mode and the infrastructure mode;negotiate one of the ad-hoc mode and the infrastructure mode for communicating with the remote device; andassociate the network device with the remote device using the negotiated one of the ad-hoc mode and the infrastructure mode.
  • 2. A method comprising: receiving, at a network device, a beacon transmitted from a remote device, wherein the remote device is operating in an ad-hoc mode, and wherein the beacon includes an information element indicating that the remote device is capable of operating in each of (i) the ad-hoc mode, and (ii) an infrastructure mode, wherein while operating in the ad-hoc mode, the network device and the remote device are configured to communicate with each other directly without having to communicate with each other via an access point, and wherein while operating in the infrastructure mode, the network device and the remote device are configured to indirectly communicate with each other via an access point;detecting, based on the information element contained in the beacon transmitted from the remote device, that the remote device is capable of operating in each of the ad-hoc mode and the infrastructure mode;negotiating one of the ad-hoc mode and the infrastructure mode for communicating with the remote device; andassociating the network device with the remote device using the negotiated one of the ad-hoc mode and the infrastructure mode.
  • 3. A network device comprising: a receiving module configured to receive a probe response transmitted from a remote device, wherein the probe response is transmitted from the remote device in response to the remote device receiving a probe request transmitted from the network device, wherein the remote device is operating in a WiFi direct peer-to-peer mode, and wherein the probe response includes an information element indicating that the remote device is capable of operating in each of (i) the WiFi direct peer-to-peer mode, wherein while operating in the WiFi direct peer-to-peer mode, (a) the network device and the remote device are configured to communicate with each other directly without having to communicate with each other via an access point, and the network device and the remote device are configured to communicate using signaling mechanisms of an infrastructure network; and (b) one of the network device and the remote device operates as a group owner and the other operates as a client station; and(ii) an ad-hoc mode, wherein while operating in the ad-hoc mode, the network device and the remote device are configured to communicate with each other directly without having to communicate with each other via an access point; anda processor configured to detect, based on the information element contained in the probe response transmitted from the remote device, that the remote device is capable of operating in each of the WiFi direct peer-to-peer mode and the ad-hoc mode;negotiate one of the WiFi direct peer-to-peer mode and the ad-hoc mode for communicating with the remote device; andassociate the network device with the remote device using the negotiated one of the WiFi direct peer-to-peer mode and the ad-hoc mode.
  • 4. A method comprising: receiving, at a network device, a probe response transmitted from a remote device, wherein the probe response is transmitted from the remote device in response to the remote device receiving a probe request transmitted from the network device, wherein the remote device is operating in a WiFi direct peer-to-peer mode, and wherein the probe response includes an information element indicating that the remote device is capable of operating in each of (i) the WiFi direct peer-to-peer mode, and (ii) an ad-hoc mode,wherein while operating in the WiFi direct peer-to-peer mode, (a) the network device and the remote device are configured to communicate with each other directly without having to communicate with each other via an access point, and the network device and the remote device are configured to communicate using signaling mechanisms of an infrastructure network; and (b) one of the network device and the remote device operates as a group owner and the other operates as a client station; and wherein while operating in the ad-hoc mode, the network device and the remote device are configured to communicate with each other directly without having to communicate with each other via an access point;detecting, based on the information element contained in the probe response transmitted from the remote device, that the remote device is capable of operating in each of the WiFi direct peer-to-peer mode and the ad-hoc mode;negotiating one of the WiFi direct peer-to-peer mode and the ad-hoc mode for communicating with the remote device; andassociating the network device with the remote device using the negotiated one of the WiFi direct peer-to-peer mode and the ad-hoc mode.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 61/301,129, filed on Feb. 3, 2010. The disclosure of the above application is incorporated herein by reference in its entirety.

US Referenced Citations (192)
Number Name Date Kind
5735583 Katayama et al. Apr 1998 A
5738583 Comas et al. Apr 1998 A
5907566 Benson et al. May 1999 A
6182248 Armstrong et al. Jan 2001 B1
6272120 Alexander Aug 2001 B1
6287200 Sharma Sep 2001 B1
6397357 Cooper May 2002 B1
6587691 Granstam et al. Jul 2003 B1
6600726 Nevo et al. Jul 2003 B1
6690935 Calot et al. Feb 2004 B1
6704866 Benayoun et al. Mar 2004 B1
6707801 Hsu Mar 2004 B2
6760587 Holtzman et al. Jul 2004 B2
6785592 Smith et al. Aug 2004 B1
6785892 Miller et al. Aug 2004 B1
6788675 Yang Sep 2004 B1
6793580 Sinclair et al. Sep 2004 B2
6795701 Baker et al. Sep 2004 B1
6799056 Curley et al. Sep 2004 B2
6859460 Chen Feb 2005 B1
6879574 Naghian et al. Apr 2005 B2
6879812 Agrawal et al. Apr 2005 B2
6909705 Lee et al. Jun 2005 B1
6932698 Sprogis Aug 2005 B2
6973580 Carroll et al. Dec 2005 B1
7013391 Herle et al. Mar 2006 B2
7024199 Massie et al. Apr 2006 B1
7072323 Roberts et al. Jul 2006 B2
7073129 Robarts et al. Jul 2006 B1
7085257 Karves et al. Aug 2006 B1
7087562 Abe et al. Aug 2006 B2
7097562 Gagner Aug 2006 B2
7136642 Massie et al. Nov 2006 B1
7143171 Eriksson et al. Nov 2006 B2
7162238 Massie et al. Jan 2007 B1
7181544 Vangal et al. Feb 2007 B2
7224964 Souissi et al. May 2007 B2
7236772 Botzas Jun 2007 B1
7251235 Wentink Jul 2007 B2
7308263 Gallagher et al. Dec 2007 B2
7324444 Liang et al. Jan 2008 B1
7400722 Qi et al. Jul 2008 B2
7435179 Ford Oct 2008 B1
7440430 Jagadeesan et al. Oct 2008 B1
7452278 Chen et al. Nov 2008 B2
7551930 Lempio et al. Jun 2009 B2
7580866 Church Aug 2009 B2
7656847 Mela et al. Feb 2010 B2
7710982 Ohmuro et al. May 2010 B2
7779334 Earle et al. Aug 2010 B2
7817545 Ho et al. Oct 2010 B2
7881284 Lin et al. Feb 2011 B2
7899017 Yu et al. Mar 2011 B2
7970384 Lambert et al. Jun 2011 B1
8099109 Altman et al. Jan 2012 B2
8099318 Moukas et al. Jan 2012 B2
8165034 Buchwald et al. Apr 2012 B2
8194600 Nagaraja Jun 2012 B2
8194629 Agulnik et al. Jun 2012 B2
8257177 Saund et al. Sep 2012 B1
8279884 Narasimha et al. Oct 2012 B1
8325659 Chen et al. Dec 2012 B2
8351394 Yao Jan 2013 B2
8374584 Lambert et al. Feb 2013 B1
8411656 Liu Apr 2013 B2
8411662 Saund et al. Apr 2013 B1
8428079 Lambert Apr 2013 B1
8489669 Johnson Jul 2013 B2
8616975 Saund et al. Dec 2013 B1
8825016 Lambert et al. Sep 2014 B1
8937963 Narasimha et al. Jan 2015 B1
9185732 Saund et al. Nov 2015 B1
20020087370 Brueckheimer et al. Jul 2002 A1
20020147642 Avallone et al. Oct 2002 A1
20020147913 Lun Yip Oct 2002 A1
20020151366 Walker et al. Oct 2002 A1
20020152388 Linnartz et al. Oct 2002 A1
20020157044 Byrd Oct 2002 A1
20020169539 Menard et al. Nov 2002 A1
20020169653 Greene et al. Nov 2002 A1
20020191560 Chen et al. Dec 2002 A1
20020199124 Adkisson Dec 2002 A1
20030065805 Barnes Apr 2003 A1
20030069018 Matta et al. Apr 2003 A1
20030088690 Zuckerman et al. May 2003 A1
20030105667 Millikan Jun 2003 A1
20030115320 Yarroll et al. Jun 2003 A1
20030133422 Bims Jul 2003 A1
20030152093 Gupta et al. Aug 2003 A1
20030169755 Ternovsky Sep 2003 A1
20030182454 Huth et al. Sep 2003 A1
20030224855 Cunningham Dec 2003 A1
20030231189 Williams Dec 2003 A1
20030231625 Calvignac Dec 2003 A1
20030235175 Naghian et al. Dec 2003 A1
20040066751 Tseng et al. Apr 2004 A1
20040081106 Bruhn Apr 2004 A1
20040082383 Muncaster et al. Apr 2004 A1
20040105415 Fujiwara et al. Jun 2004 A1
20040120309 Kurittu et al. Jun 2004 A1
20040127277 Walker et al. Jul 2004 A1
20040174829 Ayyagari Sep 2004 A1
20040185851 Nagai Sep 2004 A1
20040196808 Chaskar et al. Oct 2004 A1
20040203350 Shultz et al. Oct 2004 A1
20040225932 Hoda et al. Nov 2004 A1
20040236850 Krumm et al. Nov 2004 A1
20040243887 Sharma et al. Dec 2004 A1
20050025163 Christie Feb 2005 A1
20050032577 Blackburn et al. Feb 2005 A1
20050041660 Pennec et al. Feb 2005 A1
20050041793 Fulton et al. Feb 2005 A1
20050041796 Joseph et al. Feb 2005 A1
20050058112 Lahey et al. Mar 2005 A1
20050060547 Saito et al. Mar 2005 A1
20050073980 Thomson et al. Apr 2005 A1
20050079873 Caspi et al. Apr 2005 A1
20050099977 Williams et al. May 2005 A1
20050157661 Cho Jul 2005 A1
20050177445 Church Aug 2005 A1
20050177639 Reunamaki et al. Aug 2005 A1
20050181872 Acharya et al. Aug 2005 A1
20050197189 Schultz Sep 2005 A1
20050207342 Tanabe et al. Sep 2005 A1
20050250487 Miwa et al. Nov 2005 A1
20050250497 Ghosh et al. Nov 2005 A1
20050268003 Wang et al. Dec 2005 A1
20050286456 McNew et al. Dec 2005 A1
20060041750 Carter et al. Feb 2006 A1
20060045138 Black et al. Mar 2006 A1
20060046709 Krumm et al. Mar 2006 A1
20060063539 Beyer, Jr. Mar 2006 A1
20060135262 Kennedy et al. Jun 2006 A1
20060166740 Sufuentes Jul 2006 A1
20060172736 Nevo Aug 2006 A1
20060205409 Chiou et al. Sep 2006 A1
20060215576 Yu et al. Sep 2006 A1
20060221857 Bushnell et al. Oct 2006 A1
20060268711 Doradla et al. Nov 2006 A1
20070026866 Krishnamurthi et al. Feb 2007 A1
20070035513 Sherrard et al. Feb 2007 A1
20070047547 Conner et al. Mar 2007 A1
20070047697 Drewry et al. Mar 2007 A1
20070060128 Kil Mar 2007 A1
20070060355 Amaitis et al. Mar 2007 A1
20070060358 Amaitis et al. Mar 2007 A1
20070076683 Chung et al. Apr 2007 A1
20070078000 Saund et al. Apr 2007 A1
20070082671 Feng et al. Apr 2007 A1
20070086394 Yamada et al. Apr 2007 A1
20070086401 Hong et al. Apr 2007 A1
20070099703 Terebilo May 2007 A1
20070192183 Monaco et al. Aug 2007 A1
20070197237 Powell et al. Aug 2007 A1
20070202910 Brewer et al. Aug 2007 A1
20070258415 Lu et al. Nov 2007 A1
20070286111 Corson et al. Dec 2007 A1
20080039015 Nakata et al. Feb 2008 A1
20080052603 Wiatrowski et al. Feb 2008 A1
20080062940 Othmer et al. Mar 2008 A1
20080069105 Costa et al. Mar 2008 A1
20080082671 Meijer et al. Apr 2008 A1
20080095112 Wiemann et al. Apr 2008 A1
20080101400 Auterinen May 2008 A1
20080123608 Edge et al. May 2008 A1
20080176561 Shao et al. Jul 2008 A1
20080214216 Bragg et al. Sep 2008 A1
20080228547 Doss et al. Sep 2008 A1
20090012704 Franco et al. Jan 2009 A1
20090043658 Webb et al. Feb 2009 A1
20090181728 Park Jul 2009 A1
20090191878 Hedqvist et al. Jul 2009 A1
20090222358 Bednarek Sep 2009 A1
20090307091 Lilley Dec 2009 A1
20090319348 Khosravy et al. Dec 2009 A1
20090323648 Park et al. Dec 2009 A1
20100023401 Ariyibi Jan 2010 A1
20100070369 Fenton et al. Mar 2010 A1
20100093374 Dacosta Apr 2010 A1
20100111066 Mehta May 2010 A1
20100144372 Bouwer Jun 2010 A1
20100274626 Carlson Oct 2010 A1
20100285776 de Froment Nov 2010 A1
20110029359 Roeding et al. Feb 2011 A1
20110060652 Morton Mar 2011 A1
20110066369 Klassen et al. Mar 2011 A1
20110066485 Rissanen Mar 2011 A1
20110093876 Belz et al. Apr 2011 A1
20110269431 Hardy et al. Nov 2011 A1
20120095844 Barnes, Jr. Apr 2012 A1
20120106728 Ghaffari et al. May 2012 A1
20130096966 Barnes, Jr. Apr 2013 A1
Non-Patent Literature Citations (6)
Entry
Meredith, John; “Voice Call Continuity in 3GPP”; CompactPCI and AdvancedTCA systems; Apr. 2006; 2 pages.
“Universal Mobile Access: UMA Expands Beyond Dual-Mode Handsets”; The UMA Company; Jan. 2007; 8 pages.
IEEE Standards Board. IEEE 802.11 Standard, 1999.1999 Edition.
Newton, Harry. Newton's Telecom Dictionary. 15th Edition. Miller Freeman Inc., 1999. 762. (3 pages).
“Client-Server Protocol Session and Transactions”, Approved Version 1.3; Open Mobile Alliance Ltd; Jan. 23, 2007; 206 pages.
“IMPS Architecture”, Approved Version 1.3, Open Mobile Alliance Ltd.; Jan. 23, 2007; 24 pages.
Provisional Applications (1)
Number Date Country
61301129 Feb 2010 US