Methods and apparatus for resource management architectures for internet protocol based radio access networks

TECHNICAL FIELD The embodiments of the present invention relate to the field of wireless networks, and more specifically, to the resource management of wireless access network based on Internet Protocol (IP) (RRM) structure method and device.

BACKGROUND Wireless resource management in an IP-based wireless access network includes providing decision support and associated functions for an IP-based wireless access network. The IP-based wireless access network is, for example, the Worldwide Interoperability for Microwave Access (WiMAX) network. . Some of these functions include: for example, mobile client admission control, that is, confirming that the required radio resources are available at the potential target base station (BS) before service handover; service flow admission control, that is, creating or Modify existing/additional service flows; select values for permitted and valid quality of service (QoS) parameter sets for service flows; load control, which loads the system beyond the threshold and needs to use some counting measurements to make the system return Feasible loading conditions are managed; and HO preparation and control are used to improve and maintain overall performance indicators (for example, RRM can assist in system loading balance by helping to select the most suitable base station during the service HO period).

BRIEF DESCRIPTION OF THE DRAWINGS Through the detailed description below in conjunction with the accompanying drawings, it will be easy to understand the embodiments of the present invention. For ease of description, the same reference numerals indicate elements of the same structure. The embodiments of the present invention are shown in the drawings by way of example and not limitation.

Fig. 1 is a schematic diagram of an exemplary IP-based radio access network incorporating the principles of the present invention according to various embodiments; Fig. 2 is an exemplary RRM for an access service network incorporating the principles of the present invention according to various embodiments Schematic diagram of the structure; FIG. 3 is an IP-based wireless access network used to incorporate the principles of the present invention according to various embodiments

200780013901.2 A schematic diagram of an exemplary RRM structure of IP multicast; FIG. 4 is a flowchart showing an exemplary operation of an RRM structure according to various embodiments of the present invention; FIG. 5 is a diagram showing an exemplary operation of the RRM structure according to various embodiments of the present invention A signaling diagram of an exemplary multicast packet format used during communication within a multicast group; and FIG. 6 is a block diagram representing an exemplary processor system that can be used to implement various aspects of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS In the following detailed description, reference is made to the accompanying drawings that constitute a part of this description. In the accompanying drawings, the same reference numerals indicate the same components, and the accompanying drawings illustrate embodiments by way of example. In the embodiments, Realize the present invention. It should be understood that other embodiments and structural or logical changes may be adopted without departing from the scope of the present invention. Because the following detailed description is not intended to be limiting, and the scope of the embodiments according to the present invention is defined by the appended claims and their equivalents.

Various operations may be described in sequence according to multiple discrete operations in a manner that is helpful for understanding the embodiments of the present invention; however, the order of description should not be understood as implying that these operations are sequentially related.

This description can use orientation-based descriptions, such as up/down, back/front, and top/bottom. This description is only used to facilitate discussion and is not intended to limit the application of the embodiments of the present invention.

For the purposes of the present invention, the phrase "A/B" means A or B. For the purpose of the present invention, the phrase "A and/or B" means "(A), (B) or (A and B)". For the purpose of the present invention, the phrase "at least one of A, B and C" means "(A), (E), (C), (A and B), (A and C), (B and C) or (A, E and C)". For the purpose of the present invention, the phrase "(A) E" means "(B) or (AB)", that is, A is an optional element.

This description may use the phrase "in an embodiment" or "in multiple embodiments", which respectively refer to one or more identical or different embodiments. In addition, the terms "including", "including", "having" and the like as used for the embodiments of the present invention are synonymous.

The embodiments of the present invention provide a method and apparatus for an effective radio resource management (RRM) structure of a radio access network based on the Internet Protocol (IP). The method and system described here do not

200780013901.2 is limited to this aspect.

In order to provide a clear and understandable description of the embodiments of the present invention, a brief description of a radio access network (RAN) based on the Internet Protocol (IP) is provided below. In addition, an example of the method and apparatus for the RRM structure is described with reference to the RAN. It should be understood that the principles and techniques of the embodiments of the present invention can be applied to the RRM structure of a RAN network, where the RAN network is for example, but not limited to, a worldwide interoperability for microwave access (WiMAX) network and a wireless fidelity (Wi-Fi) network. , Third-generation cellular networks and ultra-wideband (UWB) networks. For the sake of brevity, the IP-based RANo of FIG. 1 is described in accordance with the WiMAX RAN example. In addition, although some examples are described with reference to the standards developed by the Institute of Electrical and Electronics Engineers (IEEE), the methods and systems disclosed here are not limited to Therefore, these methods and systems can be used by other special interest groups and/or standard development organizations (for example, the Wireless Fidelity (Wi-Fi) Alliance, the Worldwide Interoperability for Microwave Access (WiMAX) Forum, the Infrared Data Association (IrDA)). ), specifications and/or standards developed by the Third Generation Partnership Project (3GPP), Ultra Wideband (UWB) Forum, etc.).

Figure 1 shows a simplified exemplary IP-based RAN and radio resource management (RRM) structure incorporating the theory of the present invention according to various embodiments. The first WiMAX RAN 1 (100) shown includes a gateway (GW) 106 that is communicatively coupled to base stations 110, 112, and 114 via links 124, 126, and 128, respectively. The illustrated second WiMAX RAN 2 (102) includes GW 108, which is communicatively coupled to base stations (BS) 116 and 118 via links 130 and 132, respectively. Each GW includes an omnidirectional antenna (not shown). The third WiMAX RAN 3 (104) shown does not include a gateway, but includes two base stations 120 and 122.

Each base station includes an RRM component in the form of a radio resource agent (RRA). The RANs 100, 102, and 104 also include at least one other RRM component in the form of a radio resource controller (RRC), and the other RRM component may be located in the base station or the GW according to the deployment diagram of the RAN. Therefore, in the exemplary embodiment shown in FIG. 1, the RANs 100 and 102 include the RRC inside their GWs 106 and 108, respectively, and the RAN includes the RRC inside its base station 120. In addition, each RAN may include multiple gateways. The Internet Protocol (IP) backbone network 144 is connected to WiMAX broadband.

In one example, the mobile client device (MCD) 154 uses the IEEE 802.16 standard family (for example, IEEE standard 802.16-2004 published on September 18, 2004; IEEE standard 802.16e published on February 28, 2006, etc.) Defined physical layer (PHY) and medium access control layer (MAC) features to access the network (via the appropriate base station). Exemplary MCDs include

200780013901. 2 Notebook computers and handheld wireless devices (for example, personal digital assistants (PDAs), handheld computers, cellular phones that support 802.16 links, etc.).

To support central office operations, each MCD 154 provides an appropriate RAN interface, as represented by a PCMCIA card 158 for notebook computers, for example. Optionally, the RAN radio interface can be built into the MCD 154. Each MCD shown is communicatively coupled to the base station via link 156.

Generally, the MCD 154 can access the RAN via some form of subscription service provided by a RAN service provider, although some RAN services can be provided free of charge, such as university campuses, city coverage, and so on. Therefore, GWs 106 and 108 are depicted as being communicatively coupled to and managed by WiMAX core network 136 via links 138 and 140, respectively. In addition, GWs 106 and 108 may be communicatively coupled to each other as depicted by link 134. The RAN 104 is communicatively coupled to the WiMAX core network via its base stations 120 and 122 as depicted by link 142. It should be understood that the coupling between a given GW and WiMAX core network 136 can be via a dedicated link (eg, private trunk, etc.), or via another communication method, such as via an IP backbone network 144, which includes multiple network elements 146. (For example, backbone switches and routers), as depicted by links 135 and 145. The WiMAX core network 136 is communicatively coupled to the IP backbone network 144 via a link 143.

The illustrated Voice over IP (VoIP) provider 148 is communicatively coupled to the IP backbone 144 to enable telephone calls to be carried over the network infrastructure using packet transmission. For illustrative purposes, the VoIP device depicted in FIG. 1 passes through a VoIP provider network 148, a telco network 150, and a telephone 152 (or other suitable devices such as desktop computers, notebook computers, and handheld wireless devices (eg, personal digital Assistant (PDA), handheld computer, cellular phone)).

Fig. 2 schematically shows a general RRM structure for RAN incorporating the theory of the present invention according to various embodiments. It can be seen that the first RAN 200 includes RRC 202 and RRA 204, 205. The second RAN 206 includes RRC 208 and RRA 210, 212, and 214. RRC 202 communicates with RRC 208 and RRA 204, 205 of its own ASN. RRC 208 communicates with RRC 202 and RRA210, 212, and 214. The interface through which RRM messages are sent is based on IP.

The source words of the key message used for RAN include: base station spare capacity request, which is sent to the base station that requires a free capacity report; and Per-base station spare capacity report. ), which is sent in response to base

200780013901.2 No. station spare capacity request (base station spare capacity request). These reports are indexed by the identification (ID) of each base station and indicate the wireless resources available at a specific base station, for example as a tool for base station selection during network entry or handover. This report can be passive or unsolicited. Such reports are sent from RRA to RRC, and between RRCs, so that all relevant RRCs can obtain information about the current free capacity of the base station they are responsible for or neighbor base stations in other RANs.

Other source terms include the "Per MCD physical (PHY) layer report" request, which involves, for example, a request for radio resources used by the currently activated service flow in the MCD, and is used by the base station serving the MCD. And "Per MCD PHY report response", which is a response to "Per MCD PHY layer report" and sent from the base station serving the MCD Sent to the requesting base station.

Another source term includes base station radio resource status update (base station radio resource status update), which is generated from RRC to RRA, and is used to propose a connection from the base station on the air link based on the load from the neighbor base station (for handover purposes). ) Changes in the broadcast "neighbor advertisement message".

When switching services for MCD, before the switching occurs, the content of "base station spare capacity request" can be used. The base station currently serving MCD can select some or all of the base stations from the neighboring station list of the base station. Request the report. The neighbor list usually identifies the base stations adjacent to a specific base station used for various purposes such as service handover. In addition, the base station serving the MCD can be unsolicited from the base station serving the MCD to the neighbor list during the handover preparation. All other base stations send Per MCD PHY report response (per MCD PHY report response), or can respond to the "Per MCD physical (PHY) layer report (per MCD physical layer report)" from the target base station (once the target base station is selected (For service handover) send the "Per MCD PHY report response" from the serving base station to the target base station. The content of Per MCD PHY report response can be used to delete the neighbor station list before sending the neighbor station announcement message on the air link. This can be sent from the RRC or base station located in the network gateway to all or some of the base stations in the network.

Many of the RRM messages described above are intended for multiple recipients. A useful way to deliver messages intended for multiple recipients (with minimal message duplication transmission) is to use the Internet Protocol (IP)

200780013901.2 No. Multicast. The IP multicast technology is used to provide communication between a radio resource controller (for example, a gateway) and a radio resource agent (for example, a base station) in a network. IP multicasting involves sending a single message from a source node in the network to multiple destination nodes. Typically, a unique IP address is assigned to a predetermined group of communication nodes in the network. The message can then be delivered to the IP address and each node that is part of the group that can read the message. This reduces the number of copies of RRM messages sent, and therefore improves performance compared to sending multiple IP unicast messages.

In order to utilize IP multicast during RAN operation in the RAN, many multicast groups can be formed and maintained in the network. A unique IP multicast address can be assigned to each multicast group. Then, when information is needed or provided, RRC can send the RRM message as an IP multicast message to the corresponding multicast group. The IP multicast message is sent via the IP backbone 144.

Various processes are defined in the Requests for Comments (RFC: Requests for Comments) of the Internet Engineering Task Force (IETF), which can be used to perform various tasks related to various embodiments of the present invention. For example, RFC has procedures for the following operations: generating a multicast group, allowing entities (for example, base stations, PCs, etc.) to join and leave the multicast group, and perform packet switching in the multicast group. For example, RFC 966 (1985). These procedures can be used in various embodiments of the present invention. Optionally, other procedures can be used. In at least one embodiment of the present invention, the base stations in the multicast group use a shortest path tree-based multicast distribution tree for transmitting multicast messages. By using a multicast distribution tree based on the shortest path tree, the delay of message transmission among multicast members is reduced.

Fig. 3 schematically shows an RRM structure using IP multicast in combination with the theory of the present invention according to multiple embodiments. Specifically, FIG. 3 shows two RANs 300, 302 set up as IP multicast groups. Each RAN 300 and 302 includes RRC 304 and 306, respectively. The multicast group 300 includes a plurality of RRAs 308, 310, 312, and 314, and the multicast group 302 includes a plurality of RRAs 316, 318, and 320. Each RRM component can send and receive information, and therefore includes a transceiver. In the example of FIG. 3, the RRC is located in the gateway, but as mentioned before, it can also be located in the base station.

The establishment of a multicast group can be accomplished in several different ways. Examples include: each multicast group including all base stations in the first layer of the central cell in the RAN (ie, seven base stations constitute a multicast group); including all base stations in the neighbor list of the central cell (which will Change over time, so the multicast group association will also change over time) each multicast group; and each multicast group that can optionally include RRC. In the first and second examples, RRC is located in the gateway, and in the third example, RRC is located in the base station. Therefore, the establishment of a multicast group is an implementation scheme, which varies with the deployment scheme

200780013901.2 No. changes.

Therefore, a multicast group is set up for message reception according to various embodiments of the present invention. Each multicast group includes multiple RRAs, and may include one or more RRCs according to the implementation, for receiving multicast messages. 4, as an example of the use of a multicast group, before initiating a service handover for the MCD from the serving base station, in block 400, the RRA of the serving base station (for example, BS 310) may send a single IP multicast packet from the neighboring station All or a subset of the potential target base stations in the list request "base station spare capacity request", where the IP multicast packets are destined for all or a subset of the potential target base stations in the neighboring station list, and pass Send a request to multicast group 300 to send a single IP multicast packet. In response to block 410, RRC 304 may use a single IP multicast message to send a "Per-base station spare capacity report (per- Base station remaining capacity report) to indicate the availability of wireless resources in neighboring base stations. In addition, before the handover is initiated, the RRA of the serving base station 310 in block 420 may send a single IP multicast message to the multicast group 300 to send the MCD subject to the handover to all or a subset of the target base stations in the neighbor list. "Per MCD physical (PHY) layer report (per MCD physical layer report).

FIG. 5 is a signaling diagram showing an exemplary multicast packet format 510 used in the communication process between RRC and a multicast group in a wireless network according to an embodiment of the present invention. As shown in the figure, the multicast packet format 510 may include: an IP header 512, a transmission protocol header 514 (for example, User Datagram Protocol (UDP), Stream Control Transmission Protocol (SCTP), etc.), a RAN header 516, and a message 518. The IP header 512 may include the IP multicast address of the multicast group as the subject content of the current message, and the like. The transport protocol header 514 may include, for example, source and destination port information and other transport protocol parameters. In one example, the RAN header 516 may include header information described by the IEEE 802.16 standard family and based on the IEEE 802.16 standard family. The message 418 may include, for example, the ID of a specific RRA from which to search for messages.

FIG. 6 is a block diagram of an exemplary processor system 2000 according to different embodiments applicable to the methods and apparatuses disclosed herein. The processor system 2000 may be a desktop computer, a laptop computer, a handheld computer, a tablet computer, a PDA, a server, Internet application software, and/or other types of computing devices.

The processor system 2000 shown in FIG. 6 may include a chipset 2010, which includes a memory controller 2012 and an input/output (I/O) controller 2014. The chipset 2010 may provide storage

200780013901.2 Controller and I/O management functions, multiple general-purpose and/or special-purpose registers, timers, etc., which can be accessed or used by the processor 2020. The processor 2020 may be implemented using one or more of the following components: a processor, a wireless personal area network (WPAN) component, a wireless local area network (WLAN) component, a wireless metropolitan area network (WMAN) component, a wireless wide area network (WWAN) component, and / Or other appropriate processing components. For example, the processor 2020 can be implemented using one or more of the following technologies: Intel® Pentium® technology, Intel® Itanium® technology, Intel® CentrinoTM technology, Intel® Duo technology, Intel® XeonTM technology , And/or Intel®XScale® technology. Optionally, other processing technologies can be used to implement the processor 2020. The processor 2020 includes a cache 2022, which can use the first layer of unified standard cache (L1), the second layer of unified standard cache (L2), and the third layer of unified standard cache. (L3) and/or other suitable structures for storing data.

The memory controller 2012 can perform the following functions: enable the processor 2020 to access and communicate with the main memory 2030 through the bus 2040. The main memory 2030 includes a volatile memory 2032 and a non-volatile memory 2034. The volatile memory 2032 can be configured by The following memory implementations: 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 memory 2034 may be implemented using the following memories: flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), and/or other required types of memory devices.

The processor system 2000 also includes an interface circuit 2050 coupled to the bus 2040. The interface circuit 2050 is implemented using any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), a third-generation input/output (3GIO) interface and/ Or other suitable types of interfaces.

One or more input devices 2060 may be connected to the interface circuit 2050. The input device 2060 allows the individual to input data and commands into the processor 2020. For example, the input device 2060 may be implemented by the following components: a keyboard, a mouse, a touch-sensing display, a trackpad, a trackball, isopoint, and/or a voice recognition system.

One or more output devices 2070 may be connected to the interface circuit 2050. For example, the output device 2070 is realized by a display device (for example, a light emitting diode display (LED), a liquid crystal display (LCD), a cathode ray tube (CRT) display), a printer, and/or a speaker). In addition, the interface circuit 2050 may include an image driver card.

The processor system 2000 may also include one or more mass storage devices 2080 to store software

200780013901. 2 Article or data. Examples of such mass storage devices 2080 include: floppy disks and drives, hard disk drives, compact disks and drives, and Digital Visual Disc (DVD) and drives.

The interface circuit 2050 may also include a communication device, such as a modem or a network interface card, for exchanging data with an external computer via a network. The communication link between the processor system 2000 and the network may be any type of network connection, such as an Ethernet connection, digital subscriber line (DSL), telephone line, cellular telephone system, coaxial cable, etc.

The I/O controller 2014 controls the access to the input device 2060, the output device 2070, the mass storage device 2080, and/or the network. Specifically, the I/O controller 2014 may perform the following functions: enable the processor 2020 to communicate with the input device 2060, the output device 2070, the mass storage device 2080, and/or the network via the bus 2040 and the interface circuit 2050.

Although the components shown in FIG. 6 are depicted as independent blocks in the processor system 2000, the functions performed by some of the blocks in these blocks may be integrated within a single semiconductor circuit, or may be implemented using two or more independent integrated circuits. . For example, although the memory controller 2012 and the I/O controller 2014 are depicted as independent blocks in the chipset 2010, the memory controller 2012 and the I/O controller 2014 may be integrated in a single semiconductor circuit.

Although certain embodiments are described and exemplified here for the purpose of describing preferred embodiments, those skilled in the art should note that, without departing from the scope of the present invention, many different options are suitable for achieving the same purpose. And/or equivalent embodiments or implementations may be substituted for the illustrated and described embodiments. Those skilled in the art should note that the embodiments according to the present invention can be implemented in many different ways. This application is intended to cover any modifications and changes of the embodiments discussed herein. Therefore, it is clearly pointed out here that the embodiments according to the present invention are only limited by the claims and their equivalents.

200780013901.2