CN116156589A

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

Info

Publication number: CN116156589A
Application number: CN202310055787.0A
Authority: CN
Inventors: 张大钧; 刘佳敏
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2018-09-28
Filing date: 2018-09-28
Publication date: 2023-05-23
Also published as: WO2020063847A1; CN110972223A

Abstract

The invention provides a link release method, a device, a terminal and a second network entity, wherein the link release method comprises the following steps: and under the condition of maintaining a first data transmission link between the first network entity and a second data transmission link between the second network entity, after receiving an explicit or implicit release notification sent by the second network entity, releasing the first data transmission link and the radio resource configuration of the first network entity side. According to the scheme, the UE can independently release the wireless resource configuration of the whole source side on the premise of keeping data transmission and data reception with two network entities, so that the performance requirement that the interruption time delay in the switching process reaches 0ms is obtained, and the use experience of a user is further improved.

Description

Link release method, device, terminal and second network entity

The invention is a divisional application of the invention application of which the application date is 2018, 09, 28, 201811142464.0 and the invention name is 'a link release method, a link release device, a link release terminal and a second network entity'.

Technical Field

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

Background

As networks continue to evolve, inter-node mobility events under traditional network architectures cannot meet the higher demands placed on mobility performance. For example, maintaining a data outage of 0ms during handover has become a fundamental requirement for next generation network development; in the current common mobile scenario (such as the dual-connection network scenario shown in fig. 1), after the terminal UE moves to the overlapping position of signal coverage of two network entities, the network triggers a mobility event; in this regard, the conventional switching procedure uses to interrupt the data transmission of the original side, and then continue the service transmission after accessing the target node, so that a larger data interrupt may be caused.

In view of the above problems, an improved MBB (Make Before Break) procedure is provided in the prior art, and the improved handover procedure is as follows: after receiving the handover command, the UE still receives the data transmission from the source network entity, and then when the UE performs the uplink access procedure, the UE will interrupt the data transmission with the source side, and simultaneously, starts to apply the radio configuration of the target side and perform the data transmission to the target side.

That is, according to the prior art implementation, the UE can only keep transmitting and receiving data with a certain network entity at a certain instant of handover. In this way, when a handover process is performed from one network entity to another network entity, data interruption of an air interface will be caused, and the 0ms interruption delay requirement cannot be met, so that the use experience of a user is affected.

Disclosure of Invention

The invention aims to provide a link release method, a device, a terminal and a second network entity, which solve the problem of interruption time delay when the terminal switches network entities in the prior art.

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

and under the condition of maintaining a first data transmission link between the first network entity and a second data transmission link between the second network entity, after receiving an explicit or implicit release notification sent by the second network entity, releasing the first data transmission link and the radio resource configuration of the first network entity side.

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

And releasing the first data transmission link and the cell group configuration of the first network entity side.

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

and releasing the primary cell group configuration of the first data transmission link and the first network entity side.

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

the data bearer DRB between each terminal and the base station or the signaling bearer SRB between the terminal and the base station simultaneously maintains two packet data convergence protocol PDCP ciphering or deciphering sub-functions, two radio link layer control protocol RLC layer links, two medium access control MAC layer links and a physical layer link.

a data bearer DRB between each terminal and the base station or a signaling bearer SRB between the terminal and the base station is maintained while one packet data convergence protocol PDCP entity, two radio link layer control protocol RLC layer links, two medium access control MAC layer links and a physical layer link.

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

a first downlink packet data convergence protocol PDCP packet;

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

hybrid automatic repeat request (HARQ) acknowledgement of a first Physical Uplink Shared Channel (PUSCH) channel or radio link layer control protocol acknowledgement (RLC ACK);

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

The embodiment of the invention also provides a link release method which is applied to the second network entity and comprises the following steps:

and under the condition that the terminal maintains a first data transmission link between the terminal and the first network entity and a second data transmission link between the terminal and the second network entity, sending 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.

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

and sending a release notification to the terminal through the second data transmission link according to the downlink data transmission condition.

a first downlink packet data convergence protocol PDCP packet;

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

The embodiment of the invention also provides a terminal which comprises a memory, a processor, a transceiver and a program which is stored in the memory and can run on the processor; the processor, when executing the program, performs the steps of:

and under the condition of maintaining a first data transmission link between a first network entity and a second data transmission link between the first network entity and a second network entity, after receiving an explicit or implicit release notification sent by the second network entity through the transceiver, releasing the first data transmission link and the radio resource configuration of the first network entity side.

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:

a data bearer DRB between each terminal and a base station or a signaling bearer SRB between the terminal and the base station are kept, and simultaneously two packet data convergence protocol PDCP encryption or decryption subfunctions, two radio link layer control protocol RLC layer links, two medium access control MAC layer links and a physical layer link are kept; or alternatively

A first downlink packet data convergence protocol PDCP packet;

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

The embodiment of the invention also provides a second network entity which comprises a memory, a processor, a transceiver and a program stored in the memory and capable of running on the processor; the processor, when executing the program, performs the steps of:

and under the condition that the terminal maintains a first data transmission link between the terminal and the first network entity and a second data transmission link between the terminal and the second network entity, sending a release notification to the terminal through the second data transmission link by utilizing the transceiver, so that the terminal releases the first data transmission link and the radio resource configuration of the first network entity side.

Optionally, the processor is specifically configured to:

a first downlink packet data convergence protocol PDCP packet;

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the link release method described above.

The embodiment of the invention also provides a link release device which is applied to the terminal and comprises the following components:

and the first release module is used for releasing the first data transmission link and the radio resource configuration of the first network entity side after receiving the explicit or implicit release notification sent by the second network entity under the condition of maintaining the first data transmission link between the first network entity and the second network entity.

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

and the first release submodule is used for releasing the first data transmission link and the cell group configuration of 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:

and the second releasing submodule is used for releasing the first data transmission link and the configuration of the main cell group at the first network entity side.

a first downlink packet data convergence protocol PDCP packet;

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

The embodiment of the invention also provides a link release device which is applied to the second network entity and comprises the following components:

and the first sending module is used for sending a release notification to the terminal through the second data transmission link under the condition that the terminal maintains a first data transmission link between the terminal and the first network entity and a second data transmission link between the terminal and the second network entity, so that the terminal releases the first data transmission link and the radio resource configuration of the first network entity side.

Optionally, the first sending module includes:

and the first sending submodule is used for sending a release notification to the terminal through the second data transmission link according to the downlink data transmission condition.

a first downlink packet data convergence protocol PDCP packet;

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

The technical scheme of the invention has the following beneficial effects:

in the above scheme, the link release method releases the first data transmission link and the radio resource configuration at the first network entity side after receiving the explicit or implicit release notification sent by the second network entity under the condition that the first data transmission link between the first network entity and the second data transmission link between the second network entity are maintained; the UE can independently release the radio resource configuration of the whole source side on the premise of keeping the data transmission and the data reception with the two network entities, so that the performance requirement that the interruption time delay in the switching process reaches 0ms is obtained, and the use experience of a user is further improved.

Drawings

FIG. 1 is a schematic diagram of a prior art dual connectivity network scenario;

fig. 2 is a flowchart of a link release method according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a link release method according to a second embodiment of the present invention;

fig. 4 is a schematic diagram of a specific implementation flow of a link release method according to an embodiment of the present invention;

fig. 5 is a second flowchart of a specific implementation of the link release method according to the embodiment of the present invention;

fig. 6 is a schematic diagram of a flow chart III of a specific implementation of a link release method according to an embodiment of the present invention;

fig. 7 is a schematic diagram of a terminal structure according to an embodiment of the present invention;

fig. 8 is a schematic diagram of a second network entity structure according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of a link release device according to an embodiment of the present invention;

fig. 10 is a schematic diagram of a link release device according to an embodiment of the invention.

Detailed Description

In order to make the technical problems, technical solutions and advantages to be solved more apparent, the following detailed description will be given with reference to the accompanying drawings and specific embodiments.

The invention provides a link release method applied to a terminal, which aims at the problem of interruption time delay when the terminal switches network entities in the prior art, as shown in fig. 2, and comprises the following steps:

Step 21: and under the condition of maintaining a first data transmission link between the first network entity and a second data transmission link between the second network entity, after receiving an explicit or implicit release notification sent by the second network entity, releasing the first data transmission link and the radio resource configuration of the first network entity side.

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

The link release method provided by the embodiment of the invention releases the first data transmission link and the radio resource configuration of the first network entity side after receiving the explicit or implicit release notification sent by the second network entity under the condition of maintaining the first data transmission link between the first network entity and the second network entity; the UE can independently release the radio resource configuration of the whole source side on the premise of keeping the data transmission and the data reception with the two network entities, so that the performance requirement that the interruption time delay in the switching process reaches 0ms is obtained, and the use experience of a user is further improved.

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

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

In an embodiment of the present invention, maintaining a first data transmission link with a first network entity and a second data transmission link with a second network entity may include: the data bearer DRB between each terminal and the base station or the signaling bearer SRB between the terminal and the base station simultaneously maintains two packet data convergence protocol PDCP ciphering or deciphering sub-functions, two radio link layer control protocol RLC layer links, two medium access control MAC layer links and a physical layer link.

It may also be that maintaining a first data transmission link with a first network entity and a second data transmission link with a second network entity comprises: a data bearer DRB between each terminal and the base station or a signaling bearer SRB between the terminal and the base station, while maintaining one packet data convergence protocol PDCP entity (which may include a PDCP ciphering or deciphering sub-function), two radio link layer control protocol RLC layer links, two medium access control MAC layer links, and a physical layer link.

Specifically, the release notification includes any one of the following information sent by the second network entity to the terminal: a first downlink packet data convergence protocol PDCP packet; a first physical downlink shared channel PDSCH or physical downlink control channel PDCCH channel transmission; hybrid automatic repeat request (HARQ) acknowledgement of a first Physical Uplink Shared Channel (PUSCH) channel or radio link layer control protocol acknowledgement (RLC ACK); a radio resource control, RRC, acknowledgement message; PDCP control frames; the medium access control layer controls the element MAC CE.

The embodiment of the invention also provides a link release method applied to the second network entity, as shown in fig. 3, comprising the following steps:

step 31: and under the condition that the terminal maintains a first data transmission link between the terminal and the first network entity and a second data transmission link between the terminal and the second network entity, sending 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 link release method provided by the embodiment of the invention enables the terminal to release the first data transmission link and the radio resource configuration of the first network entity side by sending a release notice to the terminal through the second data transmission link under the condition that the terminal maintains the first data transmission link between the terminal and the first network entity and the second data transmission link between the terminal and the second network entity; the UE can independently release the radio resource configuration of the whole source side on the premise of keeping the data transmission and the data reception with the two network entities, so that the performance requirement that the interruption time delay in the switching process reaches 0ms is obtained, and the use experience of a user is further improved.

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

The link release method provided by the embodiment of the invention is further described below with reference to multiple sides such as a terminal and a second network entity, where the first network entity is exemplified by a source network entity, and the second network entity is exemplified by a target network entity.

Aiming at the technical problems, the embodiment of the invention provides a link release method (particularly an optimization method for releasing a source side link in switching), which is helpful for realizing the performance requirement that the interruption time delay in the switching process reaches 0 ms. The scheme provided by the embodiment of the invention mainly relates to the following two cases:

the first case (handover between two primary network entities, such as between two primary base stations):

in the 0ms handover procedure, if the target network entity receives a 0ms handover indication (i.e. the above-mentioned link handover request) from the source network entity and further receives an RRC (radio resource control) reconfiguration complete message (i.e. the above-mentioned access success indication) from the UE, if there is a downlink PDCP (packet data convergence protocol) data packet (data processed with new security context encryption or integrity protection) or a control frame to be sent to the UE through the new link.

Meanwhile, the target network entity can explicitly or implicitly inform the UE according to the downlink data transmission condition, the target network entity and the UE complete data transmission, and the UE is expected to release the data connection between the source network entity and the UE.

During the 0ms handover procedure, if the UE receives a 0ms handover indication (i.e., the above-mentioned link handover indication), the MCG (Master cell group, primary cell group) configuration of the target side may be immediately configured such that each DRB (data bearer between the terminal and the base station) bearer or SRB (signaling bearer between the terminal and the base station) bearer is maintained while two PDCP ciphering or deciphering sub-functions, two RLC layer links, two MAC layer links, and two physical layer links are maintained. Alternatively, one PDCP functionally 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, the HARQ (hybrid automatic repeat request) acknowledgement or RLC ACK (radio link layer control protocol acknowledgement) of the first PUSCH (physical uplink shared channel) channel (e.g., radio resource control RRC reconfiguration message), the RRC acknowledgement message, the PDCP control frame or MAC CE (MAC control element, medium access control layer control element), explicitly instructs the target network entity to complete data transmission with the UE, the UE will stop uplink transmission and downlink reception between the source network entity and the UE, and starts releasing the MCG configuration of the entire source side, e.g., releasing the MCG MAC (main cell group medium access control layer), the radio link layer RLC of the source side, and the PDCP ciphering or deciphering sub-functional entity. And performing a re-establishment procedure of the PDCP layer.

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

for LTE DC (LTE dual connectivity ), or EN-DC (E-UTRA-NR dual connectivity: evolved universal terrestrial radio Access 5G dual connectivity) or MR-DC (Multi-RAT dual connectivity, multiple radio System dual connectivity) or NR-NR DC (NR-NR dual connectivity,5G base station-5G base station dual connectivity), during a SCG (Secondary cell group, slave cell group) 0ms handover, if the target slave network entity receives an SCG 0ms handover indication from the target master network entity (i.e., the master network entity corresponding to the source slave network entity as described above) and in turn receives an access success indication from the UE, optionally, a configuration complete message (referring to a message transmitted on the interface between the master network entity and the slave network entity, not an air-interface RRC reconfiguration message) is received from the target master network entity, then if a downlink data packet (data encrypted with a new security context or data processed with integrity protection) or a control frame is to be sent to the UE over the new link.

Meanwhile, the target slave network entity can explicitly or implicitly inform the UE according to the downlink data transmission condition, the target slave network entity and the UE complete data transmission, and the UE is expected to release the data connection between the source slave network entity and the UE.

During the SCG 0ms handover procedure, if the UE receives the SCG 0ms handover indication (i.e., the above-mentioned link handover indication), the SCG configuration of the target side may be immediately configured such that each DRB bearer or SRB bearer maintains two PDCP ciphering or deciphering sub-functions, two RLC layer links, two MAC layer links, and two physical layer links. Alternatively, one PDCP functionally 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 of the first PUSCH channel, the RRC acknowledgement message, the PDCP control frame or MAC CE, explicitly indicates that the target is completing data transmission from the network entity to the UE, the UE will stop the uplink transmission and downlink reception of the source from between the network entity and the UE, and start releasing the SCG configuration of the whole source side, e.g. releasing the SCG MAC (cell group medium access control layer) of the source side, RLC, and PDCP ciphering or deciphering sub-functional entities. And performing a re-establishment procedure of the PDCP layer.

The following illustrates the scheme provided by the embodiment of the invention.

Example 1: source link release mechanism for 0ms handover procedure between eNBs (4G base stations)

As shown in fig. 4, steps 41 to 45: the original data transmission link is always kept between a source network entity (eNB) and the UE; after receiving the 0ms handover indication from the source network entity (eNB) and receiving the RRC reconfiguration complete message from the UE, the target network entity (eNB) will send a new link to the UE if there is a downlink PDCP packet (data processed with new security context ciphering or integrity protection) or control frame to be sent in the buffer.

Steps 46 to 47: the UE maintains transmission and reception of data with two network entities (enbs).

Step 48: the target network entity (eNB) explicitly or implicitly informs the UE according to the downlink data transmission condition, the target network entity (eNB) and the UE complete data transmission, and the UE is expected to release the data connection between the source network entity (eNB) and the UE;

step 49: the UE receives a release notification from a target network entity (eNB), such as: the first downlink PDCP packet, the first PDSCH or PDCCH channel transmission, the HARQ acknowledgement or RLC ACK of the first PUSCH channel (e.g., RRC reconfiguration message), the RRC acknowledgement message, the PDCP control frame or MAC CE (explicitly indicating that the target network entity (eNB) and UE completed data transmission), will stop the uplink transmission and downlink reception between the source network entity (eNB) and UE and start to release the MCG configuration of the entire source side, e.g., release the MCG MAC, RLC, and PDCP ciphering or deciphering sub-functional entities of the source side. And performing a re-establishment procedure of the PDCP layer.

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

As shown in fig. 4, the method comprises:

step 41: a Source network entity (Source eNB) sends a handover request HO request (0ms interruption indicator,0ms interrupt indicator) to a Target network entity (Target eNB);

step 42: the Target network entity (Target eNB) feeds back a switching request response (HO request ACK) to the Source network entity (Source eNB);

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

step 44: the UE accesses a Target network entity (Target eNB) according to the switching instruction, namely an 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: maintaining transmission and reception of data (User data) between the UE and a Source network entity (Source eNB);

step 47: maintaining transmission and reception of data (User data) between the UE and a Target network entity (Target eNB);

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

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

Step 410: the UE maintains transmission and reception of data (User data) only with the Target network entity (Target eNB).

Example 2: source link release mechanism for SCG 0ms handover procedure between SN (5G slave base station) or SeNB (4G slave base station) and SN or SeNB in case of LTE DC, or EN-DC, or MR-DC, or NR-NR DC

As shown in fig. 5, steps 51 to 56: the source keeps the original data transmission link between the network entity and the UE all the time; after receiving the SCG 0ms handover indication from the target slave network entity (the master network entity corresponding to the source slave network entity) and receiving the access success indication from the UE, optionally after receiving the configuration completion message from the UE, if a downlink PDCP data packet (data processed with new security context encryption or integrity protection) or a control frame is to be sent to the UE through a new link in the buffer.

Steps 57 to 58: the UE maintains transmission and reception of data with the two network slave entities.

Step 59: the target slave network entity explicitly or implicitly informs the UE according to the downlink data transmission condition, the target slave network entity and the UE complete data transmission, and the UE is expected to release 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 of the first PUSCH channel, the RRC acknowledgement message, the PDCP control frame or MAC CE (explicitly indicating that the target is completing the data transmission from the network entity and the UE), will stop the uplink transmission and downlink reception of the source from between the network entity and the UE, and start releasing the SCG configuration of the whole source side, e.g. the SCG MAC, RLC of the source side, and PDCP ciphering or deciphering sub-functional entity. And performing a re-establishment procedure of the PDCP layer.

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

The SN corresponds to the 5G master MN, and the SeNB corresponds to the 4G master MeNB.

As shown in fig. 5, the method comprises:

step 51: the master network entity MeNB/MN (MeNB or MN) sends an SCG addition request SCG Addition request (SCG 0ms interruption indicator,SCG 0ms break indicator) to the Target slave network entity Target SeNB/SN (Target SeNB or SN);

step 52: the Target slave network entity Target SeNB/SN feeds back an SCGG addition request response SCG Addition request ACK to the master network entity MeNB/MN;

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

step 54: the UE indicates an access Target from a network entity Target SeNB/SN according to RRC reconfiguration, namely the access Target;

step 55: the UE sends RRC reconfiguration complete information to the main network entity MeNB/MN (RRC Connection Reconfiguration Complete);

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

step 57: maintaining transmission and reception of data (User data) between the UE and a Source slave network entity Source SeNB/SN (Source SeNB or SN);

step 58: maintaining the transmission and the reception of data (User data) between the UE and the Target slave network entity Target SeNB/SN;

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

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

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

Example 3: source link release mechanism for 0ms handover procedure between NR gNB (5G base station) or ng-eNB (4G base station node accessible to core network 5 GC)

As shown in fig. 6, steps 61 to 65: the original data transmission link is always kept between a source network entity (NR gNB or ng-eNB) and the UE; after receiving the 0ms handover indication from the source network entity (NR gNB or ng-eNB) for the target network entity (NR gNB or ng-eNB) and receiving the RRC reconfiguration complete message from the UE, if there is a downlink PDCP packet (data processed with new security context encryption or integrity protection) or control frame to be sent in the buffer, it will be sent to the UE over the new link.

Steps 66-67: the UE maintains transmission and reception of data with two network entities (NR gNB or ng-eNB).

Step 68: the target network entity (NR gNB or ng-eNB) can explicitly or implicitly inform the UE according to the downlink data transmission condition, the target network entity (NR gNB or ng-eNB) and the UE complete data transmission, and the UE is expected to release the data connection between the source network entity (NR gNB or ng-eNB) and the UE;

step 69: the UE receives a release notification from a target network entity (NR gNB or ng-eNB), such as: the first downlink PDCP packet, the first PDSCH or PDCCH channel transmission, the HARQ acknowledgement or RLC ACK of the first PUSCH channel (e.g., RRC reconfiguration message), the RRC acknowledgement message, the PDCP control frame or MAC CE (explicitly indicating that the target network entity (NR gNB or ng-eNB) has completed data transmission with the UE), will stop the uplink transmission and downlink reception between the source network entity (NR gNB or ng-eNB) and the UE and start to release the MCG configuration of the entire source side, e.g., release the MCG MAC, RLC of the source side, and PDCP ciphering or deciphering sub-functional entities. And performing a re-establishment procedure of the PDCP layer.

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

As shown in fig. 6, the method comprises:

step 61: the Source network entity Source gNB/nr-eNB (Source gNB or nr-eNB) sends a handover request HO request (0ms interruption indicator,0ms interrupt indicator) to the Target network entity Target gNB/nr-eNB (Target gNB or nr-eNB);

step 62: the Target network entity Target gNB/nr-eNB feeds back a switching request response (HO request ACK) 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) carrying a 0ms interruption indicator to the UE;

step 64: the UE accesses a Target network entity Target gNB/nr-eNB, namely an access Target, according to the switching instruction;

step 65: the UE sends RRC reconfiguration complete information to the Target gNB/nr-eNB of the Target network entity (RRC Connection Reconfiguration Complete);

step 66: maintaining the transmission and the reception of data (User data) between the UE and a Source network entity Source gNB/nr-eNB;

step 67: maintaining the transmission and the reception of data (User data) between the UE and a Target gNB/nr-eNB;

step 68: the Target gNB/nr-eNB sends an explicit indicator explicit indicator to the UE;

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

step 610: the UE only maintains the transmission and reception of data (User data) with the Target network entity, target gNB/nr-eNB.

From the above, the scheme provided by the embodiment of the invention mainly relates to two parts:

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

the target network entity (eNB or NR gNB or ng-eNB) can explicitly or implicitly inform the UE according to the downlink data transmission condition, and the target network entity (eNB or NR gNB or ng-eNB) and the UE complete data transmission;

the UE receives display or implicit notification information from a target network entity (eNB or NR gNB or ng-eNB), stops uplink transmission and downlink reception between a source network entity (eNB or NR gNB or ng-eNB) and the UE, and starts to release MCG configuration of the whole source side;

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

for LTE DC, EN-DC, MR-DC or NR-NR DC, the target slave network entity (SeNB or SN) can explicitly or implicitly inform the UE according to the downlink data transmission condition, the target slave network entity (SeNB or SN) and the UE complete data transmission, and the UE is expected 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 the display or implicit notification information from the target slave network entity (SeNB or SN), stops the uplink and downlink transmissions between the source slave network entity (SeNB or SN) and the UE, and starts to release the SCG configuration on the entire source side.

In summary, according to the implementation of the prior art, when the UE performs a handover procedure from one network entity to another network entity, the UE will cause data interruption of the air interface, and the 0ms delay requirement cannot be satisfied. The scheme provided by the embodiment of the invention enables the UE to independently release the wireless resource configuration of the whole source side on the premise of keeping the data transmission and the data reception with two network entities, thereby obtaining the performance requirement that the interruption time delay of the air in the switching process reaches 0ms and further improving the use experience of users.

The terminal provided by the embodiment of the invention releases the first data transmission link and the radio resource configuration of the first network entity side after receiving the explicit or implicit release notification sent by the second network entity through the transceiver under the condition of maintaining the first data transmission link between the first network entity and the second network entity; the UE can independently release the radio resource configuration of the whole source side on the premise of keeping the data transmission and the data reception with the two network entities, so that the performance requirement that the interruption time delay in the switching process reaches 0ms is obtained, and the use experience of a user is further improved.

As shown in fig. 7, the terminal provided in the embodiment of the present invention includes:

a processor 71; and a memory 73 connected to the processor 71 through a bus interface 72, the memory 73 storing programs and data used by the processor 71 in performing operations, when the processor 71 calls and executes the programs and data stored in the memory 73, the following processes are performed:

in the case of maintaining a first data transmission link with a first network entity and a second data transmission link with a second network entity, upon receiving an explicit or implicit release notification sent by the second network entity through the transceiver 74, the first data transmission link and the radio resource configuration at the first network entity side are released.

Wherein a transceiver 74 is coupled to the bus interface 72 for receiving and transmitting 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, and in particular one or more processors represented by processor 71 and various circuits of the memory represented by memory 73, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 74 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 75 may also be an interface capable of interfacing with an internal connection requiring device for a different terminal, including but not limited to a keypad, display, speaker, microphone, joystick, etc. 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 in performing operations.

Those skilled in the art will appreciate that all or part of the steps of implementing the above-described embodiments may be implemented by hardware, or may be implemented by instructing the relevant hardware by a computer program comprising instructions for performing some or all of the steps of the above-described methods; and the computer program may be stored in a readable storage medium, which 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: and releasing the first data transmission link and the cell group configuration of the first network entity side.

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

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

The embodiments of the link release method at the terminal side are applicable to the embodiments of the terminal, and the same technical effects can be achieved.

The second network entity provided by the embodiment of the invention transmits a release notice to the terminal through the second data transmission link by utilizing the transceiver under the condition that the terminal maintains a first data transmission link between the terminal and the first network entity and a second data transmission link between the terminal and the second network entity, so that the terminal releases the first data transmission link and the radio resource configuration of the first network entity side; the UE can independently release the radio resource configuration of the whole source side on the premise of keeping the data transmission and the data reception with the two network entities, so that the performance requirement that the interruption time delay in the switching process reaches 0ms is obtained, and the use experience of a user is further improved.

As shown in fig. 8, the second network entity according to the embodiment of the present invention includes:

a processor 81; and a memory 83 connected to the processor 81 through a bus interface 82, the memory 83 being for storing programs and data used by the processor 81 in performing operations, when the processor 81 calls and executes the programs and data stored in the memory 83, the following processes are performed:

in case the terminal maintains a first data transmission link with the first network entity and a second data transmission link with the second network entity, a release notification is sent to the terminal by means of the transceiver 84 via the second data transmission link, such that the terminal releases the radio resource configuration at the first data transmission link and the first network entity side.

Wherein a transceiver 84 is coupled to the bus interface 82 for receiving and transmitting 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, and in particular, one or more processors represented by processor 81 and various circuits of memory represented by memory 83, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 84 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus 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 in performing operations.

Wherein, the processor is specifically configured to: and sending a release notification to the terminal through the second data transmission link according to the downlink data transmission condition.

The implementation embodiments of the link release method on the second network entity side are applicable to the embodiment of the second network entity, and the same technical effects can be achieved.

The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when being executed by a processor, implements the steps of the above-mentioned link release method at the terminal side or at the second network entity side.

The embodiments of the link release method on the terminal side or the second network entity side are applicable to the embodiments of the computer readable storage medium, and the corresponding same technical effects can be achieved.

The embodiment of the invention also provides a link release device, which is applied to a terminal, as shown in fig. 9, and comprises:

the first releasing module 91 is configured to, when maintaining the first data transmission link with the first network entity and the second data transmission link with the second network entity, release the radio resource configuration on the first data transmission link and the first network entity side after receiving an explicit or implicit release notification sent by the second network entity.

The link release device provided by the embodiment of the invention releases the first data transmission link and the radio resource configuration of the first network entity side after receiving the explicit or implicit release notification sent by the second network entity under the condition of maintaining the first data transmission link between the first network entity and the second network entity; the UE can independently release the radio resource configuration of the whole source side on the premise of keeping the data transmission and the data reception with the two network entities, so that the performance requirement that the interruption time delay in the switching process reaches 0ms is obtained, and the use experience of a user is further improved.

Wherein when the first network entity and the second network entity are both slave network entities, the first release module includes: and the first release submodule is used for releasing the first data transmission link and the cell group configuration of the first network entity side.

When the first network entity and the second network entity are both the main network entity, the first release module includes: and the second releasing submodule is used for releasing the first data transmission link and the configuration of the main cell group at the first network entity side.

The embodiments of the link release method at the terminal side are applicable to the embodiments of the link release device, and the same technical effects can be achieved.

The embodiment of the invention also provides a link release device, which is applied to a second network entity, as shown in fig. 10, and comprises:

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

The link release device provided by the embodiment of the invention sends the release notification to the terminal through the second data transmission link under the condition that the terminal maintains the first data transmission link between the terminal and the first network entity and the second data transmission link between the terminal and the second network entity, so that the terminal releases the first data transmission link and the radio resource configuration of the first network entity side; the UE can independently release the radio resource configuration of the whole source side on the premise of keeping the data transmission and the data reception with the two network entities, so that the performance requirement that the interruption time delay in the switching process reaches 0ms is obtained, and the use experience of a user is further improved.

Wherein, the first sending module includes: and the first sending submodule is used for sending a release notification to the terminal through the second data transmission link according to the downlink data transmission condition.

The above embodiments of the link release method on the second network entity side are applicable to the embodiments of the link release device, and the same technical effects can be achieved.

It should be noted that many of the functional components described in this specification are referred to as modules/sub-modules in order to more particularly emphasize their implementation independence.

In embodiments of the invention, the modules/sub-modules may be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different bits which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Likewise, operational data may be identified within modules and may be embodied 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 over different locations including over different storage devices.

Where a module may be implemented in software, taking into account the level of existing hardware technology, a module may be implemented in software, and one skilled in the art may, without regard to cost, build corresponding hardware circuitry, including conventional Very Large Scale Integration (VLSI) circuits or gate arrays, and existing semiconductors such as logic chips, transistors, or other discrete components, to achieve the corresponding functions. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and changes can be made without departing from the principles of the present invention, and such modifications and changes should also be considered as being within the scope of the present invention.

Claims

1. A link release method applied to a terminal, comprising:

under the condition of maintaining a first data transmission link between a first network entity and a second data transmission link between a second network entity, after receiving an explicit or implicit release notification sent by the second network entity, releasing the first data transmission link and radio resource configuration of a first network entity side;

Wherein maintaining a first data transmission link with a first network entity and a second data transmission link with a second network entity comprises:

a data bearer DRB between each terminal and a base station or a signaling bearer SRB between the terminal and the base station are maintained, and a packet data convergence protocol PDCP entity, two packet data convergence protocol PDCP encryption or decryption subfunctions, two radio link layer control protocol RLC layer links, two medium access control MAC layer links and a physical layer link are maintained at the same time;

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

releasing the primary cell group configuration of the first data transmission link and the first network entity side;

wherein the release notification comprises any one of the following information sent by the second network entity to the terminal:

a first downlink packet data convergence protocol PDCP packet;

A radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

2. 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 releasing the radio resource configuration of the first data transmission link and the first network entity side includes:

3. A link release method applied to a second network entity, comprising:

under the condition that a terminal maintains a first data transmission link between a first network entity and a second data transmission link between the terminal and a second network entity, sending a release notification to the terminal through the second data transmission link, so that the terminal releases the first data transmission link and radio resource configuration of the first network entity side;

wherein the sending, by the second data transmission link, a release notification to the terminal includes:

according to the downlink data transmission condition, a release notification is sent to the terminal through the second data transmission link;

When the first network entity and the second network entity are both the main network entity, the releasing the radio resource configuration of the first data transmission link and the first network entity side includes:

a first downlink packet data convergence protocol PDCP packet;

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

4. A terminal comprising a memory, a processor, a transceiver, and a program stored on the memory and executable on the processor; wherein the processor, when executing the program, performs the steps of:

under the condition of maintaining a first data transmission link between a first network entity and a second data transmission link between a second network entity, after receiving an explicit or implicit release notification sent by the second network entity through the transceiver, releasing the first data transmission link and radio resource configuration of the first network entity side;

a first downlink packet data convergence protocol PDCP packet;

A radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

5. The terminal of claim 4, wherein when the first network entity and the second network entity are both slave network entities, the processor is specifically configured to:

6. A second network entity comprising a memory, a processor, a transceiver, and a program stored on the memory and executable on the processor; wherein the processor, when executing the program, performs the steps of:

in the case that a terminal maintains a first data transmission link with a first network entity and a second data transmission link with a second network entity, sending a release notification to the terminal through the second data transmission link by using the transceiver, so that the terminal releases the first data transmission link and radio resource configuration of the first network entity side;

wherein, the processor is specifically configured to:

a first downlink packet data convergence protocol PDCP packet;

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

7. A computer readable storage medium having stored thereon a computer program, characterized in that the program when executed by a processor realizes the steps of the link release method according to any of claims 1 to 2; or alternatively

The program when executed by a processor implements the steps of the link release method as claimed in claim 3.

8. A link release device applied to a terminal, comprising:

a first release module, configured to release a radio resource configuration on a first data transmission link and a first network entity side after receiving an explicit or implicit release notification sent by a second network entity while maintaining a first data transmission link with the first network entity and a second data transmission link with the second network entity;

a first downlink packet data convergence protocol PDCP packet;

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.

9. The link release apparatus of claim 8, wherein the first release module when the first network entity and the second network entity are both slave network entities comprises:

10. A link release apparatus for use with a second network entity, comprising:

a first sending module, configured to send a release notification to a terminal through a second data transmission link under a condition that the terminal maintains a first data transmission link with a first network entity and a second data transmission link with a second network entity, so that the terminal releases the first data transmission link and radio resource configuration of the first network entity side;

Wherein, the first sending module includes:

the first sending submodule is used for sending a release notice to the terminal through the second data transmission link according to the downlink data transmission condition;

a first downlink packet data convergence protocol PDCP packet;

a radio resource control, RRC, acknowledgement message;

PDCP control frames;

the medium access control layer controls the element MAC CE.