Patent Application
20070091859
The implementation of comprehensive wireless networks has increased the productivity, efficiency and mobility of workers. Moreover, organizations can easily provide wireless coverage where network connections were not previously available without much effort. With a wireless-enabled mobile unit (“MU”), wireless networks based on, for example, the IEEE 802.11x standard, have allowed people to access communications networks such as the internet at work, school, etc, without the hassles of carrying cables and finding a network drop location. These wireless networks also allow the user to move locations and remain connected to the network. This allows the user to preserve any work that the user had be performing and also to keep any connections and/or programs from the network running.
Although wireless networks allow users a level of mobility that was not previously available, the ability to roam throughout areas where a wireless network is available while preserving the network connection is not entirely seamless. Some wireless networks may have been designed into smaller “pieces” called subnets. This type of network may be implemented for reasons of network management, subnet-specific service, etc. When a MU is trying to obtain a network connection wirelessly, it finds a wireless access point (“AP”) servicing its area. It next sends an association request packet, and after the AP has authenticated the user (e.g. user name, password, etc) and may run some further management algorithms, it assigns the MU an internet protocol (“IP”) address. This may be done by the network administrator, or by a dynamic host configuration protocol (“DHCP”) server. In the situation that a DHCP server is used to allocate IP addresses to the MUs, each AP may have a subnet of IP addresses from which to choose and give to a MU. However, when a user of a MU is roaming through different areas of a wireless network, it may become necessary to associate with a different AP. This situation may arise if the new location of the MU is out of the range of the original AP. In this situation, if the new AP has a different subnet than the original AP, then it will be necessary for the MU to re-associate with the new AP, and have the DHCP allocate a new IP address. This will cause time to be wasted in obtaining a new IP address, and may also cause any work that the user of the MU may have been performing on the network, or any connections to network-vital programs to be lost, thus having an adverse effect on efficiency and productivity.
The present invention relates to a method and system for association of mobile units (“MU”) with an access point (“AP”). Each AP transmits a beacon signal within a corresponding coverage area, each beacon signal including a subnet of Internet Protocol (“IP) addresses being served by the AP transmitting the beacon signal. The MU associates with a first one of the APs and obtaining an IP address from the subnet served by the first AP. When the MU leaves the coverage area of the first AP, the MU receives bacon signals from other ones of the APs and associates with a second AP based on the second AP serving the subnet served by the first AP.
The present invention may be further understood with reference to the following description and the appended drawings. The present invention provides a system and a method for re-associating wireless-enabled mobile units (“MUs”) to wireless access points (“APs”) based on the subnets that the APs are serving. Although the present invention will be described with reference to a IEEE 802.11x wireless network with dynamic host configuration protocol (“DHCP”) servers for allocating internet protocol (“IP”) addresses, it will be understood by those of skill in the art that the present invention may be used with any wireless network that requires a dynamic allocation of addresses to its MUs. Moreover, these addresses are not limited to IP addresses, but may be any addresses which require dynamic allocation.
In addition, the wired portion of the network may be connected to communications network 90, such as an organization's intranet, the Internet, etc. The communications network 90 and associated connection may include infrastructure such as routers, switches, servers, gateways, firewalls, etc. Thus, the MU 10, via the APs 50-80, may be connected to the communications network 90.
As shown in
While the MU 10 remains within the coverage area of the AP 50 with which it has initially associated, the MU 10 will be free to roam as far as the coverage area of the AP 50. There should be no disruptions in service from having to re-associate with a different AP since the MU 10 would be serviced by the AP 50 throughout the entire coverage area of the AP 50. However, a problem may arise if the user of the MU 10 needed to move out of the coverage area of the AP 50. As seen in
The exemplary embodiments of the present invention cure the loss of productivity of the MU having to interact with the corresponding DHCP server each time it needs to re-associate with a new AP. As seen in
As the MU 10 is attempting to re-associate with a new (depending on the respective coverage areas) AP 60, 70 or 80, it may receive each AP's respective beacon containing the data referring to the subnets that each AP is servicing. The MU 10 would then be able to choose to associate with the AP that was servicing the same subnet as the AP 50. This would allow the MU 10 to maintain the IP address that it had received from the AP 50, but associate with the new AP.
In one example, the AP 50 is servicing subnet A, the AP 60 is servicing subnet B, the AP 70 is servicing subnet A, and the AP 80 is servicing subnet B. As the MU 10 leaves the coverage area of the AP 50, and enters a location within the coverage area of the APs 60, and 70, the MU 10 may receive the beacon packets of each of the APs 60 and 70 and determine that the AP 70 is servicing the same subnet as the AP 50. The MU 10 would then disregard the AP 60 and associate with the AP 70. This would allow the MU 10 to continue to use the IP address that had been assigned by the DHCP server 55 of the AP 50. This removes the requirement of the MU 10 to interact with the DHCP server 75 of the AP 70 to obtain a new IP address.
This allows the user of the MU 10 to preserve network critical applications (e.g. instant massaging, conferencing, etc) and work being done on the network without requiring a new connection, thus saving time and maintaining productivity and efficiency. If the WLAN 100 were implemented with Symbol Technology's WS2000™ model wireless access point (or similar APs) which can support multiple subnets, the present invention would allow the MU 10 to request association with whichever subnet it had been previously associated with through the AP 50. This may be done by placing a corresponding subnet ID in the message sent from the MU 10 to the AP with which it desires to associate.
In step 210, an MU (e.g. MU 10) associates with and communicates through an AP (e.g. AP 50). As part of this association, the MU 10 obtains an IP address from the corresponding DHCP server 55 of the AP 50. The MU 10 is then free to roam throughout the coverage area of the AP 50 and not face any problems of having to associate with a new AP. While in the coverage area of the AP 50, the MU 10 may communicate, for example, with the communications network 90 using the assigned IP address.
In step 220, the MU 10 roams to a new location beyond the coverage area serviced by the AP 50. Since the MU 10 has roamed to a location outside the coverage area of the AP 50, the MU 10 will need to associate with an AP other than the AP 50 in order to have a connection to the wireless network. In the exemplary embodiment, the new location to which the MU 10 may have roamed may be serviced by one or more of the APs 60, 70, and 80. The MU 10 may be able to associate with any of the three APs found servicing this location.
In step 230, the MU 10 may receive the beacon packets of each of the APs servicing its new location. These bacon packets will contain information advising the MU 10 as to which subnets each AP is servicing. This may be performed by transmitting the subnet mask that each of the APs are utilizing. Traditionally, beacon packets are transmitted by APs so that MUs will be able to associate with a given AP. These beacon packets contain basic information regarding the wireless network such as the service set identifier (“SSID”), channel, whether it is encrypted, etc. However, in the exemplary embodiment of the present invention, additional data will be included in this beacon packet alerting MUs looking to associate with an AP the subnet that each AP is serving. This may be performed by transmitting the subnet masks available to each AP. Although these beacon packets may be standardized according to the wireless network standard on which the AP is operating (e.g. 802.11a, 802.11b, etc), those skilled in the art will understand that the information regarding the subnet being serviced can be appended onto the beacon packets in a variety of methods.
In step 240, the MU 10 may take the data regarding the subnets from each of the APs received in each of the beacon packets, and compare each of the subnets to the IP address that it had received from the DHCP server 55 of the AP 50. Determining whether or not one of the new APs that is servicing the area is servicing the same subnet as the AP 50 may lead to increased efficiency and productivity. Thus, the MU 10 will assess the data regarding the subnets serviced by the APs 60, 70 and 80, and determine whether or not any of them is servicing the same subnet as the AP 50.
In step 250, if the MU 10 has determined that one of the APs 60, 70 or 80 is servicing the same subnet as the AP 50, then the MU will associate with the selected AP. In one exemplary embodiment, if the AP 50 is servicing subnet A, the AP 60 is servicing subnet B, the AP 70 is servicing subnet C, and the AP 80 is servicing subnet A, then the MU 10 would select the AP 80. The MU 10 would then associate with the AP 80. Selecting the “new” AP based on subnets allows the MU 10 to save time by not having to interact with the DHCP server of the new AP to obtain a new IP address. Since the AP 80 is servicing the same subnet as the AP 50, the MU 10 would be able to maintain the IP address that it had obtained from the AP 50. Moreover, this type of re-association may increase productivity dealing with any network critical applications (i.e. instant messaging, conferencing software, etc) since the IP address would be preserved and a new connection may not need to be formed. This would increase the productivity in possibly eliminating some downtime of such applications.
In step 260, if none of the APs 60, 70 or 80 is servicing the same subnet as the AP 50, the subnets of the APs 60, 70 and 80 become irrelevant. Whichever AP the MU 10 associates with, the MU 10 may have to interact with the corresponding DHCP server and obtain a new IP address. In this given scenario, the MU 10 will associate with one of the APs 60, 70 or 80, and will interact with the corresponding DHCP server to obtain a new IP address.
As described above, the present invention has been described with reference to a DHCP server assigning IP addresses from a subnet to MUs. However, it will be apparent to those of skill in the art that the present invention may be implemented in any dynamic address allocation scheme, whereby different APs may serve overlapping addresses and it would be advantageous to save time and resources by not having to re-allocate a new address to the MU.
It will be apparent to those skilled in the art that various modifications and variations can be made in the structure and the methodology of the present invention, without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
