US20090275328A1 - Methods and apparatus for handling wireless roaming among and across wireless area networks - Google Patents
Methods and apparatus for handling wireless roaming among and across wireless area networks Download PDFInfo
- Publication number
- US20090275328A1 US20090275328A1 US12/263,356 US26335608A US2009275328A1 US 20090275328 A1 US20090275328 A1 US 20090275328A1 US 26335608 A US26335608 A US 26335608A US 2009275328 A1 US2009275328 A1 US 2009275328A1
- Authority
- US
- United States
- Prior art keywords
- switch
- client
- roam
- roaming
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/14—Mobility data transfer between corresponding nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
- H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/087—Mobility data transfer for preserving data network PoA address despite hand-offs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
Definitions
- the present invention relates to the field of wireless networking. More particularly, the present invention relates to a solution for wireless roaming among and across wireless local area networks.
- Wireless network has significantly grown in popularity.
- the IEEE 802.11 standards are currently the most widely used wireless networking standards.
- Wireless network can present unique problems when clients “roam”. Roaming may be defined as switching from one access point to another access point.
- the ability of a mobile client to move freely between various segments of a wireless domain without experiencing any observable service degradation or disruption is called seamless roaming.
- Roaming can occur at various layers. If a client roams between two segments that are part of the same Internet Protocol (IP) subnet, then the roaming is termed layer 2 roaming. If the client roams between segments that have different IP subnets, then the roaming is termed layer 3 roaming.
- IP Internet Protocol
- the Inter Access Point Protocol has been suggested by the IEEE 802.11 committee to address the layer 2 roaming of clients in wireless networks. It runs on wireless access points and uses a combination of Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) to facilitate roaming. However, it fails to support layer 3 roaming as it relies on layer 2 broadcast messages to find other access points.
- TCP Transmission Control Protocol
- UDP User Datagram Protocol
- IPv4 (RFC 3344) standard has been proposed by the Internet Engineering Task Force (IETF) and it attempts to address Layer 3 roaming. Though it is a generic solution, it suffers several limitations. For example, the standard relies on software upgrades to the clients to run some piece of the protocol. This requires that all users upgrade their mobile clients (laptops, mobile phones, etc.) before they can use this standard. Additionally, this standard only addresses the layer 3 roaming aspect of the generic problem.
- Wireless roaming in a computer network may be handled through a solution provided on one or more switches in the network.
- a roam request sent by a switch corresponding to the user's new location may be received by the other switches in the network. If the user is known to any of these switches, then they may execute steps to accommodate the roaming. The tasks performed may vary based on whether the roaming is on layer 2 or layer 3 , whether the switch is a home agent for the client, and/or whether the switch already corresponds to the user's new location.
- FIG. 1 is a diagram illustrating layer 2 roaming on a single WLAN switch in accordance with an embodiment of the present invention.
- FIG. 2 is a diagram illustrating layer 2 roaming between two WLAN switches in accordance with an embodiment of the present invention.
- FIG. 3 is a diagram illustrating layer 3 roaming on a single WLAN switch in accordance with an embodiment of the present invention.
- FIG. 4 is a diagram illustrating layer 3 roaming between two WLAN switches in accordance with an embodiment of the present invention.
- FIG. 5 is a diagram illustrating layer 3 roaming followed by another layer 3 roaming involving 2 WLAN switches in accordance with an embodiment of the present invention.
- FIG. 6 is a diagram illustrating layer 3 roaming to a different WLAN switch followed by another layer 3 roaming back to the original WLAN switch in accordance with an embodiment of the present invention.
- FIG. 7 is a diagram illustrating layer 3 roaming followed by another layer 3 roaming on 3 or more WLAN switches in accordance with an embodiment of the present invention.
- FIG. 8 is a diagram illustrating layer 3 roaming followed by layer 2 roaming involving 2 WLAN switches in accordance with an embodiment of the present invention.
- FIG. 9 is a diagram illustrating layer 3 roaming followed by layer 2 roaming on 3 or more WLAN switches in accordance with an embodiment of the present invention.
- FIG. 10 is a flow diagram illustrating a method for responding to client roaming at a switch in accordance with an embodiment of the present invention.
- FIG. 11 is a flow diagram illustrating a method for handling a roam request from a switch in accordance with an embodiment of the present invention.
- FIG. 12 is a flow diagram illustrating a method for handling a roam reply in a switch in accordance with an embodiment of the present invention.
- FIG. 13 is a block diagram illustrating an apparatus for responding to client roaming at a switch in accordance with an embodiment of the present invention.
- FIG. 14 is a block diagram illustrating an apparatus for handling a roam request from a switch in accordance with an embodiment of the present invention.
- FIG. 15 is a block diagram illustrating a method for handling a roam reply in a switch in accordance with an embodiment of the present invention.
- the components, process steps, and/or data structures may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines.
- devices of a less general purpose nature such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.
- FPGAs field programmable gate arrays
- ASICs application specific integrated circuits
- the present invention is described in the context of a switch. However, one of ordinary skill in the art will recognize that the term switch should be read broadly, so as to include any device that directs packets, including a router and a gateway.
- Layer 2 and Layer 3 roaming are based on the Open Systems Interconnection (OSI) network standard of layers.
- Layer 2 represents the data-link layer
- layer 3 represents the network layer.
- layer 2 roaming may involve the roaming from one access point (AP) to a new AP having the same virtual local area network (VLAN) and subnet.
- Layer 3 roaming may involve the roaming from one AP to a new AP that has either a different VLAN, or the same VLAN but different subnet.
- Clients in a wireless network can roam from one access point to another.
- a combination of access points, wireless local area network (WLAN) switches, and the underlying topology presents a challenge to manage roaming clients.
- the present invention provides a solution that allows WLAN switches to properly manage wireless roaming.
- One embodiment of the present invention involves the use of new protocols between the access point (AP) and the WLAN switch, and between WLAN switches.
- the protocol between the AP and the WLAN switch may be called the Switch Access Point Protocol (SAPP).
- the protocol between the WLAN switches may be called the Inter Switch Roaming Protocol (ISRP).
- ISRP Inter Switch Roaming Protocol
- SAPP may begin with a discovery phase in which the APs send a discovery request frame, causing any WLAN switch receiving the frame to respond with a discover reply frame. From all the discovery replies received, an AP may select a WLAN switch with which to associate, and then may send out a join request. The WLAN switch receiving the join request may then send a join reply. Upon receiving the join reply, the AP may establish a TCP session with the WLAN switch. Once the TCP session is up, the Access Point may communicate to the WLAN switch all the client related events.
- Each of the WLAN switches within a mobility domain may be configured with the IP addresses of all the other WLAN switches in that domain. This helps to establish a full mesh of TCP connections amongst them.
- the WLAN switch may send out an initialization message via ISRP to the peer WLAN switch. If the peer accepts the initialization message, it may reply with its own initialization message followed by a keep alive message.
- the new WLAN switch may send a roam mobile message to all the other WLAN switches in the mobility domain.
- a WLAN switch may check to see if it knows anything about the client. If it does, then it may invoke a roaming algorithm to handle the message. Otherwise, it may simply ignore the message.
- FIG. 1 is a diagram illustrating layer 2 roaming on a single WLAN switch in accordance with an embodiment of the present invention.
- the client has roamed from one AP 100 to another AP 102 , both of which are connected to the same WLAN switch 104 .
- the WLAN switch 104 will still be the home agent (HA).
- the client's policy should be moved from the old AP port to the new AP port on the WLAN switch 104 .
- FIG. 2 is a diagram illustrating layer 2 roaming between two WLAN switches in accordance with an embodiment of the present invention.
- the client has roamed from an AP 200 connected to a first WLAN switch 202 to another AP 204 connected to a second WLAN switch 206 .
- the client's mobility context information should be moved from WLAN switch 202 to WLAN switch 206 .
- WLAN switch 206 should be designated as the new HA.
- WLAN switch 202 should then remove the client's layer 2 information from the bridging table, and then clean up the client's data structures.
- FIG. 3 is a diagram illustrating layer 3 roaming on a single WLAN switch in accordance with an embodiment of the present invention.
- the client has roamed from one AP 300 to another AP 302 , both of which are connected to the same WLAN switch 304 .
- WLAN switch 304 will be both the HA and the foreign agent (FA).
- the packets destined for the client should be forwarded to the CPU, which may modify it to reflect the correct VLAN tag.
- FIG. 4 is a diagram illustrating layer 3 roaming between two WLAN switches in accordance with an embodiment of the present invention.
- the client has roamed from an AP 400 connected to a first WLAN switch 402 to another AP 404 connected to a second WLAN switch 404 .
- the client's mobility context information should be moved from WLAN switch 402 to WLAN switch 40 .
- the first WLAN switch 402 being the HA, should tunnel the client's traffic to the second WLAN switch 406 .
- the second WLAN switch 406 then should apply the client's policy to the port to which the client's associated AP is attached.
- FIG. 5 is a diagram illustrating layer 3 roaming followed by another layer 3 roaming involving 2 WLAN switches in accordance with an embodiment of the present invention.
- the client has roamed twice.
- the first WLAN switch 500 will be both the HA and the FA. No tunneling is needed as the client is still connected to the same WLAN switch 500 .
- VLAN tag addition or replacement may need to be performed.
- the second WLAN switch 502 will become the new FA and the following should be performed.
- the client's mobility context information should be moved from the first WLAN switch 500 to the second WLAN switch 502 .
- the first WLAN switch 500 being the HA, should then tunnel the client's traffic to the second WLAN switch 502 .
- the second WLAN switch 502 should apply the client's policy to the port to which the client's associate AP is attached. Finally, the second WLAN switch 502 should extract the packet from the IP in IP encapsulation, make the necessary VLAN changes, and forward the packet to the client.
- FIG. 6 is a diagram illustrating layer 3 roaming to a different WLAN switch followed by another layer 3 roaming back to the original WLAN switch in accordance with an embodiment of the present invention.
- the client first layer 3 roamed from an AP 600 connected to a first WLAN switch 602 to an AP 604 connected to a second WLAN switch 606 .
- This part is the same as the case described by FIG. 4 and the accompanying text, and thus the same steps should be taken.
- the client gets associated with an AP ( 600 , or possibly another AP) connected to the original WLAN switch 602 . What is performed here depends on whether the client roamed back to the same VLAN. If so, then there is no FA. If not, then the original WLAN switch 602 will be both the HA and the FA.
- FIG. 7 is a diagram illustrating layer 3 roaming followed by another layer 3 roaming on 3 or more WLAN switches in accordance with an embodiment of the present invention.
- the client has layer 3 roamed twice.
- the first roam is similar to the case described by FIG. 4 and the accompanying text, and thus the same steps should be taken.
- the client's mobility context information should be copied from the HA (WLAN switch 700 ) to the new FA (WLAN switch 704 ).
- IP in IP tunneling of the client's traffic should be performed by the HA.
- the old FA (WLAN switch 702 ) should then clean up the client's data structures.
- FIG. 8 is a diagram illustrating layer 3 roaming followed by layer 2 roaming involving 2 WLAN switches in accordance with an embodiment of the present invention.
- the client has first roamed from AP 800 to AP 802 , both of which are connected to the same WLAN switch 804 .
- the client roamed from AP 802 to AP 806 , which is connected to another WLAN switch 808 .
- WLAN switch 804 is both the HA and the FA for the client, which is similar to the case described by FIG. 3 and the accompanying text, and thus the same steps should be performed.
- the second layer 2 roam the case becomes similar to the case described by FIG. 2 and the accompanying text, and thus the same steps should be performed.
- FIG. 9 is a diagram illustrating layer 3 roaming followed by layer 2 roaming on 3 or more WLAN switches in accordance with an embodiment of the present invention.
- the client has first roamed from an AP 900 connected to WLAN switch 902 to AP 904 connected to another WLAN switch 906 .
- the client roams from AP 904 to AP 908 , which is connected to WLAN switch 910 .
- WLAN Switch 902 is the HA and WLAN switch 906 is the FA for the client, and this case is similar to that described by FIG. 4 and the accompanying texts, and thus the same steps should be performed.
- the WLAN switch 910 becomes the new FA and the following should be performed.
- the client's mobility context information should be copied from the HA (WLAN switch 902 ) to the new FA (WLAN switch 910 ). IP in IP tunneling of the client's traffic should then be performed by the HA. Finally, the old FA (WLAN switch 906 ) should clean up the client's data structures and any bridging information that it may have stored.
- FIG. 10 is a flow diagram illustrating a method for responding to client roaming at a switch in accordance with an embodiment of the present invention.
- a move request may be received at the switch from an associated access point indicating that a client has associated with the access point. This may be, for example, a SAPP move message.
- the switch may send a roam request to all peer switches in the mobility domain, including itself. This may be, for example, an ISRP roam request.
- FIG. 11 is a flow diagram illustrating a method for handling a roam request from a switch in accordance with an embodiment of the present invention. This method may be run on any switch in the mobility domain, including the switch that sent the roam request in the first place.
- roam request may be received from a switch. This roam request may be, for example, an ISRP roam request.
- the roam request may include an indication of the client that has roamed.
- it may be determined if the client is known to this switch. This may include looking up the identification of the client in a table or similar data structure. If no such client can be found, then the roam request may simply be ignored.
- the client is found, then at 1104 it may be determined if the roaming being attempted is layer 3 roaming. If so, then at 1106 it may be determined if the switch is the same as the switch that sent the roam request. This may include, for example, seeing if the source network address of the roam request matches the network address of the switch. Such a case could occur if, for example, the client is roaming between two VLANs serviced by the same switch. If it is the same switch, then at 1108 this switch may be set as the foreign agent. Then at 1110 , a VLAN tag corresponding to the client in a table or similar data structure may be updated with a new VLAN tag. This may act to change the VLAN that packets to this client will be forwarded to upon receipt by the switch.
- the switch may be determined if the switch is the Home Agent for the client. If not, then at 1114 , information regarding the client may be removed from the switch. This may make it such that the client is no longer “known” to this switch. If, however, the switch is the Home Agent for the client, then at 1116 , traffic for this client may be tunneled to the switch that sent the roam request. Then, at 1118 , the switch may proxy for the client on the local (old) network. Finally, at 1120 , a roam reply indicating success may be sent to the switch that sent the roam request. This roam reply may include all network configuration information (e.g., IP address) for the client from the switch. This may be also be performed after step 1110 .
- IP address e.g., IP address
- the switch may be determined if the switch is the same switch that sent the roam request. If not, then at 1122 , information regarding the client may be removed from the switch. Then the process may move to 1118 . If not, then the process may simply move to 1118 .
- the switch may instead send a roam reply indicating failure if something went wrong during the process, such as the failure in tunnel establishment.
- FIG. 12 is a flow diagram illustrating a method for handling a roam reply in a switch in accordance with an embodiment of the present invention. This method may be run on a switch that sent a roam request.
- a roam reply may be received.
- ARP Address Resolution Protocol
- FIG. 13 is a block diagram illustrating an apparatus for responding to client roaming at a switch in accordance with an embodiment of the present invention.
- a move request receiver 1300 may receive a move request at the switch from an associated access point indicating that a client has associated with the access point. This may be, for example, a SAPP move message. Then, a roam request peer switch sender 1302 coupled to the move request receiver 1300 may send a roam request to all peer switches in the mobility domain, including itself. This may be, for example, an ISRP roam request.
- FIG. 14 is a block diagram illustrating an apparatus for handling a roam request from a switch in accordance with an embodiment of the present invention.
- This apparatus may be located on any switch in the mobility domain, including the switch that sent the roam request in the first place.
- a roam request receiver 1400 may receive the roam request from a switch.
- This roam request may be, for example, an ISRP roam request.
- the roam request may include an indication of the client that has roamed.
- a known client checker 1402 coupled to the roam request receiver 1400 may determine if the client is known to this switch. This may include looking up the identification of the client in a table or similar data structure. If no such client can be found, then the roam request may simply be ignored.
- a layer 2 or layer 3 roaming ascertainer 1404 coupled to the known client checker 1402 may determine if the roaming being attempted is layer 3 roaming. If so, then a first switch second switch identical discoverer 1406 coupled to the layer 2 or layer 3 roaming ascertainer 1404 may determine if the switch is the same as the switch that sent the roam request. This may include, for example, seeing if the source network address of the roam request matches the network address of the switch. Such a case could occur if, for example, the client is roaming between two VLANs serviced by the same switch. If it is the same switch, then a first switch foreign agent setter 1408 coupled to the first switch second switch identical discoverer 1406 may set this switch as the foreign agent.
- a virtual network tag updater 1410 coupled to the first switch foreign agent setter 1408 may update a VLAN tag corresponding to the client in a table or similar data structure with a new VLAN tag. This may act to change the VLAN that packets to this client will be forwarded to upon receipt by the switch.
- a first switch home agent determiner 1412 may determine if the switch is the Home Agent for the client. If not, then a client information remover 1414 coupled to the first switch home agent deteminer 1412 may remove information regarding the client from the switch. This may make it such that the client is no longer “known” to this switch. If, however, the switch is the Home Agent for the client, then a second switch traffic tunneler 1416 coupled to the first switch home agent determiner 1412 may tunnel traffic for this client to the switch that sent the roam request. Then the switch may proxy for the client on the local (old) network.
- a roam reply sender 1418 coupled to the client information remover 1414 and to the second switch traffic tunneler 1416 may send a roam reply indicating success to the switch that sent the roam request.
- This roam reply may include all network configuration information (e.g., IP address) for the client from the switch.
- a client information remover 1420 coupled to the layer 2 or layer 3 roaming ascertainer 1404 may remove information regarding the client from the switch. If so, nothing special needs to be done.
- the switch may instead send a roam reply indicating failure if something went wrong during the process, such as the failure in tunnel establishment.
- FIG. 15 is a block diagram illustrating a method for handling a roam reply in a switch in accordance with an embodiment of the present invention.
- This apparatus may be located on a switch that sent a roam request.
- a roam reply receiver 1500 may receive a roam reply .
- a successful roam reply determiner 1502 coupled to the roam reply receiver 1500 may determine if the roam reply indicates that the handling of a roam request was successful or not. If not, then a failure reply access point sender 1504 coupled to the successful reply determiner 1502 may send a reply to the corresponding access point may be sent indicating failure. This may be sent via a SAPP reply. If the handling of the roam request was successful, then a foreign agent switch setter 1506 coupled to the successful roam reply determiner 1502 may set the switch as the Foreign Agent.
- a designated router switcher 1508 coupled to the foreign agent switch setter 1506 may switch a router designated by the client with a default router for the switch.
- This may include an address resolution protocol packet trapper 1510 , which may trap all Address Resolution Protocol (ARP) packets from the client, and an address resolution protocol reply sender 1512 coupled to the address resolution protocol packet trapper 1510 , which may send an ARP reply to the client with this switch's default router address. This causes the client to correctly send out data traffic having a usable router address.
- ARP Address Resolution Protocol
- a move reply access point sender 1514 coupled to the successful roam reply determiner 1502 may send a move reply to the corresponding AP.
- the new VLAN identification may also be passed to the AP.
- This reply may be a SAPP reply.
- the AP may then start to tag the client's traffic with the new VLAN tag.
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 10/785,596, entitled “Methods and Apparatus for Handling Wireless Roaming Among and Across Wireless Area Networks,” filed on Feb. 23, 2004, the entirety of which is incorporated herein by reference.
- A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
- The present invention relates to the field of wireless networking. More particularly, the present invention relates to a solution for wireless roaming among and across wireless local area networks.
- Wireless network has significantly grown in popularity. The IEEE 802.11 standards are currently the most widely used wireless networking standards. Wireless network can present unique problems when clients “roam”. Roaming may be defined as switching from one access point to another access point.
- The ability of a mobile client to move freely between various segments of a wireless domain without experiencing any observable service degradation or disruption is called seamless roaming. Roaming can occur at various layers. If a client roams between two segments that are part of the same Internet Protocol (IP) subnet, then the roaming is termed
layer 2 roaming. If the client roams between segments that have different IP subnets, then the roaming is termedlayer 3 roaming. - The Inter Access Point Protocol (IAPP) has been suggested by the IEEE 802.11 committee to address the
layer 2 roaming of clients in wireless networks. It runs on wireless access points and uses a combination of Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) to facilitate roaming. However, it fails to supportlayer 3 roaming as it relies onlayer 2 broadcast messages to find other access points. - The IPv4 (RFC 3344) standard has been proposed by the Internet Engineering Task Force (IETF) and it attempts to address
Layer 3 roaming. Though it is a generic solution, it suffers several limitations. For example, the standard relies on software upgrades to the clients to run some piece of the protocol. This requires that all users upgrade their mobile clients (laptops, mobile phones, etc.) before they can use this standard. Additionally, this standard only addresses thelayer 3 roaming aspect of the generic problem. - What is needed is a solution that can seamlessly handle both
layer 2 andlayer 3 roaming. - Wireless roaming in a computer network may be handled through a solution provided on one or more switches in the network. A roam request sent by a switch corresponding to the user's new location may be received by the other switches in the network. If the user is known to any of these switches, then they may execute steps to accommodate the roaming. The tasks performed may vary based on whether the roaming is on
layer 2 orlayer 3, whether the switch is a home agent for the client, and/or whether the switch already corresponds to the user's new location. - The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more embodiments of the present invention and, together with the detailed description, serve to explain the principles and implementations of the invention.
- In the drawings:
-
FIG. 1 is adiagram illustrating layer 2 roaming on a single WLAN switch in accordance with an embodiment of the present invention. -
FIG. 2 is adiagram illustrating layer 2 roaming between two WLAN switches in accordance with an embodiment of the present invention. -
FIG. 3 is adiagram illustrating layer 3 roaming on a single WLAN switch in accordance with an embodiment of the present invention. -
FIG. 4 is adiagram illustrating layer 3 roaming between two WLAN switches in accordance with an embodiment of the present invention. -
FIG. 5 is adiagram illustrating layer 3 roaming followed by anotherlayer 3 roaming involving 2 WLAN switches in accordance with an embodiment of the present invention. -
FIG. 6 is adiagram illustrating layer 3 roaming to a different WLAN switch followed by anotherlayer 3 roaming back to the original WLAN switch in accordance with an embodiment of the present invention. -
FIG. 7 is adiagram illustrating layer 3 roaming followed by anotherlayer 3 roaming on 3 or more WLAN switches in accordance with an embodiment of the present invention. -
FIG. 8 is adiagram illustrating layer 3 roaming followed bylayer 2 roaming involving 2 WLAN switches in accordance with an embodiment of the present invention. -
FIG. 9 is adiagram illustrating layer 3 roaming followed bylayer 2 roaming on 3 or more WLAN switches in accordance with an embodiment of the present invention. -
FIG. 10 is a flow diagram illustrating a method for responding to client roaming at a switch in accordance with an embodiment of the present invention. -
FIG. 11 is a flow diagram illustrating a method for handling a roam request from a switch in accordance with an embodiment of the present invention. -
FIG. 12 is a flow diagram illustrating a method for handling a roam reply in a switch in accordance with an embodiment of the present invention. -
FIG. 13 is a block diagram illustrating an apparatus for responding to client roaming at a switch in accordance with an embodiment of the present invention. -
FIG. 14 is a block diagram illustrating an apparatus for handling a roam request from a switch in accordance with an embodiment of the present invention. -
FIG. 15 is a block diagram illustrating a method for handling a roam reply in a switch in accordance with an embodiment of the present invention. - Embodiments of the present invention are described herein in the context of a system of computers, servers, and software. Those of ordinary skill in the art will realize that the following detailed description of the present invention is illustrative only and is not intended to be in any way limiting. Other embodiments of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations of the present invention as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.
- In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application—and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
- In accordance with the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines. In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein. Furthermore, the present invention is described in the context of a switch. However, one of ordinary skill in the art will recognize that the term switch should be read broadly, so as to include any device that directs packets, including a router and a gateway.
-
Layer 2 andLayer 3 roaming are based on the Open Systems Interconnection (OSI) network standard of layers.Layer 2 represents the data-link layer, whilelayer 3 represents the network layer. For purposes of this document,layer 2 roaming may involve the roaming from one access point (AP) to a new AP having the same virtual local area network (VLAN) and subnet.Layer 3 roaming may involve the roaming from one AP to a new AP that has either a different VLAN, or the same VLAN but different subnet. - Clients in a wireless network can roam from one access point to another. A combination of access points, wireless local area network (WLAN) switches, and the underlying topology presents a challenge to manage roaming clients. The present invention provides a solution that allows WLAN switches to properly manage wireless roaming.
- One embodiment of the present invention involves the use of new protocols between the access point (AP) and the WLAN switch, and between WLAN switches. The protocol between the AP and the WLAN switch may be called the Switch Access Point Protocol (SAPP). The protocol between the WLAN switches may be called the Inter Switch Roaming Protocol (ISRP). Use of these protocols is optional, however, and one of ordinary skill in the art will recognize that the present invention may be practiced without the use of either of these protocols.
- SAPP may begin with a discovery phase in which the APs send a discovery request frame, causing any WLAN switch receiving the frame to respond with a discover reply frame. From all the discovery replies received, an AP may select a WLAN switch with which to associate, and then may send out a join request. The WLAN switch receiving the join request may then send a join reply. Upon receiving the join reply, the AP may establish a TCP session with the WLAN switch. Once the TCP session is up, the Access Point may communicate to the WLAN switch all the client related events.
- Each of the WLAN switches within a mobility domain may be configured with the IP addresses of all the other WLAN switches in that domain. This helps to establish a full mesh of TCP connections amongst them.
- Once the TCP connection is established, the WLAN switch may send out an initialization message via ISRP to the peer WLAN switch. If the peer accepts the initialization message, it may reply with its own initialization message followed by a keep alive message.
- When roaming is detected, the new WLAN switch may send a roam mobile message to all the other WLAN switches in the mobility domain. When a WLAN switch receives this message, it may check to see if it knows anything about the client. If it does, then it may invoke a roaming algorithm to handle the message. Otherwise, it may simply ignore the message.
-
FIG. 1 is adiagram illustrating layer 2 roaming on a single WLAN switch in accordance with an embodiment of the present invention. In this case, the client has roamed from oneAP 100 to anotherAP 102, both of which are connected to thesame WLAN switch 104. There is not much that needs to be done in this case. TheWLAN switch 104 will still be the home agent (HA). The client's policy, however, should be moved from the old AP port to the new AP port on theWLAN switch 104. -
FIG. 2 is adiagram illustrating layer 2 roaming between two WLAN switches in accordance with an embodiment of the present invention. In this case, the client has roamed from anAP 200 connected to afirst WLAN switch 202 to anotherAP 204 connected to asecond WLAN switch 206. Here, the client's mobility context information should be moved fromWLAN switch 202 toWLAN switch 206. Additionally,WLAN switch 206 should be designated as the new HA.WLAN switch 202 should then remove the client'slayer 2 information from the bridging table, and then clean up the client's data structures. -
FIG. 3 is adiagram illustrating layer 3 roaming on a single WLAN switch in accordance with an embodiment of the present invention. In this case, the client has roamed from oneAP 300 to anotherAP 302, both of which are connected to thesame WLAN switch 304. Once again, there is not much that needs to be done here.WLAN switch 304 will be both the HA and the foreign agent (FA). However, if the VLAN has changed then the packets destined for the client should be forwarded to the CPU, which may modify it to reflect the correct VLAN tag. -
FIG. 4 is adiagram illustrating layer 3 roaming between two WLAN switches in accordance with an embodiment of the present invention. In this case, the client has roamed from anAP 400 connected to afirst WLAN switch 402 to anotherAP 404 connected to asecond WLAN switch 404. Here, the client's mobility context information should be moved fromWLAN switch 402 to WLAN switch 40. Then thefirst WLAN switch 402, being the HA, should tunnel the client's traffic to thesecond WLAN switch 406. Thesecond WLAN switch 406 then should apply the client's policy to the port to which the client's associated AP is attached. -
FIG. 5 is adiagram illustrating layer 3 roaming followed by anotherlayer 3 roaming involving 2 WLAN switches in accordance with an embodiment of the present invention. In this case, the client has roamed twice. After thefirst layer 3 roam, thefirst WLAN switch 500 will be both the HA and the FA. No tunneling is needed as the client is still connected to thesame WLAN switch 500. However, VLAN tag addition or replacement may need to be performed. After thesecond layer 3 roam, thesecond WLAN switch 502 will become the new FA and the following should be performed. First, the client's mobility context information should be moved from thefirst WLAN switch 500 to thesecond WLAN switch 502. Thefirst WLAN switch 500, being the HA, should then tunnel the client's traffic to thesecond WLAN switch 502. Then thesecond WLAN switch 502 should apply the client's policy to the port to which the client's associate AP is attached. Finally, thesecond WLAN switch 502 should extract the packet from the IP in IP encapsulation, make the necessary VLAN changes, and forward the packet to the client. -
FIG. 6 is adiagram illustrating layer 3 roaming to a different WLAN switch followed by anotherlayer 3 roaming back to the original WLAN switch in accordance with an embodiment of the present invention. In this case, the clientfirst layer 3 roamed from anAP 600 connected to afirst WLAN switch 602 to anAP 604 connected to asecond WLAN switch 606. This part is the same as the case described byFIG. 4 and the accompanying text, and thus the same steps should be taken. On thesecond layer 3 roam, the client gets associated with an AP (600, or possibly another AP) connected to theoriginal WLAN switch 602. What is performed here depends on whether the client roamed back to the same VLAN. If so, then there is no FA. If not, then theoriginal WLAN switch 602 will be both the HA and the FA. -
FIG. 7 is adiagram illustrating layer 3 roaming followed by anotherlayer 3 roaming on 3 or more WLAN switches in accordance with an embodiment of the present invention. In this case, the client haslayer 3 roamed twice. The first roam is similar to the case described byFIG. 4 and the accompanying text, and thus the same steps should be taken. On thesecond layer 3 roam, the client's mobility context information should be copied from the HA (WLAN switch 700) to the new FA (WLAN switch 704). Then IP in IP tunneling of the client's traffic should be performed by the HA. The old FA (WLAN switch 702) should then clean up the client's data structures. -
FIG. 8 is adiagram illustrating layer 3 roaming followed bylayer 2 roaming involving 2 WLAN switches in accordance with an embodiment of the present invention. In this case, the client has first roamed fromAP 800 toAP 802, both of which are connected to thesame WLAN switch 804. Next, the client roamed fromAP 802 toAP 806, which is connected to anotherWLAN switch 808. After the first roam,WLAN switch 804 is both the HA and the FA for the client, which is similar to the case described byFIG. 3 and the accompanying text, and thus the same steps should be performed. After thesecond layer 2 roam, the case becomes similar to the case described byFIG. 2 and the accompanying text, and thus the same steps should be performed. -
FIG. 9 is adiagram illustrating layer 3 roaming followed bylayer 2 roaming on 3 or more WLAN switches in accordance with an embodiment of the present invention. In this case, the client has first roamed from anAP 900 connected toWLAN switch 902 toAP 904 connected to another WLAN switch 906. Next, the client roams fromAP 904 to AP 908, which is connected to WLAN switch 910. After the first roam,WLAN Switch 902 is the HA and WLAN switch 906 is the FA for the client, and this case is similar to that described byFIG. 4 and the accompanying texts, and thus the same steps should be performed. After thesecond layer 2 roam, the WLAN switch 910 becomes the new FA and the following should be performed. First, the client's mobility context information should be copied from the HA (WLAN switch 902) to the new FA (WLAN switch 910). IP in IP tunneling of the client's traffic should then be performed by the HA. Finally, the old FA (WLAN switch 906) should clean up the client's data structures and any bridging information that it may have stored. -
FIG. 10 is a flow diagram illustrating a method for responding to client roaming at a switch in accordance with an embodiment of the present invention. At 1000, a move request may be received at the switch from an associated access point indicating that a client has associated with the access point. This may be, for example, a SAPP move message. Then, at 1002, the switch may send a roam request to all peer switches in the mobility domain, including itself. This may be, for example, an ISRP roam request. -
FIG. 11 is a flow diagram illustrating a method for handling a roam request from a switch in accordance with an embodiment of the present invention. This method may be run on any switch in the mobility domain, including the switch that sent the roam request in the first place. At 1100, roam request may be received from a switch. This roam request may be, for example, an ISRP roam request. The roam request may include an indication of the client that has roamed. At 1102, it may be determined if the client is known to this switch. This may include looking up the identification of the client in a table or similar data structure. If no such client can be found, then the roam request may simply be ignored. If on the other hand, the client is found, then at 1104 it may be determined if the roaming being attempted islayer 3 roaming. If so, then at 1106 it may be determined if the switch is the same as the switch that sent the roam request. This may include, for example, seeing if the source network address of the roam request matches the network address of the switch. Such a case could occur if, for example, the client is roaming between two VLANs serviced by the same switch. If it is the same switch, then at 1108 this switch may be set as the foreign agent. Then at 1110, a VLAN tag corresponding to the client in a table or similar data structure may be updated with a new VLAN tag. This may act to change the VLAN that packets to this client will be forwarded to upon receipt by the switch. - If at 1106 it was determined that the WLAN switch was not the same WLAN switch that sent the roam request, then at 1112 it may be determined if the switch is the Home Agent for the client. If not, then at 1114, information regarding the client may be removed from the switch. This may make it such that the client is no longer “known” to this switch. If, however, the switch is the Home Agent for the client, then at 1116, traffic for this client may be tunneled to the switch that sent the roam request. Then, at 1118, the switch may proxy for the client on the local (old) network. Finally, at 1120, a roam reply indicating success may be sent to the switch that sent the roam request. This roam reply may include all network configuration information (e.g., IP address) for the client from the switch. This may be also be performed after
step 1110. - If at 1104 it was determined that it was not
layer 3 roaming (but instead waslayer 2 roaming), then at 1120, it may be determined if the switch is the same switch that sent the roam request. If not, then at 1122, information regarding the client may be removed from the switch. Then the process may move to 1118. If not, then the process may simply move to 1118. - It should be noted that at 1118, the switch may instead send a roam reply indicating failure if something went wrong during the process, such as the failure in tunnel establishment.
-
FIG. 12 is a flow diagram illustrating a method for handling a roam reply in a switch in accordance with an embodiment of the present invention. This method may be run on a switch that sent a roam request. At 1200, a roam reply may be received. At 1202 it may be determined if the roam reply indicates that the handling of a roam request was successful or not. If not, then at 1204 a reply to the corresponding access point may be sent indicating failure. This may be sent via a SAPP reply. If the handling of the roam request was successful, then at 1206, the switch may be set as the Foreign Agent. At this point, if the client attempts to send packets, it will likely still be referencing a router address located in the old domain. In order to remedy this, at 1208 all Address Resolution Protocol (ARP) packets from the client should be trapped. Then at 1210, an ARP reply may be sent to the client with this switch's default router address. This causes the client to correctly send out data traffic having a usable router address. Then at 1212, a move reply may be sent to the corresponding AP. In this reply, the new VLAN identification may also be passed to the AP. This reply may be a SAPP reply. The AP may then start to tag the client's traffic with the new VLAN tag. -
FIG. 13 is a block diagram illustrating an apparatus for responding to client roaming at a switch in accordance with an embodiment of the present invention. Amove request receiver 1300 may receive a move request at the switch from an associated access point indicating that a client has associated with the access point. This may be, for example, a SAPP move message. Then, a roam requestpeer switch sender 1302 coupled to themove request receiver 1300 may may send a roam request to all peer switches in the mobility domain, including itself. This may be, for example, an ISRP roam request. -
FIG. 14 is a block diagram illustrating an apparatus for handling a roam request from a switch in accordance with an embodiment of the present invention. This apparatus may be located on any switch in the mobility domain, including the switch that sent the roam request in the first place. A roamrequest receiver 1400 may receive the roam request from a switch. This roam request may be, for example, an ISRP roam request. The roam request may include an indication of the client that has roamed. A knownclient checker 1402 coupled to the roamrequest receiver 1400 may determine if the client is known to this switch. This may include looking up the identification of the client in a table or similar data structure. If no such client can be found, then the roam request may simply be ignored. If on the other hand, the client is found, then alayer 2 orlayer 3roaming ascertainer 1404 coupled to the knownclient checker 1402 may determine if the roaming being attempted islayer 3 roaming. If so, then a first switch second switchidentical discoverer 1406 coupled to thelayer 2 orlayer 3roaming ascertainer 1404 may determine if the switch is the same as the switch that sent the roam request. This may include, for example, seeing if the source network address of the roam request matches the network address of the switch. Such a case could occur if, for example, the client is roaming between two VLANs serviced by the same switch. If it is the same switch, then a first switchforeign agent setter 1408 coupled to the first switch second switchidentical discoverer 1406 may set this switch as the foreign agent. Then a virtualnetwork tag updater 1410 coupled to the first switchforeign agent setter 1408 may update a VLAN tag corresponding to the client in a table or similar data structure with a new VLAN tag. This may act to change the VLAN that packets to this client will be forwarded to upon receipt by the switch. - If it was determined that the WLAN switch was not the same WLAN switch that sent the roam request, then a first switch
home agent determiner 1412 may determine if the switch is the Home Agent for the client. If not, then a client information remover 1414 coupled to the first switchhome agent deteminer 1412 may remove information regarding the client from the switch. This may make it such that the client is no longer “known” to this switch. If, however, the switch is the Home Agent for the client, then a secondswitch traffic tunneler 1416 coupled to the first switchhome agent determiner 1412 may tunnel traffic for this client to the switch that sent the roam request. Then the switch may proxy for the client on the local (old) network. Finally, a roamreply sender 1418 coupled to the client information remover 1414 and to the secondswitch traffic tunneler 1416 may send a roam reply indicating success to the switch that sent the roam request. This roam reply may include all network configuration information (e.g., IP address) for the client from the switch. - If it was determined that it was not
layer 3 roaming (but instead waslayer 2 roaming), then it may be determined if the switch is the same switch that sent the roam request. If not, then a client information remover 1420 coupled to thelayer 2 orlayer 3roaming ascertainer 1404 may remove information regarding the client from the switch. If so, nothing special needs to be done. - It should be noted that the switch may instead send a roam reply indicating failure if something went wrong during the process, such as the failure in tunnel establishment.
-
FIG. 15 is a block diagram illustrating a method for handling a roam reply in a switch in accordance with an embodiment of the present invention. This apparatus may be located on a switch that sent a roam request. A roamreply receiver 1500 may receive a roam reply . A successful roamreply determiner 1502 coupled to the roamreply receiver 1500 may determine if the roam reply indicates that the handling of a roam request was successful or not. If not, then a failure replyaccess point sender 1504 coupled to thesuccessful reply determiner 1502 may send a reply to the corresponding access point may be sent indicating failure. This may be sent via a SAPP reply. If the handling of the roam request was successful, then a foreignagent switch setter 1506 coupled to the successful roamreply determiner 1502 may set the switch as the Foreign Agent. At this point, if the client attempts to send packets, it will likely still be referencing a router address located in the old domain. In order to remedy this, a designatedrouter switcher 1508 coupled to the foreignagent switch setter 1506 may switch a router designated by the client with a default router for the switch. This may include an address resolutionprotocol packet trapper 1510, which may trap all Address Resolution Protocol (ARP) packets from the client, and an address resolutionprotocol reply sender 1512 coupled to the address resolutionprotocol packet trapper 1510, which may send an ARP reply to the client with this switch's default router address. This causes the client to correctly send out data traffic having a usable router address. Then a move replyaccess point sender 1514 coupled to the successful roamreply determiner 1502 may send a move reply to the corresponding AP. In this reply, the new VLAN identification may also be passed to the AP. This reply may be a SAPP reply. The AP may then start to tag the client's traffic with the new VLAN tag. - While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. The invention, therefore, is not to be restricted except in the spirit of the appended claims.
Claims (19)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/263,356 US20090275328A1 (en) | 2004-02-23 | 2008-10-31 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
US14/202,296 US20140187241A1 (en) | 2004-02-23 | 2014-03-10 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/785,596 US7477894B1 (en) | 2004-02-23 | 2004-02-23 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
US12/263,356 US20090275328A1 (en) | 2004-02-23 | 2008-10-31 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/785,596 Continuation US7477894B1 (en) | 2004-02-23 | 2004-02-23 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/202,296 Division US20140187241A1 (en) | 2004-02-23 | 2014-03-10 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090275328A1 true US20090275328A1 (en) | 2009-11-05 |
Family
ID=40223936
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/785,596 Expired - Fee Related US7477894B1 (en) | 2004-02-23 | 2004-02-23 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
US12/263,356 Abandoned US20090275328A1 (en) | 2004-02-23 | 2008-10-31 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
US14/202,296 Abandoned US20140187241A1 (en) | 2004-02-23 | 2014-03-10 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/785,596 Expired - Fee Related US7477894B1 (en) | 2004-02-23 | 2004-02-23 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/202,296 Abandoned US20140187241A1 (en) | 2004-02-23 | 2014-03-10 | Methods and apparatus for handling wireless roaming among and across wireless area networks |
Country Status (1)
Country | Link |
---|---|
US (3) | US7477894B1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080002607A1 (en) * | 2006-06-30 | 2008-01-03 | Ramakrishnan Nagarajan | Technique for handling layer 2 roaming in a network of wireless switches supporting layer 3 mobility within a mobility domain |
US20090034470A1 (en) * | 2007-07-31 | 2009-02-05 | Symbol Technologies, Inc. | Forwarding broadcast/multicast data when wireless clients layer 3 roam across ip subnets in a wlan |
Families Citing this family (104)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7720031B1 (en) * | 2004-10-15 | 2010-05-18 | Cisco Technology, Inc. | Methods and devices to support mobility of a client across VLANs and subnets, while preserving the client's assigned IP address |
US8065712B1 (en) | 2005-02-16 | 2011-11-22 | Cisco Technology, Inc. | Methods and devices for qualifying a client machine to access a network |
WO2006099540A2 (en) | 2005-03-15 | 2006-09-21 | Trapeze Networks, Inc. | System and method for distributing keys in a wireless network |
US20070009139A1 (en) * | 2005-07-11 | 2007-01-11 | Agere Systems Inc. | Facial recognition device for a handheld electronic device and a method of using the same |
US7551619B2 (en) * | 2005-10-13 | 2009-06-23 | Trapeze Networks, Inc. | Identity-based networking |
US7573859B2 (en) * | 2005-10-13 | 2009-08-11 | Trapeze Networks, Inc. | System and method for remote monitoring in a wireless network |
US7724703B2 (en) * | 2005-10-13 | 2010-05-25 | Belden, Inc. | System and method for wireless network monitoring |
US8638762B2 (en) * | 2005-10-13 | 2014-01-28 | Trapeze Networks, Inc. | System and method for network integrity |
WO2007044986A2 (en) | 2005-10-13 | 2007-04-19 | Trapeze Networks, Inc. | System and method for remote monitoring in a wireless network |
EP2763443B1 (en) * | 2005-12-01 | 2019-05-22 | Ruckus Wireless, Inc. | On-demand services by wireless base station virtualization |
US8369357B2 (en) * | 2006-02-28 | 2013-02-05 | Cisco Technology, Inc. | System and method for providing simultaneous handling of layer-2 and layer-3 mobility in an internet protocol network environment |
US7788703B2 (en) | 2006-04-24 | 2010-08-31 | Ruckus Wireless, Inc. | Dynamic authentication in secured wireless networks |
US9769655B2 (en) | 2006-04-24 | 2017-09-19 | Ruckus Wireless, Inc. | Sharing security keys with headless devices |
US9071583B2 (en) | 2006-04-24 | 2015-06-30 | Ruckus Wireless, Inc. | Provisioned configuration for automatic wireless connection |
US7558266B2 (en) | 2006-05-03 | 2009-07-07 | Trapeze Networks, Inc. | System and method for restricting network access using forwarding databases |
US8966018B2 (en) * | 2006-05-19 | 2015-02-24 | Trapeze Networks, Inc. | Automated network device configuration and network deployment |
US9258702B2 (en) | 2006-06-09 | 2016-02-09 | Trapeze Networks, Inc. | AP-local dynamic switching |
US8818322B2 (en) | 2006-06-09 | 2014-08-26 | Trapeze Networks, Inc. | Untethered access point mesh system and method |
US9191799B2 (en) * | 2006-06-09 | 2015-11-17 | Juniper Networks, Inc. | Sharing data between wireless switches system and method |
US8340110B2 (en) * | 2006-09-15 | 2012-12-25 | Trapeze Networks, Inc. | Quality of service provisioning for wireless networks |
US7873061B2 (en) | 2006-12-28 | 2011-01-18 | Trapeze Networks, Inc. | System and method for aggregation and queuing in a wireless network |
US20080226075A1 (en) * | 2007-03-14 | 2008-09-18 | Trapeze Networks, Inc. | Restricted services for wireless stations |
US20080276303A1 (en) * | 2007-05-03 | 2008-11-06 | Trapeze Networks, Inc. | Network Type Advertising |
US20080320108A1 (en) * | 2007-06-20 | 2008-12-25 | Microsoft Corporation | Management Policies For Dense Wireless Access Point Infrastructures in Wireless Local Area Networks |
US7907562B2 (en) * | 2007-06-20 | 2011-03-15 | Microsoft Corporation | Managing dense wireless access point infrastructures in wireless local area networks |
US8902904B2 (en) * | 2007-09-07 | 2014-12-02 | Trapeze Networks, Inc. | Network assignment based on priority |
US8238942B2 (en) * | 2007-11-21 | 2012-08-07 | Trapeze Networks, Inc. | Wireless station location detection |
CA2619092C (en) * | 2008-01-29 | 2015-05-19 | Solutioninc Limited | Method of and system for support of user devices roaming between routing realms by a single network server |
US8150357B2 (en) | 2008-03-28 | 2012-04-03 | Trapeze Networks, Inc. | Smoothing filter for irregular update intervals |
US8978105B2 (en) | 2008-07-25 | 2015-03-10 | Trapeze Networks, Inc. | Affirming network relationships and resource access via related networks |
US8238298B2 (en) * | 2008-08-29 | 2012-08-07 | Trapeze Networks, Inc. | Picking an optimal channel for an access point in a wireless network |
US8665886B2 (en) * | 2009-03-26 | 2014-03-04 | Brocade Communications Systems, Inc. | Redundant host connection in a routed network |
CA2672642C (en) * | 2009-07-17 | 2013-05-14 | Solutioninc Limited | Remote roaming controlling system, visitor based network server, and method of controlling remote roaming of user devices |
US8369335B2 (en) | 2010-03-24 | 2013-02-05 | Brocade Communications Systems, Inc. | Method and system for extending routing domain to non-routing end stations |
US9716672B2 (en) | 2010-05-28 | 2017-07-25 | Brocade Communications Systems, Inc. | Distributed configuration management for virtual cluster switching |
US9001824B2 (en) | 2010-05-18 | 2015-04-07 | Brocade Communication Systems, Inc. | Fabric formation for virtual cluster switching |
US9231890B2 (en) | 2010-06-08 | 2016-01-05 | Brocade Communications Systems, Inc. | Traffic management for virtual cluster switching |
US8989186B2 (en) | 2010-06-08 | 2015-03-24 | Brocade Communication Systems, Inc. | Virtual port grouping for virtual cluster switching |
US9461840B2 (en) | 2010-06-02 | 2016-10-04 | Brocade Communications Systems, Inc. | Port profile management for virtual cluster switching |
US8867552B2 (en) | 2010-05-03 | 2014-10-21 | Brocade Communications Systems, Inc. | Virtual cluster switching |
US9769016B2 (en) | 2010-06-07 | 2017-09-19 | Brocade Communications Systems, Inc. | Advanced link tracking for virtual cluster switching |
US8625616B2 (en) | 2010-05-11 | 2014-01-07 | Brocade Communications Systems, Inc. | Converged network extension |
US9270486B2 (en) | 2010-06-07 | 2016-02-23 | Brocade Communications Systems, Inc. | Name services for virtual cluster switching |
US8634308B2 (en) | 2010-06-02 | 2014-01-21 | Brocade Communications Systems, Inc. | Path detection in trill networks |
US8885488B2 (en) | 2010-06-02 | 2014-11-11 | Brocade Communication Systems, Inc. | Reachability detection in trill networks |
US9806906B2 (en) | 2010-06-08 | 2017-10-31 | Brocade Communications Systems, Inc. | Flooding packets on a per-virtual-network basis |
US9628293B2 (en) | 2010-06-08 | 2017-04-18 | Brocade Communications Systems, Inc. | Network layer multicasting in trill networks |
US9246703B2 (en) | 2010-06-08 | 2016-01-26 | Brocade Communications Systems, Inc. | Remote port mirroring |
US9608833B2 (en) | 2010-06-08 | 2017-03-28 | Brocade Communications Systems, Inc. | Supporting multiple multicast trees in trill networks |
US8446914B2 (en) | 2010-06-08 | 2013-05-21 | Brocade Communications Systems, Inc. | Method and system for link aggregation across multiple switches |
US9807031B2 (en) | 2010-07-16 | 2017-10-31 | Brocade Communications Systems, Inc. | System and method for network configuration |
JP6066997B2 (en) | 2011-05-01 | 2017-01-25 | ラッカス ワイヤレス, インコーポレイテッド | Remote cable access point reset |
US9270572B2 (en) | 2011-05-02 | 2016-02-23 | Brocade Communications Systems Inc. | Layer-3 support in TRILL networks |
US9401861B2 (en) | 2011-06-28 | 2016-07-26 | Brocade Communications Systems, Inc. | Scalable MAC address distribution in an Ethernet fabric switch |
US9407533B2 (en) | 2011-06-28 | 2016-08-02 | Brocade Communications Systems, Inc. | Multicast in a trill network |
US8879549B2 (en) | 2011-06-28 | 2014-11-04 | Brocade Communications Systems, Inc. | Clearing forwarding entries dynamically and ensuring consistency of tables across ethernet fabric switch |
US8948056B2 (en) | 2011-06-28 | 2015-02-03 | Brocade Communication Systems, Inc. | Spanning-tree based loop detection for an ethernet fabric switch |
US9007958B2 (en) | 2011-06-29 | 2015-04-14 | Brocade Communication Systems, Inc. | External loop detection for an ethernet fabric switch |
US8885641B2 (en) | 2011-06-30 | 2014-11-11 | Brocade Communication Systems, Inc. | Efficient trill forwarding |
US9736085B2 (en) | 2011-08-29 | 2017-08-15 | Brocade Communications Systems, Inc. | End-to end lossless Ethernet in Ethernet fabric |
US9699117B2 (en) | 2011-11-08 | 2017-07-04 | Brocade Communications Systems, Inc. | Integrated fibre channel support in an ethernet fabric switch |
US9450870B2 (en) | 2011-11-10 | 2016-09-20 | Brocade Communications Systems, Inc. | System and method for flow management in software-defined networks |
US8995272B2 (en) | 2012-01-26 | 2015-03-31 | Brocade Communication Systems, Inc. | Link aggregation in software-defined networks |
US8756668B2 (en) | 2012-02-09 | 2014-06-17 | Ruckus Wireless, Inc. | Dynamic PSK for hotspots |
US9742693B2 (en) | 2012-02-27 | 2017-08-22 | Brocade Communications Systems, Inc. | Dynamic service insertion in a fabric switch |
US9154416B2 (en) | 2012-03-22 | 2015-10-06 | Brocade Communications Systems, Inc. | Overlay tunnel in a fabric switch |
US9092610B2 (en) | 2012-04-04 | 2015-07-28 | Ruckus Wireless, Inc. | Key assignment for a brand |
US9374301B2 (en) | 2012-05-18 | 2016-06-21 | Brocade Communications Systems, Inc. | Network feedback in software-defined networks |
US10277464B2 (en) | 2012-05-22 | 2019-04-30 | Arris Enterprises Llc | Client auto-configuration in a multi-switch link aggregation |
EP2853066B1 (en) | 2012-05-23 | 2017-02-22 | Brocade Communications Systems, Inc. | Layer-3 overlay gateways |
US9602430B2 (en) | 2012-08-21 | 2017-03-21 | Brocade Communications Systems, Inc. | Global VLANs for fabric switches |
US9401872B2 (en) | 2012-11-16 | 2016-07-26 | Brocade Communications Systems, Inc. | Virtual link aggregations across multiple fabric switches |
US9350680B2 (en) | 2013-01-11 | 2016-05-24 | Brocade Communications Systems, Inc. | Protection switching over a virtual link aggregation |
US9413691B2 (en) | 2013-01-11 | 2016-08-09 | Brocade Communications Systems, Inc. | MAC address synchronization in a fabric switch |
US9548926B2 (en) | 2013-01-11 | 2017-01-17 | Brocade Communications Systems, Inc. | Multicast traffic load balancing over virtual link aggregation |
US9565113B2 (en) | 2013-01-15 | 2017-02-07 | Brocade Communications Systems, Inc. | Adaptive link aggregation and virtual link aggregation |
US9565099B2 (en) | 2013-03-01 | 2017-02-07 | Brocade Communications Systems, Inc. | Spanning tree in fabric switches |
US9401818B2 (en) | 2013-03-15 | 2016-07-26 | Brocade Communications Systems, Inc. | Scalable gateways for a fabric switch |
US9565028B2 (en) | 2013-06-10 | 2017-02-07 | Brocade Communications Systems, Inc. | Ingress switch multicast distribution in a fabric switch |
US9699001B2 (en) | 2013-06-10 | 2017-07-04 | Brocade Communications Systems, Inc. | Scalable and segregated network virtualization |
US9806949B2 (en) | 2013-09-06 | 2017-10-31 | Brocade Communications Systems, Inc. | Transparent interconnection of Ethernet fabric switches |
US9912612B2 (en) | 2013-10-28 | 2018-03-06 | Brocade Communications Systems LLC | Extended ethernet fabric switches |
US9548873B2 (en) | 2014-02-10 | 2017-01-17 | Brocade Communications Systems, Inc. | Virtual extensible LAN tunnel keepalives |
US10581758B2 (en) | 2014-03-19 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Distributed hot standby links for vLAG |
US10476698B2 (en) | 2014-03-20 | 2019-11-12 | Avago Technologies International Sales Pte. Limited | Redundent virtual link aggregation group |
US10063473B2 (en) | 2014-04-30 | 2018-08-28 | Brocade Communications Systems LLC | Method and system for facilitating switch virtualization in a network of interconnected switches |
US9800471B2 (en) | 2014-05-13 | 2017-10-24 | Brocade Communications Systems, Inc. | Network extension groups of global VLANs in a fabric switch |
US10616108B2 (en) | 2014-07-29 | 2020-04-07 | Avago Technologies International Sales Pte. Limited | Scalable MAC address virtualization |
US9544219B2 (en) | 2014-07-31 | 2017-01-10 | Brocade Communications Systems, Inc. | Global VLAN services |
US9807007B2 (en) | 2014-08-11 | 2017-10-31 | Brocade Communications Systems, Inc. | Progressive MAC address learning |
US9524173B2 (en) | 2014-10-09 | 2016-12-20 | Brocade Communications Systems, Inc. | Fast reboot for a switch |
US9699029B2 (en) | 2014-10-10 | 2017-07-04 | Brocade Communications Systems, Inc. | Distributed configuration management in a switch group |
US9626255B2 (en) | 2014-12-31 | 2017-04-18 | Brocade Communications Systems, Inc. | Online restoration of a switch snapshot |
US9628407B2 (en) | 2014-12-31 | 2017-04-18 | Brocade Communications Systems, Inc. | Multiple software versions in a switch group |
US9942097B2 (en) | 2015-01-05 | 2018-04-10 | Brocade Communications Systems LLC | Power management in a network of interconnected switches |
US10003552B2 (en) | 2015-01-05 | 2018-06-19 | Brocade Communications Systems, Llc. | Distributed bidirectional forwarding detection protocol (D-BFD) for cluster of interconnected switches |
US9807005B2 (en) | 2015-03-17 | 2017-10-31 | Brocade Communications Systems, Inc. | Multi-fabric manager |
US10038592B2 (en) | 2015-03-17 | 2018-07-31 | Brocade Communications Systems LLC | Identifier assignment to a new switch in a switch group |
US10579406B2 (en) | 2015-04-08 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Dynamic orchestration of overlay tunnels |
US10439929B2 (en) | 2015-07-31 | 2019-10-08 | Avago Technologies International Sales Pte. Limited | Graceful recovery of a multicast-enabled switch |
US10171303B2 (en) | 2015-09-16 | 2019-01-01 | Avago Technologies International Sales Pte. Limited | IP-based interconnection of switches with a logical chassis |
US9912614B2 (en) | 2015-12-07 | 2018-03-06 | Brocade Communications Systems LLC | Interconnection of switches based on hierarchical overlay tunneling |
CN106358189B (en) * | 2016-09-05 | 2020-01-10 | 北京小米移动软件有限公司 | Method and device for accessing wireless local area network |
US10237090B2 (en) | 2016-10-28 | 2019-03-19 | Avago Technologies International Sales Pte. Limited | Rule-based network identifier mapping |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5325362A (en) * | 1993-09-29 | 1994-06-28 | Sun Microsystems, Inc. | Scalable and efficient intra-domain tunneling mobile-IP scheme |
US5442633A (en) * | 1992-07-08 | 1995-08-15 | International Business Machines Corporation | Shortcut network layer routing for mobile hosts |
US5825759A (en) * | 1994-10-26 | 1998-10-20 | Telefonaktiebolaget Lm Ericsson | Distributing network services and resources in a mobile communications network |
US5875185A (en) * | 1995-10-10 | 1999-02-23 | Industrial Technology Research Inst. | Seamless handoff for a wireless lan/wired lan internetworking |
US6161008A (en) * | 1998-11-23 | 2000-12-12 | Nortel Networks Limited | Personal mobility and communication termination for users operating in a plurality of heterogeneous networks |
US6160804A (en) * | 1998-11-13 | 2000-12-12 | Lucent Technologies Inc. | Mobility management for a multimedia mobile network |
US6230012B1 (en) * | 1998-08-07 | 2001-05-08 | Qualcomm Incorporated | IP mobility support using proxy mobile node registration |
US6535493B1 (en) * | 1998-01-15 | 2003-03-18 | Symbol Technologies, Inc. | Mobile internet communication protocol |
US20030185172A1 (en) * | 2002-03-27 | 2003-10-02 | Seon-Soo Rue | Apparatus and method for supporting mobility between subnetworks of mobile node in wireless LAN |
US20030210671A1 (en) * | 2002-05-08 | 2003-11-13 | Siemens Canada Limited | Local area network with wireless client freedom of movement |
US20040103282A1 (en) * | 2002-11-26 | 2004-05-27 | Robert Meier | 802.11 Using a compressed reassociation exchange to facilitate fast handoff |
US20040105440A1 (en) * | 2002-11-27 | 2004-06-03 | 3Com Corporation | Packet-switched network and network switches having a network layer forwarding action performed by data link switching |
US6822955B1 (en) * | 1998-01-22 | 2004-11-23 | Nortel Networks Limited | Proxy server for TCP/IP network address portability |
US20040255033A1 (en) * | 2001-06-07 | 2004-12-16 | Jonathan Edney | Security in area networks |
US20050018637A1 (en) * | 2003-07-08 | 2005-01-27 | Theodore Karoubalis | Method and system for seamless mobility of mobile terminals in a wireless network |
US20050041674A1 (en) * | 2003-01-27 | 2005-02-24 | International Business Machines Corporation | Method for forwarding data packets by a router |
US20050083883A1 (en) * | 2003-10-20 | 2005-04-21 | Jan-Ming Ho | Mobile network agent |
US7190668B1 (en) * | 2001-11-27 | 2007-03-13 | Nokia Corporation | Method of anchoring flows |
US20080032637A1 (en) * | 2006-07-19 | 2008-02-07 | Research In Motion Limited | Handheld mobile communication device with moveable display/cover member |
US7624270B2 (en) * | 2002-11-26 | 2009-11-24 | Cisco Technology, Inc. | Inter subnet roaming system and method |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6445922B1 (en) * | 1999-12-15 | 2002-09-03 | Lucent Technologies Inc. | Method and system for support of overlapping IP addresses between an interworking function and a mobile IP foreign agent |
US7379433B1 (en) * | 2002-09-25 | 2008-05-27 | Cisco Technology, Inc. | Methods and apparatus for broadcast optimization in mobile IP |
CN101715194A (en) * | 2002-10-18 | 2010-05-26 | 卡耐特无线有限公司 | Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system |
-
2004
- 2004-02-23 US US10/785,596 patent/US7477894B1/en not_active Expired - Fee Related
-
2008
- 2008-10-31 US US12/263,356 patent/US20090275328A1/en not_active Abandoned
-
2014
- 2014-03-10 US US14/202,296 patent/US20140187241A1/en not_active Abandoned
Patent Citations (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5442633A (en) * | 1992-07-08 | 1995-08-15 | International Business Machines Corporation | Shortcut network layer routing for mobile hosts |
US5325362A (en) * | 1993-09-29 | 1994-06-28 | Sun Microsystems, Inc. | Scalable and efficient intra-domain tunneling mobile-IP scheme |
US5825759A (en) * | 1994-10-26 | 1998-10-20 | Telefonaktiebolaget Lm Ericsson | Distributing network services and resources in a mobile communications network |
US5875185A (en) * | 1995-10-10 | 1999-02-23 | Industrial Technology Research Inst. | Seamless handoff for a wireless lan/wired lan internetworking |
US6535493B1 (en) * | 1998-01-15 | 2003-03-18 | Symbol Technologies, Inc. | Mobile internet communication protocol |
US6822955B1 (en) * | 1998-01-22 | 2004-11-23 | Nortel Networks Limited | Proxy server for TCP/IP network address portability |
US6230012B1 (en) * | 1998-08-07 | 2001-05-08 | Qualcomm Incorporated | IP mobility support using proxy mobile node registration |
US6256300B1 (en) * | 1998-11-13 | 2001-07-03 | Lucent Technologies Inc. | Mobility management for a multimedia mobile network |
US6160804A (en) * | 1998-11-13 | 2000-12-12 | Lucent Technologies Inc. | Mobility management for a multimedia mobile network |
US6161008A (en) * | 1998-11-23 | 2000-12-12 | Nortel Networks Limited | Personal mobility and communication termination for users operating in a plurality of heterogeneous networks |
US20040255033A1 (en) * | 2001-06-07 | 2004-12-16 | Jonathan Edney | Security in area networks |
US7190668B1 (en) * | 2001-11-27 | 2007-03-13 | Nokia Corporation | Method of anchoring flows |
US20030185172A1 (en) * | 2002-03-27 | 2003-10-02 | Seon-Soo Rue | Apparatus and method for supporting mobility between subnetworks of mobile node in wireless LAN |
US20030210671A1 (en) * | 2002-05-08 | 2003-11-13 | Siemens Canada Limited | Local area network with wireless client freedom of movement |
US20040103282A1 (en) * | 2002-11-26 | 2004-05-27 | Robert Meier | 802.11 Using a compressed reassociation exchange to facilitate fast handoff |
US7624270B2 (en) * | 2002-11-26 | 2009-11-24 | Cisco Technology, Inc. | Inter subnet roaming system and method |
US20040105440A1 (en) * | 2002-11-27 | 2004-06-03 | 3Com Corporation | Packet-switched network and network switches having a network layer forwarding action performed by data link switching |
US20050041674A1 (en) * | 2003-01-27 | 2005-02-24 | International Business Machines Corporation | Method for forwarding data packets by a router |
US20050018637A1 (en) * | 2003-07-08 | 2005-01-27 | Theodore Karoubalis | Method and system for seamless mobility of mobile terminals in a wireless network |
US20050083883A1 (en) * | 2003-10-20 | 2005-04-21 | Jan-Ming Ho | Mobile network agent |
US20080032637A1 (en) * | 2006-07-19 | 2008-02-07 | Research In Motion Limited | Handheld mobile communication device with moveable display/cover member |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080002607A1 (en) * | 2006-06-30 | 2008-01-03 | Ramakrishnan Nagarajan | Technique for handling layer 2 roaming in a network of wireless switches supporting layer 3 mobility within a mobility domain |
US20090034470A1 (en) * | 2007-07-31 | 2009-02-05 | Symbol Technologies, Inc. | Forwarding broadcast/multicast data when wireless clients layer 3 roam across ip subnets in a wlan |
US7885233B2 (en) * | 2007-07-31 | 2011-02-08 | Symbol Technologies, Inc. | Forwarding broadcast/multicast data when wireless clients layer 3 roam across IP subnets in a WLAN |
Also Published As
Publication number | Publication date |
---|---|
US20140187241A1 (en) | 2014-07-03 |
US7477894B1 (en) | 2009-01-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7477894B1 (en) | Methods and apparatus for handling wireless roaming among and across wireless area networks | |
US8102811B2 (en) | Providing mobility management protocol information to a mobile terminal for performing handover in a mobile communication system | |
Le et al. | A review of mobility support paradigms for the internet. | |
US7353027B2 (en) | Seamless handoff in mobile IP | |
US7586879B2 (en) | Client roaming from a first access node to a second access node within a wireless network | |
US7583635B2 (en) | Establishing network address of mobile terminal in mobile communication system | |
US7606201B2 (en) | Handover enabler | |
US8175102B2 (en) | Neighbor discovery method and apparatus for mobile node in heterogeneous network environment | |
US9294548B2 (en) | Mobility handling in a communication network | |
US20060251101A1 (en) | Tunnel establishment | |
IL185710A (en) | Providing mobility management protocol information to a mobile terminal for performing handover in a mobile communication system | |
US7420943B2 (en) | Mechanism to create pinhole for existing session in middlebox | |
JP4919973B2 (en) | Method and apparatus for setting network address of mobile terminal in mobile communication system | |
JP2008160665A (en) | Switching method between heterogeneous communication interfaces, mobile terminal and management device | |
JP3669366B2 (en) | Mobile terminal and network interface switching method | |
KR101035817B1 (en) | Method for forming internet address of mobile station in wireless internet service | |
Dunmore et al. | of Deliverable: Final MIPv6 Support Guide | |
Barsk | A seamless vertical handover system prototype |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATE Free format text: SECURITY AGREEMENT;ASSIGNORS:BROCADE COMMUNICATIONS SYSTEMS, INC.;FOUNDRY NETWORKS, LLC;INRANGE TECHNOLOGIES CORPORATION;AND OTHERS;REEL/FRAME:023814/0587 Effective date: 20100120 |
|
AS | Assignment |
Owner name: FOUNDRY NETWORKS, LLC, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:FOUNDRY NETWORKS, INC.;REEL/FRAME:024733/0739 Effective date: 20090511 |
|
AS | Assignment |
Owner name: FOUNDRY NETWORKS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SINHA, VISHAL;REEL/FRAME:026264/0640 Effective date: 20040220 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: FOUNDRY NETWORKS, LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT;REEL/FRAME:034804/0793 Effective date: 20150114 Owner name: BROCADE COMMUNICATIONS SYSTEMS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT;REEL/FRAME:034804/0793 Effective date: 20150114 |