WO2012034474A1

WO2012034474A1 - Method and system for obtaining configuration information by relay node

Info

Publication number: WO2012034474A1
Application number: PCT/CN2011/078937
Authority: WO
Inventors: 梁爽; 卢飞; 游世林
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-09-14
Filing date: 2011-08-25
Publication date: 2012-03-22
Also published as: CN102404717A; CN102404717B

Abstract

Disclosed is a method for obtaining configuration information by a relay node (RN), comprising: when receiving a configuration information obtaining request sent by an RN, a network side judging whether a network node accessed by the RN is appropriate, and sending corresponding configuration information to the RN according to a judgment result. Also disclosed is a system for obtaining configuration information by an RN to implement the above method, comprising: a receiving unit, for receiving a configuration information obtaining request sent by an RN; a judging unit, for judging whether a network node accessed by the RN is appropriate according to the configuration information obtaining request; and a sending unit, for sending corresponding configuration information to the RN according to a judgment result of the judging unit. The present invention avoids downloading useless parameters by the RN to waste network resources and leakage of private information of operators, and provides higher access efficiency for the RN that needs to be reattached to the network.

Description

Method and system for relay node to acquire configuration information

The present invention relates to a technique for a relay node to acquire configuration information, and more particularly to a method and system for a relay node to obtain configuration information in a relay network. Background technique

In order to maintain the competitiveness of the third generation mobile communication system in the field of communication, the 3GPP, 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) standard working group is working on the evolution of the Evolved Packet System (EPS). Figure 1 is a system structure diagram of an evolved packet network. As shown in Figure 1, the EPS system mainly includes an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and an Evolved Packet Core Network (EPC). Evolved Packet Core) two parts. The system's EPC can support users' access from the GSM EDGE radio access network (GERAN) and the Universal Terrestrial Radio Access Network (UTRAN).

In the EPC packet core network, the home subscriber data server (HSS, Home) is included.

Subscriber Server), Mobile '1' MME, Mobility Management Entity. Service Gateway (SGW, Serving Gateway), Packet Data Network Gateway (PGW, PDN Gateway), Serving GPRS Support Node (SGSN, Serving GPRS Support Node And the Policy and Charging Enforcement Function (PCRF), where:

The home user data server is a permanent storage location for the user's subscription data, and is located in the home network signed by the user;

Mobility Management Entity (MME, Mobility Management Entity) According to the current network storage location, responsible for terminal-to-network non-access (NAS, Non-Access Stratum) layer signaling management, user idle mode tracking and paging management functions and bearer management; service gateway, is the core network The gateway to the wireless system is responsible for the user plane bearer of the terminal to the core network, the data buffer in the terminal idle mode, the function of initiating the service request by the network side, the legal eavesdropping and the packet data routing and forwarding function;

The packet data network gateway is an evolved packet domain system and a gateway of the external network of the system, and is responsible for functions such as IP address allocation, charging function, packet filtering, and policy application of the terminal.

Service GPRS Support Node (SGSN) is a service support point for GERAN and UTRAN users to access the EPC network. It is similar in function to the MME and is responsible for user location update, paging management, and bearer management.

The Policy and Charging Enforcement Function (PCRF) is responsible for providing policy control and charging rules to the PCEF.

In some scenarios, the concept of a relay node has been introduced in order to expand wireless coverage or temporarily increase the ability of wireless to provide access to users. Figure 2 is a schematic diagram of the network architecture after the introduction of the relay. As shown in Figure 2, after the relay node is introduced, the UE can access the network through the relay node, where:

The relay node (RN, Relay Node) contains two parts of functions, UE and relay node. On one hand, the RN acts as a UE accessing the network, and establishes bearers and other related operations. On the other hand, the eNB provides access to the UE as an eNB.

The donor base station (DeNB, Donor eNodeB) provides wireless access to the RN, which is terminated.

The radio resource control (RRC, Radio Resource Control) signaling of the RN-UE terminates the SI Application Protocol (S1AP) signaling and the X2 signaling of the RN-eNB. At the same time, the SGW and PGW of the RN-UE are built in.

The relay node operator system (RN OAM, Relay Node Operator and Management) from which the RN obtains the necessary connection information. When the RN is a UE, the MME and the eNB that provide services for the RN-UE need to have corresponding enhanced functions. Therefore, it is necessary to ensure that the RN can select the enhanced eNB and the MME. Figure 3 is a flow chart of the RN accessing the appropriate DeNB and MME as the UE. As shown in Figure 3, the following steps are specifically included:

Step 301: The RN initiates an RRC establishment procedure as a UE.

Step 302: The RN sends an attach request to the MME on the established RRC connection. The non-access stratum message is sent to the MME via the base station.

Step 303: If there is no context information of the user in the network, or the attach request message does not have integrity protection, or the integrity protection fails, the MME performs an authentication and authentication process for the user.

Step 304: The MME selects an SGW/PGW for the RN-UE, and creates a default bearer for the UE. Step 305: The MME sends an initial context setup request to the eNB, where the identifier of the established bearer, the QoS (Quality of Service) and other related parameters, and the attach accept message sent to the UE.

Step 306: The RRC reconfiguration process establishes a corresponding radio bearer.

Step 307: The eNB returns an initial context setup response to the MME.

Step 308: The RN sends a direct transmission message to the eNB, where the attach complete message is included. After receiving the message, the eNB forwards the message to the MME.

If the above MME and eNB are not enhanced, the process performed is consistent with the prior art. Step 309: After the RN completes the attach process, the RN obtains configuration parameters from the RN OAM. This includes information about the MME and DeNB that the RN can access. If the MME and the eNB that the RN is currently connected with are delivered by the MME, the RN may not initiate the re-attach process, that is, the subsequent process will not be performed. Otherwise, the RN needs to perform a re-attach process to access the correct MME and DeNB.

Step 310: The RN reselects a suitable DeNB according to acquiring DeNB or DeNB list information from the RN OAM. Step 311: The RN initiates an RRC establishment procedure as the UE.

Step 312: The RN sends an attach request to the MME on the established RRC connection. The non-access stratum message is sent to the MME via the base station. It includes identification information of the MME, such as a globally unique MME identifier (GUMMEI, Global Unique MME Identifier).

Step 313: The DeNB selects an MME that upgrades the support RN according to the MME identifier included in the message in step 312.

Step 314: The DeNB routes the non-access stratum message to the selected MME.

Step 315: If there is no context information of the user in the network, or the attach request message does not have integrity protection, or the integrity protection fails, the MME performs an authentication process for the user.

Step 316: The MME identifies that the access is not an ordinary UE but the RN accesses the UE, and the MME selects the SGW/PGW built in the DeNB for the RN. The selection method may be a Domain Name System (DNS) query, or according to a built-in SGW/PGW address provided by the DeNB, or according to configuration information.

Step 317: The MME creates a default bearer for the UE.

Steps 318 to 321 are similar to the previous steps 305 to 308, and are not described herein again. If the RN deletes the previous RN OAM information, you need to re-obtain the configuration information from the RN OAM.

In the prior art, the RN OAM sends the configuration parameters required by the RN to the RN in one time. Since the RN needs to provide wireless access to the UE as the eNodeB, the configuration parameters are not only a large number, but also involve the privacy of the operator. However, because the RN OAM sends the parameters that the RN can access the DeNB list, if the RN cannot access the specified DeNB, the other configuration parameters sent by the OAM to the RN are actually useless. Summary of the invention

In view of this, the main object of the present invention is to provide a method and system for a relay node to acquire configuration information, which can provide a complete configuration after confirming that a network node accessed by a relay point is suitable. Information, otherwise only configuration information for the relay node to properly access the network node is provided.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for a relay node to obtain configuration information includes:

When receiving the configuration information request sent by the relay node, the network side determines whether the network node accessed by the relay node is suitable, and sends corresponding configuration information to the relay node according to the determination result.

Preferably, the network node comprises a DeNB and/or an MME.

Preferably, the obtaining configuration information request carries the DeNB identification information currently accessed by the relay node and/or the acquired MME identification information.

Preferably, the determining whether the network node accessed by the relay node is suitable is: the network side determining, according to the DeNB identification information that is accessed by the relay node, and/or the acquired MME identification information, determining that the network node is connected Whether the incoming DeNB and/or MME is a legitimate network node that allows the relay node to access, and the network node that is accessed is suitable, otherwise it is not suitable.

Preferably, the DeNB identification information is at least one of the following: a globally unique identifier of the DeNB, a cell identifier of a cell in which the relay node currently accesses the DeNB, and a location area identifier currently accessed;

The MME identification information is at least one of the following: a globally unique identifier (GUMMEI) of the MME and a Global Unique Temporary UE Identifier (GUTI) allocated by the MME to the relay node.

Preferably, the network node is an access gateway.

Preferably, the determining whether the network node accessed by the relay node is suitable is: the network side acquiring the identifier information of the access gateway accessed by the relay node, and further determining whether the access gateway is It is a legal access gateway that allows the relay node to access, and the network node that is accessed at the time is suitable, otherwise it is not suitable.

Preferably, the identifier information of the access gateway accessed by the relay node is: an address letter of the PGW. Information, or the address information of the RN.

Preferably, the sending, by the determining result, the corresponding configuration information to the relay node according to the determination result is:

When the network node accessed by the relay node is appropriate, all configuration information is sent to the relay node, otherwise, configuration information that can be correctly accessed is sent to the relay node.

A system for obtaining configuration information by a relay node is applicable to a relay network; the system includes a receiving unit, a determining unit, and a sending unit;

a receiving unit, configured to receive a request for acquiring configuration information sent by the relay node;

a determining unit, configured to determine, according to the request for acquiring the configuration information, whether the network node accessed by the relay node is suitable;

And a sending unit, configured to send corresponding configuration information to the relay node according to the determination result of the determining unit.

Preferably, the network node comprises a DeNB and/or an MME;

The obtaining configuration information request carries the DeNB identification information currently accessed by the relay node and/or the acquired MME identification information.

Preferably, the determining unit further determines, according to the DeNB identification information that the relay node accesses and/or the acquired MME identification information, whether the accessed DeNB and/or the MME are allowed to access the relay node. The legal network node is suitable when the network node is connected, otherwise it is not suitable.

The MME identification information is at least one of the following: a globally unique identifier of the MME and a globally unique temporary UE identifier allocated by the MME for the relay node.

Preferably, the network node is an access gateway; the determining unit further acquires Determining the identification information of the access gateway accessed by the relay node, and further determining whether the access gateway is a legal access gateway that allows the relay node to access, and the network node accessed at the time is appropriate. Otherwise it is not suitable.

Preferably, the identifier information of the access gateway accessed by the relay node is: address information of the PGW, or address information of the RN.

Preferably, the sending unit sends all configuration information to the relay node when the determining unit determines that the network node accessed by the relay node is suitable, otherwise, sends the correct access to the relay node. Configuration information.

In the present invention, when the network side receives the request for the configuration information acquired by the relay node to access the network, it first determines whether the currently accessed network node is appropriate, and only sends the energy to the relay node when it is inappropriate. Make it correctly access the configuration information of the network node. The present invention ensures that the RN OAM sends the relevant configuration parameters to the RN when it is confirmed that the RN may successfully access the selected network, thereby avoiding the RN downloading useless parameters and wasting network resources and leakage of the operator's privacy information, and RNs that need to reattach to the network provide faster access efficiency. DRAWINGS

1 is a system structure diagram of an evolved packet network;

2 is a schematic diagram of a network architecture after the introduction of the Relay;

FIG. 3 is a flowchart of an RN accessing a suitable DeNB and an MME as a UE;

4 is a flowchart of Embodiment 1 of a method for acquiring configuration information of a relay node according to the present invention; FIG. 5 is a flowchart of Embodiment 2 of a method for acquiring configuration information of a relay node according to the present invention; Schematic diagram of the composition of the system of information. detailed description

The basic idea of the present invention is that when the network side receives the request for the configuration information acquired by the relay node to access the network, it first determines whether the currently accessed network node is suitable. When it is not suitable, only the configuration information of the relay node that enables it to correctly access the network node is sent.

The present invention will be further described in detail below with reference to the accompanying drawings.

4 is a flowchart of Embodiment 1 of a method for obtaining configuration information of a relay node according to the present invention. As shown in FIG. 4, the method for obtaining configuration information by the relay node in this example includes the following steps: Step 401 to Step 408 in this example. Steps 410 to 421 are performed in the same manner as in the prior art. The present invention is not described in detail in the steps. For details, refer to the corresponding steps in the process shown in FIG.

Step 401 to step 408, refer to the corresponding step 301 to step 308 in the foregoing FIG. 3, and the implementation details thereof will not be described herein.

Step 409a: When the RN sends a request message for acquiring configuration information to the RN OAM, the request message carries the information and/or MME information of the currently accessed eNB. The information of the eNB may be a globally unique identifier of the eNB, and/or a cell identifier of the cell currently accessing the eNB (including the identifier information of the eNB), and/or a location area identifier currently accessed (the identifier and the eNB have a certain identifier Correspondence). The MME information may be a globally unique identifier of the MME, and/or a GUTI allocated by the MME for the RN-UE (including the identifier information of the MME).

In this step, when the RN sends a request message for obtaining the configuration information to the RN OAM, the request message carries the relevant identifier information of the network node that the RN is currently accessing. Specifically, the DeNB that the RN is currently accessing needs to be And the MME identification information and the like that have been obtained are inserted into the foregoing request message, so that the RN OAM determines the network node information currently accessed by the RN according to the identification information, so as to further determine whether the network node accessed by the RN is suitable. Network node. The above identification information may be uniquely identified as the DeNB or the MME. For example, the location area identifier information may be specific geographical location information, such as the current geographic information of the RN determined by the global positioning system, and if the network side, such as the RN OAM, records the correspondence between the geographic information and the eNB distribution, The information of the eNB that the RN can access is determined. Step 409b: The RN OAM determines whether the RN is accessed from the appropriate DeNB and the MME according to the information of the network node carried by the RN in the foregoing step 409a. In this example, it is assumed that the DeNB or MME accessed by the RN is incorrect.

Step 409c: The RN OAM returns only configuration parameters that ensure that the RN can correctly access the RN, such as a DeNB list, and/or an MME identity. That is, returning only to the RN enables access to the network node recognized by the network side, and is limited to correctly accessing information of any of these network nodes.

Step 410 to step 421, refer to the corresponding step 310 to step 321 in the foregoing FIG. 3, and the implementation details thereof will not be described herein.

Step 422a: When the RN sends a request message for acquiring configuration information to the RN OAM, the request message needs to carry information and/or MME information of the currently accessed eNB. The information of the eNB may be a globally unique identifier of the eNB, and/or a cell identifier of the current access cell (including the identifier information of the eNB), and/or a location area identifier currently accessed (the identifier has a certain correspondence with the eNB) relationship). The MME information may be a globally unique identifier of the MME, and/or a GUTI allocated by the MME for the RN-UE (including the identification information of the MME).

In this example, when the RN sends a request message for obtaining the configuration information to the RN OAM, the request message carries the related information of the network node currently accessed by the RN, and the related information mainly refers to the identification information, so as to facilitate The network side identifies these network nodes and further determines whether the network node accessed by the RN is a suitable network node, thereby determining what configuration information is sent to the RN. The implementation of this step is substantially the same as the aforementioned step 409a.

Step 422b: The RN OAM determines whether the RN accesses from the appropriate DeNB and the MME according to the information about the network node carried in the request message for obtaining the configuration information sent by the RN in the foregoing step 422a. Since the relevant configuration information for the RN to accurately access the network node has been sent to the RN in the foregoing step 409c, the network node currently accessed by the RN should be suitable. This step assumes that the network node accessed by the RN is correct.

Step 422c: The RN OAM returns all configuration information required by the RN to the RN. Full of here Part configuration information, that is, the same configuration information as in the prior art shown in FIG. 3 described above.

5 is a flowchart of Embodiment 2 of a method for obtaining configuration information of a relay node according to the present invention. As shown in FIG. 5, the method for obtaining configuration information by the relay node in this example includes the following steps: Step 501 to Step 508 in this example. And the steps 510 to 521 are performed in the same manner as in the prior art. The present invention is not described in detail in the steps. For details, refer to the corresponding steps in the process shown in FIG.

Step 501 to step 508, refer to the corresponding steps 301 to 308 in the foregoing FIG. 3, and the implementation details thereof will not be described herein.

Step 509A: The RN sends a request message for acquiring configuration information to the RN OAM.

Step 509B: The RN OAM determines, according to the address information carried in step 509 A, whether the RN is from a suitable DeNB and a network accessed by the MME. For example, the message carries the RN address information and/or the address information of the PGW, and can identify whether the RN accesses the correct PGW. The PGW is a PGW built in the DeNB. It is assumed in this step that the correct DeNB and the MME are not connected.

Step 509C: The RN OAM returns only configuration parameters that ensure that the RN can correctly access the RN, such as a DeNB list, and/or an MME identifier.

Step 522A: The RN sends a request message for acquiring configuration information to the RN OAM.

Step 522B: The RN OAM determines, according to the address information carried in step 509 A, whether the RN accesses from the appropriate DeNB and the MME. For example, the message carries the RN address information and/or the address information of the PGW, and can identify whether the RN accesses the correct PGW, and the PGW is a PGW built in the DeNB. This step assumes that the DeNB and the MME accessed by the RN are correct.

Step 522C: The RN OAM returns all configuration information required by the RN to the RN.

The present invention ensures that the RN OAM sends the relevant configuration parameters to the RN when it is confirmed that the RN may successfully access the selected network. On the one hand, it avoids the waste of network resources by downloading useless parameters. As well as leakage of operator privacy information, on the other hand, it provides faster access efficiency for RNs that need to reattach to the network.

The system for obtaining the configuration information of the relay node of the present invention is applicable to the relay network. FIG. 6 is a schematic structural diagram of a system for acquiring configuration information by the relay node according to the present invention. As shown in FIG. 6, the relay node of the present invention obtains configuration information. The system includes a receiving unit 60, a determining unit 61, and a transmitting unit 62;

The receiving unit 60 is configured to receive an acquisition configuration information request sent by the relay node, and the determining unit 61 is configured to determine, according to the request for acquiring the configuration information, whether the network node accessed by the relay node is suitable;

The sending unit 62 is configured to send corresponding configuration information to the relay node according to the determination result of the determining unit.

The above network node includes a DeNB and/or an MME;

The determining unit 61 further determines, according to the DeNB identification information that the relay node accesses and/or the acquired MME identification information, whether the accessed DeNB and/or the MME is a legal network that allows the relay node to access. Node, is the network node that is connected when it is appropriate, otherwise it is not suitable.

The DeNB identification information is at least one of the following information: a globally unique identifier of the DeNB, a cell identifier of a cell in which the relay node currently accesses the DeNB, and a location area identifier currently accessed;

The foregoing network node is an access gateway, such as a PGW; the determining unit 61 further obtains identification information of the access gateway accessed by the relay node, and further determines that the access gateway is Whether it is a legal access gateway that allows the relay node to access, the network node that is accessed at the time is suitable, otherwise it is not suitable.

When the determining unit 61 determines that the network node accessed by the relay node is suitable, the transmitting unit 62 transmits all configuration information to the relay node, and otherwise sends configuration information that can be correctly accessed to the relay node.

It should be understood by those skilled in the art that the system for obtaining the configuration information of the relay node shown in FIG. 6 is designed to implement the foregoing method for acquiring configuration information by the relay node, and the implementation functions of the foregoing processing units may refer to the foregoing method. Understand the relevant description. The functions of the various processing units in the figure can be implemented by a program running on a processor, or by a specific logic circuit.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for obtaining configuration information by a relay node, the method comprising: determining, by a network side, whether a network node accessed by the relay node is suitable when receiving a request for acquiring configuration information sent by a relay node And sending corresponding configuration information to the relay node according to the judgment result.

2. The method according to claim 1, characterized in that the network node comprises a donor base station DeNB and/or a mobility management entity MME.

The method according to claim 2, wherein the obtaining configuration information request carries the DeNB identification information currently accessed by the relay node and/or the acquired MME identification information.

The method according to claim 3, wherein the determining whether the network node accessed by the relay node is suitable is:

Determining, by the network side, whether the accessed DeNB and/or MME is a legal network node that allows the relay node to access according to the DeNB identification information that is accessed by the relay node and/or the acquired MME identification information. When the judgment is yes, the connected network node is suitable, otherwise it is not suitable.

The method according to claim 3, wherein the DeNB identification information is at least one of the following: a globally unique identifier of the DeNB, and the DeNB cell currently accessed by the relay node. a cell identifier and a location area identifier currently accessed;

The MME identification information is at least one of the following information: a globally unique identifier of the MME and a globally unique temporary UE identifier GUTI allocated by the MME to the relay node.

6. The method according to claim 1, wherein the network node is an access gateway.

The method according to claim 6, wherein the determining whether the network node accessed by the relay node is suitable is: Obtaining, by the network side, identifier information of the access gateway accessed by the relay node, and further determining whether the access gateway is a legal access gateway that allows the relay node to access, when the determination is yes, The network node to be accessed is suitable, otherwise it is not suitable.

The method according to claim 7, wherein the identification information of the access gateway accessed by the relay node is: address information of the PGW, or address information of the RN.

The method according to any one of claims 1 to 8, wherein the transmitting the corresponding configuration information to the relay node according to the judgment result is:

A system for obtaining configuration information by a relay node, which is applicable to a relay network, and is characterized in that: the system includes a receiving unit, a determining unit, and a sending unit;

The system according to claim 10, wherein the network node comprises a DeNB and/or an MME;

The system according to claim 11, wherein the determining unit further determines the accessed DeNB and/or according to the DeNB identification information accessed by the relay node and/or the acquired MME identification information. Whether the MME is a legitimate network node that allows the relay node to access, and the network node that is accessed is suitable, otherwise it is not suitable.

13. The system according to claim 11, wherein the DeNB identification information At least one of the following information: a globally unique identifier of the DeNB, a cell identifier of the DeNB cell currently accessed by the relay node, and a currently located location area identifier;

The MME identification information is at least one of the following information: a globally unique identifier of the MME and a GUTL allocated by the MME for the relay node

The system according to claim 10, wherein the network node is an access gateway; the determining unit further acquiring identification information of the access gateway accessed by the relay node, and further determining Whether the access gateway is a legal access gateway that allows the relay node to access, and the network node that is accessed at the time is suitable, otherwise it is not suitable.

The system according to claim 14, wherein the identification information of the access gateway accessed by the relay node is: address information of the PGW, or address information of the RN.

The system according to any one of claims 10 to 15, wherein the transmitting unit sends the relay node to the relay node when the determining unit determines that the network node accessed by the relay node is suitable. All configuration information, otherwise, send configuration information that can be correctly accessed to the relay node.