WO2012100622A1 - Method, system, evolved node b, mme and rn for user release in case of network element overload - Google Patents

Abstract

Disclosed are a method, system, base station, mobility management entity (MME) and relay node (RN) for user release in case of network elements (NE) overload, comprising: while a user equipment (UE) is accessing, a donor eNB (DeNB) notifies the RN of the user equipment mobility management entity (UE-MME); when a relay node mobility management entity (RN-MME) is overloaded, the RN determines whether the RN-MME and the UE-MME are the same MME; if not, then the RN initiates UE release or handover; if yes, then wait for the RN-MME to initiate UE release. Through the present invention, after the MME is overload, the RN is capable of operating reasonably and correctly, thus reducing the MME load to a reasonable level.

Description

 User release method, system, base station, MME and RN technical field for network element overload

 The present invention relates to a user release technology, and more particularly to a user release method, system, base station, MME, and RN for overloading a network element. 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) standard working group is working on the evolution of the Packet Domain System (EPS, Evolved Packet System). Figure 1 shows the system structure of EPS. As shown in Figure 1, the EPS system mainly includes Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet Core Network (EPC, Evolved Packet). Core) two parts. The system's EPC is capable of supporting users' access from the GSM EDGE radio access network (GERAN, GSM EDGE radio access network) 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, SGW, Serving Gateway, Packet Data Network Gateway (PGW, PDN Gateway), Serving GPRS Support Node (SGSN, Serving GPRS) Support Node) and Policy and Charging Enforcement Function (PCRF), where:

The HSS is a permanent storage location for user subscription data, located in the home network to which the user subscribes. The MME is the location where the user subscription data is stored in the current network, and is responsible for terminal-to-network non-access (NAS, Non-Access Stratum) layer signaling management. Tracking and searching in user idle mode Call management function and bearer management;

 The SGW is a gateway from the core network to the wireless system, and is responsible for user plane bearer of the terminal to the core network, data buffering in the idle mode of the terminal, function of initiating a service request by the network side, legal eavesdropping, and packet data routing and forwarding functions;

 The PGW 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.

 The SGSN is a service support point for GERAN and UTRAN users to access the EPC network. It functions similarly to the MME and is responsible for user location update, paging management, and bearer management.

 The 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, establishes bearers and other related operations, and on the other hand, provides an access to the UE as an eNodeB.

 The donor base station (DeNB, Donor eNodeB) provides radio access for the RN, terminates RRC (Radio Resource Control) signaling of the RN-UE (RN as UE), and terminates the RN-eNodeB (RN as The SI Application Protocol (S1AP) signaling and the X2 signaling of the eNodeB), together with the SGW and PGW of the RN-UE.

When the RN accesses the core network as the UE, the MME and the eNodeB that provide services for the RN-UE need to have corresponding enhanced functions. Therefore, it is necessary to ensure that the RN-UE can select the enhanced eNodeB and the MME. In an actual network application, the number of users accessing the MME is limited, so the MME load overload occurs. When the UE wants to access the MME that is in compliance with the overload, the MME needs to notify the corresponding eNodeB (ie, the eNodeB serving the UE). So that the eNodeB selects the UE for the UE. Appropriate MME access, as shown in Figure 3. After the RN and the DeNB are introduced in the network, the MME of the UE is selected by the DeNB, and the RN does not know which MME the UE served by the DeNB accesses the core network through, so that it cannot be reasonably correct after the MME is overloaded. Operation reduces the MME load to a reasonable level. Summary of the invention

 In view of this, the main purpose of the present invention is to provide a user release method, system, base station, MME, and RN for network element overload. After the MME is overloaded, the RN can perform reasonable and correct operations to reduce the MME load to a reasonable level. Level.

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

 The invention provides a user release method for network element overload, the method comprising:

 In a user equipment (UE) access procedure, a donor base station (DeNB) notifies a relay node (RN) of a mobility management unit (UE-MME) accessed by the UE;

 When the MME (RN-MME) accessing the RN is overloaded, the RN determines whether the RN-MME and the UE-MME are the same MME; if not, the RN initiates release or handover of the UE; if yes, waits The RN-MME initiates release of the UE.

 Further, the RN determines whether the RN-MME and the UE-MME are the same MME, specifically: the RN compares whether the global unique MME identity (GUMMEI) of the RN-MME and the GUMMEI of the UE-MME are the same. If the same, the RN-MME and the UE-MME are determined to be the same MME; if not, the RN-MME and the UE-MME are determined to be different MMEs.

 Further, when the access process is an attach process, the DeNB notifies the UE to the RN, specifically:

 The DeNB sends the GUMMEI of the UE-MME to the RN by using an initial context setup request message.

Further, when the access process is a tracking area update (TAU) process, the DeNB will The UE-MME notifies the RN, specifically:

 The DeNB sends the GUMMEI of the UE-MME to the descriptor by using a TAU accept message.

 Further, when the attaching process or the TAU process is completed, the method further includes:

When the RN-MME is overloaded, the RN-MME sends an overload notification message carrying its own GUMMEI to the RNo through the DeNB.

 Further, the RN initiates release of the UE, including:

 The RN sends an S1 release request message to the UE-MME through the DeNB;

 The UE-MME returns an S1 release instruction message to the RN through the DeNB;

 The RN sends an RRC release request message to the UE, and carries the release cause value as "required for network balance" in the message;

 The UE sends an RRC release complete message to the RN;

 The RN sends an S1 release complete message to the UE-MME through the DeNB.

 Further, the RN initiates handover of the UE, including:

 The RN requires the UE to report the measurement signal, and the UE reports the measured measurement signal to the RN;

The RN sends a handover request message to the DeNB;

 The DeNB sends a handover response message to the RN;

 The DeNB sends a path switch request message to the UE-MME;

 The UE-MME sends a Path Switch Response message to the DeNB.

 The present invention also provides a network element overloaded user release system, the system comprising: a donor base station (DeNB), a relay node (RN) and an RN-MME, wherein:

 The DeNB is configured to notify, by the user equipment (UE), a mobility management unit (UE-MME) that the UE accesses during the access process to the RN;

And determining, by the RN, whether the RN-MME and the UE-MME are the same MME when the MME (RN-MME) that is in the access is overloaded; and when the determination result is no, Initiating release or handover of the UE;

 The RN-MME is configured to initiate release of the UE when the determination result is yes.

 Further, the RN is further configured to compare the GUMMEI of the RN-MME with the

Whether the GUMMEI of the UE-MME is the same, if the same, determining the RN-MME and the

The UE-MME is the same MME; if not, it is determined that the RN-MME and the UE-MME are different MMEs.

 Further, the DeNB is further configured to: when the access procedure is an attach procedure, send the GUMMEI of the UE-MME to the RN by using an initial context setup request message; During the Tracking Area Update (TAU) procedure, the GUMMEI of the UE-MME is sent to the RN through a TAU Accept message.

 The present invention also provides a relay node (RN), comprising: an information receiving module, an analyzing module and a triggering module; wherein:

 The information receiving module is configured to acquire information about a mobility management unit (UE-MME) accessed by the UE sent by the DeNB during a UE access process;

 The analyzing module is configured to determine, when the MME (RN-MME) that is accessed by the RN is overloaded, determine whether the RN-MME and the UE-MME are the same MME, and when the determination result is no, notify the Trigger module; when the judgment result is no, the RN-MME is notified.

 The triggering module is configured to initiate release or handover of the UE when the determination result is negative. The analyzing module is further configured to compare whether the globally unique MME identity (GUMMEI) of the RN-MME and the GUMMEI of the UE-MME are the same. If they are the same, determine that the RN-MME is the same as the UE-MME. An MME; if not, determining that the RN-MME and the UE-MME are different MMEs.

The information receiving module is further configured to: when the access procedure is an attach procedure, receive an initial context setup request message that is sent by the DeNB and that carries the GUMMEI of the UE-MME; or is further used in the access process. Receiving the DeNB when tracking the zone update (TAU) process The TAU accept message of the GUMMEI carrying the UE-MME is sent.

 The information receiving module is further configured to: when the attaching process, or the TAU process is completed, and the analyzing module determines that the RN-MME is overloaded, receive an overload notification sent by the RN-MME forwarded by the DeNB The overload notification message carries the GUMMEI of the RN-MME.

 The triggering module is further configured to: send, by the DeNB, an S1 release request message to the UE-MME; and receive an S1 release instruction message that is returned by the UE-MME through the DeNB; and then send an RRC release request message to the UE, where The message carries the release cause value as "required for network balance", and after receiving the RRC release completion message returned by the UE, the DeNB sends an SI release complete message to the UE-MME.

 The triggering module is further configured to: request the UE to report a measurement signal; after acquiring the measurement signal, send a handover request message to the DeNB, and receive a handover response message returned by the DeNB.

 The present invention also provides a mobility management unit (UE-MME) for mobile terminal access, comprising: an access module and a release module; wherein:

 The access module is configured to accept access by the UE;

 And the releasing module is configured to initiate release of the UE when an MME (RN-MME) that is accessed by the RN is overloaded, and the RN-MME and the UE-MME are not the same MME.

 Also includes:

 An information processing module, configured to provide the UE-MME's GUMMEI to the RN by using a DeNB.

The information processing module is further configured to: when the release of the UE initiated by the RN is completed, receive an S1 release completion message returned by the RN through the DeNB; and further, be used to receive the path switch request sent by the DeNB in the handover process of the UE initiated by the RN. After the message, a path switch response message is returned to the DeNB. The present invention further provides a donor base station (DeNB), comprising: an information management module, configured to acquire information of a mobility management unit (UE-MME) accessed by the UE during a UE access process, And notify the RN.

 The information management module is further configured to: when the access procedure is an attach procedure, acquire a GUMMEI from the UE-MME, and send the message to the RN by using an initial context setup request message; When the process is a TAU procedure, the GUMMEI is acquired to the UE-MME, and a TAU accept message is sent to the RN.

 The information management module is further configured to: when the MME (RN-MME) that is accessed by the RN is overloaded, receive an overload notification message sent by the RN-MME, where the attaching process, or the TAU process is completed, And forwarding to the RN; the overload notification message carries the GUMMEI of the RN-MME.

 The information management module is further configured to forward an S1 release request message from the RN to the UE-MME during the release of the RN by the RN; and forward the S1 release instruction message returned by the UE-MME to the RN And forwarding an S1 release complete message sent by the RN to the UE-MME;

 The method further includes: after receiving the handover request message sent by the RN, after receiving the handover request message sent by the RN, returning the handover response message to the RN, and sending the path switch request message to the UE-MME, and receiving the path switch response returned by the UE-MME Message.

 The basic idea of the user release method of the network element overloaded in the present invention is that, in the user access process, the DeNB sends the MME selected by the user to the RN. When the RN detects that the MME accessed by the RN is overloaded, the RN determines whether to release the user. Or switch the user to another eNodeB to make the MME reach the normal load. DRAWINGS

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

2 is a schematic diagram of a network architecture after a Relay is introduced; FIG. 3 is a flowchart of notifying the eNodeB after the MME is overloaded;

 4 is a flowchart of a user release method for a network element overload in the present invention;

 FIG. 5 is a schematic diagram of a user release method for a network element overload according to Embodiment 1 of the present invention; FIG.

 6 is a schematic diagram of a user release method for a network element overload according to Embodiment 2 of the present invention;

 7 is a schematic diagram of a user release method for a network element overload according to Embodiment 3 of the present invention;

 FIG. 8 is a schematic diagram of a user release method for a network element overload according to Embodiment 4 of the present invention; FIG.

 9 is a schematic diagram of a user release method for a network element overload according to Embodiment 5 of the present invention;

 FIG. 10 is a schematic diagram of a user release method for a network element overload according to Embodiment 6 of the present invention. detailed description

 The basic idea of the user release method of the network element overloaded in the present invention is that, in the user access process, the DeNB sends the MME selected by the user to the RN. When the RN detects that the MME accessed by the RN is overloaded, the RN determines whether to release the user. Or switch the user to another eNodeB to make the MME reach the normal load. Specifically, as shown in FIG. 4, a flowchart of a user release method for a network element overload in the present invention includes:

 Step 401: In the UE access process, the DeNB notifies the MME that the UE accesses to the RN.

The MME that the UE accesses is the MME that the DeNB selects for the UE, and is denoted as the UE-MME. In addition, the MME accessed by the RN is recorded as the RN-MME.

 Here, the access procedure is an attach procedure, or a tracking area update process.

 Step 402: When the RN-MME is overloaded, the RN determines whether the RN-MME and the UE-MME are the same MME; if it is a different MME, step 403 is performed; if it is the same MME, step 404 is performed.

 Step 403: When the MME is a different MME, the RN initiates release or handover of the UE.

 Step 404: When the MME is the same MME, wait for the RN-MME to initiate release of the UE.

 The technical solution of the present invention will be described below by way of specific embodiments.

FIG. 5 is a schematic diagram of a user release method for a network element overload according to Embodiment 1 of the present invention, where In this embodiment, the access process is an attach procedure, and the UE-MME and the RN-MME are the same MME, and the RN-MME initiates the release of the UE. As shown in FIG. 5, the method includes:

 Step 501: The UE sends an attach request message to the RN, and carries parameters such as the IMSI of the UE and the network capability of the UE.

 Step 502: The RN forwards the attach request message to the DeNB.

 Step 503: The DeNB selects, according to the network topology, the serving MME, that is, the UE-MME, and forwards the attach request message to the UE-MME.

 Step 504: The UE-MME sends an initial context setup request message to the DeNB, and carries the bearer ID and the UE-Aggregate Maximum Bit Rate (UE-AMBR), and carries the attach accept message in the initial context setup request message. The attachment accept message carries information such as a globally unique temporary identifier (GUTI), a tracking area list (TAI list, a tracking area identity list), and a bearer ID.

 Step 505: The DeNB forwards an initial context setup request to the RN, where the UE-MME carries a globally unique MME identifier (GUMMEI, Globally Unique MME Identifier);

 Step 506: The RN sends a radio resource connection (RRC, Radio Resource Connection) reconfiguration message to the UE, where the message carries the radio bearer ID.

 Step 507: The UE sends an RRC reconfiguration complete message to the RN.

 Step 508: The RN sends an initial context setup response message to the DeNB.

 Step 509, the DeNB forwards the initial context setup response message to the UE-MME.

 Step 510: The UE sends a direct transmission message to the RN, and the direct transmission message carries an attach complete message. Step 511: The RN sends an attach complete message to the DeNB.

 Step 512: The DeNB sends an attach complete message to the UE-MME; thus, the attach process is completed.

Step 513, when the RN-MME is overloaded, the RN-MME notifies the DeNB through the overload notification message, and the overload notification message carries the GUMMEI of the overloaded RN-MME; Step 514, the DeNB forwards the overload notification message to the RN, and carries the GUMMEI of the overloaded RN-MME in the message;

 Step 515: The RN sends an overload notification response message to the DeNB.

 Step 516: The DeNB sends an overload notification response message to the RN-MME.

 Step 517, the RN obtains the GUMMEI of the UE-MME in step 505, obtains the GUMMEI of the overloaded RN-MME in step 514, compares two GUMMEIs, and if they are the same, it can determine that the RN-MME is the same as the UE-MME. An MME, therefore, when the RN-MME is overloaded, the RN does nothing and waits for the RN-MME to initiate the release of the UE.

 FIG. 6 is a schematic diagram of a user release method for a network element overloaded according to Embodiment 2 of the present invention. In this embodiment, the access process is a TAU process, and the UE-MME and the RN-MME are the same MME, and the RN-MME initiates the UE. Release, as shown in Figure 6, the method includes:

 Step 601: The UE sends a Tracking Area Update (TAU) request message to the RN, and carries parameters such as the network capability of the GUTI and the UE. When the TAU request message is sent, the GUMMEI of the old UE-MME is sent to the RN. ;

 Step 602: The RN forwards the TAU request message to the DeNB.

 Step 603: If the DeNB can connect to the old UE-MME, the DeNB selects the old UE-MME for the UE to access; if the DeNB cannot connect to the old UE-MME, the DeNB selects the new UE-MME for the UE according to the network topology. Accessing, and forwarding the TAU request message to the new UE-MME;

 Step 604: The UE-MME sends a TAU accept message to the DeNB, and carries information such as a GUTI and a TAI list.

 Step 605, the DeNB forwards a TAU accept message to the RN, where the GUMMEI carrying the UE-MME is carried;

 Step 606: The RN sends a TAU accept message to the UE.

Step 607: The UE sends a direct transmission message to the RN, where the direct transmission message carries a TAU completion message. Step 608, the RN sends a TAU complete message to the DeNB;

 Step 609: The DeNB sends a TAU complete message to the UE-MME. Then, the tracking area update process is completed.

 Step 610: When the RN-MME is overloaded, the DeNB is notified by the overload notification message, and the overload notification message carries the GUMMEI of the overloaded RN-MME;

 Step 611, the DeNB forwards the overload notification message to the RN, and carries the GUMMEI of the overload RN-MME in the message;

 Step 612: The RN sends an overload notification response message to the DeNB.

 Step 613: The DeNB sends an overload notification response message to the RN-MME.

 In step 614, the RN obtains the GUMMEI of the UE-MME in step 605, obtains the GUMMEI of the overloaded RN-MME in step 611, compares two GUMMEIs, and if they are the same, it can determine that the RN-MME is the same as the UE-MME. An MME, therefore, when the RN-MME is overloaded, the RN does nothing and waits for the RN-MME to initiate the release of the UE.

 FIG. 7 is a schematic diagram of a user release method for a network element overloaded according to Embodiment 3 of the present invention. In this embodiment, the access process is an attach procedure, and the UE-MME and the RN-MME are different MMEs, and the RN initiates release of the UE. As shown in FIG. 7, the method includes:

 The attaching process of step 701 to step 712 is the same as the attaching process of step 501 to step 512, and details are not described herein again.

 Step 713, when the RN-MME is overloaded, the DeNB is notified by the overload notification message, and the overload notification message carries the GUMMEI of the overloaded RN-MME;

 Step 714: The DeNB forwards the overload notification message to the RN, and carries the overload in the message.

GUMMEI of RN-MME;

 Step 715: The RN sends an overload notification response message to the DeNB.

 Step 716: The DeNB sends an overload notification response message to the RN-MME.

Step 717, the RN acquires the GUMMEI of the UE-MME in step 705, and in step 714 The GUMMEI of the overloaded RN-MME is obtained, and the two GUMMEIs are compared. If not, the RN-MME and the UE-MME are different MMEs. In this case, the RN needs to initiate the release of the UE, and the RN sends the S1 to the DeNB. Release request message;

 Step 718: The DeNB sends an S1 release request message to the UE-MME.

 Step 719: The UE-MME sends an S1 release instruction message to the DeNB.

 Step 720: The DeNB forwards the S1 release instruction message to the RN.

 Step 721: The RN sends an RRC release request message to the UE, and carries the release cause value as “required for network balance” in the message;

 Step 722: The UE sends an RRC release complete message to the RN.

 Step 723: The RN sends an S1 release complete message to the DeNB.

 Step 724: The DeNB sends an S1 release complete message to the UE-MME.

 Step 725: The UE re-initiates the TAU procedure, and does not carry the GUMMEI of the old UE-MME in the RRC message, so that the eNodeB can re-select the MME for the UE.

 FIG. 8 is a schematic diagram of a user release method for a network element overloaded according to Embodiment 4 of the present invention. In this embodiment, the access process is a TAU process, and the UE-MME and the RN-MME are different MMEs, and the RN initiates the UE. Release, as shown in Figure 8, the method includes:

 The TAU process in steps 801 to 809 is the same as the TAU process in steps 601 to 609, and is not described here.

 Step 810, when the RN-MME is overloaded, the RN-MME notifies the DeNB by using an overload notification message, and the overload notification message carries the GUMMEI of the overloaded RN-MME;

 Step 811, the DeNB forwards the overload notification message to the RN, and carries the GUMMEI of the overload RN-MME in the message;

 Step 812: The RN sends an overload notification response message to the DeNB.

 Step 813: The DeNB sends an overload notification response message to the RN-MME.

Step 814, the RN acquires the GUMMEI of the UE-MME in step 805, in step 811. The GUMMEI of the overloaded RN-MME is obtained, and the two MMEs are compared. If different, the RN-MME and the UE-MME are different MMEs. In this case, the RN needs to initiate the release of the UE, and the RN sends the S1 release to the DeNB. Request message

 Step 815: The DeNB sends an S1 release request message to the UE-MME.

 Step 816: The UE-MME sends an S1 release instruction message to the DeNB.

 Step 817: The DeNB forwards the S1 release instruction message to the RN.

 Step 818, the RN sends an RRC release request message to the UE, and carries the release cause value as "required for network balance" in the message;

 Step 819: The UE sends an RRC release complete message to the RN.

 Step 820: The RN sends an S1 release complete message to the DeNB.

 Step 821: The DeNB sends an S1 release complete message to the UE-MME.

 Step 822: The UE re-initiates the TAU procedure, and does not carry the GUMMEI of the old UE-MME in the RRC message, so that the eNodeB can re-select the MME for the UE.

 FIG. 9 is a schematic diagram of a method for releasing a user of a network element overloaded according to Embodiment 5 of the present invention. In this embodiment, the access procedure is an attach procedure, and the UE-MME and the RN-MME are different MMEs, and the RN initiates handover of the UE. As shown in FIG. 9, the method includes:

 The attaching process of step 901 to step 912 is the same as the attaching process of step 501 to step 512, and details are not described herein again.

 Step 913, when the RN-MME is overloaded, when the RN-MME notifies the DeNB through the overload notification message, the overload notification message carries the GUMMEI of the overloaded RN-MME;

 Step 914, the DeNB forwards the overload notification message to the RN, and carries the GUMMEI of the overload RN-MME in the message;

 Step 915: The RN sends an overload notification response message to the DeNB.

 Step 916: The DeNB sends an overload notification response message to the RN-MME.

Step 917, the RN acquires the GUMMEI of the UE-MME in step 905, in step 914. The GUMMEI of the overloaded RN-MME is obtained, and the two GUMMEIs are compared. If they are not the same, the RN-MME and the UE-MME are determined to be different MMEs. At this time, the RN initiates handover of the UE: handover of the UE to other eNodeBs .

 The RN requires the UE to report the measurement signal, and the UE reports the measured measurement signal to the RN;

 Step 918: The RN sends a handover request message to the DeNB.

 Step 919: The DeNB sends a handover response message to the RN.

 Step 920: The DeNB sends a path switch request message to the UE-MME.

 Step 921: The UE-MME sends a path switch response message to the DeNB, and starts to perform handover of the eNodeB accessed by the UE.

 FIG. 10 is a schematic diagram of a user release method for a network element overloaded according to Embodiment 6 of the present invention. In this embodiment, the access process is a TAU process, and the UE-MME and the RN-MME are different MMEs, and the RN initiates the UE. Switching, as shown in Figure 10, the method includes:

 The TAU process in steps 1001 to 1009 is the same as the TAU process in steps 601 to 609, and is not described here.

 Step 1010: When the RN-MME is overloaded, the RN-MME notifies the DeNB by using an overload notification message, and the overload notification message carries the GUMMEI of the overloaded RN-MME;

 Step 1011, the DeNB forwards the overload notification message to the RN, and carries the GUMMEI of the overload RN-MME in the message;

 Step 1012: The RN sends an overload notification response message to the DeNB.

 Step 1013: The DeNB sends an overload notification response message to the RN-MME.

 In step 1014, the RN obtains the GUMMEI of the UE-MME in step 1005, and obtains the GUMMEI of the overloaded RN-MME in step 1011, and compares the two GUMMEIs. If different, the RN may determine that the RN-MME is different from the UE-MME. The MME, at this time, needs the RN to initiate handover of the UE: handover the UE to other eNodeBs.

The RN requires the UE to report the measurement signal, and the UE reports the measured measurement signal to the RN. Step 1018: The RN sends a handover request message to the DeNB.

 Step 1019: The DeNB sends a handover response message to the RN.

 Step 1020: The DeNB sends a path switch request message to the UE-MME.

 Step 1021: The UE-MME sends a path switch response message to the DeNB, and starts to perform handover of the eNodeB accessed by the UE.

 In order to implement the foregoing method, the present invention further provides a user release system with a network element overload, including: a DeNB, an RN, and an RN-MME, where:

 a DeNB, configured to notify, by the user equipment (UE), an mobility management unit (MME) (UE-MME) that the UE accesses to the RN during the access process;

 The RN is configured to determine whether the RN-MME and the UE-MME are the same MME when the MME (the RN-MME) is overloaded, and initiates the release or handover of the UE when the judgment result is no;

 The RN-MME is configured to initiate release of the UE when the determination result is yes.

 The RN is further configured to compare whether the GUMMEI of the RN-MME and the GUMMEI of the UE-MME are the same. If they are the same, determine that the RN-MME and the UE-MME are the same MME; if not, determine that the RN-MME is different from the UE-MME. MME.

 The DeNB is further configured to: when the access procedure is an attach procedure, send the UE-MME's GUMMEI to the RN by using an initial context setup request message; and when the access procedure is a tracking area update (TAU) process, the UE- The MME's GUMMEI is sent to the application for implementing the foregoing method and system by using the TAU accept message. The present invention further provides an RN, including: an information receiving module, an analyzing module, and a triggering module;

 An information receiving module, configured to acquire information about a mobility management unit (UE-MME) accessed by a UE sent by a DeNB during a UE access process;

An analysis module, configured to determine that an MME (RN-MME) accessing the RN is overloaded, and determining Whether the RN-MME and the UE-MME are the same MME, when the determination result is no, the triggering module is notified; when the determination result is no, the RN-MME is notified.

 The triggering module is configured to initiate release or handover of the UE when the determination result is no.

 among them,

 The analysis module is further configured to compare whether the globally unique MME identity (GUMMEI) of the RN-MME and the GUMMEI of the UE-MME are the same. If the same, determine that the RN-MME and the UE-MME are the same MME; if not, determine the RN- The MME and the UE-MME are different MMEs.

 The information receiving module is further configured to: receive an initial context setup request message of the UE-MME-equipped GUMMEI sent by the DeNB when the access process is an attach procedure; or, may also be used in the access process as a tracking area update (TAU) process. The TAU accept message of the GUMMEI carrying the UE-MME sent by the DeNB is received.

 The information receiving module is further configured to: when the attaching process, or the TAU process is completed, and the analyzing module determines that the RN-MME is overloaded, receive the overload notification message sent by the RN-MME forwarded by the DeNB; and the overload notification message carries the GUMMEI of the RN-MME.

 The triggering module is further configured to: send, by the DeNB, an S1 release request message to the UE-MME; and receive an S1 release instruction message that is returned by the UE-MME through the DeNB; and then send an RRC release request message to the UE, and carry the release cause value in the message. It is required for "network balancing", and after receiving the RRC release complete message returned by the UE to the UE, the DeNB transmits an S1 release complete message to the UE-MME.

 The triggering module is further configured to: request the UE to report the measurement signal; after acquiring the measurement signal, send a handover request message to the DeNB, and receive a handover response message returned by the DeNB.

 The present invention further provides a UE-MME, including: an access module and a release module; wherein: an access module, configured to receive access by the UE;

The release module is configured to initiate release of the UE when the MME (RN-MME) that the RN accesses is overloaded, and the RN-MME and the UE-MME are not the same MME. UE-MME also includes:

 An information processing module, configured to provide a GUMMEL of the UE-MME to the RN through the DeNB. The information processing module is further configured to: when the release of the UE initiated by the RN is completed, receive an S1 release completion message returned by the RN through the DeNB; During the handover process of the UE initiated by the RN, after receiving the path switch request message sent by the DeNB, the device returns a path switch response message to the DeNB.

 The present invention also provides a donor base station (DeNB), including:

 The information management module is configured to obtain information about a mobility management unit (UE-MME) accessed by the UE during the UE access process, and notify the RN.

 among them,

 The information management module is further configured to: when the access procedure is an attach procedure, acquire the GUMMEI from the UE-MME, and send the message to the RN by using an initial context setup request message; and further, when the access procedure is a TAU procedure, to the UE-MME The GUMMEI is obtained, and the TAU accept message is sent to the RN.

 The information management module is further configured to: when the MME (RN-MME) that is accessed by the RN is overloaded, receive an overload notification message sent by the RN-MME, and forward the message to the RN; and the overload notification message is sent to the RN. GUMMEL carrying RN-MME

 The information management module is further configured to forward the S1 release request message from the RN to the UE-MME during the release of the RN, and forward the S1 release command message returned by the UE-MME to the RN, and send the RN to the RN. S1 release completion message is forwarded to the UE-MME;

 The method further includes: after receiving the handover request message sent by the RN, after receiving the handover request message sent by the RN, returning the handover response message to the RN, and sending the path switch request message to the UE-MME, and receiving the path switch response returned by the UE-MME Message.

 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 user network release method for overloading a network element, the method comprising: a mobility management unit (UE-MME) in which a donor base station (DeNB) accesses a UE during a user equipment (UE) access procedure ) to the relay node (RN);  When the MME (RN-MME) accessing the RN is overloaded, the RN determines whether the RN-MME and the UE-MME are the same MME; if not, the RN initiates release or handover of the UE; if yes, waits The RN-MME initiates release of the UE.  The user release method of the network element overload according to claim 1, wherein the RN determines whether the RN-MME and the UE-MME are the same MME, specifically: the RN compares the RN-MME Whether the globally unique MME identity (GUMMEI) and the GUMMEI of the UE-MME are the same. If they are the same, it is determined that the RN-MME and the UE-MME are the same MME. If not, the RN-MME and the MME are determined. The UE-MME is a different MME.  The method for releasing the user of the network element overload according to claim 2, wherein, when the access procedure is an attach procedure, the DeNB notifies the UE to the RN, specifically:  The DeNB sends the GUMMEI of the UE-MME to the RN by using an initial context setup request message.  The method for releasing the user of the network element overload according to claim 2, wherein, when the access process is a tracking area update (TAU) process, the DeNB notifies the UE to the RN, specifically:  The DeNB sends the GUMMEI of the UE-MME to the RN through a TAU accept message.  The user release method of the network element overload according to claim 3 or 4, wherein when the attaching process or the TAU process is completed, the method further includes: When the RN-MME is overloaded, the RN-MME will carry its own overload of GUMMEI. A notification message is sent to the RNo through the DeNB  The user release method of the network element overload according to claim 5, wherein the RN initiates release of the UE, including:  The RN sends an S1 release request message to the UE-MME through the DeNB;  The UE-MME returns an S1 release instruction message to the RN through the DeNB;  The RN sends an RRC release request message to the UE, and carries the release cause value as "required for network balance" in the message;  The UE sends an RRC release complete message to the RN;  The RN sends an S1 release complete message to the UE-MME through the DeNB.  The method for releasing a user of the network element overload according to claim 5, wherein the RN initiates handover of the UE, including:  The RN requires the UE to report the measurement signal, and the UE reports the measured measurement signal to the RN; The RN sends a handover request message to the DeNB;  The DeNB sends a handover response message to the RN;  The DeNB sends a path switch request message to the UE-MME;  The UE-MME sends a Path Switch Response message to the DeNB.  8. A user release system with a network element overload, characterized in that the system comprises: a donor base station (DeNB), a relay node (RN) and an RN-MME, wherein:  The DeNB is configured to notify, by the user equipment (UE), a mobility management unit (UE-MME) that the UE accesses during the access process to the RN;  The RN is configured to determine whether the RN-MME and the UE-MME are the same MME when the MME (RN-MME) that is in the access is overloaded; and if the judgment result is no, the UE is initiated. Release or switch;  The RN-MME is configured to initiate release of the UE when the determination result is yes. 9. The network element overloaded user release system according to claim 8, wherein: The RN is further configured to compare whether the GUMMEI of the RN-MME and the GUMMEI of the UE-MME are the same. If they are the same, determine that the RN-MME and the UE-MME are the same MME; if not, determine The RN-MME and the UE-MME are different MMEs.  The user equipment release system of the network element overload according to claim 9, wherein the DeNB is further configured to: establish, by the initial context, the GUMMEI of the UE-MME when the access procedure is an attach procedure The request message is sent to the RN; and when the access procedure is a Tracking Area Update (TAU) process, the GUMMEI of the UE-MME is sent to the RN by using a TAU accept message.  A relay node (RN), comprising: an information receiving module, an analyzing module, and a triggering module; wherein:  The information receiving module is configured to acquire information about a mobility management unit (UE-MME) accessed by the UE sent by the DeNB during a UE access process;  The analyzing module is configured to determine, when the MME (RN-MME) that is accessed by the RN is overloaded, determine whether the RN-MME and the UE-MME are the same MME, and when the determination result is no, notify the Triggering module; when the judgment result is no, the RN-MME is notified;  The triggering module is configured to initiate release or handover of the UE when the determination result is negative. 12. The RN according to claim 11, wherein:  The analyzing module is further configured to compare whether the globally unique MME identity (GUMMEI) of the RN-MME and the GUMMEI of the UE-MME are the same. If they are the same, determine that the RN-MME is the same as the UE-MME. An MME; if not, determining that the RN-MME and the UE-MME are different MMEs.  13. The RN according to claim 12, characterized in that The information receiving module is further configured to: when the access procedure is an attach procedure, receive an initial context setup request message that is sent by the DeNB and that carries the GUMMEI of the UE-MME; or is further used in the access process. Receiving the DeNB when tracking the zone update (TAU) process The TAU accept message of the GUMMEI carrying the UE-MME is sent.  14. The RN according to claim 13, wherein:  The information receiving module is further configured to: when the attaching process, or the TAU process is completed, and the analyzing module determines that the RN-MME is overloaded, receive an overload notification sent by the RN-MME forwarded by the DeNB The overload notification message carries the GUMMEI of the RN-MME.  The RN according to claim 14, wherein, when the UE is released, the triggering module is further configured to send an S1 release request message to the UE-MME by using the DeNB; and receive the UE-MME to pass The S1 release instruction message returned by the DeNB; then, sending an RRC release request message to the UE, and carrying the release cause value as "required for network balance" in the message, and passing the DeNB after receiving the RRC release completion message returned by the UE to the UE The SI release complete message is sent to the UE-MME.  The RN according to claim 14, wherein, when the handover of the UE is initiated, the triggering module is further configured to: request the UE to report a measurement signal; after acquiring the measurement signal, send the signal to the DeNB And switching a request message, and receiving a handover response message returned by the DeNB.  A mobility management unit (UE-MME) for accessing a mobile terminal, comprising: an access module and a release module; wherein:  The access module is configured to accept access by the UE;  And the releasing module is configured to initiate release of the UE when an MME (RN-MME) that is accessed by the RN is overloaded, and the RN-MME and the UE-MME are not the same MME.  The UE-MME according to claim 17, further comprising: an information processing module, configured to provide the UE-MME's GUMMEI to the RN by using a DeNB. 19. The UE-MME according to claim 18, characterized in that The information processing module is further configured to: when the release of the UE initiated by the RN is completed, receive an S1 release completion message returned by the RN through the DeNB; and further, be used to receive the path switch request sent by the DeNB in the handover process of the UE initiated by the RN. After the message, a path switch response message is returned to the DeNB.  20. A donor base station (DeNB), comprising:  The information management module is configured to obtain information about a mobility management unit (UE-MME) accessed by the UE during the UE access process, and notify the RN.  21. The DeNB according to claim 20, wherein:  The information management module is further configured to: when the access procedure is an attach procedure, acquire a GUMMEI from the UE-MME, and send the message to the RN by using an initial context setup request message; When the process is a TAU procedure, the GUMMEI is acquired to the UE-MME, and a TAU accept message is sent to the RN.  22. The DeNB according to claim 21, wherein:  The information management module is further configured to: when the MME (RN-MME) that is accessed by the RN is overloaded, receive an overload notification message sent by the RN-MME, where the attaching process, or the TAU process is completed, And forwarding to the RN; the overload notification message carries the GUMMEI of the RN-MME.  23. The DeNB according to claim 22, wherein:  The information management module is further configured to forward an S1 release request message from the RN to the UE-MME during the release of the RN by the RN; and forward the S1 release instruction message returned by the UE-MME to the RN And forwarding an S1 release complete message sent by the RN to the UE-MME;  The method further includes: after receiving the handover request message sent by the RN, after receiving the handover request message sent by the RN, returning the handover response message to the RN, and sending the path switch request message to the UE-MME, and receiving the path switch response returned by the UE-MME Message.