WO2020063847A1

WO2020063847A1 - Link release method and device, terminal and second network entity

Info

Publication number: WO2020063847A1
Application number: PCT/CN2019/108507
Authority: WO
Inventors: 张大钧; 刘佳敏
Original assignee: 电信科学技术研究院有限公司
Priority date: 2018-09-28
Filing date: 2019-09-27
Publication date: 2020-04-02
Also published as: CN110972223A; CN116156589A

Abstract

Provided by the present disclosure are a link release method and device, a terminal and a second network entity, wherein the link release method comprises: releasing a first data transmission link and the wireless resource configuration of a first network entity side after receiving an explicit or implicit release notification from second network entities while maintaining the first data transmission link between first network entities as well as a second data transmission link between the second network entities.

Description

Link release method and device, terminal and second network entity

Cross-reference to related applications

This application claims the priority of Chinese Patent Application No. 201811142464.0 filed in China on September 28, 2018, the entire contents of which are hereby incorporated by reference.

Technical field

The present disclosure relates to the field of communication technologies, and in particular, to a link release method and device, a terminal, and a second network entity.

Background technique

With the continuous evolution of the network, the inter-node mobile event under the traditional network architecture cannot meet the higher requirements for mobile performance. For example, maintaining a data interruption of 0ms during the handover process has become a basic requirement for the development of next-generation networks; while in current common mobile scenarios (such as the dual-connected network scenario shown in Figure 1), the signal from the terminal UE moving to two network entities After the overlap is covered, the network will trigger a mobility event. In this regard, the traditional handover process is to interrupt the data transmission on the original side and continue the service transmission after accessing the target node, which will cause a large data interruption. .

In response to the above problems, an improved MBB (Make Before Break) process is provided in the existing solution. The improved handover process is: After receiving the handover command, the UE still receives data transmission from the source network entity, and then performs the During the uplink access process, data transmission with the source side will be interrupted. At the same time, the wireless configuration on the target side will be applied and data transmission to the target side will be started. Although this process will reduce a certain interruption delay, it will still not reach the 0ms interrupt Delay requirements.

That is, it is implemented according to the related technology. At a certain moment of handover, the UE can only keep data transmission and reception with a certain network entity. In this way, when the switching process from one network entity to another network entity is performed, the data of the air interface will be interrupted, and the 0ms interruption delay requirement cannot be met, thereby affecting the user experience.

Summary of the Invention

An object of the present disclosure is to provide a link release method and device, a terminal, and a second network entity, and solve the problem of interruption delay when the terminal switches network entities in the related art.

In order to solve the above technical problems, an embodiment of the present disclosure provides a link release method, which is applied to a terminal and includes:

Under the condition that the first data transmission link with the first network entity and the second data transmission link with the second network entity are maintained, the explicit or implicit data received by the second network entity is received. After the release notification, the first data transmission link and the radio resource configuration on the first network entity side are released.

Optionally, when the first network entity and the second network entity are slave network entities, the releasing the first data transmission link and the wireless resource configuration on the first network entity side includes:

Release the first data transmission link and the slave cell group configuration on the first network entity side.

Optionally, when the first network entity and the second network entity are both primary network entities, the releasing the first data transmission link and the radio resource configuration on the first network entity side includes:

Release the first data transmission link and the primary cell group configuration on the first network entity side.

Optionally, maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity includes:

The data bearer DRB between each terminal and the base station or the signaling bearer SRB between the terminal and the base station, while maintaining two packet data convergence protocols PDCP encryption or decryption sub-functions, two wireless link layer control protocols RLC layer chain Channel, two media access control MAC layer links and physical layer links.

The data bearer DRB between each terminal and the base station or the signalling bearer SRB between the terminal and the base station, while maintaining a packet data convergence protocol PDCP entity, two radio link layer control protocol RLC layer links, two media Access control MAC layer link and physical layer link.

Optionally, the release notification includes any one of the following information sent by the second network entity to the terminal:

The first downlink packet data convergence protocol PDCP packet;

The first physical downlink shared channel PDSCH or physical downlink control channel PDCCH channel transmission;

The first hybrid automatic retransmission of the physical uplink shared channel PUSCH channel requests HARQ confirmation or the radio link layer control protocol responds to RLC ACK;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.

An embodiment of the present disclosure further provides a link release method, which is applied to a second network entity and includes:

When the terminal maintains the first data transmission link with the first network entity and the second data transmission link with the second network entity, sending to the terminal through the second data transmission link The release notification causes the terminal to release the first data transmission link and the radio resource configuration on the first network entity side.

Optionally, the sending a release notification to the terminal through the second data transmission link includes:

Sending a release notification to the terminal through the second data transmission link according to a downlink data transmission situation.

The first downlink packet data convergence protocol PDCP packet;

The first hybrid automatic retransmission of the physical uplink shared channel PUSCH channel requests HARQ confirmation or the radio link layer control protocol responds with RLC ACK;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.

An embodiment of the present disclosure further provides a terminal, including a memory, a processor, a transceiver, and a program stored on the memory and executable on the processor; when the processor executes the program, the following steps are implemented :

Under the condition that the first data transmission link with the first network entity and the second data transmission link with the second network entity are maintained, the transceiver sends the After the explicit or implicit release notification, the first data transmission link and the radio resource configuration on the first network entity side are released.

Optionally, when the first network entity and the second network entity are both slave network entities, the processor is specifically configured to:

Optionally, when the first network entity and the second network entity are both primary network entities, the processor is specifically configured to:

The data bearer DRB between each terminal and the base station or the signaling bearer SRB between the terminal and the base station, while maintaining two packet data convergence protocols PDCP encryption or decryption sub-functions, two wireless link layer control protocols RLC layer chain Channels, two media access control MAC layer links and physical layer links; or

The first downlink packet data convergence protocol PDCP packet;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.

An embodiment of the present disclosure further provides a second network entity, including a memory, a processor, a transceiver, and a program stored on the memory and executable on the processor. Implement the following steps:

When the terminal maintains the first data transmission link with the first network entity and the second data transmission link with the second network entity, the transceiver is used to pass the second data transmission link Sending a release notification to the terminal, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side.

Optionally, the processor is specifically configured to:

The first downlink packet data convergence protocol PDCP packet;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.

An embodiment of the present disclosure also provides a computer-readable storage medium having a program stored thereon, which is executed by a processor to implement the steps of the foregoing link release method.

An embodiment of the present disclosure further provides a link release device, which is applied to a terminal and includes:

A first release module, configured to receive the second network entity while maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity After the explicit or implicit release notification is sent, the first data transmission link and the radio resource configuration on the first network entity side are released.

Optionally, when the first network entity and the second network entity are both slave network entities, the first release module includes:

The first release submodule is configured to release the first data transmission link and the slave cell group configuration on the first network entity side.

Optionally, when the first network entity and the second network entity are both primary network entities, the first release module includes:

The second release sub-module is configured to release the first data transmission link and the primary cell group configuration on the first network entity side.

The data bearer DRB between each terminal and the base station or the signalling bearer SRB between the terminal and the base station, while maintaining two packet data convergence protocols PDCP encryption or decryption sub-functions, two wireless link layer control protocols RLC layer chain Channels, two media access control MAC layer links and physical layer links; or

The first downlink packet data convergence protocol PDCP packet;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.

An embodiment of the present disclosure further provides a link release device, which is applied to a second network entity and includes:

A first sending module, configured to pass through the second data transmission when the terminal maintains a first data transmission link with the first network entity and a second data transmission link with the second network entity The link sends a release notification to the terminal, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side.

Optionally, the first sending module includes:

A first sending submodule is configured to send a release notification to the terminal through the second data transmission link according to a downlink data transmission situation.

The first downlink packet data convergence protocol PDCP packet;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.

The beneficial effects of the above technical solutions of the present disclosure are as follows:

In the above solution, the link release method receives the first data transmission link with the first network entity and the second data transmission link with the second network entity while receiving the After the explicit or implicit release notification sent by the second network entity, release the first data transmission link and the radio resource configuration on the first network entity side; enable the UE to keep sending data with the two network entities Under the premise of receiving and receiving, the radio resource configuration of the entire source side can be released separately, thereby obtaining the performance requirement that the interruption delay in the handover process reaches 0ms, further improving the user experience.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a dual-connection network scenario in related technologies;

FIG. 2 is a first schematic flowchart of a link release method according to an embodiment of the present disclosure; FIG.

3 is a second schematic flowchart of a link release method according to an embodiment of the present disclosure;

4 is a first schematic flowchart of a specific implementation of a link release method according to an embodiment of the present disclosure;

5 is a second schematic flowchart of a specific implementation of a link release method according to an embodiment of the present disclosure;

FIG. 6 is a third schematic flowchart of a specific implementation of a link release method according to an embodiment of the present disclosure;

7 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

8 is a schematic structural diagram of a second network entity according to an embodiment of the present disclosure;

9 is a first schematic structural diagram of a link release device according to an embodiment of the present disclosure;

FIG. 10 is a second schematic structural diagram of a link release device according to an embodiment of the present disclosure.

detailed description

In order to make the technical problems, technical solutions, and advantages of the present disclosure clearer, the following detailed description will be made with reference to the accompanying drawings and specific embodiments.

The present disclosure addresses a problem of interruption delay when a terminal switches network entities in the prior art, and provides a link release method, which is applied to a terminal. As shown in FIG. 2, the method includes:

Step 21: Under the condition that the first data transmission link with the first network entity and the second data transmission link with the second network entity are maintained, the explicit data sent by the second network entity is received. Or after the implicit release notification, the first data transmission link and the radio resource configuration on the first network entity side are released.

The first network entity may specifically be a source network entity, and the second network entity may specifically be a target network entity, but is not limited thereto.

The link release method provided by the embodiment of the present disclosure is obtained by receiving a first data transmission link with a first network entity and a second data transmission link with a second network entity. After the explicit or implicit release notification sent by the second network entity, release the first data transmission link and the radio resource configuration on the first network entity side; enable the UE to keep data with the two network entities Under the premise of sending and receiving, the entire source-side wireless resource configuration can be released separately, thereby obtaining the performance requirement that the interruption delay in the handover process reaches 0ms, further improving the user experience.

Wherein, when the first network entity and the second network entity are both slave network entities, the releasing the first data transmission link and the wireless resource configuration on the first network entity side includes releasing the first network entity. The data transmission link and the slave cell group configuration on the first network entity side.

When the first network entity and the second network entity are both primary network entities, the releasing the first data transmission link and the radio resource configuration on the first network entity side includes: releasing the first data transmission The link and the primary cell group configuration on the first network entity side.

In the embodiment of the present disclosure, maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity may include: a data bearer between each terminal and the base station The DRB or the signaling between the terminal and the base station carries the SRB, while maintaining two packet data convergence protocols PDCP encryption or decryption sub-functions, two radio link layer control protocols RLC layer links, two media access control MAC layer chains And physical layer links.

It may also be that maintaining a first data transmission link with the first network entity and a second data transmission link with the second network entity includes: a data bearer DRB or terminal between each terminal and the base station Signaling between the base station and SRB, while maintaining a packet data convergence protocol PDCP entity (which can include PDCP encryption or decryption sub-functions), two radio link layer control protocols, RLC layer links, two media access control MACs Layer link and physical layer link.

Specifically, the release notification includes any one of the following information sent by the second network entity to the terminal: the first downlink packet data convergence protocol PDCP packet; the first physical downlink shared channel PDSCH or physical downlink Control channel PDCCH channel transmission; HARQ acknowledgement of the first physical uplink shared channel PUSCH channel; HARQ acknowledgement or radio link layer control protocol response RLC ACK; radio resource control RRC acknowledgement message; PDCP control frame; medium access control layer control Element MAC CE.

An embodiment of the present disclosure further provides a link release method, which is applied to a second network entity. As shown in FIG. 3, the method includes:

Step 31: In a case where the terminal maintains the first data transmission link with the first network entity and the second data transmission link with the second network entity, the terminal transmits the data transmission link to the network through the second data transmission link. The terminal sends a release notification, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side.

The method for releasing a link provided in the embodiment of the present disclosure is implemented by using a method in which a terminal maintains a first data transmission link with a first network entity and a second data transmission link with a second network entity. The second data transmission link sends a release notification to the terminal, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side; it enables the UE to maintain communication with the two network entities. Under the premise of sending and receiving data, the entire source-side radio resource configuration can be released separately, so as to obtain the performance requirement that the interruption delay in the handover process reaches 0ms, further improving the user experience.

Wherein, the sending a release notification to the terminal through the second data transmission link includes: sending a release notification to the terminal through the second data transmission link according to a downlink data transmission situation.

The link release method provided by the embodiment of the present disclosure will be further described with reference to multiple sides such as a terminal and a second network entity. The first network entity takes a source network entity as an example, and the second network entity takes a target network entity as an example.

In view of the above technical problems, an embodiment of the present disclosure provides a link release method (specifically, an optimization method for releasing a source-side link during a handover), which will help achieve the performance requirement of the interruption delay in the handover process to reach 0ms. . The solutions provided by the embodiments of the present disclosure mainly involve the following two situations:

The first case (switching between two primary network entities, such as switching between two primary base stations):

During the 0ms handover process, if the target network entity receives the 0ms handover instruction from the source network entity (ie, the above-mentioned link switch request) and also receives an RRC (Radio Resource Control) reconfiguration complete message from the UE (ie, the above After the access success indication), if there is a pending downlink PDCP (packet data convergence protocol) packet (data processed with a new security context encryption or integrity protection) or control frame in the buffer, it will pass the new chain Way to UE.

At the same time, the target network entity may explicitly or implicitly notify the UE according to the downlink data transmission situation, the target network entity and the UE complete the data transmission, and the UE is expected to release the data connection between the source network entity and the UE.

During the 0ms handover process, if the UE receives the 0ms handover instruction (that is, the above link handover instruction), it can immediately configure the MCG (Master Cell Group) configuration on the target side so that each DRB (between the terminal and the base station) is configured. Data bearer) bearer or SRB (signaling bearer between terminal and base station) bearers, while maintaining two PDCP encryption or decryption sub-functions, two RLC layer links, two MAC layer links, and two physical layers link. Optionally, one PDCP function complete entity and two RLC layer links, two MAC layer links, and two physical layer links are maintained.

If the UE receives a release notification from the target network entity, such as: the first downlink PDCP packet, the first PDSCH (physical downlink shared channel) or PDCCH (physical downlink control channel) channel transmission, and the first PUSCH (physical uplink Shared channel) channel (such as: Radio Resource Control RRC reconfiguration message) HARQ (Hybrid Automatic Repeat Request) acknowledgement or RLC ACK (radio link layer control protocol response), RRC acknowledgement message, PDCP control frame or MAC CE (MAC control element, a media access control layer control element), explicitly instructs the target network entity to complete data transmission with the UE, the UE will stop the uplink transmission and downlink reception between the source network entity and the UE, and begin to release the entire source-side MCG configuration For example, release the source-side MCG MAC (primary cell group media access control layer), radio link layer RLC, and PDCP encryption or decryption sub-function entity. Perform the reconstruction process of the PDCP layer.

The second case (switching between two slave network entities, such as switching between two slave base stations):

For LTE DC (LTE dual connectivity) or EN-DC (E-UTRA-NR dual connectivity: evolved universal terrestrial wireless access 5G dual connectivity) or MR-DC (Multi-RAT dual connectivity) Wireless standard dual connection) or NR-NR DC (NR-NR dual connectivity), during the 0ms handover of SCG (Secondary Cell Group), if the target receives from the network entity from the After the SCG 0ms handover instruction of the target master network entity (that is, the above-mentioned master network entity corresponding to the source slave network entity) and the access success indication from the UE is received, optionally, the configuration from the target master network entity is received. Completion message (refers to the message transmitted on the interface between the master network entity and the slave network entity, not the RRC reconfiguration message of the air interface), if there is a pending downlink PDCP packet in the buffer (encrypted with a new security context or The integrity protection processing data) or control frame will be sent to the UE through the new link.

At the same time, the target slave network entity can explicitly or implicitly notify the UE according to the downlink data transmission situation. The target slave network entity and the UE complete data transmission. It is expected that the UE releases the data connection between the source slave network entity and the UE.

During the SCG 0ms handover process, if the UE receives the SCG 0ms handover instruction (that is, the above link handover instruction), it can immediately configure the SCG configuration on the target side so that each DRB bearer or SRB bearer, while maintaining two PDCP encryption or Decrypt sub-functions, two RLC layer links, two MAC layer links, and two physical layer links. Optionally, one PDCP function complete entity and two RLC layer links, two MAC layer links, and two physical layer links are maintained.

If the UE receives a release notification from the target slave network entity, such as: the first downlink PDCP packet, the first PDSCH or PDCCH channel transmission, the HARQ acknowledgement or RLC ACK, RRC acknowledgement message, PDCP control of the first PUSCH channel The frame or MAC CE explicitly instructs the target to complete data transmission from the network entity and the UE. The UE will stop the uplink transmission and downlink reception of the source from the network entity and the UE, and begin to release the entire source-side SCG configuration, such as releasing the source. Side SCG MAC (from the cell group media access control layer), RLC, and PDCP encryption or decryption sub-functional entities. Perform the reconstruction process of the PDCP layer.

The solutions provided by the embodiments of the present disclosure are exemplified below.

Example 1: Source link release mechanism during 0ms handover between eNBs (4G base stations)

As shown in FIG. 4, steps 41 to 45: the original network entity (eNB) and the UE always maintain the original data transmission link; the target network entity (eNB) receives a 0ms handover instruction from the source network entity (eNB) And after receiving the RRC reconfiguration complete message from the UE, if there is a pending downlink PDCP data packet (data processed with new security context encryption or integrity protection) or control frame in the buffer, it will pass the new The link is sent to the UE.

Steps 46 to 47: The UE and two network entities (eNBs) maintain data transmission and reception.

Step 48: The target network entity (eNB) will explicitly or implicitly notify the UE according to the downlink data transmission situation. The target network entity (eNB) and the UE have completed data transmission, and the UE is expected to release the connection between the source network entity (eNB) and the UE. Data connection;

Step 49: The UE receives a release notification from the target network entity (eNB), such as: the first downlink PDCP packet, the first PDSCH or PDCCH channel transmission, and the first PUSCH channel (such as an RRC reconfiguration message). HARQ acknowledgment or RLC ACK, RRC acknowledgment message, PDCP control frame or MAC CE (explicitly instructs the target network entity (eNB) to complete data transmission with the UE) will stop the uplink transmission between the source network entity (eNB) and the UE and Downlink receives and starts to release the entire MCG configuration on the source side, such as releasing the MCG MAC, RLC, and PDCP encryption or decryption sub-function entities on the source side. Perform the reconstruction process of the PDCP layer.

Step 410: The UE only maintains data transmission and reception with the target network entity (eNB).

As shown in Figure 4, including:

Step 41: The source network entity (Source eNB) sends a handover request HO request (0ms interruption indicator, 0ms interrupt indicator) to the target network entity (Target eNB);

Step 42: the target network entity (Target eNB) feeds back the handover request response HO request ACK to the source network entity (Source eNB);

Step 43: The source network entity (Source eNB) sends a handover indication (HO with 0ms interruption indicator) to the UE;

Step 44: The UE accesses the target network entity (Target eNB) according to the handover instruction, that is, the access target;

Step 45: The UE sends an RRC reconfiguration complete message (RRC Connection Reconfiguration Complete) to the target network entity (Target eNB);

Step 46: Send and receive data (User data) between the UE and the source network entity (Source eNB).

Step 47: Maintain transmission and reception of data (User data) between the UE and the target network entity (Target eNB);

Step 48: the target network entity (Target eNB) sends an explicit indicator to the UE;

Step 49: The UE stops uplink transmission and downlink reception with the source network entity (Source eNB) (Stop data transmisson / reception);

Step 410: The UE only maintains sending and receiving of data (User data) with the target network entity (Target eNB).

Example 2: In the case of LTE DC, or EN-DC or MR-DC or NR-NR DC, the source link of the SCG 0ms switching process between SN (5G slave base station) or SeNB (4G slave base station) and SN or SeNB is released mechanism

As shown in FIG. 5, steps 51 to 56: The original data transmission link is always maintained between the source slave network entity and the UE; the target slave network entity receives the master network entity (the master network entity corresponding to the source slave network entity). After receiving a SCG 0ms handover instruction and receiving an access success indication from the UE, optionally, after receiving a configuration complete message from the main network entity, if there is a pending downlink PDCP packet in the buffer (using a new The data processed by the security context encryption or integrity protection) or control frame will be sent to the UE through the new link.

Steps 57 to 58: The UE and the two networks maintain data transmission and reception from the entity.

Step 59: The target slave network entity will explicitly or implicitly notify the UE according to the downlink data transmission situation. The target slave network entity and the UE complete data transmission. It is expected that the UE releases the data connection between the source slave network entity and the UE.

Step 510: The UE receives a release notification from the target slave network entity, such as: the first downlink PDCP packet, the first PDSCH or PDCCH channel transmission, the HARQ acknowledgement or RLC ACK, RRC acknowledgement message of the first PUSCH channel, PDCP control frame or MAC CE (explicitly instructs the target to complete data transmission from the network entity and the UE), will stop the source from sending and receiving upstream from the network entity and the UE, and start releasing the entire source-side SCG configuration, such as Release the source-side SCG MAC, RLC, and PDCP encryption or decryption sub-functional entities. Perform the reconstruction process of the PDCP layer.

Step 511: The UE only maintains data transmission and reception with the target slave network entity.

Among them, SN corresponds to the 5G main base station MN, and SeNB corresponds to the 4G main base station MeNB.

As shown in Figure 5, including:

Step 51: The master network entity MeNB / MN (MeNB or MN) sends an SCG addition request SCG Addition request (SCG0ms interruption indicator, SCG0ms interrupt indicator) to the target slave network entity TargetSeNB / SN (TargetSeNB or SN);

Step 52: The target feeds back the SCGG addition request response SCG from the network entity Target SeNB / SN to the main network entity MeNB / MN;

Step 53: The main network entity MeNB / MN sends an RRC reconfiguration indication (RRC Reconfiguration with SCG 0ms interruption indicator) to the UE;

Step 54: The UE accesses the target from the network entity Target SeNB / SN, that is, the access target according to the RRC reconfiguration instruction.

Step 55: The UE sends an RRC reconfiguration complete message (RRC Connection Reconfiguration Complete) to the main network entity MeNB / MN;

Step 56: The master network entity MeNB / MN sends a reconfiguration complete message (Reconfiguration Complete) to the target slave network entity Target SeNB / SN;

Step 57: The UE and the source maintain the sending and receiving of data (User data) between the network entity Source SeNB / SN (Source SeNB or SN);

Step 58: The UE and the target maintain transmission and reception of data (User data) between the network entity Target SeNB / SN;

Step 59: the target sends an explicit indicator to the UE from the network entity Target SeNB / SN;

Step 510: the UE stops uplink transmission and downlink reception (Stop data transmisson / reception) with the source from the network entity Source SeNB / SN;

Step 511: The UE only maintains transmission and reception of data (User data) with the target slave network entity Target SeNB / SN.

Example 3: Source link release mechanism for 0ms handover between NR gNB (5G base station) or ng-eNB (4G base station node that can access the core network 5GC)

As shown in FIG. 6, steps 61 to 65: the original network entity (NR, gNB or ng-eNB) and the UE maintain the original data transmission link; for the target network entity (NR, gNB or ng-eNB), After the source network entity (NR, gNB or ng-eNB) has a 0ms handover instruction and receives an RRC reconfiguration complete message from the UE, if there is a pending downlink PDCP packet in the buffer (using a new security context encryption or The integrity protection processing data) or control frame will be sent to the UE through the new link.

Steps 66 to 67: The UE and two network entities (NR, gNB or ng-eNB) maintain data transmission and reception.

Step 68: The target network entity (NR, gNB or ng-eNB) will explicitly or implicitly notify the UE according to the downlink data transmission situation. The target network entity (NR, gNB or ng-eNB) completes the data transmission with the UE, and expects the UE to release Data connection between the source network entity (NR, gNB or ng-eNB) and the UE;

Step 69: The UE receives a release notification from the target network entity (NR, gNB or ng-eNB), such as: the first downlink PDCP packet, the first PDSCH or PDCCH channel transmission, and the first PUSCH channel (such as: RRC HARQ acknowledgement or RLC ACK, RRC acknowledgement message, PDCP control frame, or MAC CE (explicitly instructing the target network entity (NR, gNB or ng-eNB) to complete data transmission with the UE), the source network entity ( NR (NBNB or ng-eNB) and the UE send uplink and downlink reception, and start to release the MCG configuration of the entire source side, for example, release the MCG MAC, RLC, and PDCP encryption or decryption sub-functional entities on the source side. Perform the reconstruction process of the PDCP layer.

Step 610: The UE only maintains data transmission and reception with the target network entity (NR, gNB or ng-eNB).

As shown in Figure 6, including:

Step 61: The source network entity Source gNB / nr-eNB (Source gNB or nr-eNB) sends a handover request to the target network entity Target gNB / nr-eNB (Target gNB or nr-eNB) HO request (0ms interruption indicator, 0ms interruption) Indicator);

Step 62: The target network entity Target gNB / nr-eNB feeds back a handover request response HO request to the source network entity Source gNB / nr-eNB;

Step 63: The source network entity Source gNB / nr-eNB sends a handover indication (HO with 0ms interruption indicator) to the UE;

Step 64: The UE accesses the target network entity Target gNB / nr-eNB according to the handover instruction, that is, the access target;

Step 65: The UE sends an RRC reconfiguration complete message (RRC Connection Reconfiguration Complete) to the target network entity Target gNB / nr-eNB.

Step 66: Send and receive data (User data) between the UE and the source network entity Source gNB / nr-eNB.

Step 67: Send and receive data (User data) between the UE and the target network entity Target NB / nr-eNB.

Step 68: the target network entity Target gNB / nr-eNB sends an explicit indicator explicit UE to the UE;

Step 69: The UE stops uplink transmission and downlink reception with the source network entity Source NB / nr-eNB (Stop data transmisson / reception);

Step 610: The UE only maintains sending and receiving of data (User data) with the target network entity Target NB / nr-eNB.

As can be seen from the above, the solution provided by the embodiment of the present disclosure mainly involves two parts:

In the first part, during the 0ms handover process, the UE needs to maintain data transmission and reception mechanisms with two network entities (eNB or NR, gNB or ng-eNB);

The target network entity (eNB or NR gNB or ng-eNB) will notify the UE explicitly or implicitly according to the downlink data transmission situation, and the target network entity (eNB or NR gNB or ng-eNB) completes the data transmission with the UE;

The UE receives display or implicit notification information from the target network entity (eNB or NR gNB or ng-eNB), and stops the uplink transmission and downlink reception between the source network entity (eNB or NR gNB or ng-eNB) and the UE. And start to release the entire MCG configuration on the source side;

In the second part, for LTE DC, EN-DC or MR-DC or NR-NR DC, the UE needs to maintain data transmission and reception with the two network slave entities (SeNB or SN);

For LTE DC, or EN-DC or MR-DC or NR-NR DC, the target slave network entity (SeNB or SN) will explicitly or implicitly notify the UE according to the downlink data transmission situation, and the target slave network entity (SeNB or SN) completes data transmission with the UE, and expects the UE to release the data connection between the source slave network entity (SeNB or SN) and the UE;

For LTE DC, or EN-DC or MR-DC or NR-NR DC, the UE receives display or implicit notification information from the target slave network entity (SeNB or SN), and stops the source slave network entity (SeNB or SN) from Uplink transmission and downlink reception between UEs, and start to release the entire source-side SCG configuration.

In summary, according to the related technology implementation, when the UE performs a handover process from one network entity to another, the data of the air interface will be interrupted, and the 0ms delay requirement cannot be met. The solution provided by the embodiment of the present disclosure enables the UE to independently release the entire source-side radio resource configuration under the premise of maintaining data transmission and reception with two network entities, thereby obtaining an air interface interruption delay of 0ms during the handover process. Performance requirements, further improving the user experience.

The terminal provided by the embodiment of the present disclosure passes the transceiver by maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity. After receiving the explicit or implicit release notification sent by the second network entity, the first data transmission link and the radio resource configuration on the first network entity side are released; enabling the UE to maintain communication with the two network entities Under the premise of sending and receiving data, the entire source-side radio resource configuration can be released separately, so as to obtain the performance requirement that the interruption delay in the handover process reaches 0ms, further improving the user experience.

Specifically, as shown in FIG. 7, the terminal provided by the embodiment of the present disclosure includes:

A processor 71; and a memory 73 connected to the processor 71 through a bus interface 72, where the memory 73 is configured to store programs and data used by the processor 71 when performing operations, and when the processor 71 calls and When the programs and data stored in the memory 73 are executed, the following processes are performed:

Under the condition that the first data transmission link with the first network entity and the second data transmission link with the second network entity are maintained, the second network entity sends the received data through the transceiver 74. After the explicit or implicit release notification is released, the first data transmission link and the radio resource configuration on the first network entity side are released.

The transceiver 74 is connected to the bus interface 72 and is used to receive and send data under the control of the processor 71.

It should be noted that in FIG. 7, the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 71 and various circuits of the memory represented by the memory 73 are linked together. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, so they are not described further herein. The bus interface provides an interface. The transceiver 74 may be multiple elements, including a transmitter and a transceiver, providing a unit for communicating with various other devices over a transmission medium. For different terminals, the user interface 75 may also be an interface capable of externally connecting internally required devices. The connected devices include, but are not limited to, a keypad, a display, a speaker, a microphone, a joystick, and the like. The processor 71 is responsible for managing the bus architecture and general processing, and the memory 73 may store data used by the processor 71 when performing operations.

Those skilled in the art can understand that all or part of the steps for implementing the above embodiments may be completed by hardware, or related hardware may be instructed by a program that includes instructions for performing part or all of the steps of the above method; and The program may be stored in a readable storage medium, and the storage medium may be any form of storage medium.

Wherein, when the first network entity and the second network entity are both slave network entities, the processor is specifically configured to release the first data transmission link and the slave cell group configuration on the side of the first network entity.

When the first network entity and the second network entity are both primary network entities, the processor is specifically configured to release the first data transmission link and the configuration of the primary cell group on the first network entity side.

It may also be that maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity includes: a data bearer DRB or a terminal between each terminal and the base station The signaling with the base station carries the SRB, while maintaining a packet data convergence protocol PDCP entity, two radio link layer control protocol RLC layer links, two medium access control MAC layer links, and physical layer links.

The above-mentioned implementation embodiments of the terminal-side link release method are all applicable to the embodiment of the terminal, and can also achieve the same technical effect.

When the terminal maintains the first data transmission link with the first network entity and the second data transmission link with the second network entity, the transceiver is used to pass through the second data transmission link Sending a release notification to the terminal, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side.

The second network entity provided in the embodiment of the present disclosure utilizes a situation in which the terminal maintains a first data transmission link with the first network entity and a second data transmission link with the second network entity. The transceiver sends a release notification to the terminal through the second data transmission link, so that the terminal releases the first data transmission link and the radio resource configuration of the first network entity side; the UE can keep the Under the premise of sending and receiving data with two network entities, the entire source-side radio resource configuration can be released separately, thereby obtaining the performance requirement that the interruption delay in the handover process reaches 0ms, further improving the user experience.

Specifically, as shown in FIG. 8, the second network entity in the embodiment of the present disclosure includes:

A processor 81; and a memory 83 connected to the processor 81 through a bus interface 82, where the memory 83 is configured to store programs and data used by the processor 81 when performing operations, and when the processor 81 calls and When the programs and data stored in the memory 83 are executed, the following processes are performed:

When the terminal maintains the first data transmission link with the first network entity and the second data transmission link with the second network entity, the transceiver 84 is used to pass through the second data transmission link The road sends a release notification to the terminal, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side.

The transceiver 84 is connected to the bus interface 82 and is used to receive and send data under the control of the processor 81.

It should be noted that in FIG. 8, the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 81 and various circuits of the memory represented by the memory 83 are linked together. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, so they are not described further herein. The bus interface provides an interface. The transceiver 84 may be multiple elements, including a transmitter and a transceiver, providing a unit for communicating with various other devices over a transmission medium. The processor 81 is responsible for managing the bus architecture and general processing, and the memory 83 may store data used by the processor 81 when performing operations.

The processor is specifically configured to send a release notification to the terminal through the second data transmission link according to a downlink data transmission situation.

The implementation embodiments of the method for releasing the link on the second network entity side are all applicable to the embodiment of the second network entity, and can also achieve the same technical effect.

An embodiment of the present disclosure also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the steps of the foregoing link release method on a terminal side or a second network entity side.

The above-mentioned implementation embodiments of the link release method on the terminal side or the second network entity side are all applicable to the embodiment of the computer-readable storage medium, and can also achieve the corresponding technical effects.

An embodiment of the present disclosure further provides a link release device, which is applied to a terminal, as shown in FIG. 9, and includes:

The first release module 91 is configured to receive the second network while maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity. After the explicit or implicit release notification sent by the entity, the first data transmission link and the radio resource configuration on the first network entity side are released.

The link release device provided in the embodiment of the present disclosure receives the first data transmission link with the first network entity and the second data transmission link with the second network entity by receiving After the explicit or implicit release notification sent by the second network entity, release the first data transmission link and the radio resource configuration on the first network entity side; enable the UE to keep data with the two network entities Under the premise of sending and receiving, the entire source-side wireless resource configuration can be released separately, thereby obtaining the performance requirement that the interruption delay in the handover process reaches 0ms, further improving the user experience.

Wherein, when the first network entity and the second network entity are slave network entities, the first release module includes a first release sub-module for releasing the first data transmission link and the first Secondary cell group configuration on the network entity side.

When the first network entity and the second network entity are both main network entities, the first release module includes a second release sub-module for releasing the first data transmission link and the first network entity. Primary cell group configuration on the side.

The above-mentioned implementation embodiments of the terminal-side link release method are all applicable to the embodiment of the link release device, and can also achieve the same technical effect.

An embodiment of the present disclosure further provides a link release device, which is applied to a second network entity, as shown in FIG. 10, including:

The first sending module 101 is configured to pass the second data when the terminal maintains a first data transmission link with the first network entity and a second data transmission link with the second network entity. The transmission link sends a release notification to the terminal, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side.

The link release device provided in the embodiment of the present disclosure passes through a case where the terminal maintains the first data transmission link with the first network entity and the second data transmission link with the second network entity, through The second data transmission link sends a release notification to the terminal, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side; it enables the UE to maintain communication with the two network entities. Under the premise of sending and receiving data, the entire source-side radio resource configuration can be released separately, so as to obtain the performance requirement that the interruption delay in the handover process reaches 0ms, further improving the user experience.

The first sending module includes a first sending sub-module configured to send a release notification to the terminal through the second data transmission link according to a downlink data transmission situation.

The above-mentioned implementation embodiments of the link release method on the second network entity side are all applicable to the embodiment of the link release device, and can also achieve the same technical effect.

It should be noted that many functional components described in this specification are referred to as modules / submodules, in order to emphasize the independence of their implementation methods more specifically.

In the embodiment of the present disclosure, the module / submodule may be implemented by software so as to be executed by various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of computer instructions, which may be constructed, for example, as an object, procedure, or function. Nevertheless, the executable code of the identified modules need not be physically located together, but may include different instructions stored in different bits. When these instructions are logically combined, they constitute a module and implement the provisions of the module purpose.

In fact, an executable code module can be a single instruction or many instructions, and can even be distributed across multiple different code segments, among different programs, and across multiple memory devices. As such, operational data may be identified within a module, and may be implemented in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed in different locations (including on different storage devices), and may at least partially exist on the system or network only as electronic signals.

When the module can be implemented by software, taking into account the current level of hardware technology, a module that can be implemented by software, without considering the cost, a person skilled in the art can build a corresponding hardware circuit to achieve the corresponding function, The hardware circuits include conventional very large scale integration (VLSI) circuits or gate arrays as well as existing semiconductors such as logic chips, transistors, or other discrete components. Modules can also be implemented with programmable hardware devices, such as field programmable gate arrays, programmable array logic, and programmable logic devices.

The above is an optional implementation of the present disclosure. It should be pointed out that for ordinary people in the technical field, without departing from the principles described in the present disclosure, several improvements and retouches can be made. These improvements and retouches should also be made. The scope of protection of this disclosure is considered.

Claims

A link release method applied to a terminal includes:

Under the condition that the first data transmission link with the first network entity and the second data transmission link with the second network entity are maintained, the explicit or implicit data received by the second network entity is received. After the release notification, the first data transmission link and the radio resource configuration on the first network entity side are released.
The link release method according to claim 1, wherein when the first network entity and the second network entity are both slave network entities, the first data transmission link and the first network entity side are released. Radio resource configuration, including:

Release the first data transmission link and the slave cell group configuration on the first network entity side.
The link release method according to claim 1, wherein when the first network entity and the second network entity are both primary network entities, the release of the first data transmission link and the first network entity side Radio resource configuration, including:

Release the first data transmission link and the primary cell group configuration on the first network entity side.
The link release method according to claim 1, wherein maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity comprises:

The data bearer DRB between each terminal and the base station or the signaling bearer SRB between the terminal and the base station, while maintaining two packet data convergence protocols PDCP encryption or decryption sub-functions, two wireless link layer control protocols RLC layer chain Channel, two media access control MAC layer links and physical layer links.
The link release method according to claim 1, wherein maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity comprises:

The data bearer DRB between each terminal and the base station or the signalling bearer SRB between the terminal and the base station, while maintaining a packet data convergence protocol PDCP entity, two radio link layer control protocol RLC layer links, two media Access control MAC layer link and physical layer link.
The link release method according to claim 1, wherein the release notification includes any one of the following information sent by the second network entity to the terminal:

The first downlink packet data convergence protocol PDCP packet;

The first physical downlink shared channel PDSCH or physical downlink control channel PDCCH channel transmission;

The first hybrid automatic retransmission of the physical uplink shared channel PUSCH channel requests HARQ confirmation or the radio link layer control protocol responds with RLC ACK;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.
A link release method applied to a second network entity includes:

When the terminal maintains the first data transmission link with the first network entity and the second data transmission link with the second network entity, sending to the terminal through the second data transmission link The release notification causes the terminal to release the first data transmission link and the radio resource configuration on the first network entity side.
The link release method according to claim 7, wherein the sending a release notification to the terminal through the second data transmission link comprises:

Sending a release notification to the terminal through the second data transmission link according to a downlink data transmission situation.
The link release method according to claim 7, wherein the release notification includes any one of the following information sent by the second network entity to the terminal:

The first downlink packet data convergence protocol PDCP packet;

The first physical downlink shared channel PDSCH or physical downlink control channel PDCCH channel transmission;

The first hybrid automatic retransmission of the physical uplink shared channel PUSCH channel requests HARQ confirmation or the radio link layer control protocol responds with RLC ACK;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.
A terminal includes a memory, a processor, a transceiver, and a program stored on the memory and executable on the processor; wherein, when the processor executes the program, the following steps are implemented:

Under the condition that the first data transmission link with the first network entity and the second data transmission link with the second network entity are maintained, the transceiver sends the After the explicit or implicit release notification, the first data transmission link and the radio resource configuration on the first network entity side are released.
The terminal according to claim 10, wherein when the first network entity and the second network entity are both slave network entities, the processor is specifically configured to:

Release the first data transmission link and the slave cell group configuration on the first network entity side.
The terminal according to claim 10, wherein when the first network entity and the second network entity are both primary network entities, the processor is specifically configured to:

Release the first data transmission link and the primary cell group configuration on the first network entity side.
The terminal according to claim 10, wherein maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity comprises:

The data bearer DRB between each terminal and the base station or the signalling bearer SRB between the terminal and the base station, while maintaining two packet data convergence protocols PDCP encryption or decryption sub-functions, two wireless link layer control protocols RLC layer chain Channels, two media access control MAC layer links and physical layer links; or

The data bearer DRB between each terminal and the base station or the signalling bearer SRB between the terminal and the base station, while maintaining a packet data convergence protocol PDCP entity, two radio link layer control protocol RLC layer links, two media Access control MAC layer link and physical layer link.
The terminal according to claim 10, wherein the release notification comprises any one of the following information sent by the second network entity to the terminal:

The first downlink packet data convergence protocol PDCP packet;

The first physical downlink shared channel PDSCH or physical downlink control channel PDCCH channel transmission;

The first hybrid automatic retransmission of the physical uplink shared channel PUSCH channel requests HARQ confirmation or the radio link layer control protocol responds with RLC ACK;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.
A second network entity includes a memory, a processor, a transceiver, and a program stored on the memory and executable on the processor; wherein, when the processor executes the program, the following steps are implemented:

When the terminal maintains the first data transmission link with the first network entity and the second data transmission link with the second network entity, the transceiver is used to pass through the second data transmission link Sending a release notification to the terminal, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side.
The second network entity according to claim 15, wherein the processor is specifically configured to:

Sending a release notification to the terminal through the second data transmission link according to a downlink data transmission situation.
The second network entity according to claim 15, wherein the release notification includes any one of the following information sent by the second network entity to the terminal:

The first downlink packet data convergence protocol PDCP packet;

The first physical downlink shared channel PDSCH or physical downlink control channel PDCCH channel transmission;

The first hybrid automatic retransmission of the physical uplink shared channel PUSCH channel requests HARQ confirmation or the radio link layer control protocol responds with RLC ACK;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.
A computer-readable storage medium having stored thereon a program, wherein the program, when executed by a processor, implements the steps of the link release method according to any one of claims 1 to 6;

When the program is executed by a processor, the steps of the link release method according to any one of claims 7 to 9 are implemented.
A link release device applied to a terminal includes:

A first release module, configured to receive the second network entity while maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity After the explicit or implicit release notification is sent, the first data transmission link and the radio resource configuration on the first network entity side are released.
The link release device according to claim 19, wherein when the first network entity and the second network entity are both slave network entities, the first release module comprises:

The first release submodule is configured to release the first data transmission link and the slave cell group configuration on the first network entity side.
The link release device according to claim 19, wherein when the first network entity and the second network entity are both primary network entities, the first release module comprises:

The second release sub-module is configured to release the first data transmission link and the primary cell group configuration on the first network entity side.
The link release device according to claim 19, wherein maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity comprises:

The data bearer DRB between each terminal and the base station or the signalling bearer SRB between the terminal and the base station, while maintaining two packet data convergence protocols PDCP encryption or decryption sub-functions, two wireless link layer control protocols RLC layer chain Channels, two media access control MAC layer links and physical layer links; or

The data bearer DRB between each terminal and the base station or the signalling bearer SRB between the terminal and the base station, while maintaining a packet data convergence protocol PDCP entity, two radio link layer control protocol RLC layer links, two media Access control MAC layer link and physical layer link.
The link release device according to claim 19, wherein the release notification includes any one of the following information sent by the second network entity to the terminal:

The first downlink packet data convergence protocol PDCP packet;

The first physical downlink shared channel PDSCH or physical downlink control channel PDCCH channel transmission;

The first hybrid automatic retransmission of the physical uplink shared channel PUSCH channel requests HARQ confirmation or the radio link layer control protocol responds with RLC ACK;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.
A link release device applied to a second network entity includes:

A first sending module, configured to pass through the second data transmission when the terminal maintains a first data transmission link with the first network entity and a second data transmission link with the second network entity The link sends a release notification to the terminal, so that the terminal releases the first data transmission link and the radio resource configuration on the first network entity side.
The link release device according to claim 24, wherein the first sending module comprises:

A first sending submodule is configured to send a release notification to the terminal through the second data transmission link according to a downlink data transmission situation.
The link release device according to claim 24, wherein the release notification includes any one of the following information sent by the second network entity to the terminal:

The first downlink packet data convergence protocol PDCP packet;

The first physical downlink shared channel PDSCH or physical downlink control channel PDCCH channel transmission;

The first hybrid automatic retransmission of the physical uplink shared channel PUSCH channel requests HARQ confirmation or the radio link layer control protocol responds with RLC ACK;

RRC acknowledgement message;

PDCP control frame;

Media access control layer control element MAC CE.