Methods and apparatus for transferring service flow context of mobile broadband wireless access networks

Embodiments of methods and apparatus for transferring service flow context are generally described herein. Other embodiments may be described and claimed.

TECHNICAL FIELD

The present disclosure relates generally to wireless communication systems, and more particularly, to methods and apparatus for transferring service flow context of mobile broadband wireless access networks.

BACKGROUND

The 802.16 family of standards were developed by the Institute of Electrical and Electronic Engineers (IEEE) to provide for fixed, portable, and/or mobile broadband wireless access (BWA) networks (e.g., the IEEE std. 802.16, published 2004). The Worldwide Interoperability for Microwave Access (WiMAX) forum facilitates the deployment of broadband wireless networks based on the IEEE 802.16 standard. In particular, the WiMAX forum ensures the compatibility and inter-operability of broadband wireless equipment. For convenience, the terms “802.16” and “WiMAX” may be used interchangeably throughout this disclosure to refer to the IEEE 802.16 suite of air interface standards.

The WiMAX technology may support multimedia applications with multiple wireless connections characterized by quality of service (QoS) parameters. For example, the 802.16 family of standards provide packet classifiers to map the multiple wireless connections with user applications and/or interfaces such as an Ethernet network, an Internet protocol (IP) network, an asynchronous transfer mode (ATM) network, a virtual local area network (VLAN), etc. To establish the multiple wireless connections of broadband services for a mobile subscriber station, service flow context such as service flow, QoS, classifier, and/or other suitable parameters may need to be provided and/or transferred during initial registration and/or handoff of the mobile subscriber station.

DETAILED DESCRIPTION

In general, methods and apparatus for transferring service flow context are described herein. According to one example embodiment, service flow context associated with a mobile subscriber station may be identified. The service flow context may be transmitted to a base station. Accordingly, the mobile subscriber station may be managed via a proxy agent associated with the base station. The methods and apparatus described herein are not limited in this regard.

Referring toFIG. 1, an example wireless communication system100is described herein. In one example, the wireless communication system100may include one or more mobile BWA networks (e.g., one shown as200inFIG. 2). AlthoughFIG. 1depicts a mobile BWA network, the wireless communication system100may include more mobile BWA networks. Further, the wireless communication system100may include one or more fixed BWA networks (not shown). The methods and apparatus described herein are not limited in this regard.

In particular, the wireless communication system100may include one or more mobile subscriber stations (MSS)110, generally shown as112,114, and116. For example, the MSS110may be a laptop computer, a handheld computer, a tablet computer, a cellular telephone (e.g., a smart phone), a pager, an audio and/or video player (e.g., an MP3 player or a DVD player), a game device, a digital camera, a navigation device (e.g., a GPS device), and/or other suitable portable electronic devices. AlthoughFIG. 1depicts three MSS, the wireless communication system100may include more or less MSS.

The MSS110may use a variety of modulation techniques such as time-division multiplexing (TDM) modulation, frequency-division multiplexing (FDM) modulation, orthogonal frequency-division multiplexing (OFDM) modulation, multi-carrier modulation (MDM), and/or other suitable modulation techniques to communicate via wireless communication links. For example, the laptop computer114may implement OFDM modulation to transmit large amounts of digital data by splitting a radio frequency signal into multiple small sub-signals, which in turn, are transmitted simultaneously at different frequencies. In particular, the MSS110may use OFDM modulation as described in the 802.xx family of standards developed by the Institute of Electrical and Electronic Engineers (IEEE) and/or variations and evolutions of these standards (e.g., 802.11x, 802.15, 802.16x, etc.). The MSS110may also operate in accordance with other suitable wireless communication protocols that require very low power such as Bluetooth, Ultra Wideband (UWB), and/or radio frequency identification (RFID) to communicate via wireless communication links. The methods and apparatus described herein are not limited in this regard.

The wireless communication system100may also include one or more radio access networks (RAN), generally shown as160. Each RAN160may include one or more base stations (BS), generally shown as170, and other radio components necessary to provide communication services to the MSS110. The BS170may operate in accordance with the applicable standard(s) for providing wireless communication services to the MSS110. That is, each BS170may be configured to operate in accordance with one or more of several wireless communication protocols to communicate with the MSS110. In particular, these wireless communication protocols may be based on analog, digital, and/or dual-mode communication system standards such as the Global System for Mobile Communications (GSM) standard, the Frequency Division Multiple Access (FDMA) standard, the Time Division Multiple Access (TDMA) standard, the Code Division Multiple Access (CDMA) standard, the Wideband CDMA (WCDMA) standard, the General Packet Radio Services (GPRS) standard, the Enhanced Data GSM Environment (EDGE) standard, the Universal Mobile Telecommunications System (UMTS) standard, variations and evolutions of these standards, and/or other suitable wireless communication standards. AlthoughFIG. 1depicts one RAN, the wireless communication system100may include more RAN.

In addition, the wireless communication system100may include an Internet protocol (IP) transport180and a network management system (NMS)190. The IP transport180may provide one or more IP connections between the RAN160and the NMS190. As described in detail below, the NMS190may include an element management system194and a service database196.

Further, the wireless communication system100may include other wireless local area network (WLAN) devices and/or wireless wide area network (WWAN) devices (not shown) such as network interface devices and peripherals (e.g., network interface cards (NICs)), access points (APs), gateways, bridges, hubs, etc. to implement a cellular telephone system, a satellite system, a personal communication system (PCS), a two-way radio system, a one-way pager system, a two-way pager system, a personal computer (PC) system, a personal data assistant (PDA) system, a personal computing accessory (PCA) system, and/or any other suitable communication system. Although certain examples have been described above, the scope of coverage of this disclosure is not limited thereto.

In the example ofFIG. 2, a mobile broadband wireless access (BWA) network200may include one or more mobile subscriber stations (MSS), generally shown as210, and one or more base stations (BS), generally shown as260and270. The mobile BWA system200may also include an Internet protocol (IP) transport280and a network management system (NMS)290. AlthoughFIG. 2depicts one MSS, the mobile BWA network200may include more MSS. Further, whileFIG. 2depicts two BS, the mobile BWA network200may include more BS.

The MSS210may include a control plane220and a management plane240. The control plane220may include one or more media access (MAC) sublayers. In particular, the MAC sublayers may include a MAC convergence sublayer (CS)222, a MAC common part sublayer (CPS)224, and a privacy sublayer226. The control plane220may also include a physical (PHY) sublayer228to support electrical and/or mechanical interfaces to a physical medium. Further, the control plane220may include a control plane service access point (SAP)230, a CS SAP232, a MAC SAP234, and a PHY SAP236.

The MAC CS222may provide transformation and/or mapping of external network data received through the CS SAP232. The MAC CPS224may provide core MAC functionality of system access, bandwidth allocation, connection establishment, and/or connection maintenance. The MAC CPS224may receive data corresponding to particular MAC connections from the MAC CS222via the MAC SAP234. The privacy sublayer226may provide authentication, secure key exchange, and/or encryption. Data, PHY control, and/or statistics may be transferred between the MAC CPS224and the PHY sublayer228via the PHY SAP236.

The management plane240may include a management entity MAC CS242, a management entity MAC CPS244, a management entity privacy sublayer246, and a management entity PHY sublayer248. The components of the management plane240may be configured to manage the MAC sublayers of the control plane220. In particular, the management entity MAC CS242may be configured to manage the MAC CS222. The management entity MAC CPS244may be configured manage the MAC CPS224. The management entity privacy sublayer246may be configured to manage the privacy sublayer226. The management entity PHY sublayer248may be configured to manage the PHY sublayer228. Further, the management plane240may include a management plane SAP250. The management plane SAP250may be configured to manage the control plane SAP230, the CS SAP232, the MAC SAP234, and/or the PHY SAP236of the control plane220.

Each of the BS260and270may include a proxy simple network management protocol (SNMP) agent, generally shown as262and272, respectively. The proxy SNMP agents262and272may manage the MSS210via the control plane SAP230and the management plane SAP250. Each of the BS260and270may also include a management information base (MIB), generally shown as264and274, respectively. Each of the MIB264and274may be a database to store information and statistics on each network element in a network. The information and statistics stored in the MIB264and274may be used to keep track of the performance of each network element and to ensure that the network elements of the mobile BWA network200are functioning properly.

The NMS290may include a network plane SAP292, an element management system (EMS)294, and a service flow database296. As described in detail below, the EMS294may manage network elements associated with the mobile BWA network200such as the MSS210and the BS260and270. The EMS294may manage the BS260and270via the network plane SAP292based on a SNMP. The EMS294may also manage the MSS210via the network plane SAP292. In particular, the EMS294may use the proxy SNMP agents262and272at the BS260and270, respectively, to retrieve parameters located in the MSS210from control and management MAC messages. For example, control MAC messages may include uplink channel descriptor (UCD), downlink channel descriptor (DCD), registration request (REG-REQ), and/or registration response (REG-RSP) as described in the 802.16 standard developed by the Institute of Electrical and Electronic Engineers (IEEE) (e.g., the IEEE std. 802.16, published 2004). The management MAC messages may include new messages to support back-end proxy model (e.g., the IEEE std. 802.16g).

The service flow database296may store service flow context associated with the mobile BWA network200. For example, the service flow context may include service flow, quality of service, and/or classifier parameters provided by service providers of communication services. The service flow context may also include packet counters, traps, and/or events reported by the network elements.

In the mobile BWA network200, the MSS210may be dynamically associated with one or more BS (e.g., the MSS210may not be fixed to one particular BS). For example, the MSS210may move to one coverage area to another. As a result, a handoff (e.g., a transition) from one BS to another BS may be required to maintain communication services for the MSS210. The methods and apparatus described herein are not limited in this regard.

Turning toFIG. 3, for example, service flow context associated with the MSS210may be transferred when the MSS210initiate registration. In particular, a service provider (e.g., via a server) may activate service for a subscriber using the MSS210by providing the service flow context to the service flow database296(310). Alternatively, a handoff without pre-notification may proceed without the service provider providing the service flow context to the service flow database296as mentioned in connection with310because the service flow context may be previously stored in the service flow database296. The MSS210may register with the serving BS260(315). Accordingly, the serving BS260may transmit a registration interrupt to the EMS294(320). In particular, the registration interrupt may include the MAC address of the MSS210. For example, the serving BS260may send an SNMP trap400as shown inFIG. 4to the EMS294.

Referring back toFIG. 3, the EMS294may identify the service flow context from the service flow database296based on the MAC address of the MSS210(330). Accordingly, the EMS294may send an SNMP SET message to the serving BS260to download the service flow context to the serving BS260(340). The serving BS260may store the service flow context in the MIB264. Based on the downloaded service flow context, the serving BS260may transmit a dynamic service addition (DSA) message to establish connection with the MSS210(350). Accordingly, the proxy SNMP agent262may include MSS and BS objects manageable by the EMS294. To retrieve parameters from the MSS210, the SNMP agent262may convert SNMP messages from the EMS294into MAC messages to the MSS210. As a result, the EMS294may manage the MSS210via the proxy SNMP agent262associated with the serving BS260(360). The methods and apparatus described herein are not limited in this regard.

In another example, the EMS294may also transfer service flow context when a BS such as the serving BS260initiates a handoff request. In the example ofFIG. 5, the serving BS260may initiate a handoff process in response to a trigger event. For example, the EMS294may request the serving BS260to release the MSS210to another BS to optimize performance (e.g., load balancing). Accordingly, the serving BS260may transmit a handoff interrupt (e.g., an SNMP trap) to the EMS294(510). The handoff interrupt may include the MAC address of the MSS210and a target BS identifier of the target BS270. In one example, the interrupt may be an SNMP trap600as shown inFIG. 6to the EMS294.

Turning back toFIG. 5, the EMS294may identify the service flow context from the service flow database296based on the MAC address of the MSS210(520). The EMS294may also identify the target BS270based on the target BS ID. Accordingly, the EMS294may send an SNMP SET message to the target BS270to download the service flow context to the target BS270(530). The target BS270may store the service flow context in the MIB274. To request the MSS210to handoff to the target BS270, the serving BS260may send a BS handoff request message (e.g., MOB-BSHO-REQ message of the IEEE 802.16 std.) to the MSS210(540).

The MSS210may complete a ranging and registration process to handoff to the target BS270. As mentioned above (e.g.,530), the target BS270may have downloaded and locally stored the service flow context from the EMS294. Based on the downloaded service flow context, the target BS270may transmit a DSA message to establish connection with the MSS210(550). Further, the EMS294may remove the service flow context locally stored in the MIB264at the serving BS260(560). Accordingly, the proxy SNMP agent272may include MSS and BS objects manageable by the EMS294. To retrieve parameters from the MSS210, the SNMP agent272may convert SNMP messages from the EMS294into MAC messages to the MSS210. As a result, the EMS294may manage the MSS210via the proxy SNMP agent272associated with the target BS270(570). The methods and apparatus described herein are not limited in this regard.

In yet another example, the EMS294may transfer service flow context when the MSS210initiates a handoff request. Referring toFIG. 7, for example, the MSS210may select the target BS270as a target for a handoff. To request the handoff to the target BS270, The MSS210may send a MS handoff request message (e.g., MOB-MSSHO-REQ message of the IEEE 802.16 std.) to the serving BS260(710). Accordingly, the serving BS260may transmit a handoff interrupt (e.g., an SNMP trap) to the EMS294(720). The handoff interrupt may include the MAC address of the MSS210and the target BS ID of the target BS270. In one example, the handoff interrupt may be an SNMP trap600as shown inFIG. 6to the EMS294.

Referring back toFIG. 7, the EMS294may identify the service flow context from the service flow database296based on the MAC address of the MSS210(730). The EMS294may also identify the target BS270based on the target BS ID. Accordingly, the EMS294may send an SNMP SET message to the target BS270to download the service flow context to the target BS270(740). The target BS270may store the service flow context in the MIB274.

To indicate completion of the service flow context transfer, the serving BS260may send a BS handoff response message (e.g., MOB-BSHO-RSP message of the IEEE 802.16 std.) to the MSS210(750). The MSS210may complete a ranging and registration process to handoff to the target BS270. As mentioned above (e.g.,740), the target BS270may have downloaded and locally stored the service flow context from the EMS294. Based on the downloaded service flow context, the target BS270may transmit a DSA message to establish connection with the MSS210(760). Further, the EMS294may remove the service flow context locally stored in the MIB264at the serving BS260(770). Accordingly, the proxy SNMP agent272may include MSS and BS objects manageable by the EMS294. To retrieve parameters from the MSS210, the SNMP agent272may convert SNMP messages from the EMS294into MAC messages to the MSS210. As a result, the EMS294may manage the MSS210via the proxy SNMP agent272associated with the target BS270(780). The methods and apparatus described herein are not limited in this regard.

In the example ofFIG. 8, the EMS294may include a communication interface810, an identifier820, and a controller830. As described in detail below,FIG. 9depicts one manner in which the example EMS294ofFIG. 8may be configured to transfer service flow context. The example process900ofFIG. 9may be implemented as machine-accessible instructions utilizing any of many different programming codes stored on any combination of machine-accessible media such as a volatile or nonvolatile memory or other mass storage device (e.g., a floppy disk, a CD, and a DVD). For example, the machine-accessible instructions may be embodied in a machine-accessible medium such as a programmable gate array, an application specific integrated circuit (ASIC), an erasable programmable read only memory (EPROM), a read only memory (ROM), a random access memory (RAM), a magnetic media, an optical media, and/or any other suitable type of medium.

Further, although a particular order of actions is illustrated inFIG. 9, these actions can be performed in other temporal sequences. Again, the example process900is merely provided and described in conjunction with the components ofFIGS. 2 and 8as an example of one way to configure the EMS294to transfer service flow context.

In the example ofFIG. 9the process900may begin with the EMS294(e.g., via the controller830) monitoring for an interrupt for a registration or a handoff (e.g., an SNMP trap) (block910). The interrupt may include an identifier of the MSS210associated with a registration or a handoff. For example, the identifier may be the MAC address of the MSS210. If the EMS294fails to receive an interrupt via the communication interface810, the EMS294may continue to monitor for an interrupt. Otherwise if the EMS294receives an interrupt, the EMS294(e.g., via the identifier820) may identify service flow context from the service flow database296based on the MAC address of the MSS210(block920).

The EMS294may determine whether the interrupt is associated with a handoff of the MSS210(block930). If the interrupt is not associated with a handoff, the EMS294(e.g., via the communication interface810) may download the service flow context to the serving BS260to provide communication services to the MSS210(block940). For example, the EMS294may download the service flow context to the serving BS260when the MSS210initially registers for communication services as described in connection withFIG. 3. The EMS294may transmit the service flow context via an SNMP SET message. Accordingly, the serving BS260may transmit a DSA message to establish connection with the MSS210. As a result, the EMS294(e.g., via the controller830) may manage the MSS210via the proxy SNMP agent262associated with the serving BS260(block950).

Referring back to block930, if the interrupt is associated with a handoff, the EMS294may download the service flow context to the target BS270to provide communication services to the MSS210(block960). The target BS270may store the service flow context in the MIB274. In one example, the EMS294may download the service flow context to the target BS270when the serving BS260initiates a handoff request as described in connection withFIG. 5. In another example, the EMS294may also download the service flow context to the target BS270when the MSS210initiates a handoff request as described in connection withFIG. 7. The serving BS260may transmit a handoff request to the MSS210requesting the MSS210to handoff to the target BS270(block970). The target BS270may transmit a DSA message to establish connection with the MSS210. Accordingly, the EMS294may remove the service flow context locally stored in the MIB264at the serving BS260(block980). The proxy SNMP agent272may access the MSS and BS objects manageable by the EMS294that are stored in the MIB274. To retrieve parameters from the MSS210, the SNMP agent272may convert SNMP messages from the EMS294into MAC messages to the MSS210. As a result, the EMS294(e.g., via the controller830) may manage the MSS210via the proxy SNMP agent272associated with the serving BS270(block990). The methods and apparatus described herein are not limited in this regard.

Although the methods and apparatus disclosed herein are described with respect to mobile BWA networks, the methods and apparatus disclosed herein may be readily applicable to other types of BWA networks such as fixed BWA networks. Further, while the methods and apparatus disclosed herein are described with respect to BWA networks, the methods and apparatus disclosed herein may be applied to other suitable types of wireless communication networks. For example, the methods and apparatus disclosed herein may be applied to wireless personal area networks (WPANs), wireless local area networks (WLANs), wireless metropolitan area networks (WMANs), and/or wireless wide area networks (WWANs).

FIG. 10is a block diagram of an example processor system2000adapted to implement the methods and apparatus disclosed herein. The processor system2000may be a desktop computer, a laptop computer, a handheld computer, a tablet computer, a PDA, a server, an Internet appliance, and/or any other type of computing device.

The processor system2000illustrated inFIG. 10may include a chipset2010, which includes a memory controller2012and an input/output (I/O) controller2014. The chipset2010may provide memory and I/O management functions as well as a plurality of general purpose and/or special purpose registers, timers, etc. that are accessible or used by a processor2020. The processor2020may be implemented using one or more processors, WLAN components, WMAN components, WWAN components, and/or other suitable processing components. For example, the processor2020may be implemented using one or more of the Intel® Pentium® technology, the Intel® Itanium® technology, the Intel® Centrino™ technology, the Intel® Xeon™ technology, and/or the Intel® XScale® technology. In the alternative, other processing technology may be used to implement the processor2020. The processor2020may include a cache2022, which may be implemented using a first-level unified cache (L1), a second-level unified cache (L2), a third-level unified cache (L3), and/or any other suitable structures to store data.

The memory controller2012may perform functions that enable the processor2020to access and communicate with a main memory2030including a volatile memory2032and a non-volatile memory2034via a bus2040. The volatile memory2032may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM), and/or any other type of random access memory device. The non-volatile memory2034may be implemented using flash memory, Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), and/or any other desired type of memory device.

The processor system2000may also include an interface circuit2050that is coupled to the bus2040. The interface circuit2050may be implemented using any type of interface standard such as an Ethernet interface, a universal serial bus (USB), a third generation input/output interface (3GIO) interface, and/or any other suitable type of interface.

One or more input devices2060may be connected to the interface circuit2050. The input device(s)2060permit an individual to enter data and commands into the processor2020. For example, the input device(s)2060may be implemented by a keyboard, a mouse, a touch-sensitive display, a track pad, a track ball, an isopoint, and/or a voice recognition system.

One or more output devices2070may also be connected to the interface circuit2050. For example, the output device(s)2070may be implemented by display devices (e.g., a light emitting display (LED), a liquid crystal display (LCD), a cathode ray tube (CRT) display, a printer and/or speakers). The interface circuit2050may include, among other things, a graphics driver card.

The processor system2000may also include one or more mass storage devices2080to store software and data. Examples of such mass storage device(s)2080include floppy disks and drives, hard disk drives, compact disks and drives, and digital versatile disks (DVD) and drives.

The interface circuit2050may also include a communication device such as a modem or a network interface card to facilitate exchange of data with external computers via a network. The communication link between the processor system2000and the network may be any type of network connection such as an Ethernet connection, a digital subscriber line (DSL), a telephone line, a cellular telephone system, a coaxial cable, etc.

Access to the input device(s)2060, the output device(s)2070, the mass storage device(s)2080and/or the network may be controlled by the I/O controller2014. In particular, the I/O controller2014may perform functions that enable the processor2020to communicate with the input device(s)2060, the output device(s)2070, the mass storage device(s)2080and/or the network via the bus2040and the interface circuit2050.

While the components shown inFIG. 10are depicted as separate blocks within the processor system2000, the functions performed by some of these blocks may be integrated within a single semiconductor circuit or may be implemented using two or more separate integrated circuits. For example, although the memory controller2012and the I/O controller2014are depicted as separate blocks within the chipset2010, the memory controller2012and the I/O controller2014may be integrated within a single semiconductor circuit.

Although certain example methods, apparatus, and articles of manufacture have been described herein, the scope of coverage of this disclosure is not limited thereto. On the contrary, this disclosure covers all methods, apparatus, and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents. For example, although the above discloses example systems including, among other components, software or firmware executed on hardware, it should be noted that such systems are merely illustrative and should not be considered as limiting. In particular, it is contemplated that any or all of the disclosed hardware, software, and/or firmware components could be embodied exclusively in hardware, exclusively in software, exclusively in firmware or in some combination of hardware, software, and/or firmware.