WO2020088589A1

WO2020088589A1 - Switching method and apparatus, and terminal

Info

Publication number: WO2020088589A1
Application number: PCT/CN2019/114685
Authority: WO
Inventors: 张大钧; 刘佳敏
Original assignee: 电信科学技术研究院有限公司
Priority date: 2018-10-31
Filing date: 2019-10-31
Publication date: 2020-05-07
Also published as: CN111132244A

Abstract

Provided are a switching method and apparatus, and a terminal. The method comprises: connecting a packet data convergence protocol (PDCP) entity of a terminal to a target link, and keeping a connection between the PDCP entity of the terminal and a source link unchanged; after the terminal successfully accesses the target link, the terminal using the target link to transmit data; and after the data is successfully received using the target link, releasing the connection between the terminal and the source link.

Description

Switching method, device and terminal

Cross-reference of related applications

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

Technical field

The present disclosure relates to the field of communication technology, and in particular, to a switching method, device, and terminal.

Background technique

In a common mobile scenario, after the terminal moves to the overlapped signal coverage of two network entities, the network will trigger a mobility event. In the traditional handover process, the data transmission on the source side is interrupted first, and then the service transmission is continued after accessing the target node, which will cause a large data interruption.

In the improved MBB (Make Before Break) process, after the terminal receives the handover command, it still receives data transmission from the source network entity, and then interrupts the data transmission with the source side during the terminal's upstream access process At the same time, the application of the wireless configuration on the target side and the data transmission on the target side are started. Although this process will reduce a certain interrupt delay, it still cannot meet the requirement of 0ms interrupt delay.

With the continuous evolution of the network, the mobile events between nodes under the traditional network architecture cannot meet the higher demands for mobile performance. For example, during the handover process between cells in a node, the key does not need to be changed, which still causes an interruption delay of 10 to 20 ms.

In summary, according to the related technology, even if the key is not changed, at a certain moment of switching, the terminal can only keep data transmission and reception with a certain network entity. In this way, when the handover process from one network entity to another network entity is performed, the data of the air interface will be interrupted, and the 0ms delay requirement cannot be met.

Summary of the invention

The purpose of the present disclosure is to provide a handover method, device and terminal to solve the problem that the terminal cannot achieve zero-delay handover in the related art.

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

Connect the packet data aggregation protocol PDCP entity of the terminal to the target link, and keep the connection between the terminal's PDCP entity and the source link unchanged;

After the terminal successfully accesses the target link, the terminal uses the target link for data transmission;

After successfully receiving data using the target link, the connection between the terminal and the source link is released.

Wherein, the method further includes:

Receiving a handover request message, where the handover request message carries a first indication for instructing the terminal to perform zero-delay handover and a second indication for indicating that the terminal does not need to replace the security key;

The connection of the PDCP entity of the terminal's packet data aggregation protocol to the target link and keeping the connection of the terminal's PDCP entity and the source link unchanged include:

Reconfiguring the wireless bearer of the terminal into a separate bearer mode according to the handover request message;

Wherein, in the separate bearer mode, the PDCP entity corresponding to the wireless bearer is configured such that the connection with the source link is unchanged and the target link is connected.

The source link includes: at least one of a source wireless link layer RLC link, a source media access layer MAC link, and a source physical layer PHY link;

The target link includes at least one of a target RLC link, a target MAC link, and a target PHY link.

Wherein, the source link and the target link are links between the terminal and different cells in the same network node;

or,

The source link and the target link are different links between the terminal and the same cell in the same network node.

Wherein, after the terminal successfully accesses the target link, the terminal uses the target link for data transmission, including:

After the terminal successfully accesses the target link, send a handover complete message to the target network entity corresponding to the target link;

Perform data transmission with the target network entity through the target link.

Wherein, after successfully receiving the data using the target link, before releasing the connection between the terminal and the source link, the method further includes:

It is determined that the terminal successfully receives data using the target link.

Wherein, the determining that the terminal successfully receives data using the target link includes:

Determine, according to the received indication information sent by the target network entity corresponding to the target link, that the terminal successfully receives data using the target link, and the indication information is used to indicate that the terminal successfully receives the target network entity through the target Data transmitted by the link; or,

Receiving the first downlink PDCP data packet from the target link, and determining that the terminal successfully receives data using the target link; or,

Receiving the first physical downlink shared channel PUSCH or the first physical downlink control channel PUCCH sent by the target network entity corresponding to the target link, and determining that the terminal successfully receives data using the target link; or,

Upon receiving the HARQ confirmation or RLC confirmation of the first PUSCH hybrid automatic retransmission request from the target link, it is determined that the terminal successfully receives data using the target link.

Wherein, the method further includes:

Receive the preset radio resource control RRC message or PDCP control frame or media intervention control layer control unit MAC of the target network entity corresponding to the target link;

The preset RRC message or PDCP control frame or MAC CE carries the indication information.

Wherein, after successfully receiving data using the target link, releasing the connection between the terminal and the source link includes:

After successfully receiving data using the target link, stop the uplink and downlink transmission between the terminal and the source link, and release the wireless configuration of the source network entity corresponding to the source link.

An embodiment of the present disclosure also provides a switching device, which is applied to a terminal and includes:

The connection module is used to connect the packet data aggregation protocol PDCP entity of the terminal to the target link, and keep the connection between the terminal's PDCP entity and the source link unchanged;

A transmission module, configured to use the target link for data transmission after the terminal successfully accesses the target link;

The release module is configured to release the connection between the terminal and the source link after successfully receiving data using the target link.

An embodiment of the present disclosure also provides a terminal, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, and the processor is used to read the program in the memory, Perform the following procedure:

The transceiver is used to: after the terminal successfully accesses the target link, use the target link for data transmission;

The processor is also used to:

Among them, the transceiver is also used for:

The processor is also used to:

or,

Among them, the transceiver is also used for:

After the terminal successfully accesses the target link, it sends a handover complete message to the target network entity corresponding to the target link;

Among them, the processor is also used for:

Among them, the transceiver is also used for:

Among them, the processor is also used for:

Embodiments of the present disclosure also provide a computer-readable storage medium that stores a program on the computer-readable storage medium, and when the program is executed by a processor, implements the steps of the switching method described above.

The above technical solutions of the present disclosure have at least the following beneficial effects:

In the switching method, device and terminal of the embodiments of the present disclosure, for the zero-latency switching operation that does not need to update the security key, the packet data aggregation protocol PDCP entity of the terminal is connected to the target link, and the terminal's PDCP is maintained The connection between the entity and the source link is unchanged, and after the terminal successfully accesses the target link, the terminal uses the target link for data transmission; further after successfully receiving data using the target link To release the connection between the terminal and the source link; thus, zero-latency switching of the terminal can be achieved, and the user experience can be improved.

BRIEF DESCRIPTION

FIG. 1 shows a flowchart of steps of a handover method provided by an embodiment of the present disclosure;

FIG. 2 shows a schematic diagram of signaling interaction of the first example of a handover method provided by an embodiment of the present disclosure;

FIG. 3 shows a schematic diagram of signaling interaction of a second example of a handover method provided by an embodiment of the present disclosure;

FIG. 4 shows a schematic diagram of signaling interaction of a third example of a handover method provided by an embodiment of the present disclosure;

5 shows a schematic structural diagram of a switching device provided by an embodiment of the present disclosure;

FIG. 6 shows a schematic structural diagram of a terminal provided by an embodiment of the present disclosure.

detailed description

To make the technical problems, technical solutions, and advantages to be solved by the present disclosure clearer, the following will describe in detail with reference to the accompanying drawings and specific embodiments.

As shown in FIG. 1, an embodiment of the present disclosure provides a handover method, which is applied to a terminal and includes:

Step 11: Connect the packet data aggregation protocol PDCP entity of the terminal to the target link, and keep the connection between the terminal's PDCP entity and the source link unchanged;

Step 12, after the terminal successfully accesses the target link, the terminal uses the target link for data transmission;

Step 13: After successfully receiving data using the target link, release the connection between the terminal and the source link.

It should be noted that during the handover, the source link and the target link can simultaneously transmit data to the terminal, and the data packets transmitted by the source link and the target link use the original security key (that is, the same security key, It can also be called the original security context) for encryption or decryption.

Further, in the above embodiments of the present disclosure, the method further includes:

Accordingly, step 11 includes:

In the embodiment of the present disclosure, the handover operation without updating the security key may be a handover operation in different cells within the same network node, or may be a handover operation within the same cell within the same network node. That is, the source link and the target link are links between the terminal and different cells in the same network node; or, the source link and the target link are the terminal and the same network Different links between the same cell within a node.

In short, in the embodiments of the present disclosure, for a switching operation that does not require a key update, the network side is allowed to configure the terminal to perform a zero-latency switching operation. Among them, the handover request message sent to the terminal needs to indicate zero-delay handover, and it also needs to indicate that the security key does not need to be replaced; that is, for all radio bearers (signaling radio bearer SRB or data radio bearer DRB), the key is kept constant.

After receiving the handover request message, the terminal resets all related radio bearers to the split bearer mode (that is, Split bearer mode), that is, the PDCP entity corresponding to the radio bearer (NRCPPD for 5G), keeping the source link unchanged At the same time, reconnect to the new target link.

Optionally, the source link includes: at least one of a source wireless link layer RLC link, a source media access layer MAC link, and a source physical layer PHY link; the target link includes: a target RLC chain At least one of a channel, a target MAC link, and a target PHY link.

As some embodiments, step 12 includes:

After the terminal successfully accesses the target link, a handover complete message is sent to the target network entity corresponding to the target link; for example, the handover complete message may be an RRC reconfiguration complete message.

After the target network entity receives the RRC reconfiguration complete message from the terminal, if there is a downlink PDCP data packet (data encrypted or processed by the original full key encryption or integrity protection) or a control frame in the buffer, pass the target The network entity sends to the terminal.

Further, in the above embodiment of the present disclosure, before step 13, the method further includes:

Through the display indication or the implicit indication of the target network entity, it is determined that the terminal successfully receives the data using the target link.

Optionally, the display indication of the target network entity determines that the terminal successfully receives data using the target link, including:

Determine, according to the received indication information sent by the target network entity corresponding to the target link, that the terminal successfully receives data using the target link, and the indication information is used to indicate that the terminal successfully receives the target network entity through the target Data transmitted by the link;

Among them, the instruction information receiving steps are as follows:

Optionally, the implicit indication of the target network entity to determine that the terminal successfully receives data using the target link includes:

Receiving the first downlink PDCP data packet from the target link, and determining that the terminal successfully receives data using the target link; or

As some other embodiments, step 13 includes;

After successfully receiving data using the target link, stop the uplink and downlink transmission between the terminal and the source link, and release the wireless configuration of the source network entity corresponding to the source link, for example, releasing the source link MAC, RLC and PHY configuration, and perform PDCP layer recovery process.

In order to more clearly describe the handover method provided by the embodiment of the present disclosure, the following description will be made in conjunction with three examples.

Example 1: As shown in Figure 2, handover between different cells in the same base station

Step 21: The base station (5G access network entity) decides to perform the zero-delay handover based on the terminal's wireless channel conditions, load status, or other radio resource management RRM policies, and the terminal's capabilities (whether or not to support zero-delay handover) New target cell (the target cell is located in the same base station as the original cell). The base station sends a handover request message to the terminal, and the handover request message carries zero-latency handover indication information (indicator), and indicates that the security key does not need to be replaced;

Step 22: After receiving the handover request message, the terminal reconfigures all related SRB / DRB bearers into Split bearer mode. The original PDCP entity (NRPDPD for 5G) keeps the original RLC / MAC / PHY link unchanged At the same time, connect to the new target RLC / MAC / PHY link respectively.

Step 23: The terminal performs target cell operation corresponding to the uplink access target link (including 23a random access preamble and 23b random access response).

Step 24: After the terminal successfully accesses the target cell, it starts to transmit an RRC reconfiguration complete message to the base station.

Step 25: After receiving the RRC reconfiguration complete message from the terminal (ie, the handover complete message), the base station will start to transmit the uplink and downlink data packets between the target link and the UE, and these data packets are still encrypted using the original security context. / Decryption processing.

Step 26, once the terminal determines that the terminal successfully receives data using the target link through the display indication or implicit indication of the target network entity, it will stop the uplink transmission and downlink reception between the source link and the terminal, and start to release the entire source The wireless configuration on the side, such as releasing the MAC, RLC, and PHY configuration of the source cell or source link, and performing the PDCP layer recovery process.

In step 27, the terminal continues to use the new target link for data transmission with the network.

Example 2: As shown in Figure 3, under the centralized unit CU / distributed unit DU architecture, switching between different DUs in the CU

Step 31, the CU (5G access network entity) decides to perform a zero-latency switch to a new target based on the terminal's wireless channel conditions, load conditions, or other RRM strategies, and the terminal's capabilities (whether or not it supports zero-latency switching). The cell under the DU (the target DU and the source DU are located in the same CU). The CU sends a terminal context establishment request message to the target DU, where the message optionally carries zero delay switching indication information (indicator).

Step 32: After the target DU receives the context establishment request message, the target DU performs admission control, configures radio resources, and then transmits it to the CU. Optionally, the confirmation message includes zero-latency switching indication information.

In step 33, the CU generates a corresponding RRC reconfiguration message, which not only contains zero-latency switching indication information (indicator), but also indicates that the security key does not need to be changed, and then these wireless configuration parameters are included in the terminal context modification message in the form of RRC container , Sent to the source DU, which will contain zero delay switching indication information (indicator). At the same time, the CU continues to use the original security context to encrypt / decrypt the upstream and downstream data packets transmitted between the source DU and the terminal.

In step 34, the source DU transmits the received RRC reconfiguration message (handover message) to the terminal. At the same time, the source DU continues to maintain data transmission with the terminal.

In step 35, the source DU returns a terminal context modification confirmation message.

Step 36: After the terminal receives the RRC reconfiguration message, the terminal reconfigures all related SRB / DRB bearers into Split bearer mode, and the original PDCP entity (NRPDPD for 5G) maintains the original RLC / MAC / PHY link At the same time, connect to the new target RLC / MAC / PHY link respectively.

Step 37: The terminal performs an uplink access operation to the target DU (including 37a random access preamble and 37b random access response).

Step 38: After the terminal successfully accesses the target DU, it starts to transmit an RRC reconfiguration complete message to the target DU.

Step 39: After receiving the RRC reconfiguration completion message from the terminal (that is, the handover completion message), the target DU transmits it to the CU through the uplink RRC transmission process.

Step 310: After the CU receives the RRC reconfiguration complete message from the terminal (that is, the handover complete message), at the same time, it will start to transmit the upstream and downstream data packets between the target DU and the terminal, and these data packets are still encrypted using the original security context. / Decryption processing.

Step 311, once the terminal receives an explicit or implicit indication from the target DU to determine that the terminal successfully received data using the target link, it will stop the upstream transmission and downstream reception between the source DU and the terminal, and start to release the entire source The wireless configuration on the side, such as releasing the MAC, RLC, and PHY configuration of the source DU or link, and performing the PDCP layer recovery process.

Specifically, the explicit or implicit information may be: the first downlink PDCP data packet or the first PDSCH / PDCCH channel transmission, or the first PUSCH channel (such as: RRC reconfiguration complete message) received HARQ acknowledgment / RLC ACK, or receiving a specific RRC acknowledgment message or PDCP control frame or MAC CE from the network entity (explicitly instructing the target network entity to complete data transmission with the UE);

Step 312, once the source DU decides to stop data transmission, it will send a DDDS (Uplink Data Transmission Status) message to the CU.

Step 313, the CU sends a terminal context release message to the source DU.

In step 314, the source DU returns a terminal context release response message to the CU.

Example 3: As shown in Figure 4, under the dual-connected DC architecture (including: LTE DC, EN-DC, MR-DC), handover within the secondary network entity (SgNB or SN)

Step 41: The secondary network entity (SgNB) decides to perform zero-latency handover to the target cell based on the terminal's wireless channel conditions, load status, or other RRM policies, etc., and the terminal's capabilities (whether it supports zero-latency handover); The S-NODE modification request message is sent to the main network entity (MeNB or MN). The message carries the RRC container, which contains the zero-delay handover indicator information of the auxiliary network entity, and indicates that the security key does not need to be replaced.

Step 42: After receiving it, the primary network entity sends a handover request message to the terminal. The message carries the zero-latency handover indication information (indicator) of the secondary network entity, and indicates that the security key does not need to be replaced.

Step 43: After receiving, the terminal executes the split bearer operation mode for the secondary network entity, that is, reconfigures all SRB / DRB bearers related to the secondary network entity to the split bearer mode. The original PDCP entity (NRCPPD for 5G) keeps the original While the RLC / MAC / PHY link remains unchanged, it is connected to the new target RLC / MAC / PHY link respectively.

Step 44: The terminal returns an RRC reconfiguration complete message to the main network entity.

Step 45: The main network entity (MeNB or MN) returns an S-NODE modification confirmation message to the secondary network entity (SgNB), and notifies its configuration completion.

Step 46, the terminal performs uplink access to the target cell or link operation (including 46a random access preamble and 46b random access response) for the secondary network entity.

Step 47: After receiving the RRC reconfiguration completion information (ie, S-NODE modification confirmation message) from the UE, the secondary network entity completes the access process with the terminal. The new secondary network entity cell or link and the terminal will be used to transmit uplink and downlink data packets, and these data packets will still be encrypted / decrypted using the original security context.

Step 48, once the terminal receives an explicit or implicit indication from the target cell of the secondary network entity to determine that the terminal successfully received the data using the target link, it will stop the source cell or link between the secondary network entity and the terminal. Uplink transmission and downlink reception, and start to release the wireless configuration of the entire secondary network entity source side, such as releasing the MAC, RLC, and PHY configuration of the secondary network entity source cell or link, and performing the PDCP layer recovery process of the secondary network entity.

Specifically, the explicit or implicit information may be: the first downlink PDCP data packet or the first PDSCH / PDCCH channel transmission, or the HARQ confirmation / RLC ACK of the first PUSCH channel is received, or the received A specific RRC confirmation message from the network entity or a PDCP control frame or MAC CE (explicitly instructs the SCG target cell to complete data transmission with the UE);

Step 49: The terminal continues to use the target cell or link of the new secondary network entity to perform data transmission with the network.

In summary, in the above embodiments of the present disclosure, for the zero-latency switching operation that does not require the security key to be updated, the connection between the packet data aggregation protocol PDCP entity of the terminal and the source link remains unchanged, and the PDCP of the terminal is changed. The entity is connected to the target link, and after the terminal successfully accesses the target link, the terminal uses the target link for data transmission; further after successfully receiving data using the target link, releases The connection between the terminal and the source link; thus, zero-latency switching of the terminal can be achieved, and the user experience can be improved.

As shown in FIG. 5, an embodiment of the present disclosure also provides a switching device, which is applied to a terminal and includes:

The connection module 51 is used to connect the packet data aggregation protocol PDCP entity of the terminal to the target link, and keep the connection between the terminal's PDCP entity and the source link unchanged;

The transmission module 52 is configured to use the target link for data transmission after the terminal successfully accesses the target link;

The release module 53 is configured to release the connection between the terminal and the source link after successfully receiving data using the target link.

Optionally, in the above embodiments of the present disclosure, the device further includes:

A receiving module, configured to receive a handover request message, where the handover request message carries a first indication for instructing the terminal to perform zero-delay handover and a second indication for indicating that the terminal does not need to replace the security key;

The connection module includes:

A connection submodule, configured to reconfigure the wireless bearer of the terminal into a separate bearer mode according to the handover request message;

Optionally, in the above embodiments of the present disclosure, the source link includes: at least one of a source wireless link layer RLC link, a source media access layer MAC link, and a source physical layer PHY link;

Optionally, in the above embodiments of the present disclosure, the source link and the target link are links between the terminal and different cells in the same network node;

or,

Optionally, in the above embodiments of the present disclosure, the transmission module includes:

The message sending submodule is used to send a handover complete message to the target network entity corresponding to the target link after the terminal successfully accesses the target link;

The transmission sub-module is used for data transmission with the target network entity through the target link.

The determining module is configured to determine that the terminal successfully receives data using the target link.

Optionally, in the foregoing embodiment of the present disclosure, the determination module includes:

A determination submodule, configured to determine that the terminal successfully receives data using the target link according to the indication information sent by the target network entity corresponding to the received target link, and the indication information is used to indicate that the terminal successfully receives the target Data transmitted by the network entity through the target link; or,

For receiving the first downlink PDCP data packet from the target link, and determining that the terminal successfully receives data using the target link; or,

For receiving the first physical downlink shared channel PUSCH or the first physical downlink control channel PUCCH sent by the target network entity corresponding to the target link, and determining that the terminal successfully receives data using the target link; or,

A HARQ confirmation or RLC confirmation for receiving the first automatic PUSCH from the target link to determine that the terminal successfully received data using the target link.

The receiving module is used to receive the preset radio resource control RRC message or PDCP control frame or the media intervention control layer control unit MAC CE of the target network entity corresponding to the target link;

Optionally, in the above embodiments of the present disclosure, the release module includes:

A release submodule, configured to stop the uplink and downlink transmission between the terminal and the source link after successfully receiving data using the target link, and release the wireless configuration of the source network entity corresponding to the source link

It should be noted that the switching device provided by the embodiment of the present disclosure is a switching device capable of performing the above switching method, then all the embodiments of the above switching method are applicable to the switching device, and all can achieve the same or similar beneficial effects.

As shown in FIG. 6, an embodiment of the present disclosure further provides a terminal, including: a transceiver 620, a memory 610, a processor 600, and a program stored on the memory 610 and executable on the processor 600. The processor 600 is used to read the program in the memory 610 and perform the following processes:

The transceiver 620 is configured to: use the target link for data transmission after the terminal successfully accesses the target link;

The processor 600 is also used to:

Optionally, in the foregoing embodiment of the present disclosure, the transceiver 620 is further used to:

The processor 600 is also used to:

or,

Optionally, in the foregoing embodiment of the present disclosure, the processor 600 is further used to:

In summary, in the above embodiments of the present disclosure, for the zero-latency switching operation that does not require the security key to be updated, the connection between the packet data aggregation protocol PDCP entity of the terminal and the source link remains unchanged, and the PDCP of the terminal The entity is connected to the target link, and after the terminal successfully accesses the target link, the terminal uses the target link for data transmission; further after successfully receiving data using the target link, releases The connection between the terminal and the source link; thus, zero-latency switching of the terminal can be achieved, and the user experience can be improved.

It should be noted that the terminal provided by the embodiment of the present disclosure is a terminal capable of performing the above-mentioned switching method, then all the embodiments of the above-mentioned switching method are applicable to the terminal, and all can achieve the same or similar beneficial effects.

Embodiments of the present disclosure also provide a computer-readable storage medium that stores a program on the computer-readable storage medium, and when the program is executed by a processor, implements the processes of the above-described switching method embodiments, and can achieve the same In order to avoid repetition, we will not repeat them here. Wherein, the computer-readable storage medium, such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk or optical disk, etc.

It should be noted that in this article, the terms "include", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, It also includes other elements that are not explicitly listed, or include elements inherent to such processes, methods, objects, or devices. Without more restrictions, the element defined by the sentence "include one ..." does not exclude that there are other identical elements in the process, method, article or device that includes the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods in the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware, but in many cases the former is better Implementation. Based on such an understanding, the technical solution of the present disclosure can be embodied in the form of a software product in essence or part that contributes to the existing technology, and the computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, The CD-ROM includes several instructions to enable a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present disclosure.

It can be understood that the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), digital signal processor (Digital Signal Processing, DSP), digital signal processing device (DSP Device, DSPD), programmable Logic device (Programmable Logic Device, PLD), field programmable gate array (Field-Programmable Gate Array, FPGA), general-purpose processor, controller, microcontroller, microprocessor, others for performing the functions described in this disclosure Electronic unit or its combination.

For software implementation, the technology described in the embodiments of the present disclosure may be implemented through modules (eg, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure. The software codes can be stored in the memory and executed by the processor. The memory may be implemented in the processor or external to the processor.

The embodiments of the present disclosure have been described above with reference to the drawings, but the present disclosure is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are merely schematic, not limiting, and those of ordinary skill in the art Under the inspiration of the present disclosure, many forms can be made without departing from the purpose of the present disclosure and the scope protected by the claims, all of which fall within the protection of the present disclosure.

The above is an optional embodiment of the present disclosure. It should be noted that those of ordinary skill in the art can make several improvements and retouching without departing from the principles described in the present disclosure. These improvements and Retouching should also be considered as the scope of protection of this disclosure.

Claims

A switching method applied to the terminal, including:

Connect the packet data aggregation protocol PDCP entity of the terminal to the target link, and keep the connection between the terminal's PDCP entity and the source link unchanged;

After the terminal successfully accesses the target link, the terminal uses the target link for data transmission;

After successfully receiving data using the target link, the connection between the terminal and the source link is released.
The method of claim 1, further comprising:

Receiving a handover request message, where the handover request message carries a first indication for instructing the terminal to perform zero-delay handover and a second indication for indicating that the terminal does not need to replace the security key;

The connection of the PDCP entity of the terminal's packet data aggregation protocol to the target link and keeping the connection of the terminal's PDCP entity and the source link unchanged include:

Reconfiguring the wireless bearer of the terminal into a separate bearer mode according to the handover request message;

Wherein, in the separate bearer mode, the PDCP entity corresponding to the wireless bearer is configured such that the connection with the source link is unchanged and the target link is connected.
The method of claim 1, wherein the source link comprises: at least one of a source radio link layer RLC link, a source media access layer MAC link, and a source physical layer PHY link;

The target link includes at least one of a target RLC link, a target MAC link, and a target PHY link.
The method according to claim 2, wherein

The source link and the target link are links between the terminal and different cells in the same network node;

or,

The source link and the target link are different links between the terminal and the same cell in the same network node.
The method according to claim 1, wherein, after the terminal successfully accesses the target link, the terminal uses the target link for data transmission, including:

After the terminal successfully accesses the target link, send a handover complete message to the target network entity corresponding to the target link;

Perform data transmission with the target network entity through the target link.
The method according to claim 1, wherein, after successfully receiving data using the target link, before releasing the connection between the terminal and the source link, the method further comprises:

It is determined that the terminal successfully receives data using the target link.
The method according to claim 6, wherein the determining that the terminal successfully receives data using the target link includes:

Determine, according to the received indication information sent by the target network entity corresponding to the target link, that the terminal successfully receives data using the target link, and the indication information is used to indicate that the terminal successfully receives the target network entity through the target Data transmitted by the link; or,

Receiving the first downlink PDCP data packet from the target link, and determining that the terminal successfully receives data using the target link; or,

Receiving the first physical downlink shared channel PUSCH or the first physical downlink control channel PUCCH sent by the target network entity corresponding to the target link, and determining that the terminal successfully receives data using the target link; or,

Upon receiving the HARQ confirmation or RLC confirmation of the first PUSCH hybrid automatic retransmission request from the target link, it is determined that the terminal successfully receives data using the target link.
The method of claim 7, further comprising:

Receive the preset radio resource control RRC message or PDCP control frame or media intervention control layer control unit MAC of the target network entity corresponding to the target link;

The preset RRC message or PDCP control frame or MAC CE carries the indication information.
The method according to claim 1, wherein, after successfully receiving data using the target link, releasing the connection between the terminal and the source link includes:

After successfully receiving data using the target link, stop the uplink and downlink transmission between the terminal and the source link, and release the wireless configuration of the source network entity corresponding to the source link.
A switching device, applied to a terminal, includes:

The connection module is used to connect the packet data aggregation protocol PDCP entity of the terminal to the target link, and keep the connection between the terminal's PDCP entity and the source link unchanged;

A transmission module, configured to use the target link for data transmission after the terminal successfully accesses the target link;

The release module is configured to release the connection between the terminal and the source link after successfully receiving data using the target link.
A terminal includes: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; wherein, the processor is used to read the program in the memory and perform the following processes:

Connect the packet data aggregation protocol PDCP entity of the terminal to the target link, and keep the connection between the terminal's PDCP entity and the source link unchanged;

The transceiver is used to: after the terminal successfully accesses the target link, use the target link for data transmission;

The processor is also used to:

After successfully receiving data using the target link, the connection between the terminal and the source link is released.
The terminal according to claim 11, wherein the transceiver is further used to:

Receiving a handover request message, where the handover request message carries a first indication for instructing the terminal to perform zero-delay handover and a second indication for indicating that the terminal does not need to replace the security key;

The processor is also used to:

Reconfiguring the wireless bearer of the terminal into a separate bearer mode according to the handover request message;

Wherein, in the separate bearer mode, the PDCP entity corresponding to the wireless bearer is configured such that the connection with the source link is unchanged and the target link is connected.
The terminal according to claim 11, wherein the source link comprises: at least one of a source wireless link layer RLC link, a source media access layer MAC link, and a source physical layer PHY link;

The target link includes at least one of a target RLC link, a target MAC link, and a target PHY link.
The terminal according to claim 12, wherein

The source link and the target link are links between the terminal and different cells in the same network node;

or,

The source link and the target link are different links between the terminal and the same cell in the same network node.
The terminal according to claim 11, wherein the transceiver is further used to:

After the terminal successfully accesses the target link, send a handover complete message to the target network entity corresponding to the target link;

Perform data transmission with the target network entity through the target link.
The terminal according to claim 11, wherein the processor is further configured to:

It is determined that the terminal successfully receives data using the target link.
The terminal according to claim 16, wherein the processor is further configured to:

Determine, according to the received indication information sent by the target network entity corresponding to the target link, that the terminal successfully receives data using the target link, and the indication information is used to indicate that the terminal successfully receives the target network entity through the target Data transmitted by the link; or,

Receiving the first downlink PDCP data packet from the target link, and determining that the terminal successfully receives data using the target link; or,

Receiving the first physical downlink shared channel PUSCH or the first physical downlink control channel PUCCH sent by the target network entity corresponding to the target link, and determining that the terminal successfully receives data using the target link; or,

Upon receiving the HARQ confirmation or RLC confirmation of the first PUSCH hybrid automatic retransmission request from the target link, it is determined that the terminal successfully receives data using the target link.
The terminal according to claim 17, wherein the transceiver is further used to:

Receive the preset radio resource control RRC message or PDCP control frame or media intervention control layer control unit MAC of the target network entity corresponding to the target link;

The preset RRC message or PDCP control frame or MAC CE carries the indication information.
The terminal according to claim 11, wherein the processor is further configured to:

After successfully receiving data using the target link, stop the uplink and downlink transmission between the terminal and the source link, and release the wireless configuration of the source network entity corresponding to the source link.
A computer-readable storage medium, wherein a program is stored on the computer-readable storage medium, and when the program is executed by a processor, the steps of the switching method according to any one of claims 1 to 9 are realized.