WO2004028049A1 - Procede et systeme de gestion de reseau dans un reseau cable/sans fil hybride - Google Patents

Procede et systeme de gestion de reseau dans un reseau cable/sans fil hybride Download PDF

Info

Publication number
WO2004028049A1
WO2004028049A1 PCT/US2003/028337 US0328337W WO2004028049A1 WO 2004028049 A1 WO2004028049 A1 WO 2004028049A1 US 0328337 W US0328337 W US 0328337W WO 2004028049 A1 WO2004028049 A1 WO 2004028049A1
Authority
WO
WIPO (PCT)
Prior art keywords
switch
access point
access
message
qos
Prior art date
Application number
PCT/US2003/028337
Other languages
English (en)
Inventor
Ed H. Frank
Richard Martin
Original Assignee
Broadcom Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Broadcom Corporation filed Critical Broadcom Corporation
Priority to EP03749562A priority Critical patent/EP1543640A4/fr
Publication of WO2004028049A1 publication Critical patent/WO2004028049A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/2898—Subscriber equipments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2416—Real-time traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/726—Reserving resources in multiple paths to be used simultaneously
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/765—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points
    • H04L47/767—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points after changing the attachment point, e.g. after hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/801—Real time traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/822—Collecting or measuring resource availability data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/824—Applicable to portable or mobile terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/351—Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H04W16/16—Spectrum sharing arrangements between different networks for PBS [Private Base Station] arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/20—Support for services
    • H04L49/205—Quality of Service based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/14—Multichannel or multilink protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • Embodiments of the present application relate generally to local area networks, and more particularly to a system and method for managing a hybrid wired/wireless local area network (WLAN).
  • WLAN wireless local area network
  • FIG. 1a is a block diagram 100 of the OSI model.
  • the OSI model has seven distinct functional layers including layer 7, an application layer 114; layer 6, a presentation layer 112; layer 5, a session layer 110; layer 4, a transport layer 108, layer 3, a network layer 106; layer 2: a data link layer 104; and layer 1 , a physical layer 102.
  • the physical layer 102 may further include a physical layer convergence procedure (PLCP) sublayer 102b and a physical media dependent sublayer 102a.
  • the data link layer 104 may also include a Medium access control (MAC) layer 104a.
  • MAC Medium access control
  • each OSI layer describes certain tasks which are necessary for facilitating the transfer of information through interfacing layers and ultimately through the network. Notwithstanding, the OSI model does not describe any particular implementation of the various layers.
  • OSI layers 1 to 4 generally handle network control and data transmission and reception, generally referred to as end-to-end network services.
  • Layers 5 to 7 handle application issues, generally referred to as application services.
  • Specific functions of each layer may vary depending on factors such as protocol and/or interface requirements or specifications that are necessary for implementation of a particular layer.
  • the Ethernet protocol may provide collision detection and carrier sensing in the physical layer.
  • Layer 1 the physical layer 102, is responsible for handling all electrical, optical, opto- electrical and mechanical requirements for interfacing to the communication media.
  • the physical layer 102 may facilitate the transfer of electrical signals representing an information bitstream.
  • the physical layer 102 may also provide services such as, encoding, decoding, synchronization, clock data recovery, and transmission and reception of bit streams.
  • the PLCP layer 102b may be configured to adapt and map services provided by the physical layer 102 to the functions provided by the device specific PMD sublayer 102a.
  • the PLCP layer 102b may be adapted to map PHY sublayer service data units (PDSUs) into a suitable packet and/or framing format necessary for providing communication services between two or more entities communicating via the physical medium.
  • the PMD layer 102a specifies the actual methodology and/or protocols which may be used for receiving and transmitting via the physical medium.
  • the MAC sublayer 104a may be adapted to provide, for example, any necessary drivers which may be utilized to access the functions and services provided by the PLCP sublayer 102b. Accordingly, higher layer services may be adapted to utilize the services provided by the MAC sublayer 104a with little or no dependence on the PMD sublayer 102a.
  • the 802.11 is a suite of specifications promulgated by the Institute of Electrical and Electronics Engineers (IEEE), which provide communication standards for the MAC and physical (PHY) layer of the OSI model.
  • IEEE Institute of Electrical and Electronics Engineers
  • the 801.11 standard also provides communication standards for wired and wireless local area networks (WLANs). More specifically, the 802.11 standard specifies five (5) types of physical layers for WLANs. These include, frequency hopping spread spectrum (FHSS), direct sequence spread spectrum (DSSS), infrared (IR) communication, high rate direct sequence spread spectrum spread spectrum (HR-DSS) and orthogonal frequency division multiplexing (OFDM).
  • FHSS frequency hopping spread spectrum
  • DSSS direct sequence spread spectrum
  • IR infrared
  • HR-DSS high rate direct sequence spread spectrum spread spectrum
  • OFDM orthogonal frequency division multiplexing
  • the 802.11 standard also provides a PLCP frame format for each of the specified PHY layers.
  • Ethernet speeds being increased from about 1-2 megabit per second (Mbps), to 10 Mbps, to 100 Mbps, to 1 gigabit per second (Gbps) to 10 Gbps.
  • 802.11b, 802.11a and 802.11g which have been adapted to facilitate the demands for increased data rates.
  • the 802.11g standard for example, provides a maximum data rate of about 54 Mbps at a transmitter/receiver range of 19 meters (m) in a frequency range of 2.4 GHz to 2.4835 GHz.
  • the 802.11b standard for example, provides a maximum data rate of about 11 Mbps at a transmitter/receiver range of 57 meters (m) in a frequency range of 2.4 GHz to 2.4835 GHz.
  • the 802.11a standard for example, may be adapted to provide a maximum data rate of about 54 Mbps at a transmitter/receiver range of 12 meters (m) in a 300 MHz segmented bandwidth ranging from 5.150 GHz to 5.350 GHz and from 5.725 GHz to 5.825 GHz.
  • the 802.11 standard forms the basis of the other standards in the suite of specifications, and the 802.11b, 802.11a and 802.11g standards provide various enhancements and new features to their predecessor standards.
  • CSMA/CA carrier sense multiple access with collision avoidance
  • CSMA/CA utilizes a simple negotiation scheme to permit access to a communication medium. If a transmitting entity wishes to transmit information to a receiving entity, the transmitting entity may sense the communication medium for communication traffic. In a case where the communication medium is busy, the transmitting entity may desist from making a transmission and attempt transmission at a subsequent time. In a case where the communication transmission is not busy, then the transmitting entity may send information over the communication medium. Notwithstanding, there may be a case where two or more transmission entities sense that the communication medium is not busy and attempt transmission at the same instant.
  • a CSMA/OA or ready to send (RTS) and clear to send (CTS) messaging scheme may be employed, for example.
  • RTS ready to send
  • CTS clear to send
  • a transmitting device may send a ready to send message to one or more receiving device.
  • the receiving device may send a clear to send message.
  • the transmitting device may initiate transfer of data to the receiving device.
  • the receiving device may acknowledge the received frames.
  • Wi-Fi wireless fidelity
  • 802.11 utilizes one of two modulation formats including direct sequence spread spectrum (DSS) using differential binary phase shift keying and frequency hopping spread spectrum (11 -bit Barker sequence), 802.11b utilizes a higher data rate form of DSS called complementary code keying (CCK). CCK permits higher data rate and particularly less susceptible to interference effects such as multipath-propagation interference, the PSK.
  • DSS direct sequence spread spectrum
  • CCK complementary code keying
  • 802.11a utilizes orthogonal frequency-division multiplexing (OFDM) modulation/encoding scheme, which provides a maximum data rate 54 Mbps.
  • OFDM orthogonal frequency-division multiplexing
  • Orthogonal frequency-division multiplexing is a digital modulation technique which splits a signal into several narrowband channels, with each channel having a different frequency. Each narrowband channel is arranged so as to minimize the effects of crosstalk between the channels and symbols in the data stream.
  • 802.11a equipment will not interoperate with equipment designed to operate with the 802.11b standard which defines operation in the 2.4 to 2.4835 GHz frequency band.
  • 802.11b standard which defines operation in the 2.4 to 2.4835 GHz frequency band.
  • One major drawback is that companies that have invested in 802.11b equipment and infrastructure may not readily upgrade their network without significant expenditure.
  • the 802.11g standard was developed as an extension to 802.11b standard.
  • the 802.11g standard may utilize a similar OFDM modulation scheme as the 802.11a standard and delivers speeds comparable with the 802.11a standard. Since 802.11g compatible equipment operates in the same portion of the electromagnetic spectrum as 802.11b compatible equipment, 802.11g is backwards compatible with existing 802.11 b WLAN infrastructures. Due to backward compatibility of 802.11g with 802.11b, it would be desirable to have an 802.11b compliant radio card capable of interfacing directly with an 802.11g compliant access point and also an 802.11g compliant radio card capable of interfacing directly with an 802.11 b compliant access point.
  • 802.11g compatible equipment operates in the 2.4 GHz to 2.4835 GHz frequency range
  • a typical transmitted signal utilizes a bandwidth of approximately 22 MHz, about a third or 30% of the total allocated bandwidth. This limits the number of non-overlapping channels utilized by an 802.11g access point to three (3).
  • RF interference may pose additional operational problems with 802.11b and 802.11g equipment designed to operate in the 2.4 GHz portion of the electromagnetic spectrum.
  • the 2.4 GHz portion of the spectrum is an unlicensed region which has been utilized for some time and is crowded with potential interfering devices. Some of these devices include cordless telephone, microwave ovens, intercom systems and baby monitors. Other potential interfering devices may be Bluetooth devices. Accordingly, interference poses interference problems with the 802.11b and 802.11g standards.
  • 802.11a compatible equipment utilizes eight non-overlapping channels, as compared to three non-overlapping channels utilized by 802.11b. Accordingly, 802.11a access points may be deployed in a more dense manner than, for example 802.11b compatible equipment. For example, up to twelve access points each having a different assigned frequency may be deployed in a given area without causing co-channel interference. Consequently, 802.11a may be particularly useful in overcoming some of the problems associated with channel assignment, especially in areas that may have a dense user population and where increased throughput may be critical. Notwithstanding, the higher operating frequency of 802.11a causes more attenuation resulting in a shorter operating range at a given data rate. This may significantly increase deployment cost since a larger number of access points are required to service a given service area.
  • a method for network management in a hybrid wired/wireless local area network may include receiving from a first access point and/or a first switch, a first messaging protocol message containing quality of service (QoS) information. Responsive to the first messaging protocol message, at least a minimum QoS level for operation of the first switch, the first access point, a second access point and/or a second switch, may be determined. QoS information corresponding to at least the minimum QoS level may be distributed to the first switch, the first access point, the second access point and the second switch, using a second messaging protocol message.
  • QoS quality of service
  • QoS information may be distributed to at least a portion of the hybrid wired/wireless local area network.
  • the method may further include the step of providing access to at least one of a plurality access devices based on the distributed QoS information. Traffic associated with at least one of the plurality of access devices may be queued to maintain at least the minimum QoS level. The traffic associated with the plurality of access devices may be prioritized to maintain at least the minimum QoS level. Access to one or more access points by one or more access devices may be achieved on a scheduled basis. Bandwidth may be allocated and/or de-allocated to maintain at least the minimum QoS level. To maintain at least the minimum QoS level, a load on at least one of the first switch, the first access point, the second access point and the second switch may be balanced.
  • Another embodiment of the invention may provide a machine-readable storage, having stored thereon a computer program having at least one code section for providing network management for a switch in a hybrid wired/wireless local area network, the at least one code section being executable by a machine for causing the machine to perform the steps described above.
  • the system for network management may include at least one receiver, which may be adapted to receive from a first access point and/or a first switch, a first messaging protocol message containing quality of service (QoS) information.
  • At least one controller may be adapted to determine at least a minimum QoS level for operation of the first switch, the first access point, a second access point, and/or a second switch in response to the first messaging protocol message.
  • One of the controllers may be adapted to distribute QoS information corresponding to the determined minimum QoS level to the first switch, the first access point, the second access point and/or the second switch, using a second messaging protocol message.
  • the controller may further be adapted to provide access to one or more access devices based on the distributed QoS information.
  • a queue may be adapted to queue traffic associated with one or more access devices by the controller in order to maintain a minimum QoS level.
  • the controller may be further adapted to prioritize the traffic associated with any of the access devices to ensure that the determined minimum QoS level may be maintained.
  • the controller may be further adapted to schedule access by one or more of the access devices to either of he first and second access points.
  • the controller may be further adapted to distribute QoS information to at least a portion of the hybrid wired/wireless local area network. At least one of the controllers may be adapted to allocate bandwidth to maintain at least a minimum QoS level. The allocation may be dynamically achieved.
  • One or more of the controllers may be adapted to balance a load on the first switch, the first access point, the second access point and/or the second switch to maintain the minimum QoS level.
  • the first and second messaging protocol messages may be one or more of an access point status message, access point configuration message, a switch status message, a switch configuration message, a client status message and a device discovery message.
  • the at least one controller may be one or more of a bandwidth management controller, a quality of service controller, a load balancing controller a session controller, a processor and a network management controller.
  • FIG. 1a is a block diagram of the OSI model.
  • FIG. 1b is a block diagram illustrating a general PLCP frame as defined by 802.11.
  • FIG. 1c is a block diagram illustrating a PLCP frame utilized by frequency hopping spread spectrum as defined by 802.11.
  • FIG. 1d is a block diagram illustrating a PLCP frame for direct sequence spread spectrum and high rate direct sequence spread spectrum as defined by 802.11.
  • FIG. 1e is a block diagram illustrating a PLCP frame for orthogonal frequency division multiplexing as defined by 802.11.
  • FIG. 2 is a block diagram of an exemplary system for network management in a wireless local area network in accordance with an embodiment of the invention.
  • FIG. 3 is a block diagram of an exemplary Enterprise Wireless LAN having switches serving as the edge managers in accordance with an embodiment of the invention.
  • FIG. 4 is a block diagram of an exemplary switch as illustrated in FIG. 2 and FIG. 3 in accordance with an embodiment of the invention.
  • FIG. 5 is a block diagram of an exemplary switching system for bandwidth management in a wireless local area network in accordance with an embodiment of the invention.
  • FIG. 6 is a block diagram of an exemplary session control process with respect to FIG. 5 that may be utilized by the switching system for bandwidth management in accordance with an embodiment of the invention.
  • FIG. 7 is a block diagram of an exemplary load balancing process with respect to FIG. 5 that may be utilized by the switching system for bandwidth management in accordance with an embodiment of the invention.
  • FIG. 8 is a block diagram of an exemplary QoS enabling process with respect to FIG. 5 that may be utilized by the switching system for bandwidth management in accordance with an embodiment of the invention.
  • FIG. 9a is a flowchart of exemplary steps for a QoS enabling process that may be utilized by the switching system for network management in accordance with an embodiment of the invention.
  • FIG. 9b is a flowchart of exemplary steps for a QoS enabling process that may be utilized by the switching system for network management in accordance with an embodiment of the invention.
  • a method for network management in a hybrid wired/wireless local area network may include receiving from a first access point and/or a first switch, a first messaging protocol message containing quality of service (QoS) information. Responsive to the first messaging protocol message, at least a minimum QoS level for operation of the first switch, the first access point, a second access point and/or a second switch may be determined. QoS information corresponding to at least the minimum QoS level may be distributed to the first switch, the first access point, the second access point and the second switch, using a second messaging protocol message.
  • QoS quality of service
  • FIG. 1b is a block diagram 120 illustrating a general PLCP frame as defined by 802.11. Referring to FIG. 1b, there is shown preamble 122, PLCP header 124, MAC data 126, and CRC 128. Preamble 122 may include synchronization (SYNC) data 122a and synchronization delimiter 122b.
  • the PLCP header 124 may include, for example PLCP signal field (PSF) 124a, service data 124b, length 124c and other fields.
  • the preamble 122 may be dependent on the PHY.
  • the SYNC data 122a may include a unique bit stream that may be adapted to signal timing parameters such as the start of a frame.
  • the SYNC data 122a is used for bit synchronization and demodulation.
  • the SYNC delimiter 122b provides frame timing information and may be adapted to delimit the end of synchronization information.
  • PLCP header 124 may be adapted to contain information used for decoding the frame.
  • the PSF 124a may be adapted to include communication data rate information.
  • the service data 124b is generally reserved, but may be utilized to provide application specific functionality.
  • the length 124c may be adapted to indicate the length of the MAC data 126. In this regard, the length 124c may be expressed in terms of the time required to transmit the MAC data 126.
  • FIG. 1c is a block diagram 130 illustrating a PLCP frame utilized by frequency hopping spread spectrum as defined by 802.11. Referring to FIG. 1c, there is shown a SYNC data 132, PLCP header 134 and PSDU 136. The
  • PLCP header 134 may include, for example, PSDU length word (PLW) 134a, PLCP signaling field (PSF) 134b, header error check field or CRC 134c and other fields.
  • PSDU length word PLW
  • PSF PLCP signaling field
  • CRC header error check field
  • the PLW 134a may specify the number of octets contained in the PSDU 136.
  • the PSF 134 be may be 4-bits in length and may be used to denote the communication data rate.
  • FIG. 1d is a block diagram 140 illustrating a PLCP frame for direct sequence spread spectrum and high rate direct sequence spread spectrum (HR-DSS) as defined by 802.11.
  • preamble 142 may include synchronization (SYNC) data 142a and synchronization delimiter 142b.
  • SYNC synchronization
  • PLCP header 144 may include PLCP signal field (PSF) 144a, service data 144b, length 144c, and CRC field 144d.
  • the SYNC data 142a may be 128 bits as compared to 8 bits for SYNC data 132a for frequency hopping spread spectrum.
  • the CRC 144d is 16 bits, which is similar to CRC 134c for frequency hopping spread spectrum.
  • FIG. 1e is a block diagram 150 illustrating a PLCP frame for orthogonal frequency division multiplexing as defined by 802.11.
  • preamble 152 may include synchronization (SYNC) data 152a and synchronization delimiter 152b.
  • the PLCP header 154 may include length
  • the length 154a is a 12-bit field that may be adapted to indicate the length of the frame.
  • the PSF 154b is a 4-bit field that may indicate a modulation scheme utilized and its associated coding rate of the PSDU. For example, the specification utilizes binary 1011 to represent 6
  • the reserved field 154c is a 1 bit field that is reserved for future use and may be adapted for application specific use.
  • the parity field 154d may indicate odd or even parity.
  • the tail field 154e is a 6-bit field.
  • the service field 154f is a 16-bit field that may be adapted to indicate the type of service.
  • a switch is provided to facilitate network management between one or more of a plurality of access devices and/or access points, and/or other switches.
  • the switch may utilize a messaging protocol, which may be adapted to facilitate tasks such as quality of service (QoS) control and management, switch filter transfer, bandwidth management, session control and management and/or and load balancing.
  • QoS quality of service
  • the switch in accordance with an aspect of the invention, may be configured to perform various network management tasks for a wired and/or a wireless portion of the network.
  • the task of network management may involve performing one or more activities including, but not limited to, QoS management, bandwidth management including tracking bandwidth usage and allocating and de-allocating bandwidth to meet user and/or client demands.
  • the management of these activities may be directly or indirectly related to providing mobility and operability throughout a wired or wireless LAN, or a hybrid combination thereof.
  • FIG. 2 is a block diagram of an exemplary system for network management in a wireless local area network in accordance with an embodiment of the invention. Referring to FIG. 2, there is illustrated a first networking domain 214 and a second networking domain 234.
  • the first networking domain 214 may include a switch 202, and access points 204,
  • the second networking domain 234 may include a switch 222, and access points 224, 226, 228, 230, 232. Each of access points 224, 226, 208, 230, 232 may be coupled to the switch 222.
  • Switch 222 may be coupled to switch 202 through any one or more of a wired and a wireless medium.
  • at least some of the access points in any one of the networking domains 214, 234 may be coupled to each other. Notwithstanding, a plurality of actual and/or virtual channels may be provided to facilitate communication with the access points and switches.
  • the networking domains 214 and 234 are illustrated as separate networking entities, the invention is not so limited. Accordingly, the networking domain 214, 234 may be part of a single networking entity, but may represent separate security domains within the single networking entity.
  • any one or more of the switches 202, 222 may be adapted to send network management related information and parameters to any one or more of the access points in any one or more of the networking domains 214, 234.
  • switch for example, switch
  • switch 202 may be adapted to communicate QoS management information to access point 206.
  • switch 202 may be adapted to send network management related information to any one or more of access points 204,
  • switch 222 may be adapted to communicate network management related information to any one or more of access points 224,
  • the QoS information and/or network management related information may be used by an access point to efficiently allocate, distribute and/or de-allocate system resources for associating and/or dissociating access devices.
  • the switches 202, 222 may be adapted to provide, for example, certain QoS management activities to the access points using for example a messaging protocol. Accordingly, some activities such as bandwidth policing, bandwidth management, load balancing, roaming and handover may be handled by coordinating one or more switches and one or more access points utilizing, for example, a messaging protocol.
  • a switch for example, switch 222, may be configured to establish rules that may be adapted by the access points 224, 226, 228, 230, 232 in carrying out these activities.
  • the rules may be propagated from the switches 222, 202 to the access points 204, 208, 210, 214, 224, 226, 228,
  • Prioritization and processing may be based on acceptable levels of latency and bandwidth availability. For example, an IP telephone call may be assigned highest queuing and processing priority in order to minimize latency. Policing, for example, may include performing activities which may limit and control the usage of available bandwidth by a particular access device or a type of access device. These and other tasks may be controlled by the switch using the messaging protocol. Although activities such as policing and QoS management may be conducted independently of the bandwidth management, in accordance with an aspect of the invention, bandwidth management related information may be utilized for network and QoS management.
  • any one or more of the access points in any one or more of the networking domains may be adapted to acquire various QoS related information and parameters and communicate the QoS related information to one or more of the switches 202, 222.
  • access point 206 may be adapted to acquire various QoS related information and communicate the acquired information back to the switch 202.
  • any one or more of access points 204, 208, 210, 214 may acquire various bandwidth related information and parameters and communicate the acquired information to switch 202.
  • any one or more of access points 224, 226, 228, 230, 232 may acquire various QoS related information and parameters and communicate the acquired information to the switch 222.
  • any one or more of access points 224, 226, 228, 230, 232 may acquire various QoS related information and parameters and communicate the acquired information to the switch 202 through switch 222.
  • This may be particularly useful in, for example, a roaming scenario or handoff scenario.
  • switch 222 may initiate a query requesting bandwidth related information from switch 202. Consequently, switch 214 may request bandwidth related information from any one or more of access points 204, 206, 208, 210, 212.
  • switch 202 may communicate the information to the switch 222. Accordingly, the switch 222 may decide whether to handoff or permit roaming depending on the QoS and/or bandwidth related information received from the switch 202. Based on, for example, QoS related information received from one or more access devices or switches, a switch may be adapted to force an access device to roam. For example, in a case where the switch determines that there may be insufficient bandwidth or channel capacity to provide a minimal acceptable QoS, then the switch may be adapted to dynamically force existing and/or new incoming access devices to roam. In one aspect of the invention, a list of devices that have been forced to roam may be maintained.
  • a switch may be adapted to signal or notify devices on the list to reattempt establishment of service and permit access to the service provided by the network.
  • any one or more of the switches 202, 222 may be adapted to determine the total available bandwidth for any one or more of a plurality of access points and/or switches. Accordingly, the switches 202 and/or 222 may provide channel/frequency management and quality of service QoS management in order to optimize bandwidth utilization for a plurality of access devices.
  • an access prioritization scheme may be adapted and enforced by, for example, any one or more of the switches 202, 222.
  • the prioritization scheme may include, establishing a priority for all network traffic, honoring prioritized traffic from all clients, and/or honoring prioritized traffic from some select clients such as trusted clients.
  • the switches 202, 222 may be adapted to provide certain QoS management activities to the access points. Accordingly, some activities such as bandwidth policing, bandwidth management, packet prioritization and processing, and service type queuing may be handled by an access point.
  • a switch may be adapted to establish rules that may be utilized by the access points in carrying out these activities in order to maintain at least minimal acceptable level of service.
  • Prioritization and processing may be based on, for example, acceptable levels of latency and bandwidth availability. For example, an IP telephone call may be assigned highest queuing and processing priority in order to minimize latency.
  • Policing for example, may include tasks which limit and control the usage of available bandwidth by a particular access device or a type of access device. Accordingly, bandwidth may be fairly distributed amongst access devices to ensure at least a minimal acceptable level of service.
  • the switch may utilize the messaging protocol (MP) to provide enhanced communication services to one or more of a plurality of access devices or mobile stations in, for example, an enterprise Wireless LAN (WLAN).
  • MP messaging protocol
  • the enhanced communication in addition to ordinary WLAN device communication such as authentication, authorization, key exchanges, beacon broadcast, etc., may provide additional network management features not currently provided by a WLAN to its clients. These additional features may include, but are not limited to, quality of service management, bandwidth management, access control, load balancing and network management.
  • other enterprise WLAN devices that may utilize messaging protocol message transactions may include but are not limited to, wireless access points, enterprise switches and wireless stations. These devices may be messaging protocol enabled in certain instances, to take advantage of the new network management features.
  • the wireless devices may be located at the edge of the network.
  • the wireless devices may be connected or coupled to the enterprise network via the one or more access points, which in turn may be the edge devices of, for example, a wired LAN.
  • the access points may be connected to the LAN via switches.
  • switches which may be called wireless LAN switches, and in certain instances, may not only perform Layer 2 switching, but may be adapted to function as a wireless edge managers. They may also provide additional network management functionalities such as bandwidth management, access control, firewall functions, traffic privacy and quality of service management and load balancing.
  • FIG. 3 is a block diagram 300 of an exemplary Enterprise Wireless LAN having switches serving as the edge managers in accordance with an embodiment of the invention.
  • a local area network (LAN) 302 authentication server 304, switches 306, 308, access points (APs) 310, 312, 314, 316, 318, 320 and access devices 322, 324, 326, 328, 330, 332, 334, 336, 338.
  • LAN local area network
  • APs access points
  • the invention may be applicable to a wired LAN, a wireless LAN and any combination thereof. Wireless transmission or communication between the access devices or clients, and the access points may be secure.
  • the switches 306, 308 and access points 310, 312, 314, 316, 318, 320 may be adapted to communicate using, for example, an Ethernet protocol. From the switch's perspective, the switch may be switching regular layer 2 frames. However, within the switch, knowledge of a WLAN and its management intelligence may reside primarily in software. Notwithstanding, the invention is not limited in this regard.
  • FIG. 4 is a block diagram 400 of an exemplary switch 402 as illustrated in FIG. 2 and FIG. 3 in accordance with an embodiment of the invention.
  • switch 402 may include a processor 410, transmitter 404, receiver 406, generator 408 and controller 412.
  • the controller 412 may include QoS controller 414, bandwidth controller 422, load balancing controller 416, session controller 418 and network management controller 420.
  • the transmitter 404, receiver 406, generator 408 and the components of the controller 412, namely QoS controller 414, load balancing controller 416, session controller 418 and network management controller 420, may be variously coupled to processor 410.
  • the components of switch 402 may include suitable circuitry and/or software capable of implementing the various network management functions, including but not limited to, QoS management, bandwidth management, load balancing, session management and control. Notwithstanding, although the components of the switch 402 are individually shown, the invention is not limited in this regard.
  • the generator function 408 may be implemented solely by the processor 422.
  • any one or more of the bandwidth management, QoS management, load balancing, session management and control, and network management may be integrated, and with suitable logic and/or software, may be executed by the processor 410.
  • the transmitter 404 may be adapted to send a first messaging protocol message between a first switch and a first access point.
  • the receiver 406 may be adapted to receive a second messaging protocol message from the first access point and the first switch. In response to the transmittal of the first messaging protocol message, a second messaging protocol message may be received.
  • the controller 412 may be adapted to allocate system resources for one or more devices using any one or more of the first second and/or third messaging protocol messages. These devices may include but are not limited to the first switch, a second switch, the first access point, the second access point, and one or more access devices.
  • the system resources may be allocated to ensure that at least minimal acceptable level of service is maintained.
  • the generator 408 may be adapted to generate the first messaging protocol message by the first switch.
  • the receiver 406 may be adapted to receive the second messaging protocol message from a second switch.
  • the processor 410 may be adapted to control the transmitter 404, the receiver 406, the controller 412 and the generator 408.
  • the processor 410 may utilize one or more messaging protocol messages to control transmitter 404, receiver 406, generator 408, bandwidth controller 422, QoS controller 414, load balancing controller 416, session controller 418 and network management controller 420.
  • the switch may be adapted to facilitate network management, including activities such as, QoS management and bandwidth management, by utilizing a messaging protocol.
  • the messaging protocol may utilize one or more protocols associated with a device communication protocol (DCP) umbrella (DCPU).
  • the messaging protocol utilized by the switch may be adapted to run over the transmission control protocol (TCP) or user datagram protocol (UDP) using for example, a well-known port number specified under the framework of the device communication protocol.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • Under the DCP umbrella there may be several sub- protocols defined for the purpose of facilitating interoperability with other products. Some of these products may include but are not limited to, cable modems and cable modem termination systems (CMTS) equipment.
  • CMTS cable modems and cable modem termination systems
  • the messaging protocol utilized by the switch may be adapted to include the necessary protocols under DCP to facilitate communication for wired and/or WLAN devices.
  • the switch may utilize the messaging protocol to facilitate various network management activities between various wireless networking devices and/or clients.
  • one or more of WLAN switches 306, 308 may be adapted to utilize the messaging protocol to facilitate communication with one or more of the access points 310, 312, 314, 316, 318, 320 of FIG. 3.
  • Information exchanged between these two devices may include, but is not limited to, control, configuration and status information of the devices and also client session information. At least some of this information may be used for QoS management.
  • the control information may include, for example, signaling information that may be communicated in-band or out-of-band.
  • the switch may utilize the messaging protocol, which may include a plurality of message types.
  • the switch may utilize a messaging protocol that may include, for example, six (6) categories of messages or message types. Notwithstanding, the invention is not so limited. These messages and their usage may be illustrated as follows:
  • AP_Status from AP to Switch or AP
  • An AP_Status message may be used to indicate, for example, an access point capacity, bandwidth allocation, the number of attached clients, signal strength, power levels, etc.
  • An AP_Config message may be used to configure an access point to accommodate a client. This may include but is not limited to, 802.11e QoS, security information, etc.
  • Switch Status from Switch to Switch
  • a Switch_Status message may be used to indicate a switch's association with one or more clients. This may include but is not limited to, client session information, access control, QoS parameters, etc.
  • Switch_Config from Switch to Switch A Switch_Config message may be used to configure a switch such as a WLAN Switch to accommodate a client.
  • The may include but is not limited to, access control, QoS configuration, etc.
  • Client_Status from AP to Switch
  • a Client_Status message may be used to indicate a client's information. This may include but is not limited to, client identification, associated MAC address, session status, connecting location, etc.
  • the Device_Discovery message may be used by a switch and/or a server to discover clients or by client to discover servers.
  • the message may be broadcast to some or all devices in the subnet to draw responses from the intended devices.
  • the message may include, for example four (4) message subtypes — .request, .data, .alert, and .ack.
  • a message type/subtype pair of .request and .data may represent the request of data and a corresponding response of data itself.
  • the subtype pair of .alert and .ack may represent the voluntary transmission of data and its acknowledgement.
  • one or more message types and/or subtype may be used to facilitate bandwidth management.
  • United States Patent Application Serial No. 10/607,094 entitled “Communication System and Method in a Hybrid Wired/Wireless Local Area Network” filed on June 26, 2003 discloses a messaging protocol that may be utilized by the switch in accordance with an embodiment of the invention, and is incorporated herein by reference in its entirety. Exemplary valid fields and subfields for various messaging protocol messages that may be utilized by the switch in accordance with an aspect of the invention are disclosed therein.
  • September 9, 2003 discloses a messaging protocol that may be utilized by the switch in accordance with an embodiment of the invention, and is incorporated herein by reference in its entirety.
  • the switch disclosed therein may be adapted to utilize the messaging protocol to provide network management in accordance with an embodiment of the invention.
  • the switch may include a network management controller that may be configured for network management and may provide valuable information that may be utilized for QoS management.
  • the switch may be adapted to utilize, for example, the messaging protocol to transfer networking monitoring and/or status messages such as SNMP and RMON statistics from an old attachment or connection point to a new connection point.
  • the switch may be configured to use the messaging protocol to enable location-specific management of at least certain clients and/or network devices.
  • the switch may send client association information to a central management entity that may be aware of the location of the various access points and/or switches in the network. This information may be disseminated to, for example a QoS controller, a bandwidth controller and/or a load balancing controller.
  • a decision may subsequently be made to determine whether to allow or disallow access from certain locations in order to maximize bandwidth usage, balance a load within the network and/or provide a specified QoS.
  • information pertaining to at least some detected clients may be transferred to the switch.
  • the load balancing manager and/or controller located in the switch may use this information to achieve efficient load balancing.
  • the load balancing controller may include suitable circuitry and/or software that may be adapted to receive and assess various client information and effectuate an efficient load balancing. Parameters such as signal strength, access level and device type, may be indicative of the information that may be used to effectuate efficient load balancing.
  • Client association/dissociation information may be communicated between the load balancing manager and one or more access points and/or switches in order to ensure that an acceptable level of service may be received by accessing clients. Once the load-balancing manager determines an optimal load configuration, new client and/or access point association information may be passed to the various access points in the network using messaging protocol messages.
  • the switch may include a QoS controller that may be configured to utilize the messaging protocol to transfer QoS parameters from an original switch port to a new switch port, in order to facilitate roaming.
  • One or more switches in the network may be adapted to facilitate roaming between various access points located in the same network or between different networks. This may affect the QoS handling of, for example, downstream traffic destined for the roaming client or access device.
  • a switch may be adapted to utilize one or more messaging protocol messages to automatically transfer various pertinent network management parameters between access points and or other switches. This centralized management may eliminate a need for a distributed management interface, thereby providing a more robust communication system.
  • a switch may be adapted to utilize the messaging protocol to transfer QoS parameters from an old access point to a new access point. This may affect upstream traffic from the client to an access point.
  • the switch may utilize one or more messaging protocol messages to transfer QoS parameters from the old access point to the new access point. Since this handling of QoS parameters may be similar to the handling of client traffic, the messaging protocol may be used to provide seamless roaming, which may provide a greater level of acceptable service.
  • FIG. 5 is a block diagram 500 of an exemplary switching system for network management in a wireless local area network.
  • the CPU block 502 may include a quality of service (QoS) controller block 506, a bandwidth management controller block 520, a load balancing controller block
  • QoS quality of service
  • the switching fabric block 504 may include a filtering engine block 514.
  • the CPU block 502 may be adapted to interface with the switching fabric block 504.
  • One or more of the QoS controller block 506, load balancing controller block 508, session controller block 510 and network management control block 512 may interface directly with the filtering engine block 514.
  • selected signaling packets may be communicated from the switching fabric block 504 to one or more of the QoS controller block 506, bandwidth management controller block 520, load balancing controller block 508, session controller block 510 and network management control block 512.
  • Messaging protocol messages may be used to facilitate communication between the switching fabric block 504 and one or more of the bandwidth management controller block 520, QoS controller block 506, load balancing controller block 508, session controller block 510 and network management control block 512.
  • the selected signaling packets may include, but are not limited to, VoIP packets, and streaming media packets including voice, video and data.
  • the filtering engine block 514 may be adapted to filter information received from one or more of the QoS controller block 506, bandwidth management controller block 520, load balancing controller block 508, session controller block 510 and a network management control block 512.
  • the filtering engine block 514 may be adapted to filter messaging protocol messages used to control switching functions, network traffic statistics messages, layer two (2) address update messages, and filter update messages.
  • the filter update messages may include, but is not limited to, QoS messages, bandwidth management messages, access control messages and load balancing messages.
  • the switching system for network management may include a session control process that may be adapted to manage and control at least one client database and session information for some or all active clients.
  • the switching system for network management may be adapted to provide session management information that may be utilized for bandwidth management.
  • the session control process may be configured to enforce access control based on, for example, a client session, a subnet, a network management application, and switch ports. Access control may be used to facilitate, for example, QoS management, bandwidth management and load balancing in at least a portion of the network.
  • the session control process may also control and manage switching intelligence and to determine bandwidth availability in order to facilitate activities such as roaming.
  • FIG. 6 is a block diagram 600 of an exemplary session control process with respect to FIG. 5 that may be utilized by the switching system for network management in accordance with an embodiment of the invention.
  • a session control process 602 having a client database 604, an access control list (ACL) database 606, a session control manager 608 and a VoIP enabler 610.
  • ACL access control list
  • One or more interfaces may be adapted to provide communication between session manager 608 and the client database 604 and the ACL database 606.
  • the session manager 608 may include at least one interface that may be adapted to facilitate communication with the VoIP enabler 610.
  • the session control manager 608 may be adapted to process, for example, messaging protocol messages, layer two (2) updates, and filter updates.
  • the session control manager 608 may be adapted to receive information from one or more of client database 604 and ACL database 606.
  • the VoIP enabler 610 may be adapted to process VoIP signaling packets. VoIP enabler 610 may also be adapted to decode various standards-based VoIP signaling packets and prioritize filter setup.
  • Information from the session control manager 608 may be communicated to the bandwidth management controller 520, the QoS controller 506, the load balancing controller 508, and the network management controller 512 which are illustrated in FIG. 5.
  • the switching system 602 may include a load balancing process that may be adapted to obtain access point load from, for example, a QoS management process and a bandwidth management process.
  • the network management process may include but is not limited to SNMP, RMON, RMON2, and MIB.
  • the load balancing process may be adapted to keep an access point database on, for example, a plurality or bank of access points.
  • the load balancing process may include necessary intelligence for making load distribution decisions.
  • the access point database may be accessible by one or more of the QoS controller 506, the bandwidth management controller 520, the load balancing controller 508, and the network management controller 512 which are illustrated in FIG. 5.
  • the bandwidth management controller 520 may be adapted to request information from the session control manager 608 and/or the load balancing process in order to facilitate bandwidth management.
  • FIG. 7 is a block diagram 700 of an exemplary load balancing process with respect to FIG. 5 that may be utilized by the switching system for network management in accordance with an embodiment of the invention.
  • a load balancing process 702 having an access point database 702 and a load balancing manager 706. At least one interface may be adapted to provide communication between access point database 704 and the load balancing manager 706.
  • the load balancing manager 706 may be adapted to include at least one interface that may facilitate communication with a network management process.
  • the load balancing manager 706 may be adapted to process messaging protocol messages, layer two (2) updates, and filter updates.
  • the load balancing manager 706 may receive network statistics from a one or more network management processes. Information from the access point database 704 may be utilized by the load balancing manager
  • the switching system for network management may include a QoS enabling process that may be adapted to control and manage activities such as, traffic policing, metering filters, and protocol configurations.
  • the QoS enabling process may be adapted to manage, for example, 8012.11e based configurations that may be sent to the access point.
  • a VoIP enabler may be adapted to decode various standard-based VoIP signaling packets and prioritize filter setup.
  • FIG. 8 is a block diagram 800 of an exemplary QoS enabling process with respect to FIG. 8 that may be utilized by an the switching system for network management in accordance with an embodiment of the invention.
  • QoS enabling process 802 having QoS policy database 804, a QoS manager 806 and a VoIP enabler 808.
  • At least one interface may be adapted to provide communication between QoS policy database 804 and the QoS manager 806.
  • the QoS manager 806 may be adapted to include at least one interface that may facilitate communication with, for example, the VoIP enabler 808.
  • the QoS manager 806 may be adapted to process, for example, messaging protocol messages, and filter updates.
  • the QoS manager 806 may send and receive VoIP signaling information to and from
  • the bandwidth management controller 412 may be adapted to receive pertinent QoS related information from the QoS controller 414.
  • the QoS controller 414, the load balancing controller 416, the session controller 418, the network management controller 420 and/or the bandwidth management controller 412 may be adapted to transfer and/or store information in a database, for example, database 424.
  • the QoS controller may be adapted to store at least some of its related QoS related information in database 424.
  • the bandwidth management controller may access database 424 and retrieve any QoS related information that may be pertinent to bandwidth management.
  • the bandwidth management controller 422 may be adapted to request required QoS related information from the QoS controller 414.
  • real-time information not necessarily located in the database 424 may be requested from the QoS controller 414 whenever a need arises.
  • the QoS controller 414 may be adapted to also request an receive related information from any one or more of the load balancing controller 416, the session controller 418, the network management controller 420, the bandwidth management controller 422 and/or the database 424.
  • the bandwidth management process may be executed in an adaptive manner and may occur in real-time.
  • FIG. 9a is a flowchart 900 of exemplary steps for a QoS enabling process that may be utilized by the switching system for network management in accordance with an embodiment of the invention.
  • a switch may request QoS information from another switch and/or access point using a messaging protocol message.
  • QoS information may be received from the switch and/or the access point using a messaging protocol message.
  • a minimum QoS level of operation may be determined by the switch.
  • QoS information corresponding to the determined QoS level of operation may be distributed to switch and/or access point using a messaging protocol message.
  • the exemplary steps may end with step 910.
  • FIG. 910 The exemplary steps may end with step 910.
  • a switch may determine whether to queue traffic for an access point. If it is determined that traffic should be queued, then in step 926, an access point may be instructed to queue traffic using a messaging protocol message. In step 928, a switch may determine whether to prioritize traffic for an access point. If it is determined that traffic should be prioritized, then in step 930, an access point may be instructed to prioritize traffic using a messaging protocol message. In step 932, a switch may determine whether to schedule traffic for an access point. If it is determined that traffic should be scheduled, then in step 934, an access point may be instructed to prioritize traffic using a messaging protocol message.
  • Step 925 may be executed subsequent to step 926 or if it is determined that traffic should not be queued for an access point in step 924.
  • Step 932 may be executed subsequent to step 930 or if it is determined that traffic should not be prioritized for an access point in step 928.
  • the end step 925 may be executed subsequent to step 932 or if it is determined that traffic should not be scheduled for an access point in step 934. Notwithstanding, the exemplary steps illustrated in FIG. 9a and FIG.
  • step 904 may be an optional step.
  • an access point and/or a switch may be adapted to send QoS information, for example in a dynamic manner, using a messaging protocol message to the switch.
  • network management may be adapted to provide link diagnostics.
  • one or more messaging protocol messages may be used to provide testing and diagnostics. Testing and diagnostics may be carried out on the wireless interface of an access point to determine, for example, connectivity status and throughput performance of the interface. Additionally, messaging protocol messages may be used to examine and/or modify radio information such as operating channel, transmit power, supported data rates, and regulatory settings. During link testing, messaging protocol messages may be used to determine signal strength and quality, diagnose client association, dissociation and authentication, and to examine various packets sent over the wireless interface.
  • one or more of the PLCP frames illustrated in FIG. 1b, FIG. 1c, FIG. 1d and FIG. 1e may be adapted to contain information which may be utilized for providing communication in accordance with various embodiments of the invention. Additionally, the PLCP frames may be adapted to convey information for any one or more of the 801.11a, 802.11b and 802.11g modes of operation utilized by access points and/or access devices in accordance the embodiments of the invention.
  • the present invention may be realized in hardware, software, or a combination of hardware and software.
  • the present invention may be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited.
  • a typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
  • the present invention also may be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods.
  • Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.

Abstract

Certains aspects de cette invention portent sur un système et un procédé de gestion de réseau dans un réseau local câblé/sans fil hybride. Le procédé de gestion de réseau dans un réseau local câblé/sans fil hybride peut consister à recevoir d'un premier point d'accès et/ou d'un premier commutateur un premier message de protocole de messagerie (904) contenant des informations relatives à la qualité de service (QoS). En réponse au premier message de protocole de messagerie, au moins un niveau de qualité de service minimum (908) de fonctionnement peut être déterminé pour le premier commutateur, le premier point d'accès, un second point d'accès et/ou un second commutateur. Les informations de qualité de service correspondant au niveau de qualité de service minimum peuvent être distribuées (910) au premier commutateur, au premier point d'accès, au second point d'accès et au second commutateur à l'aide d'un second message de protocole de messagerie. Les informations de qualité de service peuvent être distribuées à au moins une partie du réseau local câblé/sans fil hybride.
PCT/US2003/028337 2002-09-17 2003-09-09 Procede et systeme de gestion de reseau dans un reseau cable/sans fil hybride WO2004028049A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP03749562A EP1543640A4 (fr) 2002-09-17 2003-09-09 Procede et systeme de gestion de reseau dans un reseau cable/sans fil hybride

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US41126102P 2002-09-17 2002-09-17
US41130102P 2002-09-17 2002-09-17
US60/411,301 2002-09-17
US60/411,261 2002-09-17
US43312202P 2002-12-13 2002-12-13
US60/433,122 2002-12-13
US43598402P 2002-12-20 2002-12-20
US60/435,984 2002-12-20

Publications (1)

Publication Number Publication Date
WO2004028049A1 true WO2004028049A1 (fr) 2004-04-01

Family

ID=32034403

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/028337 WO2004028049A1 (fr) 2002-09-17 2003-09-09 Procede et systeme de gestion de reseau dans un reseau cable/sans fil hybride

Country Status (2)

Country Link
EP (1) EP1543640A4 (fr)
WO (1) WO2004028049A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1675324A1 (fr) * 2004-12-27 2006-06-28 Kabushiki Kaisha Toshiba Contrôle d'accès dans un réseau de communication sans file

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5701465A (en) * 1993-06-29 1997-12-23 International Business Machines Corporation Method and apparatus for reserving system resources to assure quality of service
US5751708A (en) * 1995-10-25 1998-05-12 Lucent Technologies Inc. Access method for broadband and narrowband networks
US5898668A (en) * 1996-12-13 1999-04-27 Siemens Information And Communication Networks, Inc. Method and system for increasing quality of service at or below a threshold cost
US6049549A (en) * 1997-08-14 2000-04-11 University Of Massachusetts Adaptive media control

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI107505B (fi) * 1999-02-16 2001-08-15 Nokia Networks Oy Pääsynvalvontamenetelmä

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5701465A (en) * 1993-06-29 1997-12-23 International Business Machines Corporation Method and apparatus for reserving system resources to assure quality of service
US5751708A (en) * 1995-10-25 1998-05-12 Lucent Technologies Inc. Access method for broadband and narrowband networks
US5898668A (en) * 1996-12-13 1999-04-27 Siemens Information And Communication Networks, Inc. Method and system for increasing quality of service at or below a threshold cost
US6049549A (en) * 1997-08-14 2000-04-11 University Of Massachusetts Adaptive media control

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1543640A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1675324A1 (fr) * 2004-12-27 2006-06-28 Kabushiki Kaisha Toshiba Contrôle d'accès dans un réseau de communication sans file

Also Published As

Publication number Publication date
EP1543640A1 (fr) 2005-06-22
EP1543640A4 (fr) 2011-12-28

Similar Documents

Publication Publication Date Title
EP1515484B1 (fr) Procédé et système d'équilibrage de charges optimal dans un réseau cablé/sans fil hybride
EP1515480B1 (fr) Procédé et système pour la gestion de réseau dans un réseau hybride filaire/sans fil
US8619728B2 (en) Method and system for providing an intelligent switch for bandwidth management in a hybrid wired/wireless local area network
US9094314B2 (en) System and method for access point (AP) aggregation and resiliency in a hybrid wired/wireless local area network
US8170607B2 (en) Communication system and method in a hybrid wired/wireless local area network
EP1515494B1 (fr) Méthode et système pour fournir l'allocation et le partage de bande passante dans un réseau hybride filaire/non filaire
US7164663B2 (en) Method and system for providing an intelligent switch in a hybrid wired/wireless local area network
US9014196B2 (en) System and method for providing a super channel in a multi-band multi-protocol hybrid wired/wireless network
EP1401149A2 (fr) Réseau de communication et méthode de découverte des points terminaisons utilisant une connexion de couche liaison dans un réseau local avec/sans fil
EP1552711A1 (fr) Procede et systeme d'equilibrage de charges optimal dans un reseau cable/sans fil hybride
US20040052241A1 (en) System and method for hardware acceleration in a hybrid wired/wireless local area network
EP1401150B1 (fr) Réseau de communication et méthode dans un réseau local hybride avec/sans fil
EP1547408B1 (fr) Systeme et procede d'acceleration de materiel dans un reseau local hybride filaire/hertzien
WO2004028049A1 (fr) Procede et systeme de gestion de reseau dans un reseau cable/sans fil hybride
EP1573927A2 (fr) Procede et systeme a commutateur intelligent pour une gestion de largeur de bande dans un reseau local hybride fixe/sans fil
WO2004028132A2 (fr) Procede et systeme a commutateur intelligent dans un reseau local hybride fixe/sans fil
WO2004028058A2 (fr) Procede et systeme d'attribution et de partage de largeur de bande dans un reseau hybride cable/sans fil

Legal Events

Date Code Title Description
AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2003749562

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2003749562

Country of ref document: EP