WO2012149715A1

WO2012149715A1 - User equipment identification method and device

Info

Publication number: WO2012149715A1
Application number: PCT/CN2011/078896
Authority: WO
Inventors: 沈志超; 陈东
Original assignee: 华为技术有限公司
Priority date: 2011-08-25
Filing date: 2011-08-25
Publication date: 2012-11-08
Also published as: CN102726114A; CN102726114B

Abstract

A user equipment identification method and device. The method includes: when first user equipment in a certain cell is in a CELL-PCH or URA-PCH state, releasing the RRC connection between an RNC and the first user equipment; the RNC receiving an RRC connection request message sent from second user equipment in another cell within the administrative area thereof, and allocating to the second user equipment a first U-RNTI initially allocated to the first user equipment; the RNC receiving a CELL-UPDATE or URA-UPDATE message carrying the first U-RNTI and a first UE initial identification identifying the first user equipment; and determining that the CELL-UPDATE or URA-UPDATE message is sent from the first user equipment and not the second user equipment according to the first UE initial identification.

Description

User terminal identification method and device

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for identifying a user terminal. Background technique

In the UMTS (Universal Mobile Telecommunications System), when in the CELL-PCH (CELL Paging Channel) state or the URA-PCH (UTRAN Registration Area Paging Channel) The UE (User Equipment) in the state, after camping in another cell under the jurisdiction of the RNC (Radio Network Controller) due to cell reselection or other reasons, the UE sends CELL to the network side RNC. -UPDATE (Cell Update Message), the RNC performs the processing operation related to the cell update for the UE.

For URA updates, the process is similar. After the UE in the URA-PCH state camps in another cell under the jurisdiction of the RNC due to cell reselection or other reasons, the UE sends a URA-UPDATE (URA Update message;) to the RNC, and the RNC performs the UE for the UE. Related processing operations for URA updates.

In the prior art, when transmitting a CELL-UPDATE or URA-UPDATE, the UE carries a U-RNTI (Universal Terrestrial Radio Access Network - Radio Network Temporary Identity) to receive CELL-UPDATE. Or the RNC of the URA-UPDATE identifies the corresponding UE according to the U-RNTI.

However, because the RNC only identifies the corresponding UE according to the U-RNTI carried in the CELL-UPDATE or URA-UPDATE, when the different UEs carry the same U-RNTI, the RNC can easily cause the UE to identify the error.

Summary of the invention

The present invention provides a method and apparatus for identifying a user terminal, so that the UE can be correctly identified.

An embodiment of the present invention provides a method for identifying a user terminal, including:

When the first user terminal in a certain cell is in the CELL-PCH or URA-PCH state, releasing the RRC connection between the RNC and the first user terminal; The RNC receives an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and allocates a first U-RNTI originally allocated to the first user terminal to the second user terminal;

The RNC receives a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI and the first UE initial identifier that identifies the first user terminal;

Determining, according to the first UE initial identifier, that the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal instead of the second user terminal.

When the first user terminal in a certain cell is in the CELL-PCH or URA-PCH state, releasing the RRC connection between the RNC and the first user terminal;

Receiving, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and after the preset waiting time, assigning the first U-RNTI originally allocated to the first user terminal to the Said second user terminal;

In the waiting time, the RNC receives a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI; and according to the first U-RNTI, determines The CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal.

Receiving, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and assigning the first U-RNTI originally allocated to the first user terminal to the second user terminal, determining The area of the area to which the second user terminal is located;

The RNC receives a CELL-UPDATE or URA-UPDATE message,

Carrying the first U-RNTI in a CELL-UPDATE or URA-UPDATE message;

And obtaining an area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, when the area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs exceeds the area of the cell to which the second user terminal belongs, determining The CELL-UPDATE or The URA-UPDATE message is not sent by the second user terminal.

Receiving, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and after the preset waiting time, assigning the first U-RNTI originally allocated to the first user terminal to the Determining, by the second user terminal, a range of areas to which the cell in which the second user terminal belongs; the RNC receiving a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI;

And obtaining an area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, when the area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs exceeds the area range of the cell where the second user terminal belongs, determining The CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal.

An embodiment of the present invention provides a device for identifying a user terminal, including:

a connection release control module, configured to release an RRC connection between the RNC and the first user terminal when the first user terminal in a cell is in a CELL-PCH or URA-PCH state;

a U-RNTI allocation module, configured to receive, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and allocate the first U-RNTI originally allocated to the first user terminal to The second user terminal;

An update message receiving module, configured to receive, by the RNC, a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI and identifies the first user terminal UE initial identification;

The identifier determining module is configured to determine, according to the first UE initial identifier, that the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal instead of the second user terminal.

a time preset module, configured to preset a waiting time for allocating a first U-RNTI originally allocated to the first user terminal to the second user terminal; a U-RNTI allocation module, configured to receive, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, after the preset waiting time, assign the original to the first user terminal Assigning, by the first U-RNTI, the second user terminal;

An update message receiving module, configured to receive, by the RNC, a CELL-UPDATE or a URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI;

The identifier determining module is configured to determine, according to the first U-RNTI, that the CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal.

a region scope determining module of the cell, configured to determine a region range to which the cell where the second user terminal belongs;

An update message receiving module, configured to receive, by the RNC, a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI; Comparing the area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, and comparing the area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs and the area of the cell to which the second user terminal belongs;

The determining and determining module is configured to determine that the CELL-UPDATE or URA-UPDATE message is not when the area of the cell to which the CELL-UPDATE or URA-UPDATE message belongs exceeds the area of the cell to which the second user terminal belongs Transmitted by the second user terminal.

a time preset module, configured to preset a first U-RNTI that is originally allocated to the first user terminal Waiting time allocated to the second user terminal;

a U-RNTI allocation module, configured to receive, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, after the preset waiting time, assign the original to the first user terminal Assigning, by the first U-RNTI, the second user terminal;

The determining and determining module is configured to determine that the CELL-UPDATE or URA-UPDATE message is not when the area of the cell to which the CELL-UPDATE or URA-UPDATE message belongs exceeds the area of the cell to which the second user terminal belongs Transmitted by the second user terminal. In the embodiment of the present invention, the user terminal is configured to carry the initial identifier of the user in the sent CELL-UPDATE or URA-UPDATE message, and the corresponding user terminal is uniquely determined by using the initial identifier of the user, so that the sending may be determined according to the initial identifier of the user. The user terminal of the CELL-UPDATE or URA-UPDATE message, so as to perform corresponding message discarding processing or maintain RRC connection processing for the user terminal, and avoid releasing resources occupied by the UE that is normally connected due to the user terminal identification error. , causing the occurrence of dropped calls in normal UEs;

In addition, by carrying the U-RNTI in the CELL-UPDATE or URA-UPDATE message and preventing the same U-RNTI from being reused by the preset waiting time, the RNC receiving the CELL-UPDATE or URA-UPDATE message can Correctly identifying the UE; determining the area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, and comparing with the area range of the cell in which the UE that has established the RRC connection belongs, if the CELL-UPDATE or URA-UPDATE message belongs to When the area of the cell exceeds the range of the area to which the second user terminal belongs, the CELL-UPDATE or URA-UPDATE cancellation is determined. The information is sent by another user terminal, but not by the current UE, thereby realizing the identification of the UE. DRAWINGS

FIG. 1 is a schematic diagram of a process for identifying a user in a scenario of cell update or URA update in the prior art;

2 is a schematic flowchart of a method for identifying a user terminal according to an embodiment of the present invention; FIG. 3 is a schematic diagram of a process for identifying a user terminal in a cell update or URA update scenario according to an embodiment of the present invention;

FIG. 4 is a schematic flowchart of another method for identifying a user terminal according to an embodiment of the present invention; FIG. 5 is a schematic flowchart of another method for identifying a user terminal according to an embodiment of the present invention; FIG. 6 is still another user according to an embodiment of the present invention; FIG. 7 is a schematic structural diagram of a device for identifying a user terminal according to an embodiment of the present invention; FIG. 8 is a schematic structural diagram of another device for identifying a user terminal according to an embodiment of the present invention; A schematic diagram of the structure of the identification device of the user terminal provided by the embodiment of the invention; FIG. 10 is a schematic structural diagram of another apparatus for identifying the user terminal according to the embodiment of the present invention. detailed description

The technical solutions in the embodiments of the present invention will be described in detail with reference to the accompanying drawings. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without the creative work are all within the scope of the present invention.

In the prior art, the UE carries U when sending CELL-UPDATE or URA-UPDATE.

-RNTI, and the RNC only identifies the corresponding UE according to the U-RNTI carried in the CELL-UPDATE or URA-UPDATE. As shown in FIG. 1 , the process for identifying a user in a cell update or URA update scenario in the prior art includes the following steps:

Step 101: When the UE 1 is in the CELL1 cell and is in the CELL-PCH or URA-PCH state, the RNC needs to actively release the RRC connection with the UE 1, and sends a paging message to the UE1. At this time, the UE 1 uses the URNTI 1 to identify Self

Step 102, the RNC sends an RRC CONNECTION RELEASE message to the UE 1;

UE1 does not receive the paging message sent by the RNC at this time, nor does it send the cell update to the RNC. Therefore, even if the RNC sends an RRC Connection Release message to the UE 1, the UE1 cannot receive the RRC Connection Release message;

Step 103: UE 1 is still in the RRC connection state because it does not receive the RRC connection release message, and still uses URNTI 1 to identify itself.

Step 104: The RNC side releases the resources occupied by the UE 1, including the URNTI previously allocated to the UE1.

1;

Step 105: The UE 2 sends an RRC CONNECTION REQUEST message to the RNC in the CELL2 cell, and prepares to establish an access service with the RNC.

Step 106: After receiving the RRC CONNECTION REQUEST message of the UE2, the RNC allocates the URNTI 1 originally allocated to the UE 1 to the UE 2 in the CELL2 cell, and notifies the message through the RRC CONNECTION SETUP message. After receiving the RRC CONNECTION SETUP message, the UE 2 knows that the RNC has assigned the URNTI 1 to itself and starts to identify itself with the URNTI 1; after that, the UE 2 sends the RRC CONNECTION SETUP COMPLETE (the RRC connection establishment is completed). ) message to the RNC;

Step 108: UE 1 is still in the CELL-PCH, URA-PCH state, and moves from the CELL 1 cell to the CELL3 cell. At this time, UE 1 sends a CELL UPDATE or URA UPDATE message to the RNC, and on CELL UPDATE or URA UPDATE. The message carries URNTI 1;

Step 109: The RNC only identifies the user according to the URNTI. Since the URNTI 1 has been allocated to the UE 2 before, the URNTI 1 is considered to represent the UE 2. In this case, the CELL UPDATE or URA UPDATE message sent by the UE 1 is incorrect. It is confirmed that it is sent by the UE 2, and it is considered that the UE 2 has moved from the CELL2 cell to the CELL3 cell, thereby performing cell change;

Step 110: The RNC sends a CELL UPDATE CONFIRMATION or a URA UPDATE CONFIRMATION in the CELL3 cell.

The UPDATE CONFIRMATION is generated according to the encryption mode of UE2, and the encryption parameters of UE1 and UE2 are inconsistent. Therefore, UE1 cannot recognize CELL UPDATE CONFIRMATION and URA UPDATE CONFIRMATION, and cannot report to RNC. The response message causes the process to fail. At this time, the RNC incorrectly releases the resources occupied by the UE 2, causing the UE2 to drop the call.

In order to avoid the above-mentioned result of the RNC identifying the UE error during the CELL-UPDATE or URA-UPDATE process, the embodiment of the present invention provides a method for identifying the user terminal, as shown in FIG. 2, including the following processing steps:

Step 201: When the first user terminal in a cell is in a CELL-PCH or URA-PCH state, release an RRC connection between the RNC and the first user terminal.

Step 202: The RNC receives an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and allocates a first U-RNTI originally allocated to the first user terminal to the second user. Terminal

Step 203: The RNC receives a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI and the first UE initial identifier that identifies the first user terminal.

In this step, when transmitting a CELL-UPDATE or URA-UPDATE message, any user terminal carries the U-RNTI, and carries the initial identifier of the UE that identifies the user terminal, and the initial identifier of the UE may be uniquely corresponding to the corresponding UE. Relationship. Therefore, the corresponding UE can be uniquely determined by the initial identifier of the UE;

Step 204: Determine, according to the initial identifier of the first UE, that the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal, instead of the second user terminal. In this step, according to CELL-UPDATE Or the first UE initial identifier carried in the URA-UPDATE message may uniquely determine that the CELL-UPDATE or URA-UPDATE message is from the first user terminal, and not only the U-RNTI, the UE's recognition result is incorrect. It is determined to be the first user terminal.

Since the RRC connection between the RNC and the first user terminal has been released in the above step 201, after the user terminal transmitting the CELL-UPDATE or URA-UPDATE message is identified, the CELL-UPDATE or URA-UPDATE message is sent. When the first user terminal is used, the RNC discards the CELL-UPDATE or URA-UPDATE message and maintains an RRC connection with the second user terminal.

With this embodiment, it is possible to avoid RNC during CELL-UPDATE or URA-UPDATE The result of the erroneous recognition of the UE, thereby avoiding the occurrence of a call drop phenomenon in the normal UE due to the erroneous release of the resources occupied by the UE that is normally connected.

In order to facilitate a full understanding of the technical solutions of the embodiments of the present invention, the technical solutions in the foregoing embodiments are clearly and completely described below through a specific cell update or URA update scenario.

As shown in FIG. 3, the process for identifying a user terminal in a cell update or URA update scenario in the embodiment of the present invention includes the following steps:

Step 301: When the UE 1 is in the CELL1 cell and is in the CELL-PCH, URA-PCH state, the RNC actively releases the RRC connection with the UE 1, and sends a paging message to the UE1;

At this time, UE 1 uses URNTI 1 to identify itself;

Step 302, the RNC sends an RRC connection release message to the UE 1;

UE1 does not receive the paging message sent by the RNC at this time, and does not send the cell update message to the RNC; therefore, even if the RNC sends the RRC connection release message to the UE 1, the UE1 cannot receive the RRC connection release message;

Step 303: UE 1 is still in the RRC connection state because it does not receive the RRC connection release message, and still uses URNTI 1 to identify itself.

Step 304: The RNC side releases the resources occupied by the UE 1, including the URNTI previously allocated to the UE1.

1;

Step 305: The UE 2 sends an RRC CONNECTION REQUEST to the CELL2 cell to prepare an access service with the RNC.

Step 306: After receiving the RRC CONNECTION REQUEST message of the UE2, the RNC allocates the URNTI 1 originally allocated to the UE 1 to the UE 2 in the CELL2 cell, and notifies the UE 2 through the RRC CONNECTION SETUP message;

Step 307: After receiving the RRC CONNECTION SETUP message, the UE 2 knows that the RNC allocates the URNTI 1 to itself, and starts to identify itself by using the URNTI 1; after that, the UE 2 sends an RRC CONNECTION SETUP COMPLETE message to the RNC;

Step 308: UE 1 is still in the CELL-PCH, URA-PCH state, and moves from the CELL 1 cell to the CELL3 cell. At this time, UE 1 sends a CELL UPDATE or URA UPDATE message to the RNC, and on CELL UPDATE or URA UPDATE. The message carries the URNTI 1 and the INITIAL UE1 ID (the first UE initial identifier); Step 309: The RNC not only identifies the user according to the URNTI, but also needs to identify the user according to the first UE initial identifier. When it is determined that the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal, instead of the second user terminal, When sending, discard the CELL-UPDATE or URA-UPDATE message;

In the above steps, since the first UE initial identifier can uniquely identify the user terminal, it is avoided that an identification conflict occurs with other user terminals. When the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal according to the first UE initial identifier, instead of being sent by the second user terminal, since the RNC and the first user terminal have been released The RRC is connected. Therefore, the RNC discards the CELL-UPDATE or URA-UPDATE message and maintains an RRC connection with the second user terminal. Therefore, the phenomenon that the RNC erroneously releases the resources occupied by the UE 2 and causes the UE2 to drop the call is avoided. In another embodiment of the method for identifying a user terminal provided by the present invention, as shown in FIG. 4, the following steps are included:

Step 401: When the first user terminal in a cell is in a CELL-PCH or URA-PCH state, release an RRC connection between the RNC and the first user terminal.

Step 402: The RNC receives, sent by a second user terminal in another cell within the scope of the jurisdiction.

An RRC connection request message, after the preset waiting time, the first U-RNTI originally allocated to the first user terminal is allocated to the second user terminal;

In this step, when the RNC receives the second user terminal in another cell within the jurisdiction,

After the RRC connection request message, the first U-RNTI is not directly allocated to the second user terminal, but the first U-RNTI is allocated to the second after waiting for a certain time according to a preset setting. User terminal. Through this step, the probability of U-RNTI reuse can be reduced to some extent;

Step 403: During the waiting time, the RNC receives a CELL-UPDATE or

a URA-UPDATE message, the CELL-UPDATE or URA-UPDATE message carrying the first U-RNTI;

Step 404: Determine, according to the first U-RNTI, that the CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal. Within the preset waiting time, since the first U-RNTI is not allocated to the second user terminal, the first U-RNTI cannot be used to identify the second user terminal. Therefore, even if the RNC receives the CELL-UPDATE or URA-UPDATE message carrying the first U-RNTI, it can only be determined that the CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal.

The preset time is not specifically limited in this embodiment, and a specific time setting may be performed by a person skilled in the art according to an actual application scenario.

Since the RNC side can determine that the CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal, the RNC discards the CELL-UPDATE or URA-UPDATE message, and remains with the second user terminal. RRC connection.

In the embodiment of the present invention, by carrying in a CELL-UPDATE or URA-UPDATE message

U-RNTI, and by waiting a preset time, to prevent the same U-RNTI is recycled, so that the RNC receives a CELL-UPDATE or URA-UPDATE message is able to correctly identify the UE further ¹ J, to avoid the user terminal identifier If the error occurs, the resources occupied by the UE that is connected to the normal UE are released, and the phenomenon of dropped calls occurs in the normal UE. In another embodiment of the method for identifying a user terminal provided by the present invention, as shown in FIG. 5, the method includes: Step 501: When a first user terminal in a cell is in a CELL-PCH or URA-PCH state, release An RNC is connected to the RRC of the first user terminal;

Step 502: The RNC receives an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and allocates a first U-RNTI originally allocated to the first user terminal to the second user. Determining, by the terminal, a range of areas to which the cell where the second user terminal belongs;

In this step, after the RNC receives the RRC connection request message sent by the second user terminal in another cell in the jurisdiction, the first U-RNTI originally allocated to the first user terminal is directly allocated to the first The second user terminal is different from the previous embodiment in that the RNC needs to determine the area of the area to which the second user terminal belongs.

For a WCDMA (Wideband Code Division Multiple Access) network, the area to which the cell belongs may be determined according to LA (Location Area), RA (Routing Area), or URA; for TD-SCDMA (Time Division-Synchronous Code Division Multiple Access) network, the area to which the cell belongs The circumference can be determined according to LA, RA or SA (Service Area). In this regard, this embodiment will not be described again.

Step 503: The RNC receives a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI;

Step 504: Acquire an area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, when the area of the cell to which the CELL-UPDATE or URA-UPDATE message belongs exceeds the area of the cell to which the second user terminal belongs. When it is determined that the CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal.

In this step, when the area of the cell to which the CELL-UPDATE or URA-UPDATE message belongs exceeds the area of the cell to which the second user terminal belongs, it is determined that the CELL-UPDATE or URA-UPDATE message is The user terminal transmits, but is not sent by the second user terminal. Therefore, the RNC discards the CELL-UPDATE or URA-UPDATE message and maintains an RRC connection with the second user terminal.

In the embodiment of the present invention, by determining the area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, and comparing with the area range of the cell in which the UE that has established the RRC connection belongs, if the CELL-UPDATE or URA-UPDATE message belongs to When the area of the cell is beyond the range of the cell to which the second user terminal belongs, it is determined that the CELL-UPDATE or URA-UPDATE message is sent by another user terminal, instead of being sent by the current UE, thereby implementing the UE. Identification. In another embodiment of the method for identifying a user terminal provided by the present invention, as shown in FIG. 6, the method includes: Step 601: When a first user terminal in a cell is in a CELL-PCH or URA-PCH state, release An RNC is connected to the RRC of the first user terminal;

Step 602: The RNC receives an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and after the preset waiting time, allocates the first U-RNTI originally allocated to the first user terminal. Assigning to the second user terminal, determining a range of areas to which the cell in which the second user terminal belongs;

Step 603: The RNC receives a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI; Step 604: Acquire an area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, when the area of the cell to which the CELL-UPDATE or URA-UPDATE message belongs exceeds the area of the cell to which the second user terminal belongs. When it is determined that the CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal.

After determining that the CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal, the RNC discards the CELL-UPDATE or URA-UPDATE message, and maintains an RRC connection with the second user terminal. .

The embodiment of the present invention combines the technical solutions of the above two embodiments, and carries the U-RNTI in the CELL-UPDATE or URA-UPDATE message, and prevents the same U-RNTI from being reused by using the preset waiting time. By determining the area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, and comparing the area range of the cell to which the UE that has established the RRC connection belongs, if the area of the cell to which the CELL-UPDATE or URA-UPDATE message belongs exceeds When the area of the cell to which the second user terminal belongs is located, it is determined that the CELL-UPDATE or URA-UPDATE message is sent by another user terminal, and is not sent by the current UE, thereby realizing the identification of the UE. Corresponding to the foregoing method embodiments, the embodiment of the present invention further provides an identification device for the user terminal. As shown in FIG. 7, the device may include:

The connection release control module 701 is configured to release an RRC connection between the RNC and the first user terminal when the first user terminal in a cell is in a CELL-PCH or URA-PCH state;

The U-RNTI allocation module 702 is configured to receive, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, to allocate the first U-RNTI originally allocated to the first user terminal. Giving the second user terminal;

An update message receiving module 703, configured to receive, by the RNC, a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI and the first identifier of the first user terminal a UE initial identification;

The identifier determining module 704 is configured to determine, according to the first UE initial identifier, that the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal instead of the second user terminal. When the recognition judging module 704 determines that the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal, instead of being sent by the second user terminal, triggering an update message discarding mode

The URA-UPDATE message maintains an RRC connection with the second user terminal. As shown in FIG. 8, another identification device of the user terminal may include:

a connection release control module 801, configured to release an RRC connection between the RNC and the first user terminal when the first user terminal in a cell is in a CELL-PCH or URA-PCH state; a time preset module 802, configured to: Presetting a waiting time for assigning the first U-RNTI originally allocated to the first user terminal to the second user terminal;

The U-RNTI allocation module 803 is configured to receive, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and after the preset waiting time, assign the original to the first user terminal. The first U-RNTI is allocated to the second user terminal;

The update message receiving module 804 is configured to: when the waiting time, the RNC receives a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI;

The identifier determining module 805 is configured to determine, according to the first U-RNTI, that the CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal.

When the recognition judging module 805 determines that the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal, instead of being sent by the second user terminal, the update message discarding module 806 is triggered, and the update message discarding module 806 is used by the RNC to discard the CELL-UPDATE or URA-UPDATE message, and maintain an RRC connection with the second user terminal. As shown in FIG. 9, another identification device of the user terminal may include:

The connection release control module 901 is configured to: when the first user terminal in a certain cell is in

In the CELL-PCH or URA-PCH state, releasing the RRC connection of the RNC to the first user terminal;

a U-RNTI allocation module 902, configured to receive, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, to allocate the first U-RNTI originally allocated to the first user terminal Giving the second user terminal; The area naming module 903 of the cell is configured to determine a range of areas to which the cell where the second user terminal belongs;

An update message receiving module 904, configured to receive, by the RNC, a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI;

The area-to-area comparison module 905 is configured to obtain an area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, and compare the area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, and the second user terminal. The area to which the cell belongs;

The determining and determining module 906 is configured to determine the CELL-UPDATE or URA-UPDATE message when the area of the cell to which the CELL-UPDATE or URA-UPDATE message belongs is beyond the range of the area to which the second user terminal belongs. Not sent by the second user terminal.

When the recognition judging module 906 determines that the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal, instead of being sent by the second user terminal, the update message discarding mode is triggered.

The URA-UPDATE message maintains an RRC connection with the second user terminal. As shown in FIG. 10, another identification device of the user terminal may include:

The connection release control module 1001 is configured to release an RRC connection between the RNC and the first user terminal when the first user terminal in a certain cell is in a CELL-PCH or URA-PCH state; and a time preset module 1002, configured to: Presetting a waiting time for assigning the first U-RNTI originally allocated to the first user terminal to the second user terminal;

The U-RNTI allocation module 1003 is configured to receive, by the RNC, an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and after the preset waiting time, assign the original to the first user terminal. The first U-RNTI is allocated to the second user terminal;

a cell-to-area range determining module 1004, configured to determine a range of areas to which the cell in which the second user terminal belongs;

An update message receiving module 1005, configured to receive, by the RNC, a CELL-UPDATE or URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the First U-RNTI;

The area-to-area comparison module 1006 is configured to obtain an area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, and compare the area range of the cell to which the CELL-UPDATE or URA-UPDATE message belongs, and the second user terminal. The area to which the cell belongs;

The determining and determining module 1007 is configured to determine the CELL-UPDATE or URA-UPDATE message when the area of the cell to which the CELL-UPDATE or URA-UPDATE message belongs exceeds the range of the area to which the second user terminal belongs. Not sent by the second user terminal.

When the identification judgment module 1007 determines that the CELL-UPDATE or URA-UPDATE message is sent by the first user terminal, instead of being sent by the second user terminal, the update message discarding module 1008 is triggered, and the update message discarding module 1008 is used by the RNC to discard the CELL-UPDATE or URA-UPDATE message, and maintain an RRC connection with the second user terminal. For the device embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment. The device embodiments described above are merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, ie may be located One place, or it can be distributed to multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the embodiments of the invention. . Therefore, the present embodiments of the invention are not to be limited to the embodiments shown herein, but are to be accorded to the broadest scope of the principles and novel features disclosed herein.

Claims

Rights request

A method for identifying a user terminal, comprising:

The RNC receives an RRC connection request message sent by a second user terminal in another cell in the jurisdiction, and allocates a first U-RNTI originally allocated to the first user terminal to the second user terminal;

The method for identifying a user terminal according to claim 1, wherein the method further comprises:

The RNC discards the CELL-UPDATE or URA-UPDATE message and maintains an RRC connection with the second user terminal.

3. A method for identifying a user terminal, comprising:

The method for identifying a user terminal according to claim 3, wherein the method further comprises:

The RNC discards the CELL-UPDATE or URA-UPDATE message, and keeps RRC connection of the second user terminal.

A method for identifying a user terminal, comprising:

The RNC receives a CELL-UPDATE or URA-UPDATE message, and the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI;

The method for identifying a user terminal according to claim 5, wherein the method further comprises:

7. A method for identifying a user terminal, comprising:

The method for identifying a user terminal according to claim 7, wherein the method further comprises:

9. A device for identifying a user terminal, comprising:

The device for identifying a user terminal according to claim 9, further comprising: an update message discarding module, configured to: the RNC discard the CELL-UPDATE or

The URA-UPDATE message maintains an RRC connection with the second user terminal.

11. A device for identifying a user terminal, comprising:

a time preset module, configured to preset a waiting time for assigning a first U-RNTI originally allocated to the first user terminal to the second user terminal;

An update message receiving module, configured to receive, by the RNC, a CELL-UPDATE or a URA-UPDATE message, where the CELL-UPDATE or URA-UPDATE message carries the first U-RNTI; The identifier determining module is configured to determine, according to the first U-RNTI, that the CELL-UPDATE or URA-UPDATE message is not sent by the second user terminal.

The apparatus for identifying a user terminal according to claim 11, further comprising: an update message discarding module, configured to: the RNC discard the CELL-UPDATE or URA-UPDATE message, and keep RRC connection of the second user terminal.

13. A device for identifying a user terminal, comprising:

The device for identifying a user terminal according to claim 13, further comprising: an update message discarding module, configured to: the RNC discard the CELL-UPDATE or URA-UPDATE message, and keep RRC connection of the second user terminal.

15. A device for identifying a user terminal, comprising:

The device for identifying a user terminal according to claim 15, further comprising: an update message discarding module, configured to: the RNC discard the CELL-UPDATE or URA-UPDATE message, and keep RRC connection of the second user terminal.