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

Method and equipment for resource management framework of radio access network based on internet protocol

The embodiment of the present invention relates to the field of wireless networks, and particularly relates to a method and equipment for the resource management (RRM) architecture of a radio access network based on the Internet Protocol (IP).

Radio resource management in IP-based radio access networks involves programs that provide decision support and related functions for IP-based radio access networks such as WiMAX networks. Some of these functions include mobile client admission control (mobile client admission control), that is, first confirm the necessary radio resources that may be used by the target base station (BS) before handing over (HO) services; service flow Admission control, that is, to generate or modify existing/additional service processes for existing MSs in the network; the selection of permitted and effective quality of service (QoS) parameter group values for service processes; load control to manage system load The threshold is exceeded and some countermeasures are needed to bring the system back to the available load; and HO preparation and control to improve and maintain the overall performance index (for example, RRM can assist in selecting the most suitable base station during the HO period of service, It helps to balance system load.

The embodiments of the present invention provide a method and device for a radio resource management (RRM) architecture of a radio access network based on Internet Protocol (IP). Other embodiments will be described below, and these embodiments constitute the scope of the patent.

In the following embodiments, reference will be made to the drawings constituting a part of the present invention. In all the drawings, the same code represents similar parts, and the embodiments of the present invention are used as examples. The drawings are shown. We should understand that other embodiments can also be used, and structural and logical changes can be made without departing from the scope of the present invention. Therefore, the following implementations should not be interpreted in a restrictive manner, and the scope of the embodiments according to the present invention is defined by the final patent application scope and its equivalents.

It is possible to explain each operation as a plurality of discrete operations that are executed in sequence in a way that is helpful for understanding the embodiments of the present invention; however, the order of description should not be interpreted as that these operations are necessarily dependent on the order.

The description can use perspective-based descriptions such as top/bottom, back/front, and top/bottom. These descriptions are only used to assist the discussion, and their intention is not to limit the application of the embodiments of the present invention.

To facilitate the description of the present invention, the term "A/B" means A or B. In order to facilitate the description of the present invention, the term "A and/or B" means "(A), (B), or (A and B)". In order to facilitate the description of the present invention, the phrase "at least one of A, B, and C" means "(A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C)". In order to facilitate the description of the present invention, the word "(A)B" means "(B) or (AB)", that is, A is an optional element.

This description may use the words "in one embodiment" or "in each embodiment," and these words may respectively refer to one or more of the same or different embodiments. In addition, when the terms "including", "including", and "having" are used in the manner related to the embodiments of the present invention, these terms are all synonymous.

The embodiments of the present invention provide an efficient radio resource management (RRM) architecture method and device based on Internet Protocol (IP) radio access network. The methods and systems described in the present invention are not limited to this point.

In order to provide a clear and easy-to-understand description of the embodiments of the present invention, a brief description of the Radio Access Network (RAN) based on the Internet Protocol (IP) will be provided below. In addition, the exemplified method and device for the RRM architecture are described with reference to the RAN. We should understand that the principles and techniques of the embodiments of the present invention can be used in such as (but not limited to) WiMAX networks, wireless fidelity (Wi-Fi) networks, third-generation (3G) ) The RRM architecture of cellular networks and RAN networks such as ultra-wideband (UWB) networks. In order to simplify the description, the IP-based RAN in Figure 1 is shown and described in the manner of WiMAX RAN. In addition, although some examples are described with reference to the standards developed by the Institute of Electrical and Electronics Engineers (IEEE), the method and system disclosed in the present invention are not limited to this, and it is easy to apply these examples to other special rights groups ( special interest group) and/or standard development organizations (for example, Wireless Fidelity (Wi-Fi) Alliance, Worldwide Interoperability for Microwave Access (WiMAX) Forum, Infrared Data Association (IrDA), Third Generation Mobile Communications Cooperation Project (3GPP) , Ultra Wideband (UWB) Alliance and other units) developed many specifications and/or standards.

Figure 1 shows an IP-based RAN added to the simplified illustration of the disclosure of the present invention according to various embodiments of the Radio Resource Management (RRM) architecture. A first WiMAX RAN 1 (100) is shown, the first WiMAX RAN 1 (100) includes being communicatively coupled to a base station (110) via links (124), (126), and (128), respectively , (112), and (114) gateways (GW) (106). A second WiMAX RAN 2 (102) is shown. The second WiMAX RAN 2 (102) includes being communicatively coupled to a base station (BS) (116) and ( 118) GW(108). Each GW includes an omnidirectional antenna (not shown in the figure). A third WiMAX RAN 3 (104) is shown. The third WiMAX RAN 3 (104) does not include a gateway, but includes two base stations (120) and (122).

Each base station contains an RRM component in the form of a radio resource agent (RRA). RAN (100), (102), and (104) also include another RRM component in the form of at least one radio resource controller (RRC), and depending on the RAN deployment profile, the RRC can be set at the base station or GW. Therefore, in the embodiment shown in Figure 1, RAN (100) and (102) are included in the RRC in its GW (106) and (108), respectively, and RAN (104) is included in the base station (120) The RRC of the RAN. In addition, each RAN may include multiple gateways. The Internet Protocol (IP) backbone network (144) is connected to the WiMAX broadband network.

In one example, the mobile user device (MCD) (154) uses IEEE 802.16 series standards (for example, IEEE standard 802.16-2004 issued on September 18, 2004; IEEE standard 802.16e issued on February 28, 2006, etc. The physical layer (PHY) and media access control layer (MAC) functions specified by the standard (via an appropriate base station) access the network. Illustrated MCDs include notebook computers and handheld wireless devices (for example, personal digital assistants (PDAs) supporting 802.16 connections, pocket PCs, and cellular phones, etc.).

In order to support the operation of the mobile station, each MCD (154) provides an appropriate RAN interface, for example, the RAN interface shown in the PCMCIA interface card (158) of a notebook computer. Alternatively, the RAN wireless interface can be built into the MCD (154). Each MCD shown in the figure is communicatively coupled to the base station via a link (156).

Generally speaking, the MCD (154) can access the RAN through a certain subscription service provided by the RAN service provider, but RAN services such as university campus or urban wireless network coverage may be provided free of charge. Therefore, the figure shows that GW (106) and (108) are communicatively coupled to the WiMAX core network (136) via links (138) and (140), and are connected to the WiMAX core network (136). )manage. In addition, the link (134) shown in the figure allows GW (106) and (108) to be communicatively coupled to each other. The link (142) shown in the figure communicatively couples the RAN (104) to the WiMAX core network via its base stations (120) and (122). We should understand that the coupling between a specific GW and the WiMAX core network (136) can be via a dedicated link (for example, a dedicated link such as a private trunk), or via another communication link such as an IP backbone network (144). And the links (135) and (145) shown in the figure, and the IP backbone network (144) includes a plurality of network elements (146) (for example, backbone network switches and routers). The WiMAX core network (136) is communicatively coupled to the IP backbone network (144) via a link (143).

The Voice over Internet Protocol (VoIP) service provider (148) shown in the figure is communicatively coupled to the IP backbone network (144) so that it can be carried over the Internet infrastructure using packet transmission call. For ease of illustration, the VoIP service provider network (148), telecommunication network (150), and telephone (152) (or such as desktop computers, notebook computers, and handheld wireless devices (for example, Other applicable devices such as personal digital assistants (PDAs), pocket PCs, cellular phones), etc. representatively show VoIP equipment.

Figure 2 schematically shows a general RRM architecture of the RAN added to the disclosure of the present invention according to various embodiments. As shown in the figure, 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) and (205) of its own ASN. RRC (208) communicates with RRC (202) and RRA (210), (212), and (214). The interface used to send RRM messages is based on IP.

The key message primitives of RAN include: "base station spare capacity request" sent to the base station of the spare capacity source, and "base station spare capacity request" sent in response to the "base station spare capacity request". Per-base station spare capacity report". These reports are indexed with the identification code of each base station, and these reports indicate the available radio resources of a specific base station, which are used as a tool for base station selection such as during network entry or handover. Such reports can be solicited or unsolicited. Since the RRA transmits such reports to the RRC, and transmits such reports between RRCs, all interested RRCs can obtain information about the existing spare capacity of the responsible base station or other adjacent base stations of the RAN.

Other primitives include: "Per MCD physical (PHY) layer report" requirements, which are related to the requirements of radio resources used by the currently valid service process in MCD, and are different from each other. The request is made at any base station serving the MCD base station; and "Per MCD PHY report response" as a response to the "per MCD PHY layer report", and is from the base serving MCD The station transmits the response to the requesting base station.

Another primitive includes "base station radio resource status update", which is generated from RRC to RRA, so that the base station proposes to change the broadcast on the air link according to the load of the neighboring base station. The "neighbor advertisement message" (for the purpose of handover).

The content of "Base Station Spare Capacity Requirements" can be used when handing over MCD services before handing over. The base station currently serving the MCD may request the report from all or part of the base stations in the list of neighboring base stations. The neighboring base station list usually identifies the neighboring base stations of a specific base station for various purposes such as service delivery. In addition, during the handover preparation period, an unsolicited method can be used to send "each MCD PHY report response" from the base station serving the MCD to all other base stations in the neighboring base station list, or it can respond from the target The base station "reports each MCD PHY layer", and the primitive is transmitted from the serving base station to the target base station (once the target base station is selected for service delivery). Before transmitting the advertising message of the neighboring base station on the air link, the content of "each MCD PHY report response" can be used to delete the neighboring base station list. The primitive can be transmitted to all or part of the base station in the network from the RRC set in the network gateway or base station.

Many of the aforementioned RRM messages target multiple recipients. An advantageous way to transmit messages targeted for multiple recipients (in the case of minimum message copy transmission) is to use Internet Protocol (IP) multicasting. The IP multicast technology is used to provide communication between the radio resource controller (for example, gateway) and the radio resource agent (for example, base station) in the network. IP multicasting involves sending a single message from a source node in the network to multiple destination nodes. Usually a unique IP address is assigned to a set of predetermined communication nodes in the network. The message can then be sent to the IP address, and every node that is part of the group can read the message. This method reduces the number of copies of RRM messages that are transmitted, and thus improves performance when compared with unicast messages that transmit multiple IPs.

In order to use IP multicast during RAN operations in the RAN, some multicast groups can be formed and maintained in the network. Each multicast group can be assigned a unique IP multicast address. Then when information is needed or is being provided, RRC can transmit the RRM message as an IP multicast message to the corresponding multicast group. The IP multicast message is transmitted via the IP backbone network (144).

Various programs that can be used to perform various tasks associated with various embodiments of the present invention are defined in the Request for Comments (RFC) of the Internet Engineering Task Force (IETF). For example, there are programs in the RFC that are used to generate multicast groups so that entities (such as base stations, personal computers, etc.) can join and leave the multicast group, and perform packets in the multicast group Work such as exchange. An example is RFC 966 (1985). These programs can be used in various embodiments of the present invention. Other programs can be used instead. In at least one embodiment of the present invention, the base stations in the multicast group use a multicast distribution tree based on the shortest path tree for the transmission of multicast messages. By using a multicast distribution tree based on the shortest path tree, the message transmission between the multicast member entities will have a shorter delay.

Figure 3 schematically shows the RAN added to the disclosure of the present invention according to various embodiments using IP multicast. Figure 3 particularly shows two RANs (300), (302) configured as an IP multicast group. Each RAN (300), (302) includes RRC (304), (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 thus includes a transceiver. In the example shown in Figure 3, the RRCs are set in the gateway, but as described above, the RRCs can also be set in the base station.

The generation of multicast groups can be performed in several different ways. Examples include: each multicast group includes all base stations in the first tier of the central cell in the RAN (that is, several base stations form a multicast group); The point broadcast group includes all the base stations in the neighbor base station list of the central cell (the neighbor base station list will change from time to time, and therefore the relevance of the multicast group will also change from time to time); and each The multicast group can optionally include RRC. In the first and second examples, the RRC is set in the gateway, and in the third example, the RRC is set in the base station. Because the generation of a multicast group is an implementation point of view, the way it is generated will vary with different deployments.

Therefore, according to various embodiments of the present invention, each multicast group is configured to receive messages. Depending on the implementation, each multicast group includes a plurality of RRAs and optionally one or more RRCs in order to receive multicast messages. Please refer to Figure 4 as an example of using multicast groups. Before the service handover from the serving base station to the MCD starts, the RRA of the serving base station (for example, BS (310)) can be used in step (400 ) In the list of neighboring base stations for all or part of the possible target base station request "base station spare capacity request", the method is to transmit the request to the multicast group (300), and the transmission destination is the neighboring base station A single IP multicast packet of all or part of the possible target base station in the base station list. In step (410), RRC (304) can use a single IP multicast message to send the "report of spare capacity for each base station" to the base stations in the multicast group (300) to instruct them The available radio resources in the neighboring base station in response. In addition, before the handover starts, the RRA serving the base station (310) can in step (420) transmit the "reports of each MCDPHY layer" of the MCD that is undergoing the handover to the possible target bases in the neighboring base station list. The transmission method of all or part of the station is to transmit a single IP multicast message to the multicast group (300).

Figure 5 is a signal diagram of an exemplary multicast packet format (510) that can be used during communication between each RRC and each 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: IP header (512), transmission protocol header (514) (for example, User Data Element Protocol (UDP), Data Stream Control Transmission Protocol (SCTP) ) And other protocol headers), RAN header (516), and message (518). The IP header (512) can especially include the IP multicast address of the multicast group that is the object of the current message. The transmission protocol header (514) may include information such as source and destination port information and other transmission protocol parameters. In an example, the RAN header (516) may include header information specified by the IEEE 802.16 series of standards and/or specified according to the IEEE 802.16 series of standards. The message (518) may include, for example, the identification code of a specific RRA as the source of the message being searched.

Figure 6 is a block diagram of an exemplary processor system (2000) suitable for implementing the methods and devices disclosed in this specification according to various embodiments. The processor system (2000) can be a desktop computer, a laptop computer, a handheld computer, a tablet computer, a PDA, a server, an Internet device, and/or any other type of computing device.

The processor system (2000) shown in Figure 6 may include a chipset (2010), and the chipset (2010) includes a memory controller (2012) and an input/output (I/O) controller (2014). The chipset (2010) can provide memory and I/O management functions, as well as multiple general-purpose and/or special-purpose registers, timers, etc. that can be accessed or used by the processor (2020). Can use one or more processors, wireless personal area network (WPAN) components, wireless local area network (WLAN) components, wireless metropolitan area network (WMAN) components, wireless wide area network (WWAN) components, and/or other Appropriate processing components implement the processor (2020). For example, you can use Intel<img file="TWI334298B_D0001.tif" />Core^TMTechnology, Intel<img file="TWI334298B_D0002.tif" />Pentium^TMTechnology, Intel<img file="TWI334298B_D0003.tif" />Itanium^TMTechnology, Intel<img file="TWI334298B_D0004.tif" />Centrino^TMTechnology, Intel<img file="TWI334298B_D0005.tif" />Core^TMDuo technology, Intel<img file="TWI334298B_D0006.tif" />Xeon^TMTechnology, and/or Intel<img file="TWI334298B_D0007.tif" />XScale^TMOne or more of the technologies implement the processor (2020). In alternative embodiments, other processing techniques may be used to implement the processor (2020). The processor (2020) can include cache memory (2022), and can use the first-level unified cache (L1), the second-level unified cache (L2), and the third-level unified cache ( L3), and/or any other suitable structure for storing data implements the cache (2022).

The memory controller (2012) is executable to enable the processor (2020) to access the main memory (2032) and non-dependent memory (2034) via the bus (2040). 2030), and communicate with the main memory (2030). Can synchronize 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 to implement electrical dependency Memory (2032). Flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or any other required type of memory device can be used to implement non-electrical memory ( 2034).

The processor system (2000) may also include an interface circuit (2050) coupled to the bus (2040). The interface circuit (2050) can be 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 any other appropriate type of interface.

One or more input devices (2060) can be connected to the interface circuit (2050). The input device (2060) allows individuals to input data and commands into the processor (2020). For example, the input device (2060) can be implemented by a keyboard, a mouse, a touch-sensitive display, a trackpad, a trackball, an isopoint, and/or a voice recognition system.

One or more output devices (2070) can also be connected to the interface circuit (2050). For example, the output device (2070) may be implemented by a display device (for example, a light emitting display (LED), a liquid crystal display (LCD), a cathode ray tube (CRT) display), a printer, and/or a speaker. The interface circuit (2050) can especially include a graphics driver card.

The processor system (2000) may also include one or more mass storage devices (2080) for storing software and data. Examples of such mass storage devices (2080) include floppy disks and floppy disk drives, hard disk drives, optical discs and optical disc drives, digital versatile discs (DVD), and DVD optical disc drives.

The interface circuit (2050) can also include a communication device such as a modem or a network interface card to help exchange data with external computers via the network. The communication link between the processor system (2000) and the network can be any type of network such as Ethernet connection, digital subscriber line (DSL), telephone line, cellular telephone system, or coaxial cable. Road connection.

The I/O controller (2014) can control the use of the input device (2060), output device (2070), mass storage device (2080), and/or the network. The I/O controller (2014) is especially executable to enable the processor (2020) to communicate with the input device (2060), output device (2070), and mass storage device (2080) via the bus (2040) and interface circuit (2050). , And/or the function of the network communication.

Although the components shown in Figure 6 are shown as individual blocks in the processor system (2000), the functions performed by some of these blocks can also be integrated in a single semiconductor circuit, or can be used Two or more individual integrated circuits perform these functions. For example, although the memory controller (2012) and I/O controller (2014) are shown as separate blocks in the chipset (2010), the memory controller (2012) can also be integrated in a single semiconductor circuit And I/O controller (2014).

Although some embodiments have been shown and described for the description of the preferred embodiments in this specification, those with general knowledge of the technology will understand that it is also possible to estimate without departing from the scope of the present invention. Various alternative and/or equivalent embodiments or implementations can achieve the same purpose instead of the illustrated and described embodiments. Those skilled in the art will easily understand that the embodiments according to the present invention can be implemented in a variety of ways. This application will cover the modifications or changes of the embodiments mentioned in this specification. Therefore, the embodiments according to the present invention will obviously only be limited by the scope of patent applications and their equivalents.

<p>100. . . The first WiMAX RAN</p><p>102. . . Second WiMAX RAN</p><p>124,126,128,103,132,156,136,134,138,140,142,135,145,143. . . link</p><p>110,112,114,116,118,120,122. . . Base station</p><p>106,108. . . Gateway</p><p>104. . . Third WiMAX RAN</p><p>144. . . IP backbone network</p><p>154. . . Mobile user device</p><p>158. . . PCMCIA card</p><p>136. . . WiMAX core network</p><p>146. . . Network components</p><p>148. . . VoIP provider network</p><p>150. . . Telecommunications network</p><p>200. . . First RAN</p><p>206. . . Second RAN</p><p>202,208,304,306. . . RRC</p><p>204,205,210,212,214,308,310,312,314,316,318,320. . . RRA 300,302. . . RAN</p><p>510. . . Multicast packet format</p><p>512. . . IP header</p><p>514. . . Transport protocol header</p><p>516. . . RAN header</p><p>518. . . message</p><p>2000. . . Processor system</p><p>2010. . . Chipset</p><p>2012. . . Memory controller</p><p>2014. . . I/O controller</p><p>2020. . . processor</p><p>2022. . . Cache</p><p>2012. . . Memory controller</p><p>2040. . . Busbar</p><p>2032. . . Dependent memory</p><p>2034. . . Non-electrical memory</p><p>2030. . . Main memory</p><p>2050. . . Interface circuit</p><p>2060. . . Input device</p><p>2070. . . Output device</p><p>2080. . . Mass storage device</p>

The embodiments of the present invention can be easily understood if you refer to the detailed description in the foregoing and cooperate with the drawings. To help this description, the same code numbers indicate similar structural elements. The embodiments of the present invention are shown in the drawings by way of example but not limitation.

Figure 1 is a schematic diagram of an Internet Protocol (IP)-based radio access network based on the disclosure of the present invention according to various embodiments; Figure 2 is a schematic diagram of the disclosure of the present invention according to various embodiments. Take a schematic diagram of an exemplary radio resource management (RRM) architecture of a service network; Figure 3 is an exemplary RRM architecture of an IP-based radio access network that is added to the disclosure of the present invention according to various embodiments using IP multicast Schematic diagram; Figure 4 is a flowchart of an example operation of the RRM architecture according to various embodiments of the present invention; Figure 5 is an example used during communication between multicast groups according to various embodiments of the present invention The signal diagram of the multicast packet format; and Figure 6 is a block diagram of an exemplary processor system that can be used to implement the various aspects of the present invention.