Predictive roaming between subnets

Information

  • Patent Grant
  • 10064105
  • Patent Number
    10,064,105
  • Date Filed
    Monday, January 23, 2017
    7 years ago
  • Date Issued
    Tuesday, August 28, 2018
    5 years ago
Abstract
A network device of a subnet determines predictive roaming information for a wireless client. Predictive roaming information can identify the wireless client and a home network subnet of the wireless client. The network device provides predictive roaming information associated with a wireless client to neighboring subnets. Neighboring subnets store received predictive roaming information, and use the predictive roaming information if the wireless client roams to them.
Description
BACKGROUND

Wireless data networks allow computers or other electronic devices to exchange data without wires, typically using radio waves. Wireless networks are popular with users due to the ability to send and receive data almost anywhere within the physical coverage area of the network. This allows users to access communication networks, including local area networks, organization or company intranets, virtual private networks, and wide area networks, such as the Internet, anywhere within the physical coverage area of the wireless networks.


Wireless networks with large physical coverage areas, such as networks covering university campuses or entire cities, offer users ubiquitous access to their data and the Internet. However, typical wireless access points have ranges of around 100 feet. As a result, large wireless networks require tens, hundreds, or thousands of wireless access points to provide network coverage over a large physical area.


Configuring, managing, and operating a large number of wireless access points requires complicated network configurations. Typically, a large wireless network is divided into a number of different network subnets. Each network subnet includes one or more wireless access points. Each network subnet is assigned a specific range of IP addresses. All of the wireless access points within a subnet as well as the wireless client devices connected with these wireless access points are assigned IP addresses within the range of IP addresses associated with a subnet.


The use of multiple subnets within a wireless network introduces the problem of roaming. A wireless client, especially mobile devices, may move to different physical locations while connected with the wireless network. If a wireless client moves from the physical area associated with one wireless access point to a physical area associated with a second wireless access point, it is desirable for the wireless client to automatically connect with the second wireless access point to maintain its network connection. If both wireless access points are within the same subnet, the wireless client can keep the same IP address, allowing roaming to occur seamlessly without any noticeable disruption in the network connection or data traffic.


However, if a wireless client moves between wireless access points in different subnets, the wireless client cannot keep the same IP address. This is because each subnet has its own exclusive range of IP addresses. When the wireless client is connected with a wireless access point in a first subnet, the wireless client will have an IP address in the first subnet's IP address range. When the wireless client tries to connect with a wireless access point in a second subnet, its IP address is outside the second subnet's IP address range. As a result, the wireless client must be reauthenticated and assigned a new IP address that is valid for the second subnet. This process can cause noticeable disruption in the network connection and data traffic for the wireless client. This disruption is unacceptable for some applications, such as VoIP telephone applications.


The Mobile IP protocol is one approach for maintaining network connections of wireless devices. In the Mobile IP protocol, a wireless client is identified by its home address disregarding its current location in the Internet. The wireless client also carries the address of a home agent, which is a device located within the same subnet as its home address. When a wireless client moves from its home address to a new subnet, the wireless client locates a designated forwarding agent within the new subnet. The wireless client provides the forwarding agent with the address of its home agent. The forwarding agent then sets up a network tunnel with the home agent. Network traffic directed to the wireless client's home address is intercepted by the home agent and sent via the tunnel to the forwarding agent, which in turn forwards it to the wireless client. Similarly, network traffic from the wireless client is intercepted by the forwarding agent and sent via the tunnel to the home agent, which in turn forwards it to its intended destination.


One problem with the Mobile IP protocol is that it relies on the wireless client to maintain the network connection when roaming. The wireless client is responsible for carrying the address of the home agent and for contacting a forwarding agent as needed. To meet these responsibilities, the wireless client must either include a modified network driver stack or applications that support Mobile IP. The wireless client must keep track of two different IP addresses: the initial IP address in the client's “home” subnet and the IP address in the client's current subnet. Even if wireless clients include these capabilities, it is difficult and time-consuming to correctly configure large numbers of wireless clients to support Mobile IP roaming within a wireless network. Furthermore, wireless clients may need to be reconfigured whenever there are changes in network topology.


Therefore, there is an unmet need to enable wireless clients to roam without modifying the wireless client or its applications to support roaming protocols. There is also an unmet need for wireless clients to roam without requiring special configuration or knowledge of the network topology. There is also an unmet need to support wireless client roaming in an efficient and reliable manner.


SUMMARY

In a specific implementation, wireless access points select at least one home agent in a subnet to support network traffic from roaming wireless clients. Wireless access points can also, for example, detect neighboring wireless access points in different subnets. One or more of the wireless access points can provide the address of their home agents to neighboring wireless access points, which in turn forward these addresses to their own home agents. Thus, each home agent can be provided the addresses of home agents in other network subnets.


In a specific implementation, upon connecting with a wireless client, a wireless access point or other device determines predictive roaming information for the wireless client. Predictive roaming information may include, for example, information identifying the wireless client; its home network subnet (i.e. the network subnet associated with the wireless client's current IP address); and connection information used to communicate with the wireless client, such as session keys and virtual LAN information. In a specific implementation, the wireless access point forwards the predictive roaming information associated with a wireless client to at least a portion of its neighboring wireless access points while the wireless client is still connected with the wireless access point.


In a specific implementation, neighboring wireless access points cache or store received predictive roaming information. Upon connecting with a wireless client, a neighboring wireless access point compares identifying information of the newly connected wireless client with the cached predictive roaming information. If the newly connected wireless client matches at least a portion of the predictive roaming information, the neighboring wireless access point uses the predictive roaming information to quickly connect with the wireless client and to establish a tunnel to redirect network traffic associated with the wireless client through to its home subnet.


In a specific implementation, a neighboring wireless access point contacts its home agent to determine the address of a home agent in the home subnet of a wireless client. The neighboring wireless access point then establishes a tunnel between itself or another device in its own subnet to the home agent or other device in the home subnet of the wireless client. The home agent in the home subnet of the wireless client may or may not be selected using a load balancing technique. The home agent in the home subnet of the wireless client may or may not be configured to intercept network traffic associated with the wireless client. In a specific implementation, the neighboring wireless access point uses layer 2 routing to communicate with the wireless client, allowing the wireless client to continue using its IP address in a different subnet.


In a specific implementation, if the newly connected wireless client does not match at least a portion of the predictive roaming information of a neighboring wireless access point, the neighboring wireless access point sends a query message to its home agent to identify the home subnet of the wireless client. The home agent forwards the query message to home agents in other subnets, which in turn may or may not forward the query message to wireless access points and other devices to identify the home subnet of the wireless client. The neighboring wireless access point can eventually receive a response to the query message that identifies the home subnet of the wireless client. The wireless access point can then use this home subnet information to establish a tunnel to redirect network traffic for the wireless client through its home subnet, as described above. Later, for example, if the wireless client's network connection becomes idle, a new IP address can be assigned within the current subnet to the wireless client and potentially remove the tunnel to conserve network resources.





BRIEF DESCRIPTION OF THE DRAWINGS

Techniques related to the invention are described with reference to the drawings.



FIG. 1 illustrates an example wireless network.



FIG. 2 illustrates an example network initialization for roaming.



FIG. 3 illustrates a first part of an example of predictive roaming.



FIG. 4 illustrates a second part of an example of predictive roaming.



FIG. 5 illustrates example data traffic during predictive roaming.



FIG. 6 illustrates an example of nomadic roaming.



FIG. 7 illustrates an example method implementing predictive and nomadic roaming in a wireless access point or other network device.



FIG. 8 illustrates an example computer system suitable for implementing techniques described in this paper.





In the drawings, the use of identical reference numbers indicates identical elements.


DETAILED DESCRIPTION


FIG. 1 illustrates an example wireless network 100. Wireless network 100 includes subnet 1105, which is associated with the range of IP addresses 1.1.1.X, and subnet 2120, which is associated with the range of IP addresses 1.1.2.X. In an embodiment, devices in subnets 1105 and 2120 are connected with each other and other networks, such as the Internet, via wired or wireless network connections, which are omitted from the figures for clarity.


Subnet 1105 includes a switch 110 responsible for connecting network segments. In an embodiment, switch 110 is a layer 2 network switch, such as a network bridge, adapted to direct network traffic at the data link layer of a networking protocol, for example using media access control (MAC) addresses, rather than IP address. In another embodiment, switch 1110 may be a layer 3 network switch, such as a router, or include higher-level network traffic control, such as layer 4 firewalls and network address translation.


Subnet 1105 includes wireless access points 115, including wireless access points 115a and 115b. Wireless access points 115 may implement any type of standard or proprietary wireless data communication protocols, including the 802.11 family of protocols, such as 802.11a, 802.11b, 802.11g, and 802.11n. Wireless access points 115 are connected with the switch 110 via wired or wireless network connections. Each of the wireless access points 115 may provide wireless data communications with one or more wireless network clients. Similar to subnet 1105, subnet 2120 includes switch 125, similar to switch 110, and wireless access points 130, similar to wireless access points 115.


Each of the wireless access points 115 and 130 has a physical coverage area 117, which is the physical area in which a wireless client device may be able to connect with a wireless access point. To ensure continuous network coverage, the physical coverage areas 117 of the wireless access points 115 and 130 may overlap. For example, the physical coverage area 117a of wireless access point 115a overlaps the physical coverage area 117b of wireless access point 115b. Additionally, physical coverage areas of wireless access points in different subnets may overlap if the wireless access points are physically close together. For example, physical coverage area 117b, associated with subnet 1105, overlaps physical coverage area 117c, associated with subnet 2120, in area 132.



FIG. 2 illustrates an example network initialization 200 for roaming. In an embodiment, a wireless network, such as wireless network 100, is initialized for roaming wireless clients by 1) discovering neighboring wireless access points; 2) selecting home agents; and 3) exchanging home agent addresses.


In a specific implementation, to discover neighboring wireless access points, wireless access points can be adapted to scan available wireless data radio channels for wireless access points in different subnets. In an embodiment, wireless access points periodically broadcast a beacon signal identifying themselves to any nearby wireless access points. The beacon signal may include a wireless access point's IP address or other information identifying the wireless access point's network subnet.


Upon receiving a beacon signal from another wireless access point, an embodiment of a wireless access point compares the subnet specified by the beacon signal with its own subnet. If the wireless access point determines that the beacon signal is associated with a wireless access point in a different subnet, the wireless access point adds this wireless access point to its neighbor table with a designation indicating that it is in a different subnet. This indication may include the address, such as an IP address, of the wireless access point in the other subnet.


For example, because wireless access points 115b and 130a have overlapping physical coverage areas 117, they will detect each other's beacon signals. As a result, wireless access point 115b will add wireless access point 130a to its neighbor table 205a. In this example, neighbor table 205a will include the IP address, 1.1.2.2, of wireless access point 130a. Similarly, wireless access point 130a will add wireless access point's 115b IP address of 1.1.1.4 to its neighbor table 205b.


In a further embodiment, neighboring wireless access points may discover each other using probe request and probe response message. In this embodiment, a wireless access point periodically scans all communication channels and sends out probe request frames. Any neighboring wireless access points using one of these communication channels and receiving a probe request frame will respond with a probe response frame that includes identifying information, such as the neighboring wireless access points IP address or network subnet.


Additionally, the network initialization 200 selects one or more home agents within its network subnet for each wireless access point. A home agent may be a wireless access point, a network switch, a dedicated device, a computer system, or any other device in a subnet that is capable of performing home agent tasks, which are described in detail below. In a further embodiment, a wireless access point may act as its own home agent and optionally the home agent of one or more additional wireless access points.


In an embodiment, network initialization 200 also established a tunnel or other network connection between neighboring wireless access points in different subnets. This tunnel or network connection may be used for exchanging predictive roaming information, as described below; home agent information to be used for nomadic roaming; and/or any other data shared between subnets.


In an embodiment, a subnet may include one or more home agents for load balancing and reliability purposes. In an embodiment, each device in a subnet capable of acting as a home agent sends out a broadcast message to other devices in the subnet. Upon receiving broadcast messages from potential home agent devices, a wireless access point selects one or more of the potential home agent devices, possibly including itself, as its home agent.


A home agent is the contact point within a subnet for network traffic from roaming wireless clients in other subnets. As described in detail below, a home agent may be used to receive and retransmit network traffic associated with a roaming wireless client. In some circumstances, a home agent may also contact home agents in other subnets to locate the home subnet of a wireless client device.


For example, wireless access points 115a, 130a, and 130b are configured to act as home agents. Thus, wireless access point 115a will be selected as the home agent for subnet 1105 and wireless access points 130a and 130b will be selected as the home agents for subnet 2120. Neighbor wireless access points 115b and 130a, as well as the other wireless access points, will have the IP addresses of their respective home agents in their subnets.


To facilitate roaming, each home agent maintains a list of the addresses, such as the IP addresses, of home agents in other subnets. In an embodiment, this information is obtained by exchanging home agent addresses via the neighbor wireless access points. For example, wireless access point 115b is aware that wireless access point 130a is in a different subnet. Thus, wireless access point 115b sends home agent information 210a to the neighboring wireless access point 130a. Similarly, wireless access point 130a sends home agent information 210b to wireless access point 115b. Following the exchange of home agent information 210, wireless access points 115b and 130a have the addresses of home agents in both subnet 1105 and subnet 2120. Wireless access points 115b and 130a may then share this information with their respective home agents, so that home agents 115a, 130a, and 130b each have the addresses of home agents in both subnet 1105 and subnet 2120. In an embodiment, home agent information 210 may travel directly between neighboring wireless access points via their wireless data connection or indirectly through wired and/or wireless network connections and numerous network devices to reach neighboring wireless access points in different subnets.


Once the wireless network has been initialized by discovering neighboring wireless access points, selecting home agents, and exchanging home agent addresses, the wireless network is ready to support roaming wireless clients. One type of roaming enabled by techniques described in this paper is predictive roaming. Predictive roaming allows wireless clients to connect with one or more subnets outside of their initial or home subnet while maintaining their IP addresses in the home subnet and without any disruption to their network connections or data traffic.



FIG. 3 illustrates a first part 300 of an example of predictive roaming. In this example, a wireless network, such as wireless network 100, is connected with a wireless client 305. Wireless clients can include mobile devices, such as laptop computers, personal digital assistants, mobile Internet devices, media player devices with wireless network interfaces, voice over IP (VoIP) telephone devices, and navigation systems with wireless network interfaces; fixed devices, such as desktop computers with wireless network interfaces; and any other electronic device including a wireless network interface.


In this part 300 of the example of predictive roaming, the wireless client 305 is connected with wireless access point 115b. Wireless access point 115b provides wireless client 305 with a network connection 310 to the wireless network 100 as well as any other connected networks, such as the Internet. Upon the wireless client connecting with a wireless access point that is a neighbor to any wireless access point in a different subnet, an embodiment of the wireless access point provides connection information for the wireless client to one or more neighboring wireless access points in different subnets. This connection information is referred to as predictive roaming information and is used to maintain the wireless client's network connection if it roams to the physical coverage area of a different subnet.


In an embodiment, the predictive roaming information includes the IP address and MAC address associated with a wireless client; session keys used for security and/or encryption of the wireless client's network connection; and optionally other information used to establish and maintain the wireless client's network connection, such as virtual LAN (VLAN) information, including, for example, a virtual LAN identifier.


For example, wireless client 305 is connected via network connection 310 with wireless access point 115b. Network connection 310 includes connection information 315, including for example the IP address, MAC address, and session keys, used by wireless client 305 to communicate with wireless access point 115b. In an embodiment, when wireless client 305 establishes a connection with wireless access point 115b, wireless access point 115b forwards predictive roaming information 320, for example including the IP address, MAC address, and session keys used by the wireless client 305, to its neighbor wireless access point 130a in subnet 2120. In an embodiment, predictive roaming information 320 may travel directly between neighboring wireless access points via their wireless data connection or indirectly through wired and/or wireless network connections and numerous network devices to reach neighboring wireless access points in different subnets. Wireless access point 130a stores the predictive roaming information 320 associated with wireless client 305 for later use.



FIG. 4 illustrates a second part 400 of an example of predictive roaming. If wireless client 305 roams to the physical coverage area 117c of wireless access point 130a, wireless client 305 will attempt to establish a network connection 405 with wireless access point 130a in subnet 2120. Upon connecting with the wireless client 305, wireless access point 130a will obtain identifying information, such as the MAC address of the wireless client 305. Wireless access point 130a will compare this identifying information with its stored predictive roaming information 410.


In this example 400, the MAC address of the wireless client 305 matches the predictive roaming information 410 previously received from wireless access point 115b. As a result, wireless access point 130a knows the home IP address of the wireless client 305. Using this home IP address of wireless client 305, wireless access point 130a determines the home subnet of the wireless client 305, in this case subnet 1105. Wireless access point 130a contacts one of its home agent devices (i.e. itself or wireless access point 130b) to determine the IP address of a home agent in the home subnet (i.e. subnet 1105) of the wireless client 305, such as wireless access point 115a.


Wireless access point 130a then establishes a tunnel 415, such as a GRE tunnel, between itself and the home agent 115a in subnet 1105 for carrying network traffic associated with wireless client 305. Additionally, wireless access point 130a uses the session keys and other information included in the stored predictive roaming information 410 to communicate with the wireless client 305 via network connection 405. In a further embodiment, if other wireless clients with home IP addresses in subnet 1105 roam to wireless access point 130a in subnet 2120, tunnel 415 may be used to carry these wireless clients' network traffic as well.


The process of predictive roaming shown in FIGS. 3 and 4 may be repeated as the wireless client moves to the physical coverage areas of other wireless access points within subnet 2120 or other subnets. For example, upon the wireless client 305 connecting with wireless access point 130a, as shown in FIG. 4, wireless access point 130a will provide a copy of the predictive roaming information 410 for wireless client 305 to any neighboring wireless access points in the same or a different subnet, such as wireless access point 130b. If the wireless client 305 later moves into the physical coverage area 117d of wireless access point 130b, wireless access point 130b will use its copy of the predictive roaming information 410 to establish a tunnel between itself and the home agent 115a to handle the data traffic of wireless client 305.



FIG. 5 illustrates an example 500 of data traffic during predictive roaming. In the example 500 of FIG. 5, data 505a from wireless client 305 is communicated via network connection 405 to wireless access point 130a. Wireless access point 130a directs data 505a through tunnel 415 to wireless access point 115a, which acts a home agent for subnet 1105, the home subnet of wireless client 305. Wireless client 115a then rebroadcasts data 505b to its intended destination.


In an embodiment, when the tunnel 415 is established or when a new wireless client uses the tunnel 415, the home agent wireless access point 115a, switch 110, and any other devices in subnet 1105 modify their routing tables to redirect network traffic addressed to the wireless client to the home agent wireless access point 115a. This may be done, for example, by associating the home agent 115a with the MAC address of the wireless client 305 and using layer 2 routing to direct data traffic within the subnet. In this example, when a wireless client is newly associated with a tunnel to a home agent in its home subnet, the home agent broadcasts a routing update message to other devices within the subnet to associate the wireless client's MAC address or other identifying information with the home agent.


The updated routing information is used to intercept and redirect network traffic addressed to roaming wireless clients. During predictive roaming, the wireless client 305 believes it still has its original IP address in its home subnet 1105. Thus, example data 510a directed to the wireless client 305 will be addressed to the IP address of wireless client 305. In an embodiment, switch 110 in subnet 1105 receives data 510a addressed to the home IP address of wireless client 305 and uses layer 2 routing to redirect this data 510b to the home agent wireless access point 115a, in accordance with its updated routing tables. In this example, redirected data 510b is addressed to the MAC address of the wireless client 305.


Upon receiving redirected data 510b, home agent wireless access point 115a forwards this data 510b through tunnel 415 to wireless access point 130a. Wireless access point 130a uses layer 2 routing, such as MAC addresses, to direct data 510b to wireless client 305.


Similarly, in a further embodiment, any broadcast data traffic within subnet 1105 is also received by home agent wireless access point 115a and forwarded via tunnel 415 to the wireless client 305.


In the above examples of predictive roaming, neighboring wireless access points receive roaming information about nearby wireless clients before potentially connecting with the wireless clients. However, in some cases, a wireless access point may receive a connection request from a wireless client without previously receiving any associated roaming information. For example, a wireless device may originally connect with a wireless network in a first subnet, and then enter a low-power, inactive, or suspended operation mode. A user may then move the wireless device in its inactive state to the physical coverage area of a different, non-adjacent wireless access point in a different subnet.


In a specific implementation, a nomadic roaming mode allowing wireless clients to keep their IP address when moving to a different subnet, even if wireless access points do not have predictive roaming information for these wireless clients. FIG. 6 illustrates an example 600 of nomadic roaming. In example 600, the wireless network 100 described above has been expanded to include subnet 3605. Subnet 3605 includes a switch 607 and wireless access points 610a and 610b. In this example 600, the physical coverage areas 612 of wireless access points 610a and 610b do not overlap with the physical coverage areas of any of the wireless access points in subnets 1105 or 2120. In subnet 3605, wireless access point 610b acts as a home agent.


For example 600, it is assumed that wireless client 305 was previously connected with wireless access point 115b, as shown in FIG. 3. For example 600, wireless client 305 is moved to the physical coverage area 612a associated with wireless access point 610a. Wireless client 305 forms a network connection with wireless access point 610a. However, wireless access point 610a does not include any predictive roaming information associated with wireless client 305, for example because wireless client 305 was in an inactive state during its movement to subnet 3605 or because of a gap in the physical coverage of the wireless network 100 between subnets 1105 and 3605.


In an embodiment, wireless access point 610a compares the MAC address or other identifying information of wireless client 305 with its stored predictive roaming information, if any. If the wireless access point 610a does not have any predictive roaming information for the wireless client 305, wireless access point 610a attempts to locate the home subnet of the wireless client 305. In an embodiment, wireless access point 610a provides its home agent, in this example wireless access point 610b with the MAC address of the wireless client 305.


As described above, home agents know the address of home agents in other subnets. Home agent 610b sends a broadcast query message including wireless client's 305 MAC address to at least one of the home agents in each of the subnets 1105 and 2120. Each home agent receiving this broadcast query message will determine if this MAC address was last associated with itself, either directly or through another wireless access point in the same subnet. If a home agent does not have a cache of associated wireless clients, it will rebroadcast this query message to any other wireless access points in the subnet, asking these wireless access points if they were previously connected with a wireless client having this MAC address.


In response to this query message, at least one wireless access point will respond indicating that it was previously connected with the wireless client 305. In example 600, wireless access point 115b responds to this query message. This response is forwarded back to wireless access point's 115b home agent, wireless access point 115a, which in turn forwards the response to home agent 610b and back to wireless access point 610a. Wireless access point 610a will use this information to establish a tunnel 620 between itself and a home agent in subnet 1105, the wireless client's 305 home subnet. The establishment and operation of the tunnel 620 is similar to that of tunnel 415 used for predictive roaming discussed above. However, because wireless access point 610a does not have session keys or other security information associated with wireless client 305, wireless access point 610a will have to establish a new session and exchange new security information with wireless client 305. Despite this, wireless client 305 can continue to operate as if it had its original IP address in subnet 1105.


For both predictive and nomadic roaming, a tunnel is used to carry network traffic addressed to the wireless client's original IP address in a home subnet to the wireless client when it is in a different subnet. This allows the wireless client to roam to different network subnets without disrupting network data traffic. However, maintaining tunnels for large numbers of wireless clients may be inefficient. In a further embodiment, if a network connection of a wireless client is idle or inactive for a sufficiently long period of time, the wireless client is sent a message breaking down its old network connection and assigning the wireless client a new IP address in its current network subnet. Because the wireless client's network connection is inactive, this operation does not cause any noticeable disruption in network service. At this point, the tunnel may be discarded if not needed by other wireless clients.



FIG. 7 illustrates an example method 700 implementing predictive and nomadic roaming in a wireless access point or other network device. Step 705 selects one or more home agents within the same subnet as the wireless access point. As discussed above, a wireless access point may act as its own home agent. Multiple home agents may be used in a subnet for load balancing and reliability purposes.


Step 710 determines if any new neighboring wireless access points are detected by the wireless access point. As discussed above, in a specific implementation, wireless access points detect neighboring wireless access points using their beacon radio signals. If any new neighbor wireless access points are detected, step 715 updates the neighbor table of the wireless access point to include the new neighboring wireless access point or points. Otherwise, method 700 proceeds to step 730. Following step 715, step 720 determines if the neighboring wireless access point is in a different subnet than the wireless access point. If so, step 725 sends its home agent information to the new neighboring wireless access points. Following either steps 720 or 725, method 700 proceeds to step 730.


Step 730 determines if the wireless access point has received home agent information from any neighboring wireless access points in different network subnets. If so, step 735 forwards this home agent information to its home agent or agents, so that the home agents in the wireless access point's subnet are aware of all of the home agents in other subnets. Following either step 730 or 735, method 700 proceeds to step 740.


Step 740 determines if the wireless access point has received any predictive roaming information from other wireless access points. In an embodiment, the wireless access point may receive predictive roaming information from other wireless access points in the same subnet or a different subnet. Step 745 caches any received predictive roaming information. Following either step 740 or 745, method 700 proceeds to step 750.


Step 750 determines if a new wireless client is connecting with the wireless access point. If so, step 755 determines if the wireless client matches any of the cached predictive roaming information previously received and cached by the wireless access point. If so, step 760 determines if the wireless client has been assigned an IP address in the same network subnet as the wireless access point. If so, step 770 connects with the wireless client using standard layer 2 intra-subnet roaming techniques.


Returning to step 760, if the wireless client matches the wireless access point's cached predictive roaming information and the wireless client has an assigned IP address in a different subnet than the wireless access point, then predictive roaming as described is used to maintain the network connection with the wireless client. Step 775 establishes a tunnel, such as a GRE tunnel, between the wireless access point and a home agent in the wireless client's home subnet, if a tunnel does not already exist. If a tunnel between the wireless access point and a home agent in the wireless client's subnet already exists, an embodiment of method 700 skips step 775 and the wireless access point uses the previously created tunnel.


In an embodiment, the wireless access point in step 775 contacts its home agent to determine an IP address for one or more home agents in the home subnet of the new wireless client. In a further embodiment, the wireless access point or home agent selects one or more home agents in the wireless client's home subnet using load balancing selection techniques, such as a simple round-robin selection technique. More complicated load balancing techniques may select the home agent for tunneling using load information such as network traffic; the number of tunnels associated with a home agent; CPU, memory, network bandwidth, or other computing resource usage; and network quality of service metrics.


Following step 775, step 780 connects the wireless client with the tunnel using layer 2 routing techniques, as described above with reference to FIG. 5, so that outbound data traffic from the wireless client is directed from the wireless access point via the tunnel to the wireless client's home subnet and then to its intended destination. Similarly, inbound data traffic to the wireless client is intercepted by the home agent associated with the tunnel in the wireless client's home subnet and transferred via the tunnel to the wireless access point. The wireless access point then directs the data traffic to the wireless client using layer 2 routing.


Returning to step 755, if the wireless client connecting with the wireless access point does not match the wireless access point's cached predictive roaming information, then an embodiment of method 700 uses the nomadic roaming techniques described above to connect with the wireless client. Accordingly, the wireless access point in step 765 contacts its home agent and requests that it locates the home subnet of the wireless client. The home agent sends a query message including the MAC address and/or other identifying information of the wireless to home agents in other subnets to locate the home subnet of the wireless client, as described above.


Upon receiving a reply message identifying the home subnet of the wireless client, an embodiment of the wireless access point proceeds from step 765 to step 760. Method 700 then proceeds as described above.


Following either step 770 or 780, an embodiment of method 700 proceeds to step 785 and forwards predictive roaming information about the wireless client to neighboring wireless access points on its neighbor list. This information may be used by neighboring wireless access points if the wireless client later roams to any of the neighboring wireless access points in the same subnet or a different subnet.


Following step 785, method 700 proceeds to step 790. Step 790 determines if any of the roaming wireless clients currently connected with the wireless access point have idle network connections. If so, step 795 assigns a new IP address within the current subnet to the wireless client. If there are no more roaming wireless clients using a tunnel associated with the wireless access point, then an embodiment of step 795 may remove the tunnel to conserve network resources.


Following either step 790 or 795, method 700 may return to step 710 to repeat a portion of method 700 for additional iterations.



FIG. 8 illustrates a computer system suitable for implementing techniques described in this paper. FIG. 8 is a block diagram of a computer system 2000, such as a personal computer or other digital device, suitable for implementing techniques described in this paper. The computer system 2000 may or may not include dedicated networking devices, such as wireless access points, network switches, hubs, routers, hardware firewalls, network traffic optimizers and accelerators, network attached storage devices, and combinations thereof.


Computer system 2000 includes a central processing unit (CPU) 2005 for running software applications and optionally an operating system. CPU 2005 may be comprised of one or more processing cores. Memory 2010 stores applications and data for use by the CPU 2005. Examples of memory 2010 include dynamic and static random access memory. Storage 2015 provides non-volatile storage for applications and data and may include fixed or removable hard disk drives, flash memory devices, ROM memory, and CD-ROM, DVD-ROM, Blu-ray, HD-DVD, or other magnetic, optical, or solid state storage devices.


Optional user input devices 2020 communicate user inputs from one or more users to the computer system 2000, examples of which may include keyboards, mice, joysticks, digitizer tablets, touch pads, touch screens, still or video cameras, and/or microphones. In an embodiment, user input devices may be omitted and computer system 2000 may present a user interface to a user over a network, for example using a web page or network management protocol and network management software applications.


Computer system 2000 includes one or more network interfaces 2025 that allow computer system 2000 to communicate with other computer systems via an electronic communications network, and may include wired or wireless communication over local area networks and wide area networks such as the Internet. Computer system 2000 may support a variety of networking protocols at one or more levels of abstraction. For example, computer system may support networking protocols at one or more layers of the seven layer OSI network model. An embodiment of network interface 2025 includes one or more wireless network interfaces adapted to communicate with wireless clients and with other wireless networking devices using radio waves, for example using the 802.11 family of protocols, such as 802.11a, 802.11b, 802.11g, and 802.11n.


An embodiment of the computer system 2000 may also include a wired networking interface, such as one or more Ethernet connections to communicate with other networking devices via local or wide-area networks. In a further embodiment, computer system 2000 may be capable of receiving some or all of its required electrical power via the network interface 2025, for example using a wired networking interface power over Ethernet system.


The components of computer system 2000, including CPU 2005, memory 2010, data storage 2015, user input devices 2020, and network interface 2025 are connected via one or more data buses 2060. Additionally, some or all of the components of computer system 2000, including CPU 2005, memory 2010, data storage 2015, user input devices 2020, and network interface 2025 may be integrated together into one or more integrated circuits or integrated circuit packages. Furthermore, some or all of the components of computer system 2000 may be implemented as application specific integrated circuits (ASICS) and/or programmable logic.


The specification and drawings describe examples. Combinations, sub-combinations, deletions, variations, and applications of the above disclosed techniques can be considered within the spirit and scope of this paper. Combinations of blocks, additions of new blocks, re-arrangement of blocks, and the like are contemplated in various implementations of the techniques described in this paper. Various modifications and changes can be made without departing from the broader spirit and scope of the invention as set forth in the claims.

Claims
  • 1. A method comprising: receiving at a first wireless access point predictive roaming information indicating a home subnet uniquely associated with a first wireless client from the home subnet, when the first wireless client is connected with a second wireless access point of the home subnet;detecting at the first wireless access point a new wireless client attempting to access network services through the first wireless access point;determining if the new wireless client is the first wireless client using the predictive roaming information;if it is determined the new wireless client is the first wireless client using the predictive roaming information: determining if the first wireless access point is in the home subnet using the predictive roaming information;if it is determined the first wireless access point is out of the home subnet: establishing a tunnel from the first wireless access point to a home agent in the home subnet;using the tunnel to the home agent in the home subnet to provide the first wireless client access to the network services through the first wireless access point.
  • 2. The method of claim 1, wherein the tunnel is established as part of layer 2 routing.
  • 3. The method of claim 1, further comprising: if it is determined the new wireless client is not the first wireless client: determining if a connection of the new wireless client to the first wireless access point is idle;if it is determined the connection of the new wireless client to the first wireless access point is idle, assigning a new IP address to the new wireless client in a subnet associated with the first wireless access point.
  • 4. The method of claim 1, further comprising: if it is determined the new wireless client is not the first wireless client: determining if a connection of the new wireless client to the first wireless access point is idle;if it is determined the connection of the new wireless client to the first wireless access point is active: detecting a neighboring wireless access point to the first wireless access point;sending home agent information indicating an association of the new wireless client to a home agent of a subnet associated with the first wireless access point to the neighboring wireless access point.
  • 5. The method of claim 1, further comprising: if it is determined the new wireless client is not the first wireless client: determining if a connection of the new wireless client to the first wireless access point is idle;if it is determined the connection of the new wireless client to the first wireless access point is active: detecting a neighboring wireless access point to the first wireless access point;sending home agent information indicating an association of the new wireless client to a home agent of a subnet associated with the first wireless access point to the neighboring wireless access point, wherein the neighboring wireless access point is associated with the subnet associated with the first wireless access point.
  • 6. The method of claim 1, further comprising: if it is determined the new wireless client is not the first wireless client: determining if a connection of the new wireless client to the first wireless access point is idle;if it is determined the connection of the new wireless client to the first wireless access point is active: detecting a neighboring wireless access point to the first wireless access point;sending home agent information indicating an association of the new wireless client to a home agent of a subnet associated with the first wireless access point to the neighboring wireless access point, wherein the neighboring wireless access point is associated with a different subnet from the subnet associated with the first wireless access point.
  • 7. The method of claim 1, wherein the predictive roaming information includes connection information used to provide the first wireless client access to the network services.
  • 8. The method of claim 1, wherein the predictive roaming information is cached at the first wireless access point.
  • 9. The method of claim 1, further comprising: receiving at the first wireless access point home agent information of the home agent in the home subnet uniquely associated with the first wireless client;using the home agent information to establish the tunnel to the home agent in the home subnet.
  • 10. The method of claim 1, wherein the tunnel to the home agent in the home subnet uniquely associated with the first wireless client is established through a home agent of a subnet associated with the first wireless access point.
  • 11. A system comprising: one or more processors;memory storing applications, when executed by the one or more processors, configured to cause the one or more processors to:receive at a first wireless access point predictive roaming information indicating a home subnet uniquely associated with a first wireless client from the home subnet, when the first wireless client is connected with a second wireless access point of the home subnet;detect at the first wireless access point a new wireless client attempting to access network services through the first wireless access point;determine if the new wireless client is the first wireless client using the predictive roaming information;determine if the first wireless access point is in the home subnet using the predictive roaming information if it is determined the new wireless client is the first wireless client using the predictive roaming information;establish a tunnel from the first wireless access point to a home agent in the home subnet if it is determined the first wireless access point is out of the home subnet;use the tunnel to the home agent in the home subnet to provide the first wireless client access to the network services through the first wireless access point.
  • 12. The system of claim 11, wherein the tunnel is established as part of layer 2 routing.
  • 13. The system of claim 11, wherein the applications are further configured to cause the one or more processors to: determine if a connection of the new wireless client to the first wireless access point is idle if it is determined the new wireless client is not the first wireless client;assign a new IP address to the new wireless client in a subnet associated with the first wireless access point if it is determined the connection of the new wireless client to the first wireless access point is idle.
  • 14. The system of claim 11, wherein the applications are further configured to cause the one or more processors to: determine if a connection of the new wireless client to the first wireless access point is idle if it is determined the new wireless client is not the first wireless client;detect a neighboring wireless access point to the first wireless access point if it is determined the connection of the new wireless client to the first wireless access point is active;send home agent information indicating an association of the new wireless client to a home agent of a subnet associated with the first wireless access point to the neighboring wireless access point if it is determined the connection of the new wireless client to the first wireless access point is active.
  • 15. The system of claim 11, wherein the applications are further configured to cause the one or more processors to: determine if a connection of the new wireless client to the first wireless access point is idle if it is determined the new wireless client is not the first wireless client;detect a neighboring wireless access point to the first wireless access point if it is determined the connection of the new wireless client to the first wireless access point is active;send home agent information indicating an association of the new wireless client to a home agent of a subnet associated with the first wireless access point to the neighboring wireless access point, wherein the neighboring wireless access point is associated with the subnet associated with the first wireless access point if it is determined the connection of the new wireless client to the first wireless access point is active.
  • 16. The system of claim 11, wherein the applications are further configured to cause the one or more processors to: determine if a connection of the new wireless client to the first wireless access point is idle if it is determined the new wireless client is not the first wireless client;detect a neighboring wireless access point to the first wireless access point, if it is determined the connection of the new wireless client to the first wireless access point is active;send home agent information indicating an association of the new wireless client to a home agent of a subnet associated with the first wireless access point to the neighboring wireless access point, wherein the neighboring wireless access point is associated with a different subnet from the subnet associated with the first wireless access point if it is determined the connection of the new wireless client to the first wireless access point is active.
  • 17. The system of claim 11, wherein the predictive roaming information includes connection information used to provide the first wireless client access to the network services.
  • 18. The system of claim 11, wherein the applications are further configured to cause the one or more processors to cache the predictive roaming information at the first wireless access point.
  • 19. The system of claim 11, wherein the applications are further configured to cause the one or more processors to: receive at the first wireless access point home agent information of the home agent in the home subnet uniquely associated with the first wireless client;use the home agent information to establish the tunnel to the home agent in the home subnet.
  • 20. The system of claim 11, wherein the tunnel to the home agent in the home subnet uniquely associated with the first wireless client is established through a home agent of a subnet associated with the first wireless access point.
CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application of U.S. patent application Ser. No. 14/686,665, filed Apr. 14, 2015, which is a continuation application of U.S. patent application Ser. No. 14/139,819, filed Dec. 23, 2013, now U.S. Pat. No. 9,025,566, which is a continuation application of U.S. patent application Ser. No. 13/452,437, filed Apr. 20, 2012, now U.S. Pat. No. 8,614,989, which is a continuation application of U.S. patent application Ser. No. 12/120,338, filed May 14, 2008, now U.S. Pat. No. 8,218,502 which are incorporated herein by reference.

US Referenced Citations (252)
Number Name Date Kind
5471671 Wang et al. Nov 1995 A
5697059 Carney Dec 1997 A
5726984 Kubler et al. Mar 1998 A
5956643 Benveniste Sep 1999 A
6061799 Eldridge et al. May 2000 A
6112092 Benveniste Aug 2000 A
6154655 Borst et al. Nov 2000 A
6201792 Lahat Mar 2001 B1
6233222 Wallentin May 2001 B1
6314294 Benveniste Nov 2001 B1
6473413 Chiou Oct 2002 B1
6496699 Benveniste Dec 2002 B2
6519461 Andersson et al. Feb 2003 B1
6628623 Noy Sep 2003 B1
6628938 Rachabathuni et al. Sep 2003 B1
6636498 Leung Oct 2003 B1
6775549 Benveniste Aug 2004 B2
6865393 Baum et al. Mar 2005 B1
6957067 Iyer et al. Oct 2005 B1
7002943 Bhagwat et al. Feb 2006 B2
7057566 Theobold Jun 2006 B2
7085224 Oran Aug 2006 B1
7085241 O'Neill et al. Aug 2006 B1
7130629 Leung Oct 2006 B1
7154874 Bhagwat et al. Dec 2006 B2
7164667 Rayment et al. Jan 2007 B2
7174170 Steer et al. Feb 2007 B2
7177646 O'Neill et al. Feb 2007 B2
7181530 Halasz et al. Feb 2007 B1
7216365 Bhagwat et al. May 2007 B2
7224697 Banerjea et al. May 2007 B2
7251238 Joshi et al. Jul 2007 B2
7336670 Calhoun Feb 2008 B1
7339914 Bhagwat et al. Mar 2008 B2
7346338 Calhoun et al. Mar 2008 B1
7366894 Kalimuthu et al. Apr 2008 B1
7369489 Bhattacharya May 2008 B1
7370362 Olson et al. May 2008 B2
7440434 Chaskar et al. Oct 2008 B2
7512379 Nguyen Mar 2009 B2
7536723 Bhagwat et al. May 2009 B1
7562384 Huang Jul 2009 B1
7593356 Friday et al. Sep 2009 B1
7656822 AbdelAziz et al. Feb 2010 B1
7706789 Qi et al. Apr 2010 B2
7716370 Devarapalli May 2010 B1
7751393 Chaskar et al. Jul 2010 B2
7768952 Lee Aug 2010 B2
7793104 Zheng et al. Sep 2010 B2
7804808 Bhagwat et al. Sep 2010 B2
7843907 Abou-Emara et al. Nov 2010 B1
7844057 Meier et al. Nov 2010 B2
7856209 Rawat Dec 2010 B1
7921185 Chawla et al. Apr 2011 B2
7949342 Cuffaro et al. May 2011 B2
7961725 Nagarajan et al. Jun 2011 B2
7970894 Patwardhan Jun 2011 B1
8000308 Dietrich et al. Aug 2011 B2
8069483 Matlock Nov 2011 B1
8219688 Wang Jul 2012 B2
8249606 Neophytou et al. Aug 2012 B1
8493918 Karaoguz et al. Jul 2013 B2
8789191 Bhagwat et al. Jul 2014 B2
8824448 Narayana et al. Sep 2014 B1
8948046 Kang et al. Feb 2015 B2
8953453 Xiao Feb 2015 B1
9003527 Bhagwat et al. Apr 2015 B2
20010006508 Pankaj et al. Jul 2001 A1
20020012320 Ogier et al. Jan 2002 A1
20020021689 Robbins et al. Feb 2002 A1
20020041566 Yang Apr 2002 A1
20020071422 Amicangioli Jun 2002 A1
20020091813 Lamberton et al. Jul 2002 A1
20020114303 Crosbie Aug 2002 A1
20020116463 Hart Aug 2002 A1
20020128984 Mehta et al. Sep 2002 A1
20030005100 Barnard et al. Jan 2003 A1
20030039212 Lloyd et al. Feb 2003 A1
20030084104 Salem May 2003 A1
20030087629 Juitt May 2003 A1
20030104814 Gwon et al. Jun 2003 A1
20030129988 Lee et al. Jul 2003 A1
20030145091 Peng et al. Jul 2003 A1
20030179742 Ogier et al. Sep 2003 A1
20030198207 Lee Oct 2003 A1
20040003285 Whelan et al. Jan 2004 A1
20040013118 Borella Jan 2004 A1
20040022222 Clisham Feb 2004 A1
20040054774 Barber et al. Mar 2004 A1
20040064467 Kola et al. Apr 2004 A1
20040077341 Chandranmenon et al. Apr 2004 A1
20040103282 Meier et al. May 2004 A1
20040109466 Van Ackere et al. Jun 2004 A1
20040162037 Shpak Aug 2004 A1
20040185876 Groenendaal et al. Sep 2004 A1
20040192312 Li et al. Sep 2004 A1
20040196977 Johnson et al. Oct 2004 A1
20040236939 Watanabe et al. Nov 2004 A1
20040255028 Chu et al. Dec 2004 A1
20050053003 Cain et al. Mar 2005 A1
20050074015 Chari et al. Apr 2005 A1
20050085235 Park Apr 2005 A1
20050099983 Nakamura et al. May 2005 A1
20050122946 Won Jun 2005 A1
20050154774 Giaffreda et al. Jul 2005 A1
20050207417 Ogawa et al. Sep 2005 A1
20050259682 Yosef et al. Nov 2005 A1
20050262266 Wiberg et al. Nov 2005 A1
20050265288 Liu et al. Dec 2005 A1
20050266848 Kim Dec 2005 A1
20060010250 Eisl Jan 2006 A1
20060013179 Yamane Jan 2006 A1
20060026289 Lyndersay et al. Feb 2006 A1
20060062250 Payne, III Mar 2006 A1
20060107050 Shih May 2006 A1
20060117018 Christiansen et al. Jun 2006 A1
20060140123 Conner et al. Jun 2006 A1
20060146748 Ng et al. Jul 2006 A1
20060146846 Yarvis et al. Jul 2006 A1
20060165015 Melick et al. Jul 2006 A1
20060187949 Seshan et al. Aug 2006 A1
20060221920 Gopalakrishnan et al. Oct 2006 A1
20060233128 Sood et al. Oct 2006 A1
20060234701 Wang Oct 2006 A1
20060245442 Srikrishna et al. Nov 2006 A1
20060251256 Asokan et al. Nov 2006 A1
20060268802 Faccin Nov 2006 A1
20060294246 Stieglitz et al. Dec 2006 A1
20070004394 Chu et al. Jan 2007 A1
20070010231 Du Jan 2007 A1
20070025274 Rahman et al. Feb 2007 A1
20070025298 Jung Feb 2007 A1
20070049323 Wang et al. Mar 2007 A1
20070077937 Ramakrishnan et al. Apr 2007 A1
20070078663 Grace Apr 2007 A1
20070082656 Stieglitz et al. Apr 2007 A1
20070087756 Hoffberg Apr 2007 A1
20070091859 Sethi et al. Apr 2007 A1
20070115847 Strutt et al. May 2007 A1
20070116011 Lim et al. May 2007 A1
20070121947 Sood et al. May 2007 A1
20070133407 Choi et al. Jun 2007 A1
20070140191 Kojima Jun 2007 A1
20070150720 Oh et al. Jun 2007 A1
20070153697 Kwan Jul 2007 A1
20070153741 Blanchette Jul 2007 A1
20070156804 Mo Jul 2007 A1
20070160017 Meier et al. Jul 2007 A1
20070171885 Bhagwat et al. Jul 2007 A1
20070192862 Vermeulen et al. Aug 2007 A1
20070195761 Tatar et al. Aug 2007 A1
20070247303 Payton Oct 2007 A1
20070248014 Xie Oct 2007 A1
20070249324 Jou et al. Oct 2007 A1
20070263532 Mirtorabi et al. Nov 2007 A1
20070280481 Eastlake et al. Dec 2007 A1
20070288997 Meier et al. Dec 2007 A1
20080002642 Borkar et al. Jan 2008 A1
20080022392 Karpati et al. Jan 2008 A1
20080037552 Dos Remedios et al. Feb 2008 A1
20080080369 Sumioka Apr 2008 A1
20080080377 Sasaki et al. Apr 2008 A1
20080090575 Barak et al. Apr 2008 A1
20080095094 Innami Apr 2008 A1
20080095163 Chen et al. Apr 2008 A1
20080107027 Allan et al. May 2008 A1
20080109879 Bhagwat et al. May 2008 A1
20080130495 Dos Remedios et al. Jun 2008 A1
20080146240 Trudeau Jun 2008 A1
20080151751 Ponnuswamy et al. Jun 2008 A1
20080159128 Shaffer Jul 2008 A1
20080159135 Caram Jul 2008 A1
20080170527 Lundsgaard et al. Jul 2008 A1
20080186932 Do et al. Aug 2008 A1
20080194271 Bedekar Aug 2008 A1
20080207215 Chu et al. Aug 2008 A1
20080209186 Boden Aug 2008 A1
20080212562 Bedekar et al. Sep 2008 A1
20080219286 Ji et al. Sep 2008 A1
20080225857 Lange Sep 2008 A1
20080229095 Kalimuthu et al. Sep 2008 A1
20080240128 Elrod Oct 2008 A1
20080253370 Cremin et al. Oct 2008 A1
20080273520 Kim et al. Nov 2008 A1
20080279161 Stirbu et al. Nov 2008 A1
20090019521 Vasudevan Jan 2009 A1
20090028052 Strater et al. Jan 2009 A1
20090040989 da Costa et al. Feb 2009 A1
20090043901 Mizikovsky et al. Feb 2009 A1
20090082025 Song Mar 2009 A1
20090088152 Orlassino Apr 2009 A1
20090097436 Vasudevan et al. Apr 2009 A1
20090111468 Burgess et al. Apr 2009 A1
20090113018 Thomson et al. Apr 2009 A1
20090141692 Kasslin et al. Jun 2009 A1
20090144740 Gao Jun 2009 A1
20090168645 Tester et al. Jul 2009 A1
20090172151 Davis Jul 2009 A1
20090197597 Kotecha Aug 2009 A1
20090207806 Makela Aug 2009 A1
20090239531 Andreasen et al. Sep 2009 A1
20090240789 Dandabany Sep 2009 A1
20090247170 Balasubramanian et al. Oct 2009 A1
20090303883 Kucharczyk et al. Dec 2009 A1
20090310557 Shinozaki Dec 2009 A1
20100020753 Fulknier Jan 2010 A1
20100046368 Kaempfer et al. Feb 2010 A1
20100057930 DeHaan Mar 2010 A1
20100061234 Pai et al. Mar 2010 A1
20100067379 Zhao et al. Mar 2010 A1
20100112540 Gross et al. May 2010 A1
20100115278 Shen et al. May 2010 A1
20100115576 Hale et al. May 2010 A1
20100132040 Bhagwat et al. May 2010 A1
20100195585 Horn Aug 2010 A1
20100208614 Harmatos Aug 2010 A1
20100228843 Ok et al. Sep 2010 A1
20100240313 Kawai Sep 2010 A1
20100254316 Sendrowicz Oct 2010 A1
20100260091 Seok Oct 2010 A1
20100290397 Narayana et al. Nov 2010 A1
20100304738 Lim et al. Dec 2010 A1
20100311420 Reza et al. Dec 2010 A1
20100322217 Jin et al. Dec 2010 A1
20100325720 Etchegoyen Dec 2010 A1
20110004913 Nagarajan et al. Jan 2011 A1
20110040867 Kalbag Feb 2011 A1
20110051677 Jetcheva et al. Mar 2011 A1
20110055326 Michaelis et al. Mar 2011 A1
20110055928 Brindza Mar 2011 A1
20110058524 Hart et al. Mar 2011 A1
20110064065 Nakajima et al. Mar 2011 A1
20110085464 Nordmark et al. Apr 2011 A1
20110182225 Song et al. Jul 2011 A1
20110185231 Balestrieri et al. Jul 2011 A1
20110258641 Armstrong et al. Oct 2011 A1
20110292897 Wu et al. Dec 2011 A1
20120014386 Xiong et al. Jan 2012 A1
20120290650 Montuno et al. Nov 2012 A1
20130003729 Raman et al. Jan 2013 A1
20130003739 Raman et al. Jan 2013 A1
20130003747 Raman et al. Jan 2013 A1
20130028158 Lee et al. Jan 2013 A1
20130059570 Hara et al. Mar 2013 A1
20130086403 Jenne et al. Apr 2013 A1
20130103833 Ringland et al. Apr 2013 A1
20130227306 Santos et al. Aug 2013 A1
20130230020 Backes Sep 2013 A1
20130250811 Vasseur et al. Sep 2013 A1
20140269327 Fulknier et al. Sep 2014 A1
20140298467 Bhagwat et al. Oct 2014 A1
20150120864 Unnimadhavan et al. Apr 2015 A1
Foreign Referenced Citations (10)
Number Date Country
1642143 Jul 2005 CN
0940999 Sep 1999 EP
1732276 Dec 2006 EP
1771026 Apr 2007 EP
1490773 Jan 2013 EP
0059251 Oct 2000 WO
0179992 Oct 2001 WO
2004042971 May 2004 WO
2006129287 Dec 2006 WO
2009141016 Nov 2009 WO
Non-Patent Literature Citations (14)
Entry
Chirumamilla, Mohan K. et al., “Agent Based Intrustion Detection and Response System for Wireless LANs,” CSE Conference and Workshop Papers, Paper 64, Jan. 1, 2003.
Clausen, T., et al., “Optimized Link State Routing Protocol (OLSR),” Network Working Group, pp. 1-71, Oct. 2003.
Craiger, J. Philip, “802.11, 802.1x, and Wireless Security,” SANS Institute InfoSec Reading Room, Jun. 23, 2002.
Finlayson, Ross et al., “A Reverse Address Resolution Protocol,” Nework Working Group, Request for Comments: 903 (RFC 903), Jun. 1984.
He, Changhua et al., “Analysis of the 802.11i 4-Way Handshake,” Proceedings of the 3rd ACM Workshop on Wireless Security, pp. 43-50, Oct. 2004.
Lee, Jae Woo et al, “z2z: Discovering Zeroconf Services Beyond Local Link,” 2007 IEEE Globecom Workshops, pp. 1-7, Nov. 26, 2007.
Perkins, C., et al., “Ad hoc On-Demand Distance Vector (AODV) Routing,” Network Working Group, pp. 1-35, Oct. 2003.
Wu, Haitao et al., “Layer 2.5 SoftMAC: End-System Based Media Streaming Support on Home Networks,” IEEE Global Telecommunications Conference (Globecom '05), vol. 1, pp. 235-239, Nov. 2005.
European Patent Application No. 11823931.8, Search Report dated Aug. 29, 2016.
European Patent Application No. 12879114.2, Search Report dated Jan. 21, 2016.
International Application No. PCT/US2008/061674, International Search Report and Written Opinion dated Oct. 14, 2008.
International Application No. PCT/US2011/047591, International Search Report and Written Opinion dated Dec. 19, 2011.
International Application No. PCT/US2012/059093, International Search Report and Written Opinion dated Jan. 4, 2013.
IEEE Computer Society, “IEEE Std 802.11i—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications—Amendment 6: Medium Access Control (MAC) Security Enhancements,” Section H.4.1, pp. 165-166, Jul. 23, 2014.
Related Publications (1)
Number Date Country
20170134991 A1 May 2017 US
Continuations (4)
Number Date Country
Parent 14686665 Apr 2015 US
Child 15412949 US
Parent 14139819 Dec 2013 US
Child 14686665 US
Parent 13452437 Apr 2012 US
Child 14139819 US
Parent 12120338 May 2008 US
Child 13452437 US