BR112019025745A2 - DELIVERY METHOD AND TERMINAL DEVICE - Google Patents

Abstract

Revealed by the embodiments of the present application are a switching method, an access network device and a terminal device, the method comprising: a first access network device triggering a terminal device and/or a second network device to configure a second protocol stack, where the second protocol stack is used to maintain order of data packets from the second access network device and the terminal device and/or a key of data packets from the second device access network and terminal device; before the first access network device triggers the terminal device and/or the second access network device to use the second protocol stack to maintain the order of the terminal device's data packets, the first access network device with the use of a first protocol stack to sequence data packets to be processed from the first access network device and the end device. The method, access network device and terminal device of the embodiments of the present application facilitate the reduction of delay in data transmission to the terminal device in a switching process.

Description

DELIVERY METHOD AND TERMINAL DEVICE FIELD OF TECHNIQUE

[0001] Disclosure modalities refer to the field of communication and, more particularly, to a handover method, an access network device and a terminal device.

BACKGROUND

[0002] A handover flow in an existing Long Term Evaluation (LTE) system is as follows. A source access network device sends a handover request to a destination access network device, according to a measurement report reported by an end device, and after receiving a response to the handover request from the target access network device, sends a handover command to the terminal device. The terminal device performs reconfiguration according to the handover command, exits a source cell, and performs synchronization with a target cell. For data between the end device and the source access network device, the source access network device is required to transmit cached data to the destination access network device, and the data can be processed only when the synchronization between the target access network device and the endpoint device is complete. For this data, a relatively long wait delay is required in a handover process of the terminal device.

SUMMARY

[0003] In view of this, the embodiments of the disclosure provide a handover transfer method, an access network device and a terminal device, which are favorable for reducing a delay in the transmission of data from a terminal device in a transfer process. by handover.

[0004] In a first aspect, a handover handover method is provided, which includes: a first access network device triggers at least one of a terminal device or a second access network device to configure a second protocol stack , wherein the second protocol stack is configured to maintain at least one of a sequence of data packets between the second access network device and the terminal device or a security key of the data packets between the second network device of access and the terminal device; and before the first access network device triggers at least one terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack, the first network device of access sequentially processes data packets to be processed between the first access network device and the end device using a first protocol stack.

[0005] A data packet usually consists of a header and a data part, where the header is a label for a receiver to recognize and the data part is raw data. In the embodiments of the disclosure, the data packet may include, without limitation, a Data Protocol Unit (PDCP) of the Packet Data Convergence Protocol (PDCP)

and the data portion may include, without limitation, a PDCP Service Data Unit (SDU).

[0006] Optionally, the first access network device can trigger only a first terminal device. For example, when the first endpoint device passes into coverage of the second access network device connected to a second endpoint device and the first endpoint device can form a Device-to-Device (D2D) connection with the second endpoint device, the first endpoint device network can trigger the first endpoint device and the first endpoint device can trigger the second network device through the second endpoint device to configure a new protocol stack.

[0007] Optionally, the first access network device can also trigger only the second access network device. For example, when the first end device passes into the coverage of the second access network device connected to the second end device and the first end device can form the D2D connection with the second end device, the first network device can trigger the second end device. network, and the second network device can trigger the first endpoint device through the second endpoint device to configure a new protocol stack.

[0008] Optionally, the operation where the first access network device triggers the endpoint device and the second access network device to configure the second protocol stack includes: the first access network device sends the first trigger information for the second access network device, wherein the first trigger information is configured to prompt the second access network device to configure the second protocol stack; the first access network device receives information responding to the first trigger information from the second access network device; and the first access network device sends the second trigger information to the terminal device in accordance with the response information, wherein the second trigger information is configured to instruct the terminal device to configure the second protocol stack.

[0009] The sequence of data packets continues to be maintained by the old protocol stack before the first access network device triggers at least one of the terminal device or the second access network device to fully use the new protocol stack , so that data from the terminal device can be processed in a timely manner, and a delay in transmitting data from the terminal device in a handover transfer process is reduced.

[0010] In a possible deployment, the data packets to be processed may include the first data packets, and the operation where the first access network device sequentially processes the data packets to be processed between the first network device access device and the terminal device using the first protocol stack before the first access network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack may include that: before the first access network device triggers at least one of the endpoint device or the second access network device to maintain the sequence of data packets from the endpoint device with the using the second protocol stack, the first access network device receives the first data packets sent by the device ends l; the first access network device decrypts the first data packets or a piece of data in each of the first data packets using the first protocol stack; and the first access network device sequentially processes the first data packets decrypted using the first protocol stack.

[0011] In a possible deployment, the data packets to be processed may include second data packets and the operation that the first access network device sequentially processes the data packets to be processed between the first access network device and the terminal device using the first protocol stack before the first access network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device via the Use of the second protocol stack may include that: before the first access network device triggers at least one endpoint device or the second access network device to maintain the sequence of data packets from the endpoint device using the second stack protocol, the first access network device receives a piece of data in each of the second data packets sent by a main network device and the first access network device sequentially process the second data packets using the first protocol stack. The method may further include that: the first access network device encrypts the second sequentially processed data packets or the data portion in each of the second data packets using the first protocol stack.

[0012] In a possible deployment, the data packets to be processed may include third party data packets and the operation where the first access network device sequentially processes the data packets to be processed between the first access network device and the terminal device using the first protocol stack before the first access network device triggers at least one terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack may include that: before the first access network device triggers at least one of the end device or the second access network device to maintain the sequence of data packets from the end device using the second stack protocol, the first access network device receives the third data packets sent by the second access network device. cess, the third data packets or a piece of data in each of the third data packets being decrypted by the second access network device using the second protocol stack; and the first access network device sequentially processes the third decrypted data packets.

[0013] In a possible deployment, the data packets to be processed may include fourth data packets, and the operation where the first access network device sequentially processes the data packets to be processed between the first access network device access and the endpoint device using the first protocol stack before the first access network device triggers at least one endpoint device or the second access network device to maintain the sequence of data packets from the endpoint device using of the second protocol stack may include that: before the first access network device triggers at least one terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack protocol, the first access network device receives a piece of data in each of the fourth data packets sent by a device network and the first access network device sequentially processes the fourth data packets using the first protocol stack. The method may further include that: the first access network device sends the fourth sequentially processed data packets to the second access network device such that the second access network device encrypts the fourth sequentially processed data packets or the data part in each of the fourth data packets using the second protocol stack.

[0014] In a possible deployment, the method may further include that: under the condition that the first access network device determines that it is not necessary that it is not necessary that any data packets or data from the terminal device be processed by the first access network device, the first access network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack.

[0015] In one possible deployment, the operation where the first access network device triggers the endpoint device to keep the data packets from the endpoint device sequence using the second protocol stack under the condition that the first device access network device determines that it is not necessary for any data packets or data from the endpoint device to be processed by the first access network device may include that: under the condition that the first access network device determines that it is not necessary that no data packets or data from the terminal device are processed by the first access network device, the first access network device sends the first indication information to the terminal device, where the first indication information is configured to instruct the terminal device to maintain the sequence of data packets from the terminal device using the second pr stack otocol.

[0016] In a possible deployment, the first indication information can still be configured to instruct the terminal device to release the first protocol stack.

[0017] In a possible deployment, the first indication information could be any RRC (Radio Resource Control) signaling, RRC signaling,

Media Access (MAC), Downlink Control (DCI) information, or a bit in a data packet.

[0018] In a possible deployment, the operation where the first access network device triggers the second access network device to maintain the sequence of data packets from the terminal device, with the use of the second protocol stack under the condition that the first access network device determines that it is not necessary for any of the data packets or data from the terminal device to be processed by the first access network device may include that: under the condition that the first access network device determines that no data packets from the terminal device are required to be processed by the first access network device, the first access network device sends second indication information to the second access network device, wherein the second access network device indication are configured to instruct the second access network device to keep the sequence of data packets from the terminating device. al using the second protocol stack.

[0019] In a possible deployment, the method may further include that: the first access network device determines that no data packets from the terminal device are required to be processed by the first access network device.

[0020] In a possible deployment, the operation where the first access network device determines that it is not necessary for any data packets or data from the terminal device to be processed by the first access network device may include that: the first device access network device receives third indication information sent by the main network device, wherein the third indication information to indicate that no data packet from the terminal device is required to be processed by the first access network device; and the first access network device determines, in accordance with the third indication information, that it is not necessary for any data packets or data from the terminal device to be processed by the first access network device.

[0021] The third indication information can be an end marker.

[0022] In a possible deployment, the method may further include that: the first access network device receives the fourth indication information sent by the second access network device, where the fourth indication information indicates that the terminal device has completed the configuration of the second protocol stack; and the first access network device sends path switching information to the main network device in accordance with the fourth indication information, the path switching information being configured to instruct the main network device to switch a network device of access, responsible for maintaining the sequence of data packets from the terminal device, from the first access network device to the second access network device.

[0023] Optionally, in a possible deployment, the operation where the first access network device receives the third indication information sent by the main network device may include that: after the first access network device sends the information of switching path to the main network device, the first access network device receives the third indication information sent by the main network device.

[0024] In a possible deployment, the first access network device may be a source access network device and the second access network device may be a target access network device; or the first access network device can be a primary access network device in a multi-connect scenario and the second access network device can be a secondary access network device in a multi-connect scenario.

[0025] In a second aspect, a handover transfer method is provided, which includes: a second access network device receives the first trigger information sent through a first access network device, where the first trigger are configured to trigger the second access network device to configure a second protocol stack and wherein the second protocol stack is configured to maintain at least one of a sequence of data packets between the second access network device and a terminal device or a security key for data packets between the second access network device and the terminal device; and the second access network device receives the second trigger information sent by the first access network device, wherein the second trigger information is configured to trigger the second access network device to maintain the sequence of data packets from the access network device. terminal device using the second protocol stack.

[0026] In a possible deployment, the method may further include that: before the second access network device receives the second trigger information sent by the first access network device, the second access network device receives a first packet of sequentially processed and encrypted data sent by the first access network device; and the second access network device forwards the first sequentially processed and encrypted data packets to the terminal device.

[0027] In a possible deployment, the method may further include that: before the second access network device receives the second trigger information sent by the first access network device, the second access network device receives a second packet of sequentially processed data sent by the first access network device; the second access network device encrypts the second data packets or a piece of data in each of the second data packets using the second protocol stack; and the second access network device sends the second encrypted data packets to the end device.

[0028] In a possible deployment, the method may further include that: before the second access network device receives the second trigger information sent by the first access network device, the second access network device receives third party packets. data sent by the terminal device; and the second access network device forwards the third data packets to the first access network device such that the first access network device sequentially decrypts and processes the third data packets or a piece of data in each of third-party data packets.

[0029] In a possible deployment, the method may further include that: before the second access network device receives the second trigger information sent by the first access network device, the second access network device receives the fourth packets of data sent by the terminal device; the second access network device decrypts the fourth data packets or a portion of data in each of the fourth data packets using the second protocol stack; and the second access network device sends the fourth decrypted data packets to the first access network device such that the first access network device sequentially processes the fourth decrypted data packets.

[0030] In a possible deployment, the method may further include that: the second access network device receives the first indication information sent by the terminal device, where the first indication information indicates that the terminal device has completed the configuration of the second protocol stack; and the second access network device sends path switching information to a main network device in accordance with the first indication information or the second access network device triggers the first access network device to send the switching information path to the main network device according to the first indication information, where the path switching information is configured to instruct the main network device to switch an access network device by maintaining the sequence of data packets from the main network device. terminal device from the first access network device to the second access network device.

[0031] In a possible deployment, the second trigger information can be any RRC signaling, MAC signaling, DCI or a bit in a data packet.

[0032] In a possible deployment, the first access network device may be a source access network device and the second access network device may be a target access network device; or the first access network device can be a primary access network device in a multi-connect scenario and the second access network device can be a secondary access network device in a multi-connect scenario.

[0033] In a third aspect, a handover transfer method is provided, which includes that: a terminal device configures a second protocol stack according to the first trigger information sent through a first access network device, in that the second protocol stack is configured to maintain at least one of a sequence of data packets between a second access network device and the endpoint device or a security key of data packets between the second access network device and the terminal device; and before the terminal device receives the second trigger information sent by at least one of the first access network device or the second access network device, the terminal device sequentially processes data packets to be processed from the terminal device with the use of a first protocol stack, where the second trigger information is configured to trigger the end device to maintain the sequence of data packets from the end device using the second protocol stack.

[0034] In a possible deployment, the data to be processed may include the first data, and the operation where the terminal device sequentially processes the data packets or data to be processed from the terminal device using the first protocol stack before the end device receiving the second trigger information sent by at least one of the first access network device or the second access network device may include the end device sequentially processing the first data using the first protocol stack . The method may further include that: the terminal device encrypts the first data or data packets processed sequentially, including the first data, using the first protocol stack, and the terminal device sends the encrypted data packets, including the first data to at least one of the first access network device or the second access network device.

[0035] In a possible deployment, the data packets to be processed may include the first data packets and the operation in which the terminal device sequentially processes the data packets or data to be processed from the terminal device, using the first protocol stack before the terminal device receives the second trigger information sent by at least one of the first access network device or the second access network device may include that: before the terminal device receives the second trigger information sent by at least one of the first access network device or the second access network device, the terminal device receives the first data packets sent by at least one of the first access network device or the second network device of access; the terminal device decrypts the first data packets or a piece of data in each of the first data packets using the first protocol stack; and the terminal device sequentially processes the first data packets decrypted using the first protocol stack.

[0036] In a possible deployment, the data to be processed may include second data, and the operation where the terminal device sequentially processes the data packets or data to be processed from the terminal device using the first protocol stack before the terminal device receiving the second trigger information sent by at least one of the first access network device or the second access network device may include the terminal device sequentially processing the second data using the first protocol stack. The method may further include that: the terminal device encrypts the second data or sequentially processed data packets, including the second data, using the second protocol stack, and the terminal device sends the encrypted data packets, including the second data to the second access network device.

[0037] In a possible deployment, the data packets to be processed may include second data packets and the operation that the terminal device sequentially processes the data packets or data to be processed from the terminal device, using the first stack of protocol before the end device receives the second trigger information sent by at least one of the first access network device or the second access network device may include that: the end device receives the second data packets sent by the second device network; the terminal device decrypts the second data packets or a piece of data in each of the second data packets using the second protocol stack; and the terminal device sequentially processes the second data packets decrypted using the first protocol stack.

[0038] In a possible implementation, the method may further include that: the terminal device receives the second trigger information sent by at least one of the first access network device or the second access network device; and the end device maintains the sequence of data packets from the end device using the second protocol stack in accordance with the second trigger information.

[0039] In a possible deployment, the second trigger information may still be configured to instruct the terminal device to release the first protocol stack, and the method may further include that: the terminal device releases the first protocol stack in accordance with the second trigger information.

[0040] In a possible deployment, the second trigger information can be any RRC signaling, MAC signaling, DCI or a bit in a data packet.

[0041] In a possible deployment, the first access network device may be a source access network device and the second access network device may be a target access network device; or the first access network device can be a primary access network device in a multi-connect scenario and the second access network device can be a secondary access network device in a multi-connect scenario.

[0042] In a fourth aspect, an access network device is provided, configured to perform the method in the first aspect or any possible implementation of the first aspect. Specifically, the access network device includes units configured to perform the method in the first aspect or any possible implementation of the first aspect.

[0043] In a fifth aspect, an access network device is provided, configured to perform the method in the second aspect or any possible implementation of the second aspect. Specifically, the access network device includes units configured to perform the method in the second aspect or any possible implementation of the second aspect.

[0044] In a sixth aspect, a terminal device is provided, which is configured to execute the method in the third aspect or any possible implementation of the third aspect. Specifically, the endpoint device includes units configured to run the method in the third aspect or any possible implementation of the third aspect.

[0045] In a seventh aspect, an access network device is provided, which includes a memory, a processor, an input interface and an output interface. Memory, processor, input interface and output interface are connected through a bus system. Memory is configured to store an instruction. The processor is configured to execute instructions stored in memory to execute the method in the first aspect or any possible implementation of the first aspect.

[0046] In an eighth aspect, an access network device is provided, which includes a memory, a processor, an input interface and an output interface. Memory, processor, input interface and output interface are connected through a bus system. Memory is configured to store an instruction. The processor is configured to execute the instruction stored in memory to execute the method in the second aspect or any possible implementation of the second aspect.

[0047] In a ninth aspect, a terminal device is provided, which includes a memory, a processor, an input interface and an output interface. Memory, processor, input interface and output interface are connected through a bus system. Memory is configured to store an instruction. The processor is configured to execute the instruction stored in memory to execute the method in the third aspect or any possible implementation of the third aspect.

[0048] In a tenth aspect, a computer storage medium is provided, configured to store a computer software instruction to perform the method in the first aspect or any possible implementation of the first aspect, or the method in the second aspect or any implementation possible implementation of the second aspect, or the method in the third aspect, or any possible implementation of the third aspect, wherein the instruction includes a program designed to perform the above aspects.

[0049] In an eleventh aspect, a computer program product is provided, including an instruction, when executed on a computer, the computer program product causes the computer to execute the method in the first aspect or any deployment optional aspect of the first aspect, or the method in the second aspect or in any optional implementation of the second aspect, or the method in the third aspect or any optional implementation of the third aspect.

[0050] These or other aspects of the revelation will become clearer and easier to understand through the following descriptions of the modalities.

BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 is a schematic diagram showing an application scenario of a disclosure modality.

[0052] Figure 2 is a schematic diagram showing another application scenario of a disclosure modality.

[0053] Figure 3 is a schematic flowchart showing an LTE handover handover.

[0054] Figure 4 is a schematic block diagram showing a handover transfer method according to an embodiment of the disclosure.

[0055] Figure 5 is a block diagram showing a protocol stack deployment for a handover method according to an embodiment of the disclosure.

[0056] Figure 6 is a block diagram showing another implementation of a protocol stack for a handover method according to an embodiment of the disclosure.

[0057] Figure 7 is a block diagram showing yet another implementation of a protocol stack for a handover method according to an embodiment of the disclosure.

[0058] Figure 8 is a block diagram showing yet another implementation of a protocol stack for a handover method according to an embodiment of the disclosure.

[0059] Figure 9 is another schematic block diagram of a handover transfer method according to an embodiment of the disclosure.

[0060] Figure 10 is yet another schematic block diagram of a handover transfer method according to an embodiment of the disclosure.

[0061] Figure 11 is a schematic block diagram of an access network device according to an embodiment of the disclosure.

[0062] Figure 12 is another schematic block diagram of an access network device according to an embodiment of the disclosure.

[0063] Figure 13 is a schematic block diagram of a terminal device in accordance with an embodiment of the disclosure.

[0064] Figure 14 is yet another schematic block diagram of an access network device according to an embodiment of the disclosure.

[0065] Figure 15 is yet another schematic block diagram of an access network device in accordance with an embodiment of the disclosure.

[0066] Figure 16 is another schematic block diagram of a terminal device in accordance with an embodiment of the disclosure.

DETAILED DESCRIPTION

[0067] The technical solutions in the development modes will be clearly and completely described below in combination with the drawings in the development modes.

[0068] It should be understood that the technical solutions in the disclosure modalities can be applied to various communication systems, for example, a Global Mobile Communication System (GSM), a CDMA (Code Division Multiple Access) system, a Code Division Multiple Access (WCDMA), a GPRS (General Packet Radio Service), an LTE system, an LTE Frequency Division Duplexing (FDD) system,

LTE Time Division Duplexing (TDD), a Universal Mobile Telecommunications System (UMTS), a World Wide Interoperability System for Microwave Access (WiMAX), a New Radio (NR) system, or a 5th generation system ( 5G) future.

[0069] Particularly, the technical solutions in the disclosure modalities can be applied to various non-orthogonal multiple access technology-based communication systems, for example, a sparse code multiple access (SCMA) system or a signature system. density (LDS), and of course the SCMA system and the LDS system may also have other names in the field of communication. Furthermore, the technical solutions in the disclosure modalities can be applied to a multi-carrier transmission system that adopts non-orthogonal multiple access technology, e.g. Orthogonal Frequency Division Multiplexing (OFDM), Multi-carrier Filter Bank (FBMC), Generalized Frequency Division Multiplexing (GFDM) and Filtered OFDM (F-OFDM) systems adopting non-orthogonal multiple access technologies.

[0070] In the embodiments of the disclosure, a terminal device may refer to User Equipment (UE), an access terminal, a user unit, a user station, a mobile station, mobile radio station, remote station, terminal remote, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The access terminal can be a cell phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant

(PDA), a handheld device with a wireless communication function, a computer device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device on a future 5G network, a terminal device in a future-evolved Public Land Mobile Network (PLMN) or similar, which is not limited in the disclosure modalities.

[0071] In the development modes, a network device can be a device configured to communicate with the terminal device. The network device can be a Base Transceiver Station (BTS) in GSM or CDMA, it can also be a NodeB (NB) in WCDMA system, it can also be an Evolutionary Node B (eNB or eNodeB) in LTE system, and it can further , be a wireless controller in a Cloud Radio Access Network (CRAN) scenario. The network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in the future 5G network, a network device in the future PLMN evolved or similar, which is not limited in the modalities of disclosure.

[0072] Figure 1 is a schematic diagram showing an application scenario of a disclosure modality. A communication system in Figure 1 may include a terminal device 120 and a network device 110. The network device 110 is configured to provide a communication service for the terminal device 120 to access a main network. End device 120 looks for a synchronization signal, a broadcast signal and the like sent by network device 110 to access the network, thereby communicating with the network. Arrows shown in Figure 1 may represent uplink/downlink transmission deployed over a cellular link between end device 120 and network device 110.

[0073] Figure 2 is a schematic diagram showing another application scenario of a disclosure modality. Access network devices around a terminal device 230 in Figure 2 include a primary access network device 210 and at least one secondary access network device 220. The at least one secondary access network device 220 is connected to the primary access network device 210, respectively, to form various connections, and is connected to the terminal device 230 to provide service thereto, respectively. Primary access network device 210 may be an LTE network and secondary access network device 220 may be an NR network. Alternatively, primary access network device 210 may be an NR network, and secondary access network device 220 may be an LTE network. Alternatively, primary access network device 210 and secondary access network device 220 are NR networks. The application scenarios of the technical solutions are not limited in the disclosure. The terminal device 230 can establish connections simultaneously with the primary access network device 210 and the secondary access network device 220. The connection established between the terminal device 230 and the primary access network device 210 is a primary connection and the The connection established between the terminal device 230 and the secondary access network device 220 is a secondary connection. Control signaling to the terminal device 230 may be transmitted over the primary connection, and the data to the terminal device may be transmitted simultaneously through the primary connection and the secondary connection, and may also be transmitted only through the secondary connection.

[0074] In the embodiments of the disclosure, the primary access network device can be, for example, a Macrocell, and the secondary access network device can be, for example, a Microcell, Pico-cell or Femto-cell . However, the modalities of revelation are not limited to this.

[0075] More specifically, the primary access network device can be an LTE network device and the secondary access network device is an NR network device. It must be understood that the modalities of revelation are not limited to this. The primary access network device can also be a GSM network device, a CDMA network device, and the like. The secondary access network device may also be a GSM network device, a CDMA network device and the like, which is not limited in the embodiments of the disclosure.

[0076] In the embodiments of the disclosure, a main network device can be a Mobility Management Entity (MME) and can also be a Server Communication Port (S-GW) or a Packet Data Network Port (P- GW), which is not limited in revelation.

[0077] For ease of understanding, a handover flow in an LTE system will be described below in combination with Figure 3 in detail. As shown in Figure 3, the handover transfer flow includes part or all of the following steps.

[0078] In 1, a source eNB transmits a measurement configuration to the UE, where a measurement result from the UE is used to assist the source eNB in executing the handover decision.

[0079] In 2, the UE reports a metering report according to the metering configuration.

[0080] In 3, the source eNB executes the handover decision according to its own handover algorithm with reference to a measurement result reported by the UE.

[0081] In 4, the source eNB sends a handover request message to a destination eNB, where the message includes information about a preparation for handover transfer, mainly including an X2/UE signaling context reference S1, an identifier of a target cell, a security key, an RRC context, an Access Layer (AS) configuration, an Evolved Universal Terrestrial Radio Access context (E-UTRAN) Radio Access Carrier ( E-RAB) and the like. The message also includes a Physical Identifier (PHY) of a source cell and a message authentication and verification code for a possible recovery process after a failed handover transfer. The UE X2/S1 signaling context reference can help the destination eNB to find a position of the source eNB. The E-RAB context includes required radio network layer (RLN) and transport network layer (TNL) address information, E-RAB quality of service (QoS) information, and the like.

[0082] At 5, the destination eNB performs admission control according to the information received from E-RAB QoS to increase a successful handover throughput. For admission control, reservation of a corresponding resource, a Temporary Cellular Radio Network Identifier (C-RNTI), allocation of a dedicated random access preamble, and the like must be considered. The AS configuration for a target cell can be a complete configuration completely independent of a source cell, and it can also be an incremental configuration based on the source cell (incremental configuration refers to the same part not being configured, just a different part is reconfigured through signaling, and the UE will continue to use the original configuration for the configuration that was not received).

[0083] At 6, the destination eNB makes Layer 1 (L1)/Layer 2 (L2) handover preparations and simultaneously sends a handover request acknowledgment (ACK) message to the source eNB . The message includes an RRC container and specific content is a handover command that triggers the UE to perform the delivery. The source eNB sends the handover command to the UE in a broadcast transparent manner (without any modification). The handover command includes a new C-RNTI and a case algorithm identifier of the target eNB, and may also contain the dedicated random access preamble, an access parameter, system information, and the like. If necessary, the handover request ACK message can still contain the RNL/TNL information for forwarding data. After the source eNB receives the ACK message of the handover request or forwards the handover command to the UE, data forwarding can be started.

[0084] In 7, the handover command (an RRC connection reconfiguration message containing mobility control information) is generated by the destination eNB and transmitted transparently to the UE through the source eNB. The source eNB performs necessary encryption and integrity protection on the message. The UE, after receiving the message, can initiate a handover process using a related parameter in the message. The UE can initiate the handover process without waiting for a hybrid auto-repeat request (HARQ)/auto-repeat request (ARQ) response sent to the source eNB by a lower layer.

[0085] In 8, the source eNB sends a Sequence Number (SN) status broadcast message to the destination eNB to transmit an uplink SNP PDCP receive status and an uplink SNP PDCP send status. downlink of an E-RAB. The uplink SNP PDCP receive situation includes at least one PDCP SNP from a last uplink SDU received in sequence and may also include SNs from lost uplink SDUs that cause out-of-order reception and are represented in a form of bit mapping (if such SDUs exist, it may be necessary for these SDUs to be retransmitted by the UE in the destination cell). The downlink SNP PDCP send status indicates a serial number of an upcoming SDU that must be allocated by the destination eNB. If there is no E-RAB that needs to send a PDCP status report, the originating eNB can omit the message.

[0086] At 9, the UE, after receiving the handover transfer command, performs synchronization with the target cell. If the dedicated random access preamble is configured in the handover command, a contention-free random access procedure is used to access the target cell. If no dedicated preamble is configured, a contention-based random access procedure is used to access the target cell. The UE calculates a key that must be used by the destination eNB and configures a security algorithm selected by a network to be used by the destination eNB to communicate with the destination eNB after successful transfer.

[0087] At 10, the network returns an uplink resource allocation indication and a timing advance.

[0088] At 11, after the UE successfully accesses the destination cell, the UE sends an RRC connection reconfiguration complete message to the destination eNB to confirm that the handover process has been completed. If sufficient resources are available, the message may also be accompanied by an uplink Uplink Status Report (BSR) improvement. The destination eNB receives the complete RRC connection reconfiguration message to confirm successful transfer. The destination eNB can then start sending data to the UE.

[0089] At 12, the destination eNB sends a path switching request message to an MME to notify that the UE has been delivered to another cell. In this case, the radio handover completed successfully.

[0090] On 13, the MME sends a user plan update request message to an S-GW.

[0091] At 14, the S-GW switches a downlink data path to one side of the destination eNB. The S-GW sends one or more “end marker packets” to the source eNB through an old path, and then a resource in the source eNB's user plane can be released.

[0092] On 15, the S-GW sends a User Plan Update Reply message to the MME.

[0093] At 16, the MME sends a path switching request ACK message to the destination eNB. A path switching process completes between 12 and 16 and this process is performed to switch a user plane data path from the source eNB to the destination eNB. After the S-GW switches the downlink path, data packets from one forwarding path and a new path can alternately arrive at the destination eNB. The destination eNB must transmit all data packets forwarded to the UE first and then transmit packets received from the new path. Adopting this method for the target eNB can forcefully guarantee a correct transmission sequence. To assist a rebalancing function on the destination eNB, after the E-RAB path switches, the S-GW immediately sends one or more “end marker packets” on the old path. The “end marker package” does not include user data and is indicated by a General Data Transfer Platform (GTP) header. After completing sending the packet with a marker, the S-GW should not send any data packets in the old path. After receiving the “end marker packet”, if forwarding is active for that carrier, the source eNB must send the packet to the destination eNB. After detecting the “End Marker Packet”, the destination eNB must discard the “End Marker Packet” and start any flow necessary to keep sending a user sequentially, and the data is forwarded over an X2 interface or received from the S - GW via an S1 interface after path switching.

[0094] At 17, the destination eNB sends a UE context release message to the source eNB to notify the source eNB of the successful transfer and trigger the source eNB to release resources. The destination eNB, after receiving the path-switching ACK message returned by the MME, sends the message.

[0095] In 18, the originating eNB, after receiving the context release message from the UE, can release a radio bearer and a control plane resource related to a UE context. Any data forwarding in progress is continued.

[0096] As shown in Figure 3, after the source eNB sends the RRC connection reconfiguration message to the UE, the UE can leave a source cell and perform synchronization with the destination cell, i.e. the UE can disconnect a network connection from the source eNB. For data between the UE and the source eNB, the source eNB is required to transmit cached data to the destination eNB, and the data can be processed until a carrier between the destination eNB and the UE is established. For such data, a relatively long wait delay is required in the UE handover process. For the UE, the time to disconnect the UE from the network is also relatively long and a service from the UE may not be processed in a timely manner, so the network transmission performance is relatively low.

[0097] Figure 4 is a schematic block diagram showing a handover method 300 in accordance with an embodiment of the disclosure. As shown in Figure 4, method 300 includes part or all of the content in the following operations.

[0098] At the S310, a first access network device triggers a terminal device and/or a second access network device to configure a second protocol stack, wherein the second protocol stack is configured to maintain a sequence of packets of data between the second access network device and the terminal device and/or a security key of the data packets between the second access network device and the terminal device.

[0099] At S320, before the first access network device triggers the end device and/or the second access network device to maintain the sequence of data packets from the end device using the second protocol stack, the first access network device sequentially processes data packets to be processed between the first access network device and the terminal device using a first protocol stack.

[0100] Those skilled in the art understand that a data packet generally consists of a header and a data part, the header is a label for a receiver to recognize and the data part is raw data. In the development mode, the data packet can include, without limitation, a PDCP PDU. Henceforth, the data packet in the development mode is, for example, a PDCP PDU and the data part in the data packet in the development mode is an SDU. The modality of revelation is not limited to this.

[0101] Optionally, the disclosure modality technical solution can not only be applied to a single-link handover scenario in Figure 1, but can also be applied to a multi-connection role switching scenario in Figure 2. For the sake of description, the technical solution of method 100 will be briefly presented below with the single sign-on handover scenario as an example at first.

[0102] Specifically, the first access network device, i.e. a source access network device, may trigger the terminal device and/or the second access network device, i.e. an access network device destination, to configure the second protocol stack (referred to as the new protocol stack hereinafter) according to part or all of steps 1 through 7 in the handover transfer flow shown in Figure

3. The new protocol stack includes a PDCP layer/Radio Link Control (RCL) layer/MAC layer/PHY layer. The PDCP layer of the new protocol stack can maintain a sequence of sending or receiving PDCP PDUs and a security key of PDCP PDUs. That is, after the endpoint device is delivered to the second access network device, a data packet can be transmitted between the endpoint device and the second access network device using the new protocol stack. In the disclosure mode,

by triggering the terminal device and/or the second access network device to configure the second protocol stack, the first access network device may notify the terminal device and/or the second access network device not to release the first protocol stack (hereinafter referred to as the old protocol stack). That is, when the end device and/or the second access network device are triggered by the first access network device to configure the new protocol stack, the end device is kept connected to the first access network device. In the disclosure mode, the first access network device can further trigger the endpoint device and/or the second access network device to maintain the sequence of PDCP PDUs, using the new protocol stack afterwards, i.e., the first access network device triggers the endpoint device to be completely handed over to the second access network device or the first access network device triggers the second access network device to notify a main network device to completely change a network path downlink. Before the first access network device triggers the endpoint device and/or the second access network device to maintain sequence of PDCP PDUs using the new protocol stack, the first access network device can continue to maintain sequence of PDCP PDUs, using the old protocol stack for uplink and downlink data cached on the first access network device.

[0103] In such a way, according to the handover method in the disclosure mode, the sequence of data packets is maintained through the use of the old protocol stack before the first access network device triggers the device terminal and/or the second accesses the network device to fully use the new protocol stack, so that the terminal device data can be processed in a timely manner and reduce the delay in transmitting data from the terminal device in a handover process.

[0104] Optionally, in the development mode, the first access network device can trigger only a first terminal device. For example, when the first end device passes into coverage of the second access network device connected to a second end device and the first end device can form a D2D connection with the second end device, the first network device can trigger the first end device. endpoint device, and the first endpoint device can trigger the second network device through the second endpoint device to configure the new protocol stack.

[0105] Optionally, in the disclosure mode, the first access network device can also trigger only the second access network device. For example, when the first end device passes into the coverage of the second access network device connected to the second end device and the first end device can form the D2D connection with the second end device, the first network device can trigger the second end device. network device and the second network device can trigger the first endpoint device through the second endpoint device to configure the new protocol stack.

[0106] Optionally, in the development mode, the operation in which the first access network device triggers the terminal device and the second access network device to configure the second protocol stack includes the following actions. The first access network device sends the first trigger information to the second access network device, where the first trigger information is configured to request the second access network device to configure the second protocol stack. The first access network device receives response information from the first trigger information sent by the second access network device. The first access network device sends the second trigger information to the terminal device in accordance with the response information, wherein the second trigger information is configured to instruct the terminal device to configure the second protocol stack.

[0107] Specifically, reference can be made to 4 to 7 as shown in Figure 3. For example, the first access network device can send a handover request to the second access network device. The second access network device, after determining, in accordance with the handover request, that the terminal device can be delivered to the second access network device, may return a response to the handover request to the first device. access network device, and the response may contain various parameters configured for the terminal device by the second access network device. The first access network device can transparently directly transmit various parameters configured by the second access network device to the terminal device, and the terminal device can further configure a protocol stack for communication with the second access network device accordingly. with these parameters.

[0108] It should be understood that when the first access network device triggers the end device to configure the new protocol stack, the first access network device can simultaneously notify the end device to maintain a connection with the first access network device. access network. For example, the indication information can be contained in the handover command sent by the first access network device to the terminal device, and the indication information can directly instruct the terminal device to maintain the connection with the first network device. of access. Alternatively, the first access network device may separately send indication information to the end device to notify the end device to maintain connection with the first access network device after receiving the handover command sent by the first access network device. access.

[0109] It should also be understood that when the first access network device triggers the terminal device to use the new protocol stack, the first access network device can simultaneously notify the terminal device to break the connection with the first device access network, i.e. freeing up the old protocol stack. For example, the first access network device can separately send indication information to the end device, and the indication information can directly instruct the end device to break the connection with the first access network device. Alternatively, the first access network device may also contain a bit in a last data packet sent to the end device to instruct the end device to break the connection with the first access network device.

[0110] Optionally, in the disclosure mode, the data packets to be processed include first data packets and the operation that the first access network device sequentially processes the data packets to be processed between the first access network device and the end device using the first protocol stack before the first access network device triggers the end device and/or the second access network device to maintain the sequence of data packets from the end device through use of the second protocol stack includes the following actions. Before the first access network device triggers the end device and/or the second access network device to maintain the sequence of data packets from the end device using the second protocol stack, the first access network device receives the first data packets sent by the terminal device. The first access network device decrypts the first data packets or a piece of data in each of the first data packets using the first protocol stack. The first access network device sequentially processes the first decrypted data packets using the first protocol stack.

[0111] Two modalities of the single-link handover scenario and the multi-link function switching scenario will be described below in detail in combination with Figures 5 and 6, respectively.

[0112] Figure 5 illustrates the single sign-on handover transfer scenario. As shown in Figure 5, in a first stage (which can be considered the stage prior to step 7 in Figure 3), the first access network device provides network service to the endpoint device, i.e. a PDCP layer of the first access network device serves as a convergence layer to maintain a send/receive sequence (SN in LTE) of data packets from the endpoint device, and the PDCP layer of the first access network device also maintains a security key. unified security for the endpoint device. For uplink data, a specific flow might be as follows. The endpoint device sends a PDCP PDU to the first access network device (the endpoint device is required to sequence SDUs in the PDCP PDU initially, including adding an SN, and the endpoint device can further encrypt the PDCP PDUs sequenced PDCP or the SDUs in it). The PDCP layer of the first access network device, after receiving the PDCP PDUs from an RLC layer, decrypts the PDCP PDUs initially or can also decrypt the SDU in the PDCP PDU. In addition, the first access network device can sequence the received PDCP PDUs or SDUs according to the SN obtained by decryption.

[0113] In a second stage (which can be considered the stage between 7 and 11 in Figure 3), that is, the process of executing the handover transfer in Figure 3, during this period, the terminal device can maintain the connection with the first access network device, i.e. the end device cannot leave a source cell in a synchronization process with the second access network device, and in that case, if the end device has data that needs to be transmitted, the end device can still transmit the data to the first access network device. That is, the first access network device can also receive a PDCP PDU sent by the endpoint device (the endpoint device is required to sequence SDUs into the PDCP PDUs initially, i.e. add an SN, and the endpoint device can encrypt further plus the string. PDCP PDUs or SDUs), the PDCP layer of the first access network device, after receiving the PDCP PDUs from the RLC layer, decrypts the PDCP PDUs first or can also decrypt the SDU in the PDCP and, in addition, the first access network device can sequence the received PDCP PDUs or SDUs according to the SN obtained by decryption. In other words, at this stage, data is still transmitted between the terminal device and the first access network device.

[0114] In a third stage (which can be considered as a flow after 11 in Figure 3), i.e. a handover completion process in Figure 3, during this period, once the terminal device has completed the reconfiguration with the second access network device, in other words, the end device was able to communicate with the second access network device, the end device certainly can directly send a PDCP PDU to the second access network device. Likewise, the second access network device, after receiving the PDCP PDUs sent by the endpoint device, can decrypt the PDCP PDU or an SDU through a newly configured PDCP layer, sending the PDCP PDUs or SDUs sequentially. to a higher tier according to the purchased SNs.

[0115] The functions of a PDCP and how to use these PDCP functions will not be presented here in detail and may refer to an LTE protocol.

[0116] Figure 6 illustrates a multi-connection function switching scenario. As shown in Figure 6, in a first stage (which can be considered the stage prior to 7 in Figure 3), the first access network device and the second access network device jointly provide network services to the terminal device. The first access network device may be a primary access network device and the second access network device may be a secondary access network device. The end device may send PDCP PDUs to one side of the network device through the first access network device and the second access network device. On the network device side, the PDCP layer of the first access network device serves as a convergence layer to maintain a send/receive sequence (SN in LTE) of data packets from the endpoint device and,

meanwhile, the PDCP layer of the first access network device maintains a unified key for the endpoint device. For uplink data, a specific flow might be as follows. End device sends PDCP PDUs to first access network device and second access network device (end device is required to sequence SDUs into PDCP PDUs first, i.e. add SNs, end device can encrypt further sequenced PDCP PDUs or the SDU on the same and the endpoint device can further send the encrypted PDCP PDUs to the network device side through the RLC layer of the first access network device and an RLC layer of the second access network device, respectively). The PDCP layer of the first access network device, after receiving the PDCP PDUs from the RLC layer of the first access network device and the RLC layer of the second access network device, decrypts the PDCP PDUs initially or also can decrypt SDU into PDCP PDU. In addition, the first access network device can sequence the received PDCP PDUs or SDUs according to the SNs obtained by decryption.

[0117] In a second stage (which can be considered the stage between 7 and 11 in Figure 3), that is, the process of executing the handover transfer in Figure 3, during this period, the terminal device can maintain the connection with the first access network device, i.e. in the process of synchronizing the terminal device with the second access network device, the PDCP of the first access network device can still be used to maintain a sequence of sending/receiving data from the first access network device. terminal device and data key. In that case, if the data terminal device has data required to be transmitted, the terminal device may still transmit the data to the first access network device and/or transmit the data to the second access network device. However, the data can ultimately be processed by the PDCP layer of the first access network device. In other words, during this period, the network device can still process data through the old protocol stack.

[0118] It should be understood that the data transmitted in the first stage and in the second stage can be transmitted over two links in dual connections and may also be transmitted over one link in the same. However, no matter if it is being transmitted over one link or two links, the data is ultimately converged to the PDCP layer of the first access network device, i.e., the PDCP layer of the primary access network device in a dual connection scenario.

[0119] In a third stage (which can be considered as a flow after 11 in Figure 3), that is, the handover completion process in Figure 3, during this period, once the terminal device has completed the reconfiguration with the second access network device, in other words, the second access network device has completed the PDCP layer configuration, the terminal device can directly communicate with the second access network device, that is, the network device can decrypt a PDCP PDU sent by the end device or an SDU through the PDCP layer of the second access network device. Furthermore, the layer

PDCP of the second access network device can sequentially send the PDCP PDUs or SDUs to the upper layer according to the acquired SNs.

[0120] Optionally, in the third stage, i.e. after the transfer is complete, the first access network device can release only the PDCP layer functions, i.e. after the transfer, the first access network device can serve as a secondary access network device of the second access network device. The endpoint device can send data to the network device side over two links, and the data on the two links is finally converged to the newly configured PDCP layer of the second access network device. The PDCP configuration layer of the second access network device decrypts the data and sends it sequentially to the upper layer, according to an SN obtained by decryption.

[0121] Optionally, in the third stage, i.e. after the transfer is completed, the first access network device can completely release the connection with the terminal device, and the terminal device can transmit data over the link with the second device only. access network. Furthermore, the PDCP layer established by the second access network device decrypts the data and sends it sequentially to the upper layer according to an SN obtained by decryption.

[0122] Although descriptions are made in this document with dual connections as an example, the disclosure modality is not limited to this. There may also be a multi-connection circumstance, that is, one primary access network device and multiple secondary access network devices provide network service to the endpoint device together.

[0123] The application of the disclosure modality technical solution to the single-link handover scenario and the multi-link function switching scenario is described above with uplink data as an example. The technical solution is also applied to downlink data.

[0124] Optionally, in the disclosure mode, the PDCP PDUs to be processed may include second PDCP PDUs and the operation that the first access network device sequentially processes the PDCP PDUs to be processed between the first access network device. access device and the endpoint device using the first protocol stack before the first access network device triggers the endpoint device and/or the second access network device to maintain the sequence of the endpoint device's PDCP PDUs using the second Protocol stack includes the following actions. Before the first access network device triggers the endpoint device and/or the second access network device to maintain the sequence of the endpoint device's PDCP PDUs using the second protocol stack, the first access network device receives the second PDCP PDUs sent by a main network device, and the first access network device sequentially processes the second PDCP PDUs using the first protocol stack. The method further includes the following operation. The first access network device encrypts the second sequentially processed PDCP PDUs or one SDU in each of the second PDCP PDUs, using the first protocol stack.

[0125] The transmission of the downlink data may refer to that of the uplink data. For simplicity, no further elaboration will be made in this document.

[0126] Optionally, in the disclosure mode, the PDCP PDUs to be processed include third party PDCP PDUs and the operation that the first access network device sequentially processes the PDCP PDUs to be processed between the first access network device and the endpoint device using the first protocol stack before the first access network device triggers the endpoint device and/or the second access network device to maintain the sequence of the endpoint device's PDCP PDUs using the endpoint device. second protocol stack includes the following actions. Before the first access network device triggers the endpoint device and/or the second access network device to maintain the sequence of the endpoint device's PDCP PDUs using the second protocol stack, the first access network device receives the third PDCP PDUs sent by the second access network device and the third PDCP PDUs or SDU in the third PDCP PDUs were decrypted by the second access network device using the second protocol stack. The first access network device sequentially processes the third decrypted PDCP PDUs.

[0127] Optionally, in the disclosure mode, the PDCP PDUs to be processed include fourth data packets and the operation that the first access network device sequentially processes the PDCP PDUs to be processed between the first access network device and the endpoint device using the first protocol stack before the first access network device triggers the endpoint device and/or the second access network device to maintain the sequence of the endpoint device's PDCP PDUs using the endpoint device. second protocol stack includes the following actions. Before the first access network device triggers the endpoint device and/or the second access network device to maintain the sequence of the endpoint device's PDCP PDUs using the second protocol stack, the first access network device receives the fourth PDCP PDUs sent by the main network device, and the first access network device sequentially processes the fourth PDCP PDUs using the first protocol stack. The method further includes the following operation. The first access network device sends the fourth processed PDCP PDUs sequentially to the second access network device, so that the second access network device to encrypt the fourth processed PDCP PDUs sequentially or an SDU in each of the fourth PDCP PDUs using the second protocol stack.

[0128] It should be understood that the PDCP PDUs appearing in this document refer to data packets in some places and refer to a piece of data in each of the data packets in some places, and those skilled in the art should distinguish them. For example, for uplink data, the end device sequentially processes the data to generate data packets and sends the data packets to the network device, and the end device does not directly process the data packets. For another example, for downlink data, the access network device obtains the data from the main network device and the access network device sequentially processes the received downlink data to generate data packets and sends the same to the terminal device.

[0129] Two other modalities of the single-link handover scenario and the multi-link function switching scenario will be described below in combination with Figures 7 and 8 in detail.

[0130] Figure 7 illustrates the single sign-on handover handover scenario. As shown in Figure 7, in a first stage (which can be considered the stage prior to 7 in Figure 3), the first access network device provides network service to the terminal device, i.e. the PDCP layer of the first access network device serves as the convergence layer to maintain a send/receive sequence (SN in LTE) of data packets from the endpoint device, and the PDCP layer of the first access network device also maintains a unified key to the terminal device. For uplink data, a specific flow might be as follows. End device sends PDCP PDUs to first access network device (end device is required to sequence SDUs in PDCP PDU initially, i.e. add an SN, and end device can further encrypt PDCP PDUs sequenced or the SDUs in it). The PDCP layer of the first access network device, after receiving the PDCP PDUs from an RLC layer, decrypts the PDCP PDUs initially or can also decrypt the SDU in the PDU from

PDCP In addition, the first access network device can sequence the received PDCP PDUs or SDUs according to the SN obtained by decryption.

[0131] In a second stage (which can be considered the stage between 7 and 11 in Figure 3), that is, the process of executing the handover transfer in Figure 3, during this period, the terminal device can maintain the connection with the first access network device i.e. the end device cannot leave a source cell in a synchronization process with the second access network device and part of the PDCP functions of the network device can be transferred to the second protocol stack, that is, the PDCP configuration layer of the second access network device can keep the terminal device key. In this case, if the end device has data to transmit, the end device can transmit the data to the second access network device using the second protocol stack. The second access network device decrypts the received data and, after completing the decryption, sends the data to the first access network device for sequential sending. That is, an incoming PDCP PDU can be decrypted through the PDCP layer of the second access network device, but the final sequential send is implemented through the PDCP layer of the first access network device. In other words, at this stage, the data can be decrypted using the new protocol stack, but the data is still processed sequentially using the old protocol stack.

[0132] In a third stage (which can be considered as a flow after 11 in Figure 3), that is, the handover completion process in Figure 3, during this period, once the terminal device has completed the reconfiguration with the second access network device, in other words, a sequencing and sending function to keep the terminal device data has been transferred from the first access network device to the second access network device, the terminal device can certainly send directly a PDCP PDU to the second access network device. The second access network device, after receiving the PDCP PDUs sent by the endpoint device, can decrypt the PDCP PDU or an SDU through the newly configured PDCP layer, sequentially sending the PDCP PDUs or SDUs to the upper layer of agreement for purchased SNs.

[0133] Figure 8 illustrates a multi-link function switching scenario. As shown in Figure 8, in a first stage (which can be considered the stage before 7 in Figure 3), the first access network device and the second access network device provide network service together to the end device. The first access network device may be a primary access network device and the second access network device may be a secondary access network device. The end device may send PDCP PDUs to one side of the network device through the first access network device and the second access network device. On the network device side, the PDCP layer of the first access network device serves as a convergence layer to maintain a send/receive sequence (SN in LTE) of data packets from the endpoint device, and meanwhile, the PDCP layer of the first access network device also maintains a unified key to the endpoint device. For uplink data, a specific flow might be as follows. The endpoint device sends one PDCP PDUs to the first access network device and the second access network device (the endpoint device is required to sequence SDUs into the PDCP PDUs first, i.e. add an SN, the endpoint device can further encrypt the sequenced PDCP PDUs or SDUs contained therein, and the endpoint device can still send the encoded PDCPs to the network device side through an RLC layer of the first access network device and an RLC layer of the second access network device, respectively). The PDCP layer of the first access network device, after receiving the PDCP PDUs from the RLC layer of the first access network device and the RLC layer of the second access network device, decrypts the PDCP PDUs initially or also can decrypt SDU into PDCP PDU. In addition, the first access network device can sequence the received PDCP PDUs or SDUs according to the SN obtained by decryption.

[0134] In a second stage (which can be considered the stage between 7 and 11 in Figure 3), that is, the process of executing the handover transfer in Figure 3, during this period, the terminal device can maintain the connection with the first access network device, i.e., in the process of synchronizing the terminal device with the second access network device, a sequence of sending/receiving data from the terminal device is maintained through the PDCP of the first network device of the access network. access and the key to the data is maintained through the newly configured PDCP. In that case, if the end device has data that needs to be transmitted, the end device can still transmit the data to the first access network device and/or transmit the data to the second access network device. However, the data can finally be decompressed through the PDCP configuration layer of the second access network device and the data is sequentially processed through the PDCP layer of the first access network device. In other words, during this period, the network device is still processing data through the old protocol stack and the new protocol stack.

[0135] It should be understood that data transmitted in the first stage and in the second stage can be transmitted over two links in dual connections and may also be transmitted over one link in the same. However, no matter if it is being transmitted over one link or two links, the data is ultimately converged to the PDCP layer of the first access network device, i.e., the PDCP layer of the primary access network device in a dual connection scenario.

[0136] In a third stage (which can be considered as a flow after 11 in Figure 3), that is, the handover completion process in Figure 3, during this period, once the terminal device has completed the reconfiguration with the second access network device, in other words, the second access network device has completed the PDCP layer configuration, the terminal device can directly communicate with the second access network device. That is, the network device side can decrypt a PDCP PDU sent by the endpoint device or an SDU through the PDCP layer of the second access network device. In addition, the PDCP layer of the second access network device can sequentially present the PDCP or PDUs from the SDUs to the upper layer according to an acquired SN.

[0137] Downlink data transmission may refer to uplink data transmission. For simplicity, no further elaboration will be made here.

[0138] It should be understood that in each modality in Figures 5 to 8, the PDCP configured to maintain the sequence of PDCP PDUs from the terminal device in the second stage may be a PDCP entity in the first access network device and may also be a unified convergence layer outside the PDCP entity and the unified convergence layer can be connected to the PDCP entity of the first access network device and to a PDCP entity of the second access network device, respectively. Thus, the convergence layer outside the PDCP entity of the first access network device, instead of the PDCP entity, can be used in the second stage. The modality of revelation is not limited to this.

[0139] It should also be understood that the data can be split into two parts for data transmission in the second stage. One part of the data is decrypted using the new protocol stack and the other part is decrypted using the old protocol stack, or the new protocol stack or the old protocol stack can be independently adopted for decryption. There are no established limits on the modality of disclosure.

[0140] Optionally, in the development mode, the method further includes the following operation. If the first access network device determines that no data or data packets from the end device are to be processed by the first access network device, the first access network device triggers the end device and/or the second access network device. access to maintain the sequence of data packets from the terminal device using the second protocol stack.

[0141] Specifically, in the flow shown in Figure 3, the main network device, after completing the downlink path switching, can send an end marker to the first access network device to notify the first access network device that there will be no data to be sent to the first access network device. Then, the first access network device can transmit that circumstance to the terminal device and/or the second access network device, respectively, notifying the terminal device and/or the second access network device that the terminal device and the second access network device can directly communicate with each other, and the first access network device is no longer needed for transmission. For example, the end marker could be “end marker” in 16 and it could also be other indication information.

[0142] That is, when the terminal device receives indication information sent by the first access network device, the terminal device can determine that there is no data to be transmitted with the first access network device and the terminal device can directly execute the subsequent data transmission using the new protocol stack. The terminal device can also release the old protocol stack according to the indication information.

[0143] Optionally, in the disclosure mode, the indication information sent by the first access network device to the terminal device can be any one of RRC signaling, MAC signaling, DCI or a bit in a data packet.

[0144] Optionally, in the development mode, the method further includes the following operations. The first access network device receives third indication information sent by the second access network device, wherein the third indication information indicates that the terminal device has completed the configuration of the second protocol stack. The first access network device sends path switching information to the main network device in accordance with the third indication information, where the path switching information is configured to instruct the main network device to switch a access network, which is responsible for maintaining the sequence of data packets from the terminal device, from the first access network device to the second access network device.

[0145] That is, after the second access network device determines that the endpoint device has completed the configuration, the second access network device can trigger the first access network device to send the path switching information to switch the downlink path to the main network device. For example, after the second access network device receives the reset complete message, as shown in Figure 3, the second access network device sends indication information to the first access network device to notify the first network device that the endpoint device has completed configuring the new protocol stack. The first access network device can notify the main network device to change the downlink path. After the second access network device receives the reconfiguration complete message, as shown in Figure 3, the second access network device can directly notify the main network device to change the downlink path.

[0146] Optionally, in the disclosure mode, the first access network device is a source access network device and the second access network device is a target access network device. Alternatively, the first access network device is a primary access network device in a multilink scenario and the second access network device is a secondary access network device in the multilink scenario.

[0147] Figure 9 is a schematic block diagram showing a handover method 400 in accordance with an embodiment of the disclosure. As shown in Figure 9, method 400 includes the following operations.

[0148] In S410, a second access network device receives the first trigger information sent through a first access network device, where the first trigger information is configured to trigger the second access network device to configure a second protocol stack and wherein the second protocol stack is configured to maintain a sequence of data packets between the second access network device and an endpoint device and/or a security key of the data packets between the second device access network and the terminal device.

[0149] At S420, the second access network device receives the second trigger information sent by the first access network device, wherein the second trigger information is configured to trigger the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack.

[0150] In such a way, according to the handover method in the disclosure mode, the sequence of data packets is maintained by the old protocol stack before the first access network device triggers the terminal device and/or the second access network device to fully use the new protocol stack, so that the terminal device data can be processed in a timely manner, and a delay in the transmission of data from the terminal device in a handover transfer process is reduced.

[0151] Optionally, in the development mode, the method further includes the following operations. Before the second access network device receives the second trigger information sent by the first access network device, the second access network device receives a sequentially processed and encrypted first data packet sent by the first access network device and the second access network device forwards the first sequentially processed and encrypted data packets to the end device.

[0152] Optionally, in the development mode, the method further includes the following operations. Before the second access network device receives the second trigger information sent by the first access network device, the second access network device receives a second sequentially processed data packet sent by the first access network device, the second access network device encrypts the second data packets or a piece of data in each of the second data packets using the second protocol stack and the second access network device sends the second encrypted data packets to the device terminal.

[0153] Optionally, in the development mode, the method further includes the following operations. Before the second access network device receives the second trigger information sent by the first access network device, the second access network device receives third data packets sent by the terminal device and the second access network device forwards the third party data packets for the first access network device for the first access network device to decrypt and sequentially process the third data packets or a piece of data in each of the third data packets.

[0154] Optionally, in the development mode, the method further includes the following operations. Before the second access network device receives the second trigger information sent by the first access network device, the second access network device receives the fourth data packet sent by the terminal device, the second access network device decrypts the fourth data packets or a piece of data in each of the fourth data packets using the second protocol stack and the second access network device sends the fourth decrypted data packets to the first access network device for that the first access network device sequentially process the fourth decrypted data packets.

[0155] Optionally, in the development mode, the method further includes the following operations. The second access network device receives the first indication information sent by the terminal device, where the first indication information indicates that the terminal device has completed the configuration of the second protocol stack. The second access network device sends path switching information to a main network device according to the first indication information, or the second access network device triggers the first access network device to send the path switching information. path to the main network device according to the first indication information, where the path switching information is configured to instruct the main network device to switch an access network device, responsible for maintaining the sequence of the packets of terminal device data from the first access network device to the second access network device.

[0156] Optionally, in the development mode, the method further includes the following operations. After the second access network device sends the path switching information to the main network device, the second access network device receives second indication information sent by the first access network device, wherein the second access network device indication are set to indicate that no data or data packets from the terminal device should be processed by the first access network device.

[0157] Optionally, in the disclosure mode, the second trigger information can be any one of RRC signaling, MAC signaling, DCI or a bit in a data packet.

[0158] Optionally, in the disclosure mode, the first access network device is a source access network device and the second access network device is a destination access network device. Alternatively, the first access network device is a primary access network device in a multilink scenario and the second access network device is a secondary access network device in the multilink scenario.

[0159] It should be understood that the interactions between the second access network device and each of the first access network devices and the terminal device, properties, related functions and the like described on the second side of the access network device correspond to the properties and related functions of the first access network device. Also, related content was described in detail in method 300 and for simplicity will not be elaborated here.

[0160] Figure 10 is a schematic block diagram showing a handover method 500 in accordance with an embodiment of the disclosure. As shown in Figure 10, method 500 includes the following operations.

[0161] In the S510, a terminal device configures a second protocol stack according to the first trigger information sent through a first access network device, where the second protocol stack is configured to maintain a sequence of packets of data between a second access network device and the terminal device and/or a security key of data packets between the second access network device and the terminal device.

[0162] At S520, before the terminal device receives the second trigger information sent by the first access network device and/or the second access network device, the terminal device sequentially processes data packets or data to be processed from the terminal device using a first protocol stack, where the second trigger information is configured to trigger the terminal device to maintain the sequence of data packets from the terminal device using the second protocol stack.

[0163] In such a way, according to the handover method in the disclosure mode, the sequence of data packets is maintained by the old protocol stack before the first access network device triggers the terminal device and/or the second access network device to fully use the new protocol stack, so that the terminal device data can be processed in a timely manner, and a delay in the transmission of data from the terminal device in a handover transfer process is reduced.

[0164] Optionally, in the disclosure mode, the data to be processed includes the first data and the operation that the terminal device sequentially processes the data packets or data to be processed from the terminal device using the first protocol stack before the end device receiving the second trigger information sent by the first access network device and/or the second access network device includes the following action. The terminal device sequentially processes the first data using the first protocol stack. The method further includes that: the terminal device encrypts the first data or data packets processed sequentially, including the first data, using the first protocol stack, and the terminal device sends the encrypted data packets, including the first data to the first access network device and/or the second access network device.

[0165] Optionally, in the disclosure mode, the data packets to be processed include first data packets and the operation in which the terminal device sequentially processes the data packets or data to be processed from the terminal device using the first stack protocol before the end device receives the second trigger information sent by the first access network device and/or the second access network device includes the following actions. Before the end device receives the second trigger information sent by the first access network device and/or the second access network device, the end device receives the first data packets sent by the first access network device and/or the second access network device, the terminal device decrypts the first data packets or a piece of data in each of the first data packets using the first protocol stack, and the terminal device sequentially processes the first data packets decrypted using the first protocol stack.

[0166] Optionally, in the development mode, the data to be processed includes second data and the operation that the terminal device sequentially processes the data packets or data to be processed from the terminal device using the first protocol stack before the terminal device receiving the second trigger information sent by the first access network device and/or the second access network device includes the following action. The terminal device sequentially processes the second data using the first protocol stack. The method further includes that: the terminal device encrypts the second data or sequentially processed data packets, including the second data, using the second protocol stack, and the terminal device sends the encrypted data packets, including the second data to the second network device.

[0167] Optionally, in the disclosure mode, the data packets to be processed include second data packets and the operation that the terminal device sequentially processes the data packets or data to be processed from the terminal device using the first stack of protocol before the end device receives the second trigger information sent by the first access network device and/or the second access network device includes the following actions. The end device receives the second data packets sent by the second network device, the end device decrypts the second data packets or a piece of data in each of the second data packets using the second protocol stack, and the end device terminal sequentially processes the second decrypted data packets using the first protocol stack.

[0168] Optionally, in the development mode, the method further includes the following operations. The terminal device receives the second trigger information sent by the first access network device and/or the second access network device, and the terminal device maintains the sequence of data packets from the terminal device using the second protocol stack. according to the second triggering information.

[0169] Optionally, in the reveal mode, the second trigger information is still configured to instruct the terminal device to release the first protocol stack. The method may further include that: the terminal device releases the first protocol stack according to the second trigger information.

[0170] Optionally, in the disclosure mode, the second trigger information is any one of RRC signaling, MAC signaling, DCI or a bit in a data packet.

[0171] Optionally, in the disclosure mode, the first access network device is a source access network device and the second access network device is a target access network device. Alternatively, the first access network device is a primary access network device in a multilink scenario and the second access network device is a secondary access network device in the multilink scenario.

[0172] It should be understood that the terms "system" and "network" are often used interchangeably herein. In disclosure, the term “and/or” is just an association relationship that describes associated objects and represents that three relationships can exist. For example, A and/or B can represent three conditions: that is, independent existence of A, existence of A and B, and independent existence of B. Also, the character “/” in the revelation usually represents the associated objects before and after form an “or” relationship.

[0173] It should be understood that the interaction between the terminal device and the network device and the related properties, functions and the like described in the terminal device correspond to the related properties and functions of the network device. Also, related content was described in detail in method 300 and for simplicity will not be elaborated here.

[0174] The transfer methods according to the disclosure modalities are described above in detail and the devices according to the disclosure modalities will be described below in combination with Figures 11 to 16. The technical characteristics described in the method modalities are applied to the following device modalities.

[0175] Figure 11 is a schematic block diagram showing an access network device 600 in accordance with an embodiment of the disclosure. Access network device 600 is a first access network device. As shown in Figure 11 , access network device 600 includes a first trigger unit 610 and a sequential processing unit 620.

[0176] Drive unit 610 is configured to trigger a terminal device and/or a second access network device to configure a second protocol stack, where the second protocol stack is configured to hold a sequence of PDCP PDUs between the second access network device and the terminal device and/or a data packet security key between the second access network device and the terminal device.

[0177] Sequential processing unit 620 is configured so that, before the first access network device triggers the terminal device and/or the second access network device, to maintain the sequence of data packets from the terminal device using of the second protocol stack, sequentially process the data packets to be processed between the first access network device and the terminal device using a first protocol stack.

[0178] In such a way, according to the access network device in the disclosure mode, the sequence of data packets is maintained by the old protocol stack before the first access network device triggers the terminal device and/or the second access network device to fully use the new protocol stack, so that the terminal device data can be processed in a timely manner, and a delay in the transmission of data from the terminal device in a handover transfer process is reduced.

[0179] Optionally, in the disclosure mode, the data packets to be processed include first data packets and the sequential processing unit 620 is configured specifically for, before the first access network device triggers the terminal device and/or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack, receive the first data packets sent by the terminal device, decrypt the first data packets or a piece of data in each of the first data packets using the first protocol stack and sequentially processes the first decrypted data packets using the first protocol stack.

[0180] Optionally, in the disclosure mode, the data packets to be processed include second data packets and the sequential processing unit is configured specifically for, before the first access network device triggers the terminal device and/or the second access network device to maintain the sequence of data packets from the end device using the second protocol stack, receive the second data packets sent by a main network device, and sequentially process the second data packets using of the first protocol stack. The access network device further includes a first encryption unit configured to encrypt the second sequentially processed data packets or a piece of data in each of the second data packets using the first protocol stack.

[0181] Optionally, in the disclosure mode, the data packets to be processed include third data packets and the sequential processing unit is configured specifically for, before the first access network device triggers the terminal device and/or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack, receives the third data packets sent by the second access network device, wherein the third data packets or a piece of data in each of the third data packets is decrypted by the second access network device using the second protocol stack and sequentially processes the third decrypted data packets.

[0182] Optionally, in the disclosure mode, the data packets to be processed include fourth data packets and the sequential processing unit is configured specifically for, before the first access network device triggers the terminal device and/or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack, receive the fourth data packets sent by the main network device, and sequentially process the fourth data packets using the first protocol stack. The access network device further includes a second encryption unit configured to send the fourth sequentially processed data packets to the second access network device to the second access network device to encrypt the fourth sequentially processed data packets or a piece of data in each of the fourth data packets using the second protocol stack.

[0183] Optionally, in the disclosure mode, the access network device further includes a second trigger unit configured to, under the circumstance that the first access network device determines that no data packet from the device is required terminal is processed by the first access network device, trigger the terminal device and/or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack.

[0184] Optionally, in the disclosure mode, the second trigger unit is configured specifically for, under the circumstance that the first access network device determines that it is not necessary for any data packets from the terminal device to be processed by the first access device access network, send first indication information to the terminal device, the first indication information being configured to instruct the terminal device to keep the sequence of data packets from the terminal device using the second protocol stack.

[0185] Optionally, in the reveal mode, the first indication information is still configured to instruct the terminal device to release the first protocol stack.

[0186] Optionally, in the disclosure mode, the first indication information is any one of RRC signaling, MAC signaling, DCI or a bit in a data packet.

[0187] Optionally, in the disclosure mode, the second trigger unit is configured specifically for, under the circumstance that the first access network device determines that it is not necessary for any data packets from the terminal device to be processed by the first access device access network device, sending, via the first access network device, second indication information to the second access network device, wherein the second indication information is configured to instruct the second access network device to maintain the access network device. sequence of data packets from the terminal device using the second protocol stack.

[0188] Optionally, in the disclosure mode, the access network device further includes a determination unit, configured to determine that no data packets from the terminal device are required to be processed by the first access network device.

[0189] Optionally, in the disclosure mode, the determination unit is configured specifically to receive the third indication information sent by the main network device, where the third indication information indicates that no data packet from the device is required. terminal is processed by the first to access the network device and determine, according to the third indication information, that it is not necessary for any data packets from the terminal device to be processed by the first network device.

[0190] Optionally, in the disclosure mode, the access network device further includes a receiving unit and a sending unit. The receiving unit is configured to receive the fourth indication information sent by the second access network device, where the fourth indication information indicates that the terminal device has completed the configuration of the second protocol stack. The sending unit is configured to send path switching information to the main network device according to the fourth indication information, where the path switching information is configured to instruct the main network device to switch a network device of access, responsible for maintaining the sequence of data packets from the terminal device, from the first access network device to the second access network device.

[0191] Optionally, in the disclosure mode, the first trip unit is configured specifically to send the first trip information to the second access network device, where the first trip information is configured to request the second network device to configure the second protocol stack, receive response information from the first trigger information from the second access network device, and send second trigger information to the terminal device in accordance with the response information, wherein the second trigger information is configured to instruct the endpoint device to configure the second protocol stack.

[0192] Optionally, in the disclosure mode, the first access network device is a source access network device and the second access network device is a target access network device. Alternatively, the first access network device is a primary access network device in a multilink scenario and the second access network device is a secondary access network device in the multilink scenario.

[0193] It should be understood that the access network device 600 according to the disclosure method may correspond to the first access network device in the disclosure method modality. The aforementioned operations and/or functions and/or functions of each unit in the access network device 600 are intended to implement the corresponding flows performed by the network device in the methods shown in Figures 4 and 8, respectively, and will not be elaborated on here for simplicity.

[0194] Figure 12 is a schematic block diagram showing an access network device 700 in accordance with an embodiment of the disclosure. Access network device 700 is a second access network device. As shown in Figure 12 , access network device 700 includes a first receive unit 710 and a second receive unit 720.

[0195] The first receiving unit 710 is configured to receive the first trigger information sent through a first access network device, wherein the first trigger information is configured to trigger the second access network device to configure a second protocol stack and wherein the second protocol stack is configured to maintain a sequence of data packets between the second access network device and an endpoint device and/or a security key of the data packets between the second network device access network and the terminal device.

[0196] The second receiving unit 720 is configured to receive the second trigger information sent by the first access network device, wherein the second trigger information is configured to trigger the second access network device to maintain the sequence of events. data packets from the terminal device using the second protocol stack.

[0197] In such a way, according to the access network device in the disclosure mode, the sequence of data packets is maintained by the old protocol stack before the first access network device triggers the terminal device and/or the second access network device to fully use the new protocol stack, so that the terminal device data can be processed in a timely manner, and a delay in the transmission of data from the terminal device in a handover transfer process is reduced.

[0198] Optionally, in the disclosure mode, the access network device further includes a third receiving unit and a first sending unit. The third receiving unit is configured to receive, before the second access network device receives the second trigger information sent by the first access network device, a first sequentially processed and encrypted data packet sent by the first access network device. access. The first sending unit is configured to forward the first processed and encrypted data packets sequentially to the terminal device.

[0199] Optionally, in the disclosure mode, the access network device further includes a fourth receiving unit, a first encryption unit and a second sending unit. The fourth receiving unit is configured to receive, before the second access network device receives the second trigger information sent by the first access network device, a second sequentially processed data packet sent by the first access network device. The first encryption unit is configured to encrypt the second data packets or a piece of data in each of the second data packets using the second protocol stack. The second sending unit is configured to send the second encrypted data packets to the terminal device.

[0200] Optionally, in the disclosure mode, the access network device further includes a fifth receiving unit and a third sending unit. The fifth receiving unit is configured to receive, before the second access network device receives the second trigger information sent by the first access network device, third data packets sent by the terminal device. The third sending unit is configured to forward the third data packets to the first access network device so that the first access network device decrypts and sequentially processes the third data packets or a piece of data in each of the third party data packages.

[0201] Optionally, in the disclosure mode, the access network device further includes a sixth receiving unit, a first decryption unit and a fourth sending unit. The sixth receiving unit is configured to receive, before the second access network device receives the second trigger information sent by the first access network device, the fourth data packets sent by the terminal device. The first decryption unit is configured to decrypt the fourth data packets or a piece of data in each of the fourth data packets using the second protocol stack. The fourth sending unit is configured to send the fourth decrypted data packets to the first access network device so that the first access network device sequentially processes the fourth decrypted data packets.

[0202] Optionally, in the disclosure mode, the access network device further includes a seventh receiving unit and a fifth sending unit. The seventh receiving unit is configured to receive the first indication information sent by the terminal device, where the first indication information indicates that the terminal device has completed the configuration of the second protocol stack. The fifth sending unit is configured to send path switching information to a main network device according to the first indication information or triggering the first access network device to send the path switching information to the network device according to the first indication information, where the path switch information is configured to instruct the main network device to switch an access network device, which is responsible for maintaining the sequence of data packets from the terminal device , from the first access network device to the second access network device.

[0203] Optionally, in the disclosure mode, the access network device further includes an eighth receiving unit. The eighth receiving unit is configured so that, after the seventh sending unit sends the path switching information to the main network device, it receives, through the second access network device, second indication information sent by the first network device. access network, wherein the second indication information indicates that no data or data packets from the terminal device need to be processed by the first access network device.

[0204] Optionally, in the disclosure mode, the second trigger information is any one of RRC signaling, MAC signaling, DCI or a bit in a data packet.

[0205] Optionally, in the disclosure mode, the first access network device is a source access network device and the second access network device is a destination access network device. Alternatively, the first access network device is a primary access network device in a multilink scenario and the second access network device is a secondary access network device in the multilink scenario.

[0206] It is to be understood that the access network device 700 according to the disclosure method may correspond to the second access network device in the disclosure method modality. The aforementioned operations and/or functions of each unit in the access network device 700 are intended to implement the corresponding flows performed by the network device in the methods of Figures 5 and 9, respectively, and will not be elaborated here for simplicity.

[0207] Figure 13 is a schematic block diagram showing a terminal device 800 in accordance with an embodiment of the disclosure. As shown in Figure 13, the terminal device 800 includes a configuration unit 810 and a first sequential processing unit 820.

[0208] Configuration unit 810 is configured to configure a second protocol stack according to the first trigger information sent through a first access network device, where the second protocol stack is configured to maintain a sequence of data packets between a second access network device and the terminal device and/or a security key of the data packets between the second access network device and the terminal device.

[0209] The first sequential processing unit 820 is configured so that, before the terminal device receives the second trigger information sent by the first access network device and/or the second access network device, sequentially process data packets to be processed from the end device using a first protocol stack, wherein the second trigger information is configured to trigger the end device to maintain sequence of data packets from the end device using the second protocol stack.

[0210] In such a way, according to the endpoint device of the disclosure mode, the sequence of data packets is maintained by the old protocol stack before the first access network device triggers the endpoint device and/or the second device network to fully use the new protocol stack, so that data from the terminal device can be processed in a timely manner, and a delay in transmitting data from the terminal device in a handover transfer process is reduced.

[0211] Optionally, in the development mode, the data packets to be processed include first data, and the first sequential processing unit is configured specifically to sequentially process the first data using the first protocol stack. The terminal device further includes a first encryption unit and a first sending unit. The first encryption unit is configured to encrypt the first data or data packets processed sequentially, including the first data, using the first protocol stack. The first sending unit is configured to send the encrypted data packets, including the first data, to the first access network device.

[0212] Optionally, in the disclosure mode, the data packets to be processed include first data packets and the first sequential processing unit is configured specifically for, before the terminal device receives the second trigger information sent by the first processing device access network and/or the second access network device, receive the first data packets sent by the first access network device, decrypt the first data packets or a piece of data in each of the first data packets with the using the first protocol stack and sequentially processing the first decrypted data packets using the first protocol stack.

[0213] Optionally, in the development mode, the data to be processed includes second data and the first sequential processing unit is specifically configured to sequentially process the second data using the first protocol stack. The terminal device further includes a second encryption unit and a second sending unit. The second encryption unit is configured to encrypt the second data or sequentially processed data packets including the second data using the second protocol stack. The second sending unit is configured to send the encrypted data packets, including the seconds, to the second network device.

[0214] Optionally, in the disclosure mode, the data packets to be processed include second data packets and the first sequential processing unit is configured specifically to receive the second data packets sent by the second network device, decrypt the second packets of data or data breaks into each of the second data packets using the second protocol stack and sequentially processing the second decrypted data packets using the first protocol stack.

[0215] Optionally, in the disclosure mode, the terminal device further includes a first receiving unit and a second sequential processing unit. The first receiving unit is configured to receive the second trigger information sent by the first access network device and/or the second access network device. The second sequential processing unit is configured to maintain the sequence of data packets from the terminal device, using the second protocol stack according to the second trigger information.

[0216] Optionally, in the reveal mode, the second trigger information is still configured to instruct the terminal device to release the first protocol stack. The terminal device further includes a release unit configured to release the first protocol stack in accordance with the second trigger information.

[0217] Optionally, in the disclosure mode, the second trigger information is any one of RRC signaling, MAC signaling, DCI or a bit in a data packet.

[0218] Optionally, in the disclosure mode, the first access network device is a source access network device and the second access network device is a destination access network device. Alternatively, the first access network device is a primary access network device in a multilink scenario and the second access network device is a secondary access network device in the multilink scenario.

[0219] It should be understood that the terminal device 800 according to the disclosure method may correspond to the terminal device in the disclosure method modality. The aforementioned and other operations and/or functions of each unit in the terminal device 800 are intended to implement the corresponding flows performed by the terminal device in the methods shown in Figures 5 to 8 and 10, respectively, and will not be elaborated here for simplicity.

[0220] As shown in Figure 14, one embodiment of the disclosure also provides an access network device

900. Access network device 900 may be access network device 600 in Figure 11, and may be configured to play content played by the first access network device in method 300 in Figures 4 to 8. access network 900 includes an input interface 910, an output interface 920, a processor 930 and a memory 940. The input interface 910, the output interface 920, the processor 930 and the memory 940 may be connected via a bus system. Memory 940 is configured to store a program, instruction, or code. Processor 930 is configured to execute the program, instruction, or code in memory 940 to control input interface 910 to receive a signal, control output interface 920 to send a signal, and complete operations in method embodiments.

[0221] In such a way, according to the access network device in the disclosure mode, the sequence of data packets is maintained by the old protocol stack before the first access network device triggers the terminal device and/or the second access network device to fully use the new protocol stack, so that the terminal device data can be processed in a timely manner, and a delay in the transmission of data from the terminal device in a handover transfer process is reduced.

[0222] It should be understood that, in the embodiment of the disclosure, the processor 930 can be a Central Processing Unit (CPU) and the processor 930 can also be another universal processor, a Digital Signal Processor (DSP), an Integrated Circuit Specific Application

(ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device or discrete hardware component and the like. The universal processor can be a microprocessor or the processor can also be any conventional processor and the like.

[0223] Memory 940 may include read-only memory (ROM) and random access memory (RAM) and may provide instruction and data to processor 930. A portion of memory 940 may further include non-volatile RAM. For example, memory 940 may still store information of one type of device.

[0224] In a deployment process, the content of the above methods may be completed by an integrated logic circuit in a hardware form in processor 930 or an instruction in a software form. The content of the disclosed methods in combination with the disclosure modalities may be directly incorporated to be executed and completed by a hardware processor or executed and completed by a combination of hardware and software modules in the processor. The software module may be located on a storage medium mature in this field, such as RAM, flash memory, ROM, programmable ROM or electrically erasable programmable ROM and a register. The storage medium is located in memory 940. Processor 930 reads information from memory 940 and completes the contents of the method in combination with the hardware thereof. No more detailed description will be given here to avoid repetition.

[0225] In a specific deployment, the sending unit on the access network device 600 may be deployed by the output interface 920 in Figure 14 and the receiving unit on the access network device 600 may be deployed by the input interface 910 in Figure 14. The first trigger unit, the second trigger unit, the sequential processing unit, the determination unit, the first encryption unit and the second encryption unit in the access network device 600 can be deployed by the processor 930 in Figure 14.

[0226] As shown in Figure 15, one embodiment of the disclosure further provides an access network device

1000. Access network device 1000 may be access network device 700 in Figure 12, and may be configured to play content played by the second access network device in method 400 in Figures 5 to 9. access network 1000 includes an input interface 1010, an output interface 1020, a processor 1030 and a memory 1040. The input interface 1010, the output interface 1020, the processor 1030 and the memory 1040 may be connected via a bus system. Memory 1040 is configured to store a program, instruction, or code. Processor 1030 is configured to execute the program, instruction, or code in memory 1040 to control input interface 1010 to receive a signal, control output interface 1020 to send a signal, and complete operations in method embodiments.

[0227] In such a way, according to the access network device in the disclosure mode, the sequence of data packets is maintained by the old protocol stack before the first access network device triggers the terminal device and/or the second access network device to fully use the new protocol stack, so that the terminal device data can be processed in a timely manner, and a delay in the transmission of data from the terminal device in a handover transfer process is reduced.

[0228] It should be understood that, in the embodiment of the disclosure, the processor 1030 can be a CPU and the processor 1030 can also be another universal processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete port or logic device. transistor, discrete hardware component and the like. The universal processor can be a microprocessor or the processor can also be any conventional processor and the like.

[0229] Memory 1040 can include a ROM and a RAM and can supply an instruction and data to the processor

1030. A portion of memory 1040 may further include non-volatile RAM. For example, memory 1040 may still store information of one type of device.

[0230] In a deployment process, the content of the above methods can be completed by an integrated logic circuit in a form of hardware in the processor 1030 or an instruction in a form of software. The content of the disclosed method in combination with the disclosure modalities may be directly incorporated to be executed and completed by a hardware processor or executed and completed by a combination of hardware and software modules in the processor. The software module may be located on a storage medium mature in this field, such as RAM, flash memory, ROM, programmable ROM or electrically erasable programmable ROM and a register. The storage medium is located in memory 1040. Processor 1030 reads information from memory 1040 and completes the contents of the method in combination with the hardware thereof. No more detailed description will be given here to avoid repetition.

[0231] In a specific deployment, the first sending unit to the sixth sending unit in the access network device 700 can be deployed via the output interface 1020 in Figure 15, and the first receiving unit to the sixth receiving unit in the access network device 700 may be deployed by input interface 1010 in Figure 15. The first encryption unit and first decryption unit in the access network device 700 may be deployed by processor 1030 in Figure 15.

[0232] As shown in Figure 16, one embodiment of the disclosure also provides a terminal device 2000. The terminal device 2000 may be the terminal device 800 in Figure 13 and may be configured to play content executed by the terminal device in the methods of Figures 5 to 8 and 10. The terminal device 2000 includes an input interface 2010, an output interface 2020, a processor 2030 and a memory 2040. The input interface 2010, the output interface 2020, the processor 2030 and the memory 2040 can be connected through a bus system. Memory 2040 is configured to store a program, instruction, or code. Processor 2030 is configured to execute the program, instruction, or code in memory 2040 to control input interface 2010 to receive a signal, control output interface 2020 to send a signal, and complete operations in method embodiments.

[0233] In such a way, according to the endpoint device in the disclosure mode, the sequence of data packets is maintained by the old protocol stack before the first access network device triggers the endpoint device and/or the second device network to fully use the new protocol stack, so that data from the terminal device can be processed in a timely manner, and a delay in transmitting data from the terminal device in a handover transfer process is reduced.

[0234] It should be understood that, in the embodiment of the disclosure, the processor 2030 can be a CPU and the processor 2030 can also be another universal processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete port or logic device transistor, discrete hardware component and the like. The universal processor can be a microprocessor or the processor can also be any conventional processor and the like.

[0235] Memory 2040 can include a ROM and a RAM and can supply an instruction and data to the processor

2030. A portion of the memory 2040 may further include non-volatile RAM. For example, memory 2040 can still store information of a device type.

[0236] In a deployment process, the content of methods can be completed by an integrated logic circuit in a form of hardware in the 2030 processor or an instruction in a form of software. The content of the disclosed method in combination with the disclosure modalities may be directly incorporated to be executed and completed by a hardware processor or executed and completed by a combination of hardware and software modules in the processor. The software module may be located on a storage medium mature in this field, such as RAM, flash memory, ROM, programmable ROM or electrically erasable programmable ROM, and a register. The storage medium is located in memory 2040. Processor 2030 reads information in memory 2040 and completes the contents of the method in combination with the hardware thereof. No more detailed description will be given here to avoid repetition.

[0237] In a specific deployment, the first sending unit and the second sending unit in the terminal device 800 can be deployed by the output interface 2020 in Figure 16, and the first receiving unit in the terminal device 800 can be deployed by the interface 2010 in Figure 16. The configuration unit, the first sequential processing unit, the first encryption unit, the first decryption unit and the second sequential processing unit in the terminal device 800 can be deployed by the processor 2030 in Figure 16 .

[0238] Those skilled in the art may appreciate that the units and algorithm steps of each example described in combination with the modalities disclosed in the disclosure may be implemented by electronic hardware or a combination of computer software and electronic hardware. The execution of these functions in hardware or software depends on specific application and design constraints of the technical solutions. Practitioners may deploy the functions described for each specific application using different methods, and such deployment must be within the scope of disclosure.

[0239] Those skilled in the art can clearly understand that system, device and unit specific work processes described above may refer to corresponding processes in the method embodiment and will not be elaborated here for convenient and brief description.

[0240] In some embodiments provided by the disclosure, it is to be understood that the disclosed system, device and method may be implanted in another way. For example, the device modality described above is schematic only, and for example, the division of units is just a division of the logical function, and other ways of division can be adopted during practical implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be overlooked or not implemented. In addition, the coupling or direct coupling or the communication connection between the components shown or discussed may be an indirect coupling or the communication connection implemented through some interfaces, devices or units, and may be electrical, mechanical or take other forms. .

[0241] Units depicted as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, and may be located in the same location or may also be distributed to multiple network drives. Part or all units may be selected to achieve the objective of modalities solutions according to a practical requirement.

[0242] In addition, each functional unit in each embodiment of disclosure can be integrated into a processing unit, each unit can also physically exist independently, and two or more than two units can also be integrated into one unit.

[0243] When deployed as a functional unit of software and sold or used as a standalone product, the function can also be stored on a computer-readable storage medium. Based on this understanding, the technical solutions of the disclosure substantially or in parts that contribute to the conventional technique or part of the technical solutions can be incorporated in the form of a software product. The computer software product is stored on a storage medium, including a plurality of instructions configured to allow a computer device (which may be a personal computer, a server, a network device or the like) to perform all or part of the steps in each mode of development. The storage medium includes various media capable of storing program code, such as a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0244] Only various specific deployments of the disclosure are disclosed above and are not intended to limit the scope of protection of the disclosure. Any variations or substitutions apparent to those skilled in the art within the technical scope revealed by the disclosure must be within the scope of protection of the disclosure. Therefore, the scope of protection of disclosure must be subject to the scope of protection of claims.

Claims (15)

1. DELIVERY METHOD, characterized in that it comprises: triggering, by means of a first access network device, at least one of a terminal device or a second access network device to configure a second protocol stack, wherein the second stack protocol is configured to hold at least one of: a sequence of data packets between the second access network device and the endpoint device, or a security key of the data packets between the second access network device and the end device. terminal; and before the first access network device is triggered at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack, process sequentially, by the first access network device, data packets to be processed from the terminal using a first protocol stack. 2. METHOD, according to claim 1, characterized in that the data packets to be processed comprise the first data packets and sequentially processing, by means of the first access network device, the data packets to be processed from the terminal device using the first protocol stack before the first access the network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second stack of protocol: before the first access network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack received by the first device access network, the first data packets sent by the terminal device; decrypting, by the first access network device, the first data packets or a portion of data in each of the first data packets, using the first protocol stack; and sequentially processing, via the first access network device, the first decrypted data packets using the first protocol stack. 3. METHOD, according to claim 1, characterized in that the data packets to be processed comprise second data packets and sequentially process, by means of the first access network device, the data packets to be processed from the terminal device with the use of the first protocol stack before the first access network device triggers at least one of the end device or the second access network device to maintain the sequence of data packets from the end device using the second protocol stack : before the first access network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack, receive, by means of of the first access network device, a piece of data in each of the second data packets sent by a main network device pal, and sequentially processing, by the first access network device, the second data packets using the first protocol stack; and wherein the method further comprises: encrypting, by the first access network device, the sequentially processed second data packets or the data portion in each of the second data packets using the first protocol stack. 4. METHOD, according to any one of claims 1 or 2, characterized in that the data packets to be processed comprise third party data packets and sequentially process, by means of the first access network device, the data packets to be processed from the terminal device using the first protocol stack before the first access network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack comprises: before the first access network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack , receive, through the first access network device, the third data packets decrypted by the second device active access network using the second protocol stack of the second access network device; and sequentially processing, by the first access network device, the third decrypted data packets. 5. METHOD, according to any one of claims 1 or 3, characterized in that the data packets to be processed comprise fourth data packets and sequentially process, by means of the first access network device, the data packets to be processed from the terminal device using the first protocol stack before the first access network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using of the second protocol stack comprises: before the first access network device triggers at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack protocol, receive, through the first access network device, a piece of data in each of the fourth data packets sent by a main network device and sequentially processing, via the first access network device, the fourth data packets using the first protocol stack; and wherein the method further comprises: sending, via the first access network device, the fourth sequentially processed data packets to the second access network device, such that the second access network device encrypts the fourth packets of data processed sequentially or the data part in each of the fourth data packets using the second protocol stack. 6. METHOD, according to any one of claims 1 to 5, characterized in that it further comprises: under the condition that the first access network device determines that no data or data packets from the terminal device are to be processed by the first access device access network, triggering, by means of the first access network device, at least one of the terminal device or the second access network device to maintain the sequence of data packets from the terminal device using the second protocol stack . 7. TERMINAL DEVICE, characterized in that it comprises: a configuration unit, configured to configure a second protocol stack in accordance with the first trigger information sent through a first access network device, in which the second protocol stack is configured to maintain at least one of: a sequence of data packets between a second access network device and the terminal device or a security key of data packets between the second access network device and the terminal device; and a first sequential processing unit configured to, before the terminal device receives second trigger information sent by at least one of the first access network device or the second access network device, sequentially process data packets or data to be processed from the end device using a first protocol stack, wherein the second trigger information is configured to trigger the end device to maintain the sequence of data packets from the end device using the second protocol stack. 8. TERMINAL DEVICE, according to claim 7, characterized in that the data to be processed comprises the first data and the first sequential processing unit is specifically configured to: sequentially process the first data using the first protocol stack; and wherein the terminal device further comprises: a first encryption unit configured to encrypt the first data or sequentially processed data packets comprising the first data using the first protocol stack, and a first sending unit configured to send the encrypted data packets comprising the first data to the first access network device. 9. TERMINAL DEVICE, according to claim 7, characterized in that the data packets to be processed comprise first data packets and the first sequential processing unit is specifically configured for: before the terminal device receives the second trigger information sent by at least one of the first access network device or the second access network device, receive the first data packets sent by the first access network device, decrypt the first data packets or a piece of data in each of the first data packets using the first protocol stack, and sequentially processing the first decrypted data packets using the first protocol stack. 10. TERMINAL DEVICE according to either of claims 7 or 8, characterized in that the data to be processed comprises second data and the first sequential processing unit is specifically configured to: sequentially process the second data using the first protocol stack ; and wherein the terminal device further comprises: a second encryption unit configured to encrypt the second data or sequentially processed data packets comprising the second data using the second protocol stack, and a second sending unit configured to send the encrypted data packets comprising the second data to the second network device. 11. TERMINAL DEVICE, according to any one of claims 7 or 9, characterized in that the data packets to be processed comprise second data packets and the first sequential processing unit is configured to: receive the second data packets sent by the second device network, decrypting the second data packets or a piece of data in each of the second data packets using the second protocol stack, and sequentially processing the second data packets decrypted using the first protocol stack. 12. TERMINAL DEVICE, according to any one of claims 7 to 11, characterized in that it further comprises: a first receiving unit, configured to receive second trigger information sent by at least one of the first access network device or the second access network device; and a second sequential processing unit configured to maintain the sequence of data packets from the terminal device using the second protocol stack in accordance with the second trigger information. 13. TERMINAL DEVICE, according to claim 12, characterized in that the second trigger information is further configured to instruct the terminal device to release the first protocol stack and the terminal device further comprises: a release unit, configured to release the first protocol stack according to the second trigger information. 14. TERMINAL DEVICE, according to any one of claims 7 to 13, characterized in that the second trigger information is any one of Radio Resource Control (RRC) signaling, Radio Resource Control signaling Media Access (MAC), Downlink Control Information (DCI), or a bit in a data packet. 15. TERMINAL DEVICE according to any one of claims 7 to 14, characterized in that the first access network device is a source access network device and the second access network device is a target access network device; or the first access network device is a primary access network device in a multilink scenario and the second access network device is a secondary access network device in the multilink scenario.