WO2012010037A1

WO2012010037A1 - Method and system for deleting terminal information on direct interface

Info

Publication number: WO2012010037A1
Application number: PCT/CN2011/076221
Authority: WO
Inventors: 王昇明; 李大鹏; 奚进
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-07-23
Filing date: 2011-06-23
Publication date: 2012-01-26
Also published as: CN102340881A

Abstract

The invention discloses a method for deleting terminal information on a direct interface. The method includes the following steps: a source network element sends a reset request message carrying a terminal identifier through the direct interface; after receiving the reset request message on the direct interface, a target network element deletes the resources allocated for the terminal corresponding to the terminal identifier. A system for deleting terminal information on a direct interface is also disclosed. With the method and system of the invention, the number of terminal resource release signalings is reduced, the efficiency of resource release is enhanced, and thus the network performance is improved.

Description

Method and system for deleting terminal information on direct interface

The present invention relates to wireless cellular communication technologies, and in particular, to a method and system for terminal information deletion on a direct interface. Background technique

The Long Term Evolution (LTE) system of the third generation mobile communication is based on Orthogonal Frequency Division Multiplexing (OFDM A) developed by the 3GPP (3GPP, Third Generation Partnership Projects). Access) technology for new wireless communication systems. Compared with the existing wireless communication technology, LTE has the advantages of large data transmission bandwidth, high spectral efficiency, good anti-interference to wireless signal multipath interference, and the like, and is the main technology of the next generation communication system. The LTE system is composed of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a User Equipment (UE), and an Evolved Packet Core (EPC). As shown in FIG. 1 , the E-UTRAN is composed of an evolved base station (eNB, evolved NodeB), and the eNB is connected to a Mobility Management Entity (MME) and a Serving Gateway (S-GW) through an SI interface. The eNBs are connected through an X2 interface. On the basis of LTE, 3GPP is continuing to develop the LTE-Advanced (Long-Term Evolution Advance) standard. LTE-A uses technologies such as spectrum aggregation (CA), wireless relay (Relay), and high-order multiple input multiple output (MIMO) to achieve higher system performance.

In wireless communication networks, some areas cannot connect to the wired backbone network of ordinary base stations due to terrain or environmental reasons, or have temporary wireless coverage requirements for some corners or hotspots, but the cost of base station equipment with line connections is higher. . For these wireless coverage needs Seeking, you can usually use the Relay device to solve. As shown in FIG. 2, the relay device and the existing network base station are connected by using a wireless signal, and provide services to UEs within their coverage, thereby achieving coverage expansion, reducing coverage dead angle, and transferring hotspot load.

Wireless relay is one of the technologies supported by LTE-A. In LTE-A, a base station that is wirelessly connected to a relay node (RN, Relay Node) is called a donor base station (DeNB, Donor eNB), and a radio link between the DeNB and the RN is called a backhaul link. Its air interface is called the Un interface. The radio link between the RN and the UE is called an access link, and the air interface is called the Uu interface. The RN acts as an eNB for the UE it serves, and acts as a UE for its DeNB. The downlink data arrives at the DeNB first, and then passes to the RN, which then transmits to the UE, and vice versa. The LTE-A system mainly uses the "Type 1 Relay", the so-called first type of wireless relay, which has the following characteristics: For the UE, the relay node is an independent cell, which is different from the DeNB. Cell, and the Relay cell has an independent physical cell ID (PCI, Physical Cell ID)

The RN can establish a direct interface with other surrounding RNs and macro base stations, and the RN establishes a direct interface with other base stations through the DeNB. That is, the RN transmits the information on the direct interface to the DeNB through the Un interface, and the DeNB is responsible for transmitting the information on the direct interface to the target network element of the direct interface.

In addition, with the development of wireless systems, in order to increase the coverage of macro networks and improve high-speed data services for users, the concept of a home base station is proposed. The home base station is a general term for a home base station (HNB, Home NodeB) and an evolved home base station (HeNB, Home evolved NodeB), and is simply referred to as H (e) NB. H ( e ) NB is a small, low-power base station deployed in indoor locations such as homes and offices. Its main function is to provide users with higher service rates and lower the cost of using high-speed services. There is a shortage of coverage of distributed cellular wireless communication systems. The advantages of H(e)NB are affordable, convenient, low power output, plug and play, and more. The home base station user is connected to the core network through an H (e) NB access network (AN, Access Network), as shown in FIG. 3 and FIG. 4, FIG. 3 is a schematic diagram of a network structure of the HNB system in the prior art. 4 is a schematic diagram of a network structure of a HeNB system in the prior art. The H ( e ) NB AN is composed of H ( e ) NB and H ( e ) NB gateways ( GW , Gateway ). The main functions performed by the H ( e ) NB GW are: processing H ( e ) NB registration and connection Incoming control, verifying H(e)NB, responsible for exchanging data of core network and H(e)NB. In addition, the H ( e ) MS is an H ( e ) NB management system that performs operation and maintenance management on the H ( e ) NB , and configures and controls H ( e ) NB according to the operator 's requirements , the most important being H ( e ) NB . Implement configuration management functions, including verification of location information, parameter configuration for H(e)NB, mainly related to parameter configuration of the core network (CN, Core Network) level, and radio access network (RAN, Radio Access Network) side Parameter configuration and parameter configuration of radio frequency (RF, Radio Frequency).

Similarly, a direct interface can be established between H ( e ) NBs, and the direct interface between H ( e ) NBs is completed by the H ( e ) NB GW . That is, the information transfer between the H(e)NBs of the direct interface is established, and the information forwarding to the target network element needs to be performed by the H(e)NBGW.

Since both RN and H(e)NB introduce a direct interface, and the structural difference between RN and H(e)NB is the difference between the wireless connection and the wired connection, the problems existing after the introduction of the direct interface are consistent. The following takes RN as an example for analysis.

As shown in FIG. 5, the RN1 establishes a direct interface with the eNB and the RN2 through the DeNB, where the direct interface between the RN1 and the DeNB is marked as the direct interface A, and the direct interface between the DeNB and the RN2 is marked as the direct interface B. The direct interface between the DeNB and the eNB is labeled as direct interface C. The reason for the above division is as follows: The direct interface between the RN 1 and the RN2 and the eNB is established. Since the DeNB functions as a proxy, the two direct interfaces exist respectively, and the RN1 knows that the information can directly reach the RN2 through the direct interface A. And eNB.

In the case of a reset (Reset) on the direct interface A, the following problems will occur: Since the Reset function of the direct interface is used for the resources between its interfaces, it does not affect the application. Layer data, that is, does not affect the application layer data when the interface is established; when the RN1 sends a Reset message to the DeNB, it is desirable for the DeNB to release all resources related to the RN1, including related UE resources; after receiving the Reset message, the DeNB It is obviously inappropriate for the RN or eNB to perform the direct interface information transmission to send the Reset message, because other base stations (such as RN3 in FIG. 5) may share these direct interfaces; then the DeNB should send multiple UE-related resources to the RN1 or the eNB. Release the message (such as the handover cancellation message), which will inevitably generate a large amount of terminal resource release signaling, and some UE resource release can only be completed by the timer timeout protection, for example: Before the RN1 reset occurs, if there is more on the RN1 When a UE switches to RN2, multiple resources are wasted instantaneously on RN2, so that resources cannot be released in time. Summary of the invention

In view of this, the main purpose of the present invention is to provide a method and system for deleting terminal information on a direct interface, so as to reduce the number of terminal resource release signaling and improve resource release efficiency.

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

The present invention provides a method for deleting terminal information on a direct interface, the method comprising: sending, by a source network element, a reset request message carrying a terminal identifier through a direct interface;

After receiving the reset request message on the direct interface, the target network element deletes the resource allocated by the terminal corresponding to the terminal identifier.

The terminal identifier is at least one of the following: the source network element is an identifier assigned by the terminal, and the target network element is an identifier allocated by the terminal.

The source network element is: a relay node (RN), an evolved base station (eNB), a donor base station (DeNB), a home base station, or a home base station gateway.

The target network element is: RN, eNB, DeNB, home base station or home base station gateway.

After deleting the resources allocated by the terminal corresponding to the terminal identifier, the method further includes:

Returning, by the target network element, a reset response message to the source network element, where the reset response message carries the The terminal identifier.

The present invention also provides a system for deleting terminal information on a direct interface, the system comprising: a source network element, configured to send a reset request message carrying a terminal identifier through a direct interface; and a target network element, configured to receive on a direct interface After the reset request message, the resources allocated by the terminal corresponding to the terminal identifier are deleted.

The source network element is: an RN, an eNB, a DeNB, a home base station, or a home base station gateway.

The target network element is: an RN, an eNB, a DeNB, a home base station, or a home base station gateway.

The target network element is further configured to: after deleting the resource allocated by the terminal corresponding to the terminal identifier, return a reset response message to the source network element, where the reset response message carries the terminal identifier.

The method and system for deleting terminal information on a direct interface provided by the present invention, the source network element sends a reset request message carrying the terminal identifier through the direct interface; after the target network element receives the reset request message on the direct interface, the target network element deletes The terminal allocates the resources allocated by the corresponding terminal. With the method and system of the present invention, the number of terminal resource release signaling can be reduced, the resource release efficiency is improved, and network performance is improved. DRAWINGS

1 is a schematic structural diagram of a structure of an LTE system in the prior art;

2 is a schematic structural diagram of a wireless communication network including a relay device in the prior art; FIG. 3 is a schematic diagram of a network structure of an HNB system in the prior art;

4 is a schematic diagram of a network structure of a HeNB system in the prior art;

5 is a schematic diagram of establishing a direct interface in an RN application scenario in the prior art; FIG. 6 is a flowchart of a method for deleting terminal information on a direct interface according to Embodiment 1 of the present invention; FIG. 7 is a schematic diagram of a direct interface on a second embodiment of the present invention; Flow chart of method for deleting terminal information; FIG. 8 is a flowchart of a method for deleting terminal information on a direct interface according to Embodiment 3 of the present invention; FIG. 9 is a flowchart of a method for deleting terminal information on a direct interface according to Embodiment 4 of the present invention. detailed description

The technical solutions of the present invention are further elaborated below in conjunction with the accompanying drawings and specific embodiments. In order to reduce the number of terminal resource release signaling and improve the resource release efficiency, the method for deleting terminal information on the direct interface provided by the present invention includes: the source network element sends a reset request message carrying the terminal identifier through the direct interface; After receiving the reset request message on the direct interface, the element deletes the resource allocated by the terminal corresponding to the terminal identifier according to the terminal identifier in the reset request message. The terminal identifier is at least one of the following: the source network element is an identifier assigned by the terminal, and the target network element is an identifier assigned by the terminal. In addition, the source network element of the present invention may be: RN, eNB, DeNB, home base station or home base station gateway; the target network element may be: RN, eNB, DeNB, home base station or home base station gateway.

The method for deleting the terminal information on the direct interface described above is further elaborated in conjunction with the specific embodiments.

The first embodiment of the present invention describes the process of performing direct interface relocation by using the terminal information deletion method of the present invention in the application scenario of the RN. For convenience of description, it is assumed that RN1 establishes a direct interface with RN2 through the DeNB. Since the DeNB completes the proxy function of the direct interface, the DeNB regards RN1 and RN2 as cells, and therefore there are two between RN1 and DeNB, and between RN2 and DeNB. Segment direct interface. As shown in Figure 6, when RN1 initiates a reset of the direct interface, the specific processing procedure includes:

Step 601: When the RN1 has a memory application problem, the RN1 sends a reset request message to the DeNB through the direct interface, where the reset request message carries the cause of the reset. The reset request message may also carry the terminal identifier, and is used to reset the specific terminal. information.

Step 602: After receiving the reset request message on the direct interface sent by the RN1, the DeNB returns a reset response message to the RN1 through the Un interface, and deletes the resource allocated for the RN1; When the request message carries the terminal identifier, the DeNB deletes the resource allocated for the specific terminal.

Step 603: The DeNB receives the reset request message. If the reset request message does not include the terminal identifier, the DeNB sends a reset request message of the direct interface to the RN2, where the information exchange process (such as switching) between the RN1 and the RN2 is performed. The identity of all terminals. The identifier may be an identifier on the direct interface allocated by the RN2 for the terminal (such as the EN2 eNB UE X2AP ID allocated by the RN2 for the terminal), or an identifier on the direct interface allocated by the DeNB for the terminal (for example, the DeNB eNB UE allocated by the DeNB for the terminal) X2 AP ID ), or RN 1 is the identifier of the direct interface allocated by the terminal (for example, RN1 is the RN1 eNB UE X2AP ID assigned by the terminal), and may also be any combination of the identifier on the direct interface allocated by the RN2 for the terminal and the following identifier. : The identifier on the direct interface assigned by the DeNB to the terminal, and the identifier on the direct interface assigned by the RN1 to the terminal. If the reset request message received by the DeNB includes the terminal identifier, the RN2 sends a reset request message of the direct interface, where the terminal identifier of the DeNB corresponding to the terminal identifier in the reset request message received by the DeNB to the terminal on the direct interface of the RN2 is included. Logo.

Step 604, after receiving the reset request message of the direct interface that includes the terminal identifier, the RN2 terminates the processing flow of the terminal corresponding to the terminal identifier, deletes the resource allocated to the terminal, includes all the contexts of the terminal, and returns the reset response of the direct interface to the DeNB. The message carries a terminal identification message, and the identifier is consistent with the terminal identifier in the reset request message.

The second embodiment of the present invention describes the process of performing direct interface relocation by using the terminal information deletion method of the present invention in the application scenario of the RN. For convenience of description, it is assumed that RN1 establishes a direct interface with RN2 through the DeNB. Since the DeNB completes the proxy function of the direct interface, the DeNB regards RN1 and RN2 as cells, and therefore there are two between RN1 and DeNB, and between RN2 and DeNB. Segment direct interface. As shown in Figure 7, when RN1 initiates a reset of the direct interface, the specific processing procedure includes:

Step 701: When the RN1 has a memory application problem, the RN1 sends a reset request message to the DeNB through the direct interface, where the reset request message carries the cause of the reset; wherein, the reset The request message may also carry a terminal identifier to reset information of a specific terminal.

Step 702: After receiving the reset request message on the direct interface sent by the RN1, the DeNB deletes the resource allocated for the RN1. When the reset request message carries the terminal identifier, the DeNB deletes the resource allocated for the specific terminal. If the terminal identifier is not included in the reset request message, the DeNB sends a reset request message of the direct interface to the RN2, including the identifiers of all terminals that are performing an information exchange process (such as handover) between the RN 1 and the RN 2. The identifier may be an identifier on the direct interface allocated by the RN2 for the terminal (such as the EN2 eNB UE X2AP ID allocated by the RN2 for the terminal), or an identifier on the direct interface allocated by the DeNB for the terminal (for example, the DeNB eNB UE allocated by the DeNB for the terminal) The identifier of the direct interface allocated by the terminal (such as the RN1 eNB UE X2AP ID allocated by the RN1), and the RN2 may be any combination of the identifier on the direct interface allocated by the terminal and the following identifier: DeNB The identifier on the direct interface assigned to the terminal, and RN1 is the identifier on the direct interface assigned by the terminal. If the reset request message received by the DeNB includes the terminal identifier, the RN2 sends a reset request message of the direct interface, where the terminal identifier of the DeNB corresponding to the terminal identifier in the reset request message received by the DeNB to the terminal on the direct interface of the RN2 is included. Logo.

Step 703: After receiving the reset message of the direct interface that includes the terminal identifier, the RN2 terminates the processing flow of the terminal corresponding to the terminal identifier, and deletes the resource allocated to the terminal, including all the contexts of the terminal. The RN2 returns a reset response message of the direct interface to the DeNB, where the message carries a terminal identification message, and the identifier is consistent with the terminal identifier in the reset request message.

Step 704: After receiving the reset response message on the direct interface sent by the RN2, the DeNB returns a reset response message to the RN1 through the Un interface, where the DeNB may also carry the terminal identifier.

The method in the foregoing embodiment is applicable to the direct interface reset process initiated by the RN and the DeNB, and is also applicable to the direct interface reset process of the normal eNB, and the processing procedure is similar, and details are not described herein again.

Embodiment 3 of the present invention describes that terminal information deletion by the present invention is performed under the HeNB system. The method completes the process of direct interface relocation. For convenience of description, it is assumed that the HeNB1 establishes a direct interface with the HeNB2 through the HeNB GW. Since the HeNB GW completes the proxy function of the direct interface, the HeNB GW regards the HeNB1 and the HeNB2 as cells, and therefore there are HeNB1 and HeNB GW, and HeNB2 and HeNB. The two sections of the GW are directly interfaced. As shown in FIG. 8, when the HeNB1 initiates a reset of the direct interface, the specific processing procedure includes:

Step 801: When the HeNB1 has a memory application problem, the HeNB1 sends a reset request message on the direct interface to the HeNB GW, where the reset request message carries the cause of the reset. The reset request message may also carry the terminal identifier to reset the specific Terminal information.

Step 802: After receiving the reset request message on the direct interface sent by the HeNB 1, the HeNB GW returns a reset response message to the HeNB1, where the HeNB GW may also carry the terminal identifier.

Step 803: The HeNB GW receives the reset request message, and deletes the resource allocated to the HeNB1. When the reset request message carries the terminal identifier, the HeNB GW deletes the resource allocated for the specific terminal. If the terminal identifier is not included in the reset request message, the HeNB GW sends a reset request message of the direct interface to the HeNB2, including the identifiers of all terminals that are performing an information exchange process (such as handover) between the HeNB 1 and the HeNB 2. The identifier may be an identifier on the direct interface allocated by the HeNB2 for the terminal (such as the HeNB2 eNB UE X2AP ID allocated by the HeNB2 for the terminal), or an identifier on the direct interface allocated by the HeNB GW for the terminal (such as the HeNB_GW allocated by the HeNB GW for the terminal). The eNB UE X2AP ID), or the identifier on the direct interface allocated by the HeNB1 for the terminal (such as the HeNB1 eNB UE X2AP ID allocated by the HeNB1 for the terminal), may also be any combination of the identifier on the direct interface allocated by the HeNB2 for the terminal and the following identifier. : The HeNB GW is the identifier on the direct interface assigned by the terminal, and the HeNB 1 is the identifier on the direct interface allocated by the terminal. If the reset request message received by the HeNB GW includes the terminal identifier, the HeNB2 sends a direct interface reset request message to the HeNB2, where the HeNB GW to the HeNB2 corresponding to the terminal identifier in the reset request message received by the HeNB GW is directly connected. Terminal identification on.

Step 804, after receiving the reset request message of the direct interface including the terminal identifier, the HeNB2 receives the reset request message. Terminating the processing flow of the terminal corresponding to the terminal identifier, deleting the resource allocated for the terminal, including all the contexts of the terminal, and returning a reset response message of the direct interface to the HeNB GW, where the message carries the terminal identification message, and the terminal in the identifier and the reset request message The logos are consistent.

The above processing method may also use the sequence of steps described in the second embodiment, that is, the HeNB GW sends a reset response to the HeNB1 after receiving the reset response from the HeNB2.

The method in the foregoing embodiment is applicable to the direct interface resetting process initiated by the HeNB and the HeNB GW, and is also applicable to the direct interface reset process of the normal eNB, and the processing procedure is similar, and details are not described herein again.

Embodiment 4 of the present invention describes a flow of direct interface relocation by the terminal information deletion method of the present invention under the HNB system. For convenience of description, it is assumed that HNB1 establishes a direct interface with HNB2 through HNB GW. Since HNB GW completes the proxy function of the direct interface, HNB GW regards HNB1 and HNB2 as cells, so there exists between HNB1 and HNB GW, and HNB2 and HNB. The two sections of the GW are directly interfaced. As shown in Figure 9, when HeNB1 initiates a reset of the direct interface, the specific processing flow includes:

Step 901: When the HNB1 has a memory application problem, the HNB1 sends a reset request message on the direct interface to the HNB GW, where the reset request message carries the cause of the reset. The reset request message may also carry the terminal identifier to reset the specific Terminal information.

Step 902: After receiving the reset request message on the direct interface sent by the HNB1, the HNB GW returns a reset response message to the HNB1, where the HNB GW may also carry the terminal identifier.

Step 903: The HNB GW receives the reset request message, and deletes the resource allocated to the HNB 1. When the reset request message carries the terminal identifier, the HNB GW deletes the resource allocated for the specific terminal. If the reset request message does not include the terminal identifier, the HNB GW sends a reset request message of the direct interface to the HNB2, including the identifiers of all terminals that are performing an information exchange process (such as a relocation process) between the HNB 1 and the HNB 2. The identifier may be an identifier on a direct interface allocated by the HNB2 for the terminal, or an identifier on a direct interface allocated by the HNB GW to the terminal, Or HNB 1 is an identifier on the direct interface allocated by the terminal, and may be any combination of the identifier on the direct interface allocated by the HNB2 for the terminal and the following identifier: HNB GW is the identifier of the direct interface allocated by the terminal, and HNB 1 is the terminal. The identifier on the assigned direct interface. If the reset request message received by the HNB GW includes the terminal identifier, the HNB2 sends a reset request message of the direct interface, where the HNB GW corresponding to the terminal identifier in the reset request message received by the HNB GW is directly connected to the HNB2. Terminal identification on.

Step 904: After receiving the reset request message of the direct interface that includes the terminal identifier, the HNB2 terminates the processing flow of the terminal corresponding to the terminal identifier, deletes the resource allocated to the terminal, includes all the contexts of the terminal, and returns a reset of the direct interface to the HNB GW. In response to the message, the message carries a terminal identification message, and the identifier is consistent with the terminal identifier in the reset request message.

The method in the foregoing embodiment is applicable not only to the reset process of the direct interface initiated by the HNB and the HNB GW, but also to the direct interface reset process of the normal RNC, and the processing procedure is similar, and details are not described herein again.

It should be noted that the reset request message and the reset response message on the direct interface of the HNB may be a newly added HNBAP (HNB Application Part) message and a RANAP (RAN Application Part) user. Adaptation (RUA, RANAP User Adaption) message or Radio Network Subsystem Application Part (RSS) message. The present invention does not limit the specific message. In addition, the foregoing processing method may also use the sequence of steps described in Embodiment 2, that is, the HNB GW sends a reset response to the HNB after receiving the reset response from the HNB 2.

Corresponding to the method for deleting terminal information on the direct interface, the present invention further provides a system for deleting terminal information on a direct interface, including: a source network element and a target network element. The source network element is configured to send, by using a direct interface, a reset request message that carries the identifier of the terminal. The target network element is configured to: after receiving the reset request message on the direct interface, delete the resource allocated by the terminal corresponding to the terminal identifier according to the terminal identifier in the reset request message. The terminal identifier is at least one of the following: the source network element is an identifier allocated by the terminal, and the target network element is an identifier allocated by the terminal. The source network element is: an RN, an eNB, a DeNB, a home base station, or a home base station gateway. The target network element is: RN, eNB, DeNB, home base station or home base occupied gateway.

Preferably, the target network element is further configured to: after deleting the resource allocated by the terminal corresponding to the terminal identifier, return a reset response message to the source network element, where the reset response message carries the terminal identifier.

In summary, the present invention can reduce the number of terminal resource release signaling and improve resource release efficiency by transmitting a reset request message carrying a terminal identifier instead of transmitting a large number of terminal resource release signaling, thereby improving network performance.

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 deleting a terminal information on a direct interface, the method comprising: the source network element sending, by using a direct interface, a reset request message carrying a terminal identifier;

The method for deleting the terminal information on the direct interface according to claim 1, wherein the terminal identifier is at least one of the following: the source network element is an identifier allocated by the terminal, and the target network element is an identifier allocated by the terminal.

The method for deleting terminal information on a direct interface according to claim 1 or 2, wherein the source network element is: a relay node (RN), an evolved base station (eNB), a donor base station (DeNB), Home base station or home base station gateway.

The method for deleting terminal information on a direct interface according to claim 1 or 2, wherein the target network element is: RN, eNB, DeNB, home base station or home base station gateway.

The method for deleting the terminal information on the direct interface according to claim 1 or 2, wherein after deleting the resource allocated by the terminal corresponding to the terminal identifier, the method further comprises:

The target network element returns a reset response message to the source network element, where the reset response message carries the terminal identifier.

A system for deleting terminal information on a direct interface, the system comprising: a source network element, configured to send a reset request message carrying a terminal identifier by using a direct interface; and a target network element, configured to receive on a direct interface After the reset request message, the resources allocated by the terminal corresponding to the terminal identifier are deleted.

The system for deleting a terminal information on a direct interface according to claim 6, wherein the terminal identifier is at least one of the following: the source network element is an identifier allocated by the terminal, and the target network element is an identifier allocated by the terminal.

The system for deleting terminal information on a direct interface according to claim 6 or 7, wherein the source network element is: an RN, an eNB, a DeNB, a home base station, or a home base station gateway.

The system for deleting terminal information on a direct interface according to claim 6 or 7, wherein the target network element is: an RN, an eNB, a DeNB, a home base station, or a home base station gateway.

The system for deleting the terminal information on the direct interface according to claim 6 or 7, wherein the target network element is further configured to: after deleting the resource allocated by the terminal corresponding to the terminal identifier, The source network element returns a reset response message, where the reset response message carries the terminal identifier.