WO2021169732A1 - 一种切换方法及通信装置 - Google Patents

一种切换方法及通信装置 Download PDF

Info

Publication number
WO2021169732A1
WO2021169732A1 PCT/CN2021/074503 CN2021074503W WO2021169732A1 WO 2021169732 A1 WO2021169732 A1 WO 2021169732A1 CN 2021074503 W CN2021074503 W CN 2021074503W WO 2021169732 A1 WO2021169732 A1 WO 2021169732A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
data packet
terminal device
target network
pdcp
Prior art date
Application number
PCT/CN2021/074503
Other languages
English (en)
French (fr)
Inventor
王瑞
韩锋
戴明增
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21760714.2A priority Critical patent/EP4087318A4/en
Publication of WO2021169732A1 publication Critical patent/WO2021169732A1/zh
Priority to US17/893,858 priority patent/US20220408319A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0069Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00698Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using different RATs
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016Hand-off preparation specially adapted for end-to-end data sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/02Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023Buffering or recovering information during reselection
    • H04W36/0235Buffering or recovering information during reselection by transmitting sequence numbers, e.g. SN status transfer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface

Definitions

  • This application relates to the field of wireless communication technology, and in particular to a handover method and communication device.
  • a cross-system handover occurs.
  • the terminal device When the terminal device moves between the coverage areas of different communication systems, a cross-system handover occurs.
  • the terminal device When performing a cross-system handover, the terminal device will first disconnect the data transmission with the source network device, and then perform data transmission with the target network device after accessing the target network device. If the data processing of the communication system in which the source network device and the target network device are located is inconsistent, there may be a problem of data loss in the terminal device during the cross-system handover, which affects the user's service experience.
  • the embodiments of the present application provide a handover method and a communication device to avoid data loss during the cross-system handover process of terminal equipment.
  • an embodiment of the present application provides a handover method, which can be executed by a source network device, and the method includes: the source network device sends a handover command to the terminal device, and the handover command is used to instruct the terminal device to switch from the source network device to The target network device, the source network device and the target network device adopt different wireless access technologies; the source network device sends at least one data packet unsuccessfully received by the terminal device to the target network device, and at least one data packet unsuccessfully received by the terminal device It includes one or more of the following data packets: data packets that have been processed by the packet data convergence protocol PDCP but have not received an acknowledgement response from the terminal device, and data packets that have not been PDCP processed.
  • the source network device sends a handover command to the terminal device, and the handover command is used to instruct the terminal device to switch from the source network device to The target network device, the source network device and the target network device adopt different wireless access technologies; the source network device sends at least one data packet unsuccessfully received by the terminal device to the
  • the source network device after the source network device sends a handover command to the terminal device, it can also send at least one data packet that the terminal device has not successfully received to the target network device, so that after the terminal device accesses the target network device, the target network device can The at least one data packet received from the source network device is sent to the terminal device. Since the data packets forwarded by the source network device to the target network device include data packets in which the source network device has performed PDCP processing but has not received a confirmation response from the terminal device, data loss of the terminal device during the cross-system handover can be effectively avoided.
  • the source network device and the target network device adopting different wireless access technologies can be embodied in that the protocol stack corresponding to the terminal device and the source network device includes the processing of the SDAP layer, and the terminal device The protocol stack corresponding to the target network device does not include the processing of the SDAP layer.
  • the source network device may The service data adaptation protocol SDAP header in the packet is removed, and then the data packet with the SDAP header removed is sent to the target network device.
  • the source network device may map the data packet to the corresponding DRB, and then The data packet mapped to the corresponding DRB is sent to the target network device, and the data packet does not contain the SDAP header.
  • the source network device removes the SDAP header from the data packet that has undergone PDCP processing but has not received the confirmation response from the terminal device, and maps the data packet that has not undergone PDCP processing to the DRB and then sends it directly, so that the source The data packets sent by the network device to the target network device do not include the SDAP header, so the data packets forwarded by the target network device to the terminal device do not include the SDAP header. In this way, after the terminal device is connected to the target network device, it can correctly receive and decode the data packet received from the target network device.
  • the source network device may The packet is sent to the target network device, and the data packet includes the SDAP header.
  • the source network device may not remove the SDAP header in the data packet, but instead The terminal device processes the data packets that contain the SDAP header and the data packets that do not contain the SDAP header received from the target network device separately. In this way, the terminal device can also correctly receive and decode the data packets received from the target network device. .
  • the method further includes: the source network device may send the PDCP sequence number corresponding to the data packet that has undergone PDCP processing but has not received the confirmation response from the terminal device to the target network device; And/or, the source network device may also send the first PDCP sequence number that can be allocated by the target network device to the target network device.
  • the target network device can inherit or continue the PDCP on the source network device side when assigning PDCP serial numbers to the data packets received from the source network device without PDCP processing and the data packets received from the core network.
  • Serial number so as to support terminal equipment in the process of cross-system handover according to the PDCP sequence number of the data packet in order to submit and de-duplicate processing.
  • an embodiment of the present application provides a handover method, which can be executed by a target network device, and the method includes: the target network device receives from the source network device at least one data packet that the terminal device unsuccessfully receives, and the terminal device is unsuccessful
  • the received at least one data packet includes one or more of the following data packets: the source network device has performed PDCP processing but has not received the data packet of the confirmation response from the terminal device, and the source network device has not performed PDCP
  • the source network device and the target network device adopt different wireless access technologies; after the terminal device accesses the target network device, the target network device sends at least one data packet that the terminal device has not successfully received to the terminal device .
  • the target network device can receive from the source network device at least one data packet unsuccessfully received by the terminal device, and after the terminal device accesses the target network device, send the at least one data packet to the terminal device. Since the at least one data packet includes a data packet in which the source network device has performed PDCP processing but has not received a confirmation response from the terminal device, data loss of the terminal device during the cross-system handover process can be effectively avoided.
  • the source network device and the target network device adopt different wireless access technologies, which can be embodied in that the protocol stack corresponding to the terminal device and the source network device includes the processing of the SDAP layer, and the terminal device The protocol stack corresponding to the target network device does not include the processing of the SDAP layer.
  • the data packet received by the target network device from the source network device that has been PDCP-processed by the source network device but has not received a confirmation response from the terminal device does not contain service data. Equipped with SDAP header.
  • the source network device removes the SDAP header before sending this part of the data packet to the target network device.
  • the terminal device since the data packet that the source network device has undergone PDCP processing sent by the target network device to the terminal device does not contain the SDAP header, the terminal device can be enabled to receive data from the target network device after accessing the target network device. The data packets are received and decoded correctly.
  • the source network device that the target network device receives from the source network device has undergone PDCP processing but has not received a confirmation response from the terminal device.
  • the data packet contains the SDAP header; the method further includes : The target network device sends the final identification packet to the terminal device, and the final identification packet is used to indicate that the data packet containing the SDAP header is sent.
  • the source network device can also directly send the data packet that has undergone PDCP processing but has not received the confirmation response of the terminal device to the target network device without removing the SDAP header.
  • the data packet sent by the target network device to the terminal device may include a data packet including an SDAP header and/or a data packet not including an SDAP header.
  • the terminal device can identify the data packet containing the SDAP header received from the target network device and the data packet not containing the SDAP header according to the final identification packet, so that the data packet containing the SDAP header And the data packet that does not contain the SDAP header is processed separately, so that the data packet can be received and decoded correctly.
  • the method further includes: the target network device may receive from the source network device the PDCP sequence corresponding to the data packet for which the source network device has performed PDCP processing but has not received the confirmation response from the terminal device And/or, the target network device can receive the first PDCP serial number that can be allocated by the target network device from the source network device.
  • the target network device can inherit or continue the PDCP serial number of the source network device, and continue to allocate PDCP serial numbers for the data packets received from the source network device without PDCP processing and the data packets received from the core network, thereby Support terminal equipment in the process of cross-system handover according to the PDCP sequence number of the data packet for sequential delivery and de-duplication processing.
  • an embodiment of the present application provides a handover method that can be executed by a terminal device.
  • the method includes: the terminal device receives a handover command from a source network device, the handover command is used to instruct the terminal device to switch from the source network device to the target Network equipment, the source network equipment and the target network equipment adopt different wireless access technologies; the terminal equipment accesses the target network equipment and receives the final identification packet from the target network equipment; the terminal equipment recognizes the reception from the target network equipment according to the final identification packet
  • the data packet of contains the data packet of the service data adaptation protocol SDAP header and/or the data packet that does not contain the SDAP header.
  • the terminal device can identify the data packet containing the SDAP header and/or the data packet not containing the SDAP header received from the target network device according to the last identification packet received from the target network device, and then targeting the data containing the SDAP header Packets and data packets that do not contain SDAP headers are processed separately, so that data packets can be correctly received and decoded, and data loss of terminal devices during cross-system handover is avoided.
  • the terminal device can identify the data packet that contains the SDAP header and/or the data packet that contains the SDAP header in the data packet received from the target network device according to the PDCP sequence number corresponding to the last identification packet. Packets containing SDAP headers.
  • the source network device and the target network device adopting different wireless access technologies can be embodied in that the protocol stack corresponding to the terminal device and the source network device includes the processing of the SDAP layer, and the terminal device The protocol stack corresponding to the target network device does not include the processing of the SDAP layer.
  • the PDCP entity in the terminal device when the terminal device recognizes that the data packet received from the target network device contains the SDAP header, the PDCP entity in the terminal device can perform PDCP processing on the data packet, and then the data packet It is sent to the SDAP entity in the terminal device, and the SDAP entity removes the SDAP header in the data packet.
  • the terminal device recognizes that the data packet received from the target network device does not contain the SDAP header, the PDCP entity in the terminal device can perform PDCP processing on the data packet, but after performing PDCP processing on the data packet, the data packet does not need to be Then send it to the SDAP entity to remove the SDAP header.
  • the data packets submitted by the PDCP entity in the terminal device to the upper layer may not include the SDAP header, so that the upper layer of the PDCP layer in the terminal device can correctly receive and decode the data.
  • the SDAP entity in the terminal device may send the data packet with the SDAP header removed to the upper layer; or, the PDCP entity in the terminal device may receive the SDAP header from the SDAP entity after removing the SDAP header. After sorting the data packets according to the PDCP sequence number of the data packets, the data packets are sent to the upper layer in sequence.
  • an embodiment of the present application provides a handover method that can be executed by a source network device.
  • the method includes: the source network device sends a handover command to the terminal device, the handover command instructs the terminal device to switch from the source network device to the target network
  • the source network device and the target network device adopt different wireless access technologies; the source network device continues to send data packets to the terminal device, and the source network device sends at least one data packet of the terminal device to the target network device, and the terminal device At least one data packet of is a data packet that has been processed by the source network device through PDCP; the source network device stops sending to the terminal device after receiving the first indication information used to indicate that the terminal device has successfully connected to the target network device data pack.
  • the source network device can continue to send data packets to the terminal device after sending the handover command to the terminal device, while sending at least one data packet of the terminal device that has undergone PDCP processing to the target network device.
  • the network device After the network device receives the first indication information used to indicate that the terminal device has successfully accessed the target network device, it stops sending data packets to the terminal device. In this way, the connection between the terminal device and the network device is not interrupted during the cross-system handover process, thereby improving the business continuity of the terminal device.
  • the source network device continues to send data packets to the terminal device through a PDCP entity, and the source network device can send at least one data packet of the terminal device processed by the PDCP entity to the target network equipment.
  • the source network device can continue to send data packets to the terminal device through the same PDCP entity while forwarding the data packets to the target network device on the other side, thereby avoiding data loss of the terminal device during the cross-system handover.
  • the source network device and the target network device adopt different wireless access technologies, which can be embodied in that the protocol stack corresponding to the terminal device and the source network device includes the processing of the SDAP layer, and the terminal device The protocol stack corresponding to the target network device does not include the processing of the SDAP layer.
  • the source network device may remove the service data adaptation protocol SDAP header in at least one data packet of the terminal device, and then remove the at least one data packet after the SDAP header is removed Send to the target network device.
  • At least one data packet sent by the source network device to the target network device does not include the SDAP header, so at least one data packet forwarded by the target network device to the terminal device does not include the SDAP header, so that the terminal can be After the device is connected to the target network device, it can correctly receive and decode the data packet received from the target network device.
  • the source network device may send at least one data packet of the terminal device to the target network device, and the data packet includes an SDAP header.
  • the SDAP header in the data packet may not be removed. Instead, the terminal device may respond to the received data packet containing the SDAP header from the target network device.
  • the data packet and the data packet that does not contain the SDAP header are processed separately, so that the terminal device can also correctly receive and decode the data packet received from the target network device.
  • the method further includes: the source network device may send the PDCP sequence number corresponding to the data packet that has undergone PDCP processing to the target network device; and/or the source network device may The first PDCP sequence number that can be allocated by the target network device is sent to the target network device.
  • the target network device can inherit or continue the PDCP sequence number on the source network device side when allocating the PDCP sequence number to the data packet received from the core network, thereby supporting the terminal device in the cross-system handover process according to the data
  • the PDCP serial number of the packet is submitted in order and de-duplicated processing.
  • an embodiment of the present application provides a handover method that can be executed by a target network device.
  • the method includes: the target network device receives at least one data packet of the terminal device from the source network device, and the source network device and the target network device Different wireless access technologies are adopted; after the terminal device is connected to the target network device, the target network device sends the at least one data packet to the terminal device, and the at least one data packet is processed by the source network device through PDCP Data packet; the target network device sends first indication information to the source network device, where the first indication information is used to indicate that the terminal device has successfully accessed the target network device.
  • the target network device can receive at least one data packet of the terminal device from the source network device, and after the terminal device accesses the target network device, the at least one data packet is sent to the terminal device and sent to the source network device.
  • the first indication information indicating that the terminal device has successfully accessed.
  • the target network device may send second indication information to the terminal device.
  • the second indication information is used to instruct the terminal device to stop receiving data packets from the source network device, so that the terminal device can complete the cross-connection. The process of system switching.
  • the source network device and the target network device adopting different wireless access technologies can be embodied in that the protocol stack corresponding to the terminal device and the source network device includes the processing of the SDAP layer, and the terminal device The protocol stack corresponding to the target network device does not include the processing of the SDAP layer.
  • the data packet that the source network device has performed PDCP processing does not include the service data adaptation protocol SDAP header.
  • the source network device may remove the SDAP header from the PDCP-processed data packet before sending it to the target network device.
  • the target network device can forward at least one data packet that does not contain the SDAP header to the terminal device, the terminal device can be enabled to correctly perform the correct data packet reception from the target network device after accessing the target network device. Receiving and decoding.
  • the data packet that the source network device has undergone PDCP processing includes an SDAP header; the method further includes: the target network device sends a final identification packet to the terminal device, and the final identification packet is used to indicate The data packet containing the SDAP header is sent.
  • the source network device can also directly send the PDCP processed data packet to the target network device without removing the SDAP header.
  • the data packet sent by the target network device to the terminal device may include For data packets containing SDAP headers and/or data packets not containing SDAP headers, by sending a final identification packet to the terminal device, the terminal device can recognize the data packet containing the SDAP header received from the target network device according to the final identification packet, and The data packet that does not contain the SDAP header, so that the data packet that contains the SDAP header and the data packet that does not contain the SDAP header are processed separately, so that the data packet can be correctly received and decoded.
  • the method further includes: the target network device receives from the source network device the PDCP sequence number corresponding to the data packet that the source network device has performed PDCP processing; and/or, the target network device receives the PDCP sequence number from the source network device; The network device receives the first PDCP serial number that the target network device can assign.
  • the target network device can inherit or continue the PDCP sequence number of the source network device, and continue to allocate PDCP sequence numbers for data packets received from the core network, thereby supporting the terminal device in the cross-system handover process according to the PDCP sequence of the data packet Numbers are submitted in order and de-duplicated processing.
  • an embodiment of the present application provides a handover method, which can be executed by a terminal device, and the method includes: the terminal device receives a handover command from a source network device, the handover command instructs the terminal device to switch from the source network device to the target network device , The source network device and the target network device adopt different wireless access technologies; the terminal device continues to receive data packets from the source network device through the PDCP entity of the packet data convergence protocol; the terminal device accesses the target network device and receives data from the target network device through the PDCP entity The network device receives at least one data packet.
  • the terminal device after receiving the handover command from the source network device, the terminal device can continue to receive data packets from the source network device on the one hand, and access the target network device on the other side, and receive the target network device forwarding from the target network device through the same PDCP entity At least one packet.
  • the connection between the terminal device and the network device is not interrupted during the cross-system handover process, thereby improving the business continuity of the terminal device.
  • the source network device and the target network device adopting different wireless access technologies can be embodied in that the protocol stack corresponding to the terminal device and the source network device includes the processing of the SDAP layer, and the terminal device The protocol stack corresponding to the target network device does not include the processing of the SDAP layer.
  • the data packet received by the terminal device from the source network device includes a service data adaptation protocol SDAP header; the method further includes: the PDCP entity performs PDCP on the data packet received from the source network device Process, and send the PDCP processed data packet to the SDAP entity in the terminal device to remove the SDAP header.
  • the SDAP entity can send the data packet with the SDAP header removed to the upper layer, or the PDCP entity can also receive the data packet with the SDAP header removed from the SDAP entity, and then the PDCP entity will remove the data after the SDAP header The packet is sent to the upper layer. In this way, the terminal device can correctly receive and decode the data packet received from the source network device.
  • the data packet received by the terminal device from the target network device does not contain the SDAP header; optionally, the source network device may remove the data packet before sending the data packet to the target network device. Among them is the SDAP header.
  • the method further includes: the PDCP entity performs PDCP processing on the data packet received from the target network device.
  • the terminal device since the data packet sent by the target network device to the terminal device does not contain the SDAP header, the terminal device can correctly receive and decode the data packet received from the target network device.
  • the data packet received by the terminal device from the target network device includes a data packet containing a SDAP header and/or a data packet not containing a SDAP header; the method further includes: the PDCP entity receives from the target The network device receives the last identification packet; according to the last identification packet, the PDCP entity identifies the data packet containing the SDAP header and/or the data packet not containing the SDAP header in the data packet received from the target network device.
  • the source network device can also directly send the data packet that has undergone PDCP processing but has not received the confirmation response of the terminal device to the target network device without removing the SDAP header.
  • the data packet sent by the target network device to the terminal device may include a data packet containing the SDAP header and/or a data packet not containing the SDAP header, and the data packet containing the SDAP header may be received by the target network device from the source network device
  • a data packet, a data packet that does not include the SDAP header may be a data packet received by the target network device from the core network.
  • the terminal device can identify the data packet that contains the SDAP header and the data packet that does not contain the SDAP header received from the target network device according to the final identification packet.
  • the data packets containing the SDAP header are processed separately, so that the data packets can be received and decoded correctly.
  • the method when the terminal device recognizes the data packet containing the SDAP header received from the target network device, the method further includes: the PDCP entity performs PDCP processing on the data packet, and performs PDCP processing The latter data packet is sent to the SDAP entity to remove the SDAP header; the PDCP entity receives the data packet with the SDAP header removed from the SDAP entity.
  • the method further includes: the PDCP entity performs PDCP processing on the data packet.
  • the terminal device separately processes the data packet that contains the SDAP header and the data packet that does not contain the SDAP header received from the target network device.
  • the PDCP entity After the PDCP entity performs the PDCP processing on the data packet, it will include the SDAP header.
  • the data packet is sent to the SDAP entity to remove the SDAP header. In this way, none of the data packets submitted to the upper layer can include the SDAP header, so that all data packets can be received and decoded correctly.
  • the PDCP entity includes a first processing unit and a second processing unit, where the first processing unit corresponds to the security configuration of the source network device, and the second processing unit corresponds to the target network device.
  • the method further includes: the PDCP entity performs PDCP processing on the data packet received from the source network device through the first processing unit, and performs PDCP processing on the data packet received from the target network device through the second processing unit.
  • the PDCP entity in the terminal device can be a dynamic dual-stack structure, that is, the PDCP entity can include two processing units, and each processing unit is connected to the source network device and the target network device. Configure accordingly.
  • the terminal device can use different processing units in the PDCP entity to perform PDCP processing on the data packet received from the source network device and the data packet received from the target network device, so that the data packet received from the source network device and the data packet received from the target network device
  • the received data packets can be processed by normal PDCP, which enhances the applicability of the switching method and avoids the problem of data processing failure due to inconsistencies in the PDCP security configuration adopted by the source network device and the target network device.
  • the method further includes: the PDCP entity sorts the data packets received from the source network device and the data packets received from the target network device according to the PDCP sequence number of the data packet and/or De-duplication processing: The PDCP entity sends the processed data packets to the upper layer in sequence.
  • an embodiment of the present application provides a communication device that has the function of a source network device in any possible design of the foregoing first aspect or the first aspect, or has the capability to implement the foregoing second or second aspect.
  • the function of the target network device in any possible design of the aspect, or the function of the source network device in any possible design of the fourth aspect or the fourth aspect, or the function of the source network device in any possible design of the foregoing fourth aspect or the fourth aspect, or the realization of the fifth aspect or the fifth aspect.
  • the device can be a network device or a chip contained in the network device.
  • the functions of the above-mentioned communication device may be realized by hardware, or may be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units or means corresponding to the above-mentioned functions.
  • the device may also have the function of realizing the terminal device in any possible design of the foregoing fourth aspect or the fourth aspect, or have the function of realizing the terminal device in any possible design of the foregoing sixth aspect or the sixth aspect
  • the device can be a terminal device or a chip included in the terminal device.
  • the functions of the above-mentioned communication device may be realized by hardware, or may be realized by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units or means corresponding to the above-mentioned functions.
  • the structure of the device includes a processing module and a transceiver module, wherein the processing module is configured to support the device to perform the first aspect or the corresponding source network device in any of the first aspects of the design.
  • Function, or perform the corresponding function of the target network device in the above-mentioned second aspect or any one of the second aspects of the design, or perform the corresponding function of the source network device in any possible design of the above-mentioned fourth aspect or the fourth aspect Or perform the corresponding function of the target network device in any possible design of the fifth aspect or the fifth aspect, or perform the corresponding function of the terminal device in any possible design of the sixth aspect or the sixth aspect, or Perform the corresponding function of the terminal device in any possible design of the seventh aspect or the seventh aspect.
  • the transceiver module is used to support communication between the device and other communication devices. For example, when the device is a source network device, it can send at least one data packet that the terminal device has not successfully received to the target network device.
  • the communication device may also include a storage module, which is coupled with the processing module, which stores program instructions and data necessary for the device.
  • the processing module may be a processor
  • the communication module may be a transceiver
  • the storage module may be a memory.
  • the memory may be integrated with the processor or may be provided separately from the processor, which is not limited in this application.
  • the structure of the device includes a processor and may also include a memory.
  • the processor is coupled with the memory, and can be used to execute the computer program instructions stored in the memory, so that the device executes the above-mentioned first aspect or any one of the possible design methods of the first aspect, or executes the above-mentioned second aspect or the second aspect.
  • the method in any possible design of the aspect, or the method in any possible design of the above third aspect or the third aspect, or the method in any possible design of the fourth aspect or the fourth aspect above
  • the method in, or implements the method in any possible design of the fifth aspect or the fifth aspect, or implements the method in any possible design of the sixth aspect or the sixth aspect.
  • the device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication interface may be a transceiver or an input/output interface; when the device is a chip included in the network device or terminal device, the communication interface may be an input/output interface of the chip.
  • the transceiver may be a transceiver circuit, and the input/output interface may be an input/output circuit.
  • an embodiment of the present application provides a chip system, including: a processor, the processor is coupled to a memory, the memory is used to store a program or an instruction, when the program or instruction is executed by the processor , So that the chip system implements the method in any possible design of the first aspect or the first aspect, or implements the method in any possible design of the second aspect or the second aspect, or implements the method in the first aspect.
  • the method in any possible design of the third aspect or the third aspect, or the method in any possible design of the foregoing fourth aspect or the fourth aspect, or the realization of any of the foregoing fifth aspect or the fifth aspect A possible design method, or a possible design method for implementing the sixth aspect or the sixth aspect described above.
  • the chip system further includes an interface circuit, which is used to exchange code instructions to the processor.
  • processors in the chip system, and the processors may be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be set on different chips.
  • the setting method of the processor is not specifically limited.
  • an embodiment of the present application provides a computer-readable storage medium on which a computer program or instruction is stored.
  • the computer executes the first aspect or any one of the first aspect.
  • the embodiments of the present application provide a computer program product.
  • the computer reads and executes the computer program product, the computer executes the first aspect or any one of the possible design methods in the first aspect, Or implement the method in any possible design of the above second aspect or the second aspect, or implement the method in any possible design of the above third aspect or the third aspect, or implement the fourth or first aspect above Any one of the four possible design methods, or implement any of the above fifth or fifth aspects, or implement any one of the above sixth or sixth aspects Method in design.
  • an embodiment of the present application provides a communication system, which includes the aforementioned source network device, target network device, and at least one terminal device.
  • the communication system may also include core network equipment.
  • FIGS 1a to 1c are schematic diagrams of application scenarios to which the embodiments of this application are applicable;
  • FIG. 2 is a schematic flowchart of a handover method provided by an embodiment of the application
  • 3a is a schematic diagram of an air interface protocol stack in a communication system of the first communication standard provided by an embodiment of the application;
  • 3b is a schematic diagram of an air interface protocol stack in a communication system of a second communication standard provided by an embodiment of the application;
  • FIG. 4 is a schematic diagram of a first implementation manner of a handover method in the first scenario provided by an embodiment of this application;
  • FIG. 5 is a schematic diagram of a second implementation manner of a handover method in the first scenario provided by an embodiment of this application;
  • FIG. 6 is a schematic diagram of an implementation manner of a handover method in the second scenario provided by an embodiment of this application.
  • FIG. 7 is a schematic flowchart of another handover method provided by an embodiment of the application.
  • FIG. 8 is a schematic diagram of a first implementation manner of another handover method in the first scenario provided by an embodiment of this application.
  • FIG. 9 is a schematic diagram of a second implementation manner of another handover method in the first scenario provided by an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 11 is another schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 12 is another schematic structural diagram of another communication device according to an embodiment of the application.
  • FIG. 13 is a schematic diagram of another structure of another communication device provided by an embodiment of this application.
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE frequency division duplex FDD
  • TDD LTE Time division duplex
  • UMTS universal mobile telecommunication system
  • WIMAX worldwide interoperability for microwave access
  • the technical solutions provided by the embodiments of this application are applicable to scenarios where communication systems of different communication standards coexist.
  • Figures 1a to 1c are schematic diagrams of application scenarios to which the embodiments of this application apply, or networks to which the embodiments of this application apply.
  • the network architecture includes a source network device, a target network device, and a terminal device.
  • the source network device refers to the network device that the terminal device accesses before the handover
  • the target network device refers to the network device that the terminal device accesses after the handover.
  • the source network device and the target network device adopt different radio access technologies (radio access technology, RAT).
  • RAT radio access technology
  • the source network device and the target network device are network devices in a communication system with different communication standards.
  • the technical solution provided by the embodiment of the present application can support the terminal device to switch between communication systems of different communication standards.
  • the terminal device may switch between the 5G communication system and the 4G communication system
  • the source network device may be a network device in the 5G communication system
  • the target network device may be a network device in the 4G communication system.
  • the source network device may be a network device in a 4G communication system
  • the target network device may be a network device in a 5G communication system.
  • the 5G communication system can also be referred to as a 5G system for short
  • the 4G communication system can also be referred to as a 4G system for short. generation core, 5GC).
  • the core network to which network devices are connected is called an evolved packet core (EPC).
  • EPC evolved packet core
  • the embodiments of the present application may cover a variety of different handover scenarios.
  • the coverage area of the 5G communication system overlaps the coverage area of the 4G communication system.
  • the terminal device may switch across systems due to the movement of the location, such as switching from a 5G communication system to a 4G communication system, or switching from a 4G communication system to a 5G communication system.
  • the terminal device may also switch from a single connection to a dual connection or a multi-connection across the system due to the movement of the location. Dual connection of 4G communication system.
  • terminal equipment may undergo cross-system handover due to changes in the services performed, that is, a fallback of access to the network occurs.
  • FIGS. 1a to 1c are described by taking the terminal device switching between a 5G communication system and a 4G communication system as an example, but this is only an example and does not constitute a limitation of the present application.
  • the handover scenario in the embodiment of the present application is not limited to the handover scenario described in FIG. 1a to FIG. 1c.
  • the switching may be switching between single connection and dual connection, or switching between single connection and multiple connections.
  • the dual connectivity refers to that a terminal device is simultaneously connected to two network devices. Among them, one network device is the main network device, and the other network device is the auxiliary network device. The main network device can also be called the main network device. A node (master node, MN), and a secondary network device may also be called a secondary node (secondary node, SN). Multi-connection is similar to this. It means that the terminal device is connected to multiple network devices at the same time. Among them, one network device is the main network device, and the other one or more network devices are the auxiliary network devices.
  • terminal equipment can support evolved universal land surface wireless access and new air interface dual connectivity (E-UTRA NR dual connectivity, EN-DC).
  • E-UTRA NR dual connectivity EN-DC
  • terminal equipment is connected to two network devices at the same time One is a network device in a 4G communication system, and the other is a network device in a 5G communication system.
  • the network device in the 4G communication system is the main network device, and the network device in the 5G communication system is the auxiliary network device.
  • terminal equipment in the future can also support the new air interface and the evolved universal land surface wireless access dual connectivity (NR E-UTRA dual connectivity, NE-DC), in the NE-DC mode, terminal equipment access at the same time
  • One of the two network devices is a network device in the 4G communication system
  • the other is a network device in the 5G communication system
  • the network device in the 5G communication system is the main network device
  • the network device in the 4G communication system is the auxiliary network equipment.
  • the terminal device can also support the evolved universal land surface wireless access and the new air interface dual connection (Next Generation E-UTRA NR dual connectivity, NGEN-DC) connected to the 5GC, and the dual connection NR-DC of NR and NR.
  • Next Generation E-UTRA NR dual connectivity, NGEN-DC Next Generation E-UTRA NR dual connectivity
  • Dual connectivity includes primary cell group (master cell group, MCG) and secondary cell group (secondary cell group, SCG), MCG can include one or more carriers, if it includes multiple carriers, these carriers There can be carrier aggregation (CA), and the SCG can include one or more carriers. If multiple carriers are included, the carriers can be CA.
  • the main network device is responsible for the scheduling of the MCG
  • the auxiliary network device is responsible for the scheduling of the SCG.
  • Terminal equipment is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air ( For example, airplanes, balloons, satellites, etc.
  • the terminal device may communicate with the core network via a radio access network (RAN), and exchange voice and/or data with the RAN.
  • the terminal device may be a mobile phone (mobile).
  • the embodiments of this application do not limit the application scenarios. Terminal devices may also be used sometimes. It is called user equipment (UE), mobile station, remote station, etc.
  • the embodiments of the present application do not limit the specific technology, device form, and name adopted by the terminal device.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices or smart wearable devices, etc. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes Wait.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • Use such as all kinds of smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring.
  • the terminal device in the embodiments of the present application may also be a vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip, or vehicle-mounted unit that is built into a vehicle as one or more components or units, and the vehicle passes through the built-in vehicle-mounted module, vehicle-mounted Modules, on-board components, on-board chips, or on-board units can implement the method of the present application.
  • Network equipment also called access network equipment, is a device in the network used to connect terminal equipment to the wireless network.
  • the network device may be a node in a radio access network, may also be called a base station, or may be called a radio access network (RAN) node (or device).
  • the network device can be used to convert received air frames and Internet Protocol (IP) packets into each other, and act as a router between the terminal device and the rest of the access network, where the rest of the access network can include an IP network.
  • IP Internet Protocol
  • the network equipment can also coordinate the attribute management of the air interface.
  • the network equipment may include an evolved base station (NodeB or eNB or e-NodeB, evolutional NodeB) in a long term evolution (LTE) system or an evolved LTE system (LTE-Advanced, LTE-A), such as
  • LTE long term evolution
  • LTE-A evolved LTE system
  • the traditional macro base station eNB and the micro base station eNB in the heterogeneous network scenario may also include the next generation node B (next generation) in the new radio (NR) system of the fifth generation mobile communication technology (5th generation, 5G).
  • NR new radio
  • node B node B, gNB
  • RNC radio network controller
  • node B node B
  • BSC base station controller
  • base transceiver station base transceiver station
  • BTS transmission reception point
  • TRP home base station
  • home evolved NodeB for example, home evolved NodeB, or home Node B, HNB
  • baseband unit BBU
  • baseband pool BBU pool or WiFi access Access point (AP), etc.
  • AP WiFi access Access point
  • CU centralized unit
  • DU distributed unit
  • the application examples are not limited.
  • CU supports radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP), and service data adaptation protocol (service data adaptation). Protocol, SDAP) and other protocols; DU mainly supports radio link control (RLC), media access control (MAC) and physical layer protocols.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • service data adaptation protocol service data adaptation protocol
  • SDAP radio link control
  • MAC media access control
  • “Multiple” refers to two or more than two. In view of this, “multiple” may also be understood as “at least two” in the embodiments of the present application. "At least one” can be understood as one or more, for example, one, two or more. For example, including at least one means including one, two or more, and it does not limit which ones are included. For example, if at least one of A, B, and C is included, then A, B, C, A and B, A and C, B and C, or A and B and C are included. In the same way, the understanding of "at least one" and other descriptions is similar.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the order, timing, priority, or importance of multiple objects.
  • the descriptions of “first” and “second” do not limit the objects to be different.
  • FIG. 2 is a schematic flowchart of a handover method provided by an embodiment of this application. The method specifically includes the following steps:
  • Step S201 The source network device sends a switching command to the terminal device, where the switching command is used to instruct the terminal device to switch from the source network device to the target network device.
  • the terminal device before the source network device sends a handover command to the terminal device, the terminal device can access the source network device and perform data transmission with the source network device.
  • the aforementioned handover command may be a handover command message or signaling, which is not limited.
  • Step S202 The source network device sends at least one data packet that the terminal device has not successfully received to the target network device.
  • the at least one data packet unsuccessfully received by the terminal device refers to at least one data packet that the source network device considers that the terminal device has not successfully received, that is, all possible data packets that are not successfully received by the terminal device at present.
  • the at least one data packet that the terminal device has not successfully received may include: a data packet that the source network device has sent to the terminal device but has not yet received a confirmation response from the terminal device, and the source network device has not yet sent to the terminal device Packets.
  • the data packet that the source network device has sent to the terminal device but has not received an acknowledgment response from the terminal device may be a data packet processed by the source network device through the packet data convergence protocol (packet data convergence protocol, PDCP), such as packet data Convergence protocol protocol data unit (packet data convergence protocol protocol data unit, PDCP PDU).
  • packet data convergence protocol packet data convergence protocol
  • PDCP PDU packet data Convergence protocol protocol data unit
  • the data packet that the source network device does not send to the terminal device may include a data packet that the source network device has performed PDCP processing, such as PDCP PDU, and may also include a data packet that the source network device has not yet undergone PDCP processing through the PDCP layer, such as packet
  • the data convergence protocol service data unit packet data convergence protocol service data unit, PDCP SDU
  • the source network device has sent a data packet to the terminal device but has not yet received the confirmation response from the terminal device. This does not absolutely mean that the data packet has not been successfully received by the terminal device, or that the data packet After that, it will not be successfully received by the terminal device.
  • the terminal device has not sent a confirmation response to the source network device; it is also possible that the data packet has been successfully received by the terminal device, and the terminal device has also sent a confirmation response to the source network device, but The source network device has not received the confirmation response; it is also possible that the data packet has not been successfully received by the terminal device at present, but was successfully received by the terminal device afterwards, and the terminal device has sent the confirmation response corresponding to the data packet to the source network device .
  • step S201 and step S202 does not limit the order of execution of step S201 and step S202, for example, first execute S201 and then execute S202, or execute S202 first and then execute S201.
  • Step S203 The target network device receives from the source network device at least one data packet that the terminal device has not successfully received.
  • Step S204 The terminal device receives the switching command from the source network device.
  • the terminal device after receiving the switching command from the source network device, the terminal device can disconnect the connection with the source network device and stop data transmission with the source network device.
  • Step S205 The terminal device accesses the target network device.
  • the terminal device may initiate a random access process to access the target network device after receiving the handover command from the source network device.
  • the target network device may send at least one data packet that the terminal device has not successfully received to the terminal device after the terminal device accesses the target network device.
  • the terminal device may receive the aforementioned at least one data packet from the target network device.
  • the source network device can forward all possible current data packets that the terminal device has not successfully received to the target network device, and the target network device sends this part of the data packet to the terminal device, it can effectively avoid different systems.
  • the data of the terminal device is lost during the switching process, thereby improving the user experience.
  • the at least one data packet that the terminal device mentioned in step S202 has not successfully received may also be classified according to whether the source network device has performed PDCP processing on the data packet. That is, the at least one data packet that the terminal device mentioned in step S202 has not successfully received may include one or more of the following data packets: the source network device has performed PDCP processing but has not received a confirmation response from the terminal device Data packets that are not PDCP processed by the source network device.
  • the data packet in which the source network device has performed PDCP processing but has not received the confirmation response from the terminal device may include: the source network device has performed PDCP processing and the source network device has sent data packets to the terminal device through the air interface , And data packets that the source network device has processed PDCP but the source network device has not sent to the terminal device.
  • the source network device that has performed PDCP processing can be understood as the source network device has processed all or part of the functional modules in the PDCP entity on the data packet. For example, if the data packet is assigned a corresponding PDCP sequence number, it can be The data packet assigned with the PDCP sequence number is considered to be a data packet that has undergone PDCP processing.
  • the data packet that the source network device has performed PDCP processing may be a PDCP PDU.
  • the data packets that the source network device has not undergone PDCP processing may include: data packets that the source network device has not yet sent to the PDCP layer for PDCP processing, and data packets of the terminal device newly received by the source network device from the core network device ( That is, fresh data).
  • the source network device when a terminal device performs a cross-system handover, the source network device does not forward the PDCP processed data packet to the target network device. Therefore, if this part of the data packet is not received by the terminal device, it is equivalent to being lost during the handover.
  • at least one data packet forwarded by the source network device to the target network device may include a data packet in which the source network device has performed PDCP processing but has not yet received a confirmation response from the terminal device, and the source network device Data packets that are not processed by PDCP can effectively avoid data loss of terminal devices during cross-system handover, thereby improving user experience.
  • the source network device may be a network device in a communication system that adopts the first communication standard.
  • the air interface protocol stack of the network device and the terminal device includes the SDAP layer Processing.
  • the target network device may be a network device in a communication system that adopts the second communication standard.
  • the air interface protocol stack of the network device and the terminal device does not include SDAP layer processing.
  • the source network device may be an access network device in a 5G communication system
  • the target network device may be an access network device in a 4G communication system.
  • FIG. 3a is a schematic diagram of an air interface protocol stack of a network device and a terminal device in a communication system of the first communication standard provided by an embodiment of this application.
  • the process of sending data from the source network device to the terminal device specifically includes: the SDAP entity in the source network device first performs quality of service (QoS) on the packet received from the upper layer. ) Mapping from flow to data radio bearer (DRB), where there is a one-to-one correspondence between DRB and PDCP entities, that is, one DRB corresponds to one PDCP entity. Subsequently, the SDAP entity can perform other processing on the data packet.
  • QoS quality of service
  • DRB data radio bearer
  • the SDAP entity can add a SDAP header to the data packet to generate a SDAP PDU, and the generated SDAP PDU can be used as a PDCP SDU and sent to the PDCP corresponding to the DRB.
  • the SDAP header is not configured, the SDAP entity can directly send the data packet as a PDCP SDU to the PDCP entity corresponding to the DRB for further processing.
  • the PDCP entity receives the PDCP SDU from the SDAP entity, it can perform processing such as numbering the PDCP SDU, security protection (including integrity protection and/or encryption), adding PDCP headers, and generating PDCP PDU.
  • the PDCP entity may also perform header compression, routing, copying, and other processing, which is not limited in this application.
  • the PDCP PDU generated by the PDCP entity can be sent to the RLC, after further processing by the RLC, sent to the MAC and PHY, and finally carried on the air interface for transmission.
  • the terminal device when it receives data from the source network device, it can perform symmetric processing in the reverse direction, that is, it is processed by PHY and MAC first, and then sent to RLC to obtain PDCP PDU. Then the obtained PDCP PDU is sent to the PDCP entity for processing such as removal of the PDCP header, security processing (including decryption and/or integrity check), reordering/repetition detection, etc., to generate a PDCP SDU.
  • the generated PDCP SDU can be sent as SDAP PDU to the SDAP entity for processing. If it is the SDAP header, the SDAP entity needs to remove the SDAP header, and then map the obtained data packet to the QoS flow through the DRB corresponding to the PDCP entity and send it to upper layer.
  • FIG. 3b is a schematic diagram of the air interface protocol stack of the network device and the terminal device in the communication system of the second communication standard according to an embodiment of this application.
  • the upper layer data can be directly sent to the PDCP entity for processing.
  • the PDCP entity receives the data packet from the upper layer, it can perform processing such as numbering, header compression, security protection (including integrity protection and/or encryption), and adding a PDCP header to the data packet to generate a PDCP PDU.
  • the generated PDCP PDU is sent to the RLC layer for further processing, and then processed by the MAC and PHY, and then transmitted to the terminal device through the air interface.
  • the target network device can Use the same PDCP (such as NR PDCP) as the source network device side, or use a different PDCP (such as E-UTRA PDCP), which is not limited in this application.
  • the terminal device when it receives data from the source network device, it can perform symmetric processing in the reverse direction, that is, it is processed by PHY and MAC first, and then sent to RLC to obtain PDCP PDU. Then the obtained PDCP PDU is sent to the PDCP entity for removal of the PDCP header, security processing (including decryption and/or integrity check), reordering/repetitiveness detection, etc., to obtain the PDCP SDU, and then send it to the upper layer.
  • symmetric processing in the reverse direction that is, it is processed by PHY and MAC first, and then sent to RLC to obtain PDCP PDU.
  • the obtained PDCP PDU is sent to the PDCP entity for removal of the PDCP header, security processing (including decryption and/or integrity check), reordering/repetitiveness detection, etc., to obtain the PDCP SDU, and then send it to the upper layer.
  • At least one unsuccessful data packet sent by the source network device to the target network device may contain an SDAP header.
  • the target network device forwards this part of the data packet to the terminal device, because after the terminal device is connected to the target network device, it matches the target network device
  • the protocol stack of the air interface does not include the processing of the SDAP layer. After the terminal device receives the data packet, it does not recognize the SDAP header in it, and cannot process the SDAP header in the data packet, which will cause data reception and decoding. fail.
  • the first possible implementation is that, among at least one data packet that the terminal device has not successfully received, the source network device has performed PDCP processing but has not yet received the confirmation response from the terminal device.
  • the network device can remove the SDAP header in the data packet before sending the data packet to the target network device, and then send the data packet with the SDAP header removed to the target network device, and then the data packet can be sent to the target network device.
  • the packet is sent to the terminal device.
  • the source network device can assign each packet that has undergone PDCP processing but has not received a confirmation response from the terminal device to correspond to
  • the PDCP sequence number is sent to the target network device together with the data packet.
  • the source network device can also send the first PDCP serial number that can be allocated by the target network device to the target network device. Since PDCP serial numbers are generally allocated in sequence, the first PDCP serial number that can be allocated by the target network device can be The next PDCP sequence number of the PDCP sequence number allocated by the source network device.
  • the target network device can continue or inherit the PDCP serial number on the source network device side, and allocate the PDCP serial number to the data packet that the source network device does not perform PDCP processing and the data packet of the terminal device received by the target network device from the core network; accordingly; Yes, when the terminal device receives a data packet from the target network device, it can perform sequential delivery and repetitive detection according to the PDCP sequence number corresponding to the data packet.
  • the terminal device can also send a PDCP status report to the target network device to inform the target network device of data packets that it has not received.
  • the data packet in which the source network device has performed PDCP processing but has not received the confirmation response from the terminal device may be a PDCP SDU, that is, the source network device may send the PDCP SDU that has not received the confirmation response from the terminal device.
  • the source network device may send the PDCP SDU that has not received the confirmation response from the terminal device.
  • the target network device can use its own PDCP to continue processing the received data packet to generate PDCP PDU, for example, the target network device can use its own security
  • the mechanism encrypts and/or protects the integrity of the received data packet, as shown in Figure 5, T-encryption and T-integrity protection, and then is processed by RLC, MAC, PHY, etc., and then sent to the terminal through the air interface equipment.
  • the data packets forwarded from the source network device sent by the target network device to the terminal device can be correctly received and decoded by the terminal device, avoiding the inconsistency of the PDCP used by the source network device side and the target network device side and the terminal device accessing the target After the network device, using a protocol stack that matches the target network device, it is impossible to perform symmetric PDCP processing on the data packets processed by the source network device's PDCP.
  • the source network device can remove the SDAP header at the PDCP layer, or at the SDAP layer, or remove the SDAP header in other ways, such as other methods in the protocol stack.
  • the SDAP header is removed from the layer, which is not limited in this application.
  • the source network device can map the data packet to the corresponding DRB without adding the SDAP header to the data packet, and then The data packet mapped to the DRB is sent to the target network device. If the source network device has performed SDAP processing on some data packets and added SDAP headers, but has not yet been sent to the PDCP layer, the source network device should also remove the added SDAP headers in the data packets, and then remove them The data packet with the SDAP header is sent to the target network device.
  • the target network device after the target network device receives this part of the data packet that the source network device has not processed by PDCP, it can use its own PDCP for processing, and then after processing by RLC, MAC, PHY, etc., it is sent to the terminal device through the air interface .
  • this part of the data packets that the source network device has not processed PDCP has not yet been assigned the corresponding PDCP serial number by the source network device, so the source network device will not
  • the PDCP sequence number corresponding to this part of the data packet is sent to the target network device.
  • the target network device can assign a PDCP serial number to this part of the data packets that have not been processed by the PDCP of the source network device by itself, and perform PDCP processing. For example, the target network device may start from the first allocatable PDCP sequence number received by the source network device, and allocate the corresponding PDCP sequence number to the data packet received from the source network device that has not been PDCP processed by the source network device.
  • the source network device received by the target network device from the source network device has undergone PDCP processing and the source network device has not undergone PDCP processing in the data packet does not include the SDAP header, and the source network device
  • the PDCP SDU or fresh data forwarded by the target network device can be PDCP processed by the target network device, so that the terminal device can correctly receive and decode at least one data packet received from the target network device.
  • the second possible implementation manner is that, as shown in FIG. 5, when the source network device sends at least one data packet that the terminal device has not successfully received to the target network device, the process of removing the SDAP header may not be performed. That is, the source network device may send at least one data packet that the terminal device unsuccessfully receives to the target network device, and the at least one data packet that the terminal device unsuccessfully receives may include a data packet containing an SDAP header and/or not containing Data packet with SDAP header. Wherein, in the at least one data packet that the terminal device has not successfully received, the data packet in which the source network device has performed the PDCP processing but has not received the confirmation response from the terminal device includes the SDAP header added before the PDCP processing. In the at least one data packet that the terminal device has not successfully received, the data packet in which the source network device has not performed PDCP processing does not include the SDAP header.
  • the target network device may receive at least one data packet that the terminal device has not successfully received from the source network device, and after the terminal device accesses the target network device, the at least one data packet that the terminal device has not successfully received and the first final identification packet Sent to the terminal device, the first last identification packet is used to indicate that the data packet containing the SDAP header is sent.
  • the terminal device can identify the data packet that contains the SDAP header and/or the data packet that does not contain the SDAP header in the data packet received from the target network device according to the first last identification packet, and identify the data packet that contains the SDAP header and the data packet that does not contain the SDAP header.
  • the data packets containing the SDAP header are processed separately.
  • the terminal device can identify the data packet that contains the SDAP header and/or the data packet that does not contain the SDAP header in the data packet received from the target network device according to the PDCP sequence number of the first and last identification packet. For example, when the first last identification packet is an empty data packet sent by the target network device to the terminal device to identify the end, the terminal device may consider that the PDCP sequence number received from the target network device is less than the PDCP of the first last identification packet The data packet of the serial number contains the SDAP header, and the data packet whose PDCP serial number received from the target network device is greater than the serial number of the first and last identification packet does not contain the SDAP header.
  • the terminal device may consider that it is from the target network device
  • the received PDCP sequence number is less than the PDCP sequence number of the first and last identification packet, and the first and last identification packet contains the SDAP header, and the PDCP sequence number received from the target network device is greater than the sequence number of the first and last identification packet.
  • the SDAP header is not included in the packet.
  • Another implementation of the first last identification packet can also be that the target network device sends a terminal device to identify the first data packet that does not contain the SDAP header.
  • the PDCP sequence number of the packet is N
  • the last The PDCP sequence number of a packet containing the SDAP header is N-1, that is, packets with a PDCP sequence number less than N need to be processed to remove the SDAP header, and datagrams with a PDCP sequence number greater than or equal to N do not contain the SDAP header .
  • the terminal device can send the data packet in the PDCP
  • the SDAP entity sent to the terminal device removes the SDAP header, and then submits it to the upper layer, so that the data packet can be correctly received and decoded.
  • the SDAP entity can directly submit the data packet with the SDAP header removed to the upper layer, or it can send the data packet with the SDAP header removed back to the PDCP entity.
  • the serial numbers are reordered, they are submitted to the upper layer in order.
  • the upper layer refers to the upper layer of the PDCP layer in the protocol stack matching the target network device established by the terminal device, that is, other protocol layers located above the PDCP layer in the protocol stack, referred to as upper layer for short.
  • the terminal device when performing cross-system handover, after receiving the handover command, releases the configuration and protocol stack of the source system (including the PDCP entity and SDAP layer), applies the configuration of the target system, and establishes and The peer-to-peer protocol stack of the target station.
  • the terminal device when a cross-system handover is performed, may not release the PDCP entity and/or SDAP layer equivalent to the source station after receiving the handover command.
  • the terminal device processes the PDCP entity and/or SDAP layer based on the configuration of the target system (for example, re-establishes the PDCP entity and uses the security configuration of the target system), and continues to use the PDCP entity and/or the target station after accessing the target station.
  • the SDAP layer receives and processes data packets.
  • the terminal device releases the SDAP layer after successfully receiving all data packets containing the SDAP header (for example, all data packets whose PDCP sequence numbers are less than the PDCP sequence number of the first and last identification packet) and the processing is completed and submitted to the upper layer.
  • the terminal device can send the data packet to the PDCP entity After PDCP processing in the middle, and then reorder, and finally submit to the upper layer in order.
  • the last mark packet described in the embodiment of the present application may also be called the end mark (end mark/end marker).
  • the above-mentioned first last identification packet may be the last data packet sent by the target network device to the terminal device in which the source network device has performed PDCP processing but has not received the confirmation response from the terminal device.
  • the last mentioned here is It means that the PDCP sequence number of the data packet is the last one; or, the first last identification packet may also be an empty data packet used to identify the end sent by the target network device to the terminal device.
  • the first final identification packet may contain a flag, for example, a certain field in the header is set to a special value to indicate that the data packet is the first final identification packet, and other data packets whose PDCP sequence number is before the data packet It is a data packet containing the SDAP header. If the data packet is received, it can be considered that the target network device has already sent the data packet containing the SDAP header.
  • the source network device has already performed PDCP processing but has not received a confirmation response from the terminal device for the data packet, because the source network device has assigned the corresponding PDCP serial number for this part of the data packet, the source network device It is also possible to send the PDCP sequence number corresponding to each data packet to the target network device together with the data packet when sending this part of the data packet to the target network device. Furthermore, the data packet and the PDCP serial number corresponding to the data packet are sent to the terminal device through the target network device, so that the terminal device can determine whether the data packet contains the SDAP header according to the PDCP serial number corresponding to the data packet.
  • the source network device can also send the first PDCP number that the target network device can assign to the target network device, so that the target network device is the data packet that the source network device does not perform PDCP processing, and the terminal received by the target network device from the core network
  • the data packet of the device is assigned the corresponding PDCP sequence number.
  • the PDCP sequence number allocated by the target network device can continue or inherit the PDCP sequence number allocated by the source network device side. Therefore, it can support the terminal device to carry out the sequential delivery and de-duplication of data packets during the cross-system handover process, as well as the PDCP status report Report, etc., so as to improve the business continuity of the terminal equipment.
  • the data packet for which the source network device has performed the PDCP processing but has not received the confirmation response from the terminal device may be a PDCP SDU, and the PDCP SDU includes the SDAP header added before the PDCP processing.
  • the target network device can use its own PDCP to continue processing the PDCP SDU to generate a PDCP PDU, which is then processed by RLC, MAC, and PHY, and then sent to the terminal device through the air interface.
  • the source network device can directly send this part of the data packet to the target network device, and the target network device performs PDCP processing on this part of the data packet to generate PDCP PDU, and then After being processed by RLC, MAC, and PHY, it is sent to the terminal device through the air interface. It should be noted that since the source network device does not allocate the corresponding PDCP serial number for this part of the data packet, the source network device will not send the PDCP serial number corresponding to this part of the data packet to the target network device.
  • the data packets that the source network device does not perform PDCP processing may be new data (that is, fresh data) received by the source network device from the core network, and these new data have not been processed by the SDAP layer of the source network device, so Does not include SDAP header.
  • the source network device can send at least one piece of data that the terminal device has not successfully received to the target network device through the downlink data forwarding tunnel corresponding to the DRB.
  • Packets for example, PDCP SDUs that have not yet received the confirmation response from the terminal device or fresh data (fresh data) received from the core network and mapped to the DRB.
  • the data forwarding tunnel between the source network device and the target network device can be DRB granular, that is, each DRB that needs to perform data forwarding can have a dedicated downlink data forwarding tunnel.
  • the source network device may receive from the core network a second last identification packet for instructing the core network to stop sending data to the terminal device through the source network device, and send the second last identification packet to the target network device.
  • the target network device can learn from the second final identification packet that the source network device forwarded to the target network device at least one identification packet that the terminal device did not successfully receive has been sent, and thereafter, the target network device can send to the terminal device Data packets received from the core network.
  • the second last identification packet may be the last data packet containing valid data of the terminal device sent by the core network to the source network device, or an empty data packet sent by the core network for identifying the end.
  • the second final identification packet may include a flag, for example, a certain field in the packet header is set to a special value to instruct the core network to stop sending data to the terminal device through the source network device.
  • the second last identification packet may also be of DRB granularity, that is, the core network may send a second last identification packet for one DRB.
  • the source network device may be a network device in a communication system that adopts the second communication standard.
  • the air interface protocol stack between the network device and the terminal device does not include SDAP Layer processing.
  • the target network device may be a network device in a communication system adopting the first communication standard.
  • the air interface protocol stack between the network device and the terminal device includes SDAP layer processing.
  • the source network device may be an access network device in a 4G communication system
  • the target network device may be an access network device in a 5G communication system.
  • the source network device can send at least one data packet that the terminal device has not successfully received to the target network device, and the terminal device has at least one data packet that the terminal device has not successfully received.
  • the data packet may include one or more of the following data packets: a data packet in which the source network device has performed PDCP processing but has not received a confirmation response from the terminal device, and a data packet in which the source network device has not performed PDCP processing.
  • the protocol stack of the source network device does not include the processing of the SDAP layer, the SDAP header is not included in the two types of data packets.
  • the target network device may receive from the source network device at least one data packet that the terminal device has not successfully received, and receive the data packet of the terminal device from the core network. After the terminal device accesses the target network device, the target network device may send at least one data packet that the terminal device has not successfully received and a third final identification packet to the terminal device, where the third final identification packet is used to indicate that the SDAP header is not included The data packet of has been sent, or at least one data packet received from the source network device that the terminal device has not successfully received has been sent.
  • the target network device may also receive a second last identification packet from the source network device.
  • the second last identification packet is used to instruct the core network to stop sending data packets to the terminal device through the source network device.
  • the target network device may Second, the last identification packet: it is determined that at least one data packet forwarded by the source network device to the target network device has been sent.
  • the target network device may send the data packet received from the core network to the terminal device after receiving the second final identification packet.
  • the protocol stack of the target network device includes the processing of the SDAP layer, the target network device sends the data packet to the terminal device.
  • the data packet received from the core network sent by the device includes the SDAP header.
  • the terminal device can identify the data packet that does not contain the SDAP header and/or the data packet that contains the SDAP header in the data packet received from the target network device according to the third final identification packet, and identify the data packet that contains the SDAP header and the data packet that does not contain the SDAP header.
  • the data packets containing the SDAP header are processed separately.
  • the terminal device can identify the data packet that does not contain the SDAP header and/or the data packet that contains the SDAP header in the data packet received from the target network device according to the PDCP sequence number of the third final identification packet. For example, when the third last identification packet is an empty data packet sent by the target network device to the terminal device to identify the end, the terminal device may consider that the PDCP sequence number received from the target network device is less than the PDCP of the third last identification packet The data packet of the serial number does not contain the SDAP header, and the data packet with the PDCP serial number received from the target network device greater than the PDCP serial number of the third and last identification packet contains the SDAP header.
  • the terminal device may consider that it is from the target network device
  • the received PDCP sequence number is less than the PDCP sequence number of the third final identification packet and the third final identification packet does not contain the SDAP header, and the PDCP sequence number received from the target network device is greater than the sequence number of the third final identification packet
  • the data packet contains the SDAP header.
  • Another way to implement the third final identification packet can also be that the target network device sends a terminal device to identify the first data packet containing the SDAP header.
  • the PDCP sequence number of the packet is N
  • the last one is The PDCP sequence number of the data packet that does not contain the SDAP header is N-1, that is, the data packet with the PDCP sequence number less than N does not contain the SDAP header, and the data packet with the PDCP sequence number greater than or equal to N needs to be processed to remove the SDAP header. .
  • the terminal device can pair with the PDCP entity
  • the data packet is processed by PDCP, and then submitted to the upper layer in order after repeated detection.
  • the terminal device can place the data packet in the PDCP entity After PDCP processing is performed, the data packet is sent to the SDAP entity to remove the SDAP header, and then submitted to the upper layer in order after repeated detection.
  • the SDAP entity can directly submit the data packet with the SDAP header removed to the upper layer, or it can send the data packet with the SDAP header removed to the PDCP entity, and the PDCP entity sorts the data packets according to the PDCP sequence number of the data packet Then, the data packets are delivered to the upper layer in order, or there may be a sorting module in the terminal device, the SDAP entity can send the data packets with the SDAP header removed to the sorting module, and the sorting module will use the PDCP according to the PDCP of the data packet. After the data packets are sorted by the sequence number, they are then delivered to the upper layer in order.
  • the sorting module can be part of the PDCP function, or part of the SDAP function, or a new protocol layer in the protocol stack. This application does not Not limited.
  • the third final identification packet may be the last packet sent by the target network device to the terminal device in which the source network device has undergone PDCP processing but has not received the confirmation response from the terminal device, the last mentioned here It means that the PDCP sequence number of the data packet is the last one; or, the third last identification packet may also be an empty data packet used to identify the end sent by the target network device to the terminal device.
  • the third final identification packet may contain a flag, for example, a certain field in the header of the packet is set to a special value to indicate that the data packet is the third final identification packet, and other data packets whose PDCP sequence number is before the data packet For the data packet that does not contain the SDAP header, if the data packet is received, it can be considered that the target network device has already sent the data packet that does not contain the SDAP header.
  • the third final identification packet may also be the second final identification packet, that is, the last identification packet received by the source network device from the core network and used to instruct the core network to stop sending data to the terminal device through the source network device, that is,
  • the third final identification package may be the same data package as the second final identification package.
  • the second final identification package reference may be made to the above description, which will not be repeated here.
  • the data packet in which the source network device has performed PDCP processing but has not received the confirmation response from the terminal device may be a PDCP SDU, and the PDCP SDU does not include an SDAP header.
  • the target network device can use its own PDCP to continue processing the PDCP SDU to generate a PDCP PDU, which is then processed by RLC, MAC, and PHY, and then sent to the terminal device through the air interface.
  • the source network device can send this part of the data packet directly to the target network device, and the target network device performs PDCP processing on this part of the data packet to generate PDCP PDU, and then pass the RLC, MAC , After PHY is processed, it is sent to the terminal equipment through the air interface. It should be noted that since the source network device does not allocate the corresponding PDCP serial number for this part of the data packet, the source network device will not send the PDCP serial number corresponding to this part of the data packet to the target network device.
  • the data packets that the source network device does not perform PDCP processing may be new data (that is, fresh data) received by the source network device from the core network, and the new data does not include the SDAP header.
  • the source network device can also combine the PDCP sequence number corresponding to each data packet that has undergone PDCP processing but has not received the confirmation response from the terminal device with the data packet. Send to the target network device. Furthermore, the data packet and the PDCP serial number corresponding to the data packet are sent to the terminal device through the target network device, so that the terminal device can determine whether the data packet contains the SDAP header according to the PDCP serial number corresponding to the data packet.
  • the source network device can also send the first PDCP number that the target network device can assign to the target network device, so that the target network device is the data packet that the source network device does not perform PDCP processing, and the terminal received by the target network device from the core network The data packet of the device is assigned the corresponding PDCP sequence number.
  • the PDCP serial number allocated by the target network device can continue or inherit the PDCP serial number allocated by the source network device side, so as to support the terminal device to carry out the sequential delivery and deduplication of data packets during the cross-system handover, and the PDCP status Reporting, etc., to improve the business continuity of terminal equipment.
  • the source network device can also send to the target network device at least one data packet that the terminal device has not successfully received through the downlink data forwarding tunnel corresponding to the DRB, for example, a PDCP SDU that has not received a confirmation response from the terminal device or a slave New data (fresh data) received by the core network and mapped to the DRB.
  • the data forwarding tunnel between the source network device and the target network device can be DRB granular, that is, each DRB that needs to perform data forwarding can have a dedicated downlink data forwarding tunnel.
  • FIG. 7 is a schematic flowchart of another handover method provided by an embodiment of this application.
  • the method specifically includes the following steps:
  • Step S701 The source network device sends a switching command to the terminal device, where the switching command is used to instruct the terminal device to switch from the source network device to the target network device.
  • the switching command includes a non-interruption indication.
  • the terminal device before the source network device sends a handover command to the terminal device, the terminal device can access the source network device and perform data transmission with the source network device.
  • the aforementioned handover command may be a handover command message or signaling, which is not limited.
  • Step S702 The source network device continues to send data packets to the terminal device, and the source network device sends at least one data packet of the terminal device to the target network device.
  • the at least one data packet of the terminal device is PDCP processed by the source network device. data pack.
  • the data packet that the source network device has performed PDCP processing may be a PDCP SDU.
  • the source network device may continue to send data packets to the terminal device through the first PDCP entity in the source network device, and the source network device may also send the terminal device processed by the first PDCP entity to the target network device. At least one data packet of the device. That is, the source network device can send data packets to the terminal device and the target network device through the same PDCP entity.
  • Step S703 The target network device receives at least one data packet of the terminal device from the source network device.
  • the target network device may also receive the data packet of the terminal device from the core network.
  • Step S704 The terminal device receives the handover command from the source network device.
  • Step S705 The terminal device continues to receive data packets from the source network device through the second PDCP entity, and accesses the target network device.
  • Step S706 After the terminal device accesses the target network device, the target network device sends at least one data packet of the terminal device received from the source network device to the terminal device.
  • Step S707 The terminal device receives at least one data packet from the target network device through the second PDCP entity.
  • the terminal device after the terminal device receives the non-interruption indication of the handover command, it can continue to receive data packets from the source network device through the second PDCP entity in the terminal device. After the terminal device accesses the target network device, the terminal device can also At least one data packet is received from the target network through the second PDCP entity. That is, in the process of cross-system handover, the terminal device can receive data packets from the source network device and the target network device through the same PDCP entity.
  • Step S708 The target network device sends first indication information to the source network device, where the first indication information is used to indicate that the terminal device has successfully accessed the target network device.
  • the target network device may also send second indication information to the terminal device, where the second indication information is used to instruct the terminal device to stop receiving data packets from the source network device.
  • Step S709 After receiving the first indication information used to indicate that the terminal device has successfully accessed the target network device, the source network device stops sending data packets to the terminal device.
  • the source network device may also send a final identification packet to the target network device, and the final identification packet is used to indicate that at least one data packet of the terminal device forwarded to the target network device has been sent.
  • the last identification packet may be a data packet received by the source network device from the core network and used to instruct the core network to stop sending data to the terminal device through the source network device.
  • the target network device can send the data packet received from the core network to the terminal device.
  • the target network device may also send the last identification packet to the terminal device, which is used to indicate that the data packet of the terminal device received from the source network device has been sent.
  • the final identification package refer to the second final identification package in Embodiment 1, which will not be repeated here.
  • the terminal device will not immediately disconnect the connection with the source network device after receiving the handover command sent by the source network device.
  • the terminal device can continue to receive data packets from the source network device and initiate a random access procedure to access the target network device.
  • the terminal device can disconnect the connection with the source network device after successfully accessing the target network device.
  • the source network device may stop sending data packets to the terminal device after determining that the terminal device has successfully accessed the target network device. In this way, the connection between the terminal device and the network device is not interrupted during the cross-system handover process, thereby improving the business continuity of the terminal device and improving the user experience.
  • the source network device may be a network device in a communication system adopting the first communication standard.
  • the air interface protocol stacks of the network device and the terminal device both include the SDAP layer Processing.
  • the target network device may be a network device in a communication system adopting the second communication standard.
  • the air interface protocol stack of the network device and the terminal device does not include SDAP layer processing.
  • the source network device may be an access network device in a 5G communication system
  • the target network device may be an access network device in a 4G communication system.
  • the source The network device can continue to send data packets to the terminal device, where the data packet sent by the source network device to the terminal device includes the SDAP header added before the PDCP processing; on the other hand, the source network device can send at least one data packet of the terminal device Remove the SDAP header in the data packet, and then send the data packet with the SDAP header removed to the target network device.
  • At least one data packet of the terminal device is a data packet that has been PDCP processed by the source network device.
  • the at least A data packet can be a PDCP SDU.
  • the target network device may receive at least one data packet of the terminal device from the source network device, and after the terminal device accesses the target network device, send the at least one data packet of the terminal device received from the source network device to the terminal device.
  • the target network device may also receive the data packet of the terminal device from the core network, and send the data packet received from the core network to the terminal device. It can be understood that since the protocol stack of the target network device does not include the processing of the SDAP layer, and the data packet received by the target network device from the source network device has removed the SDAP header added before the PDCP processing, therefore, in this scenario Below, the data packet sent by the target network device to the terminal device does not include the SDAP header.
  • the terminal device may receive data packets from the source network device and the target network device, and use the same PDCP entity (ie, the second PDCP entity) to process the data packets received from the source network device and the data packets received from the target network device.
  • the second PDCP entity after the second PDCP entity performs PDCP processing on the data packet, it can also perform unified sorting and de-duplication processing on the data packets received from the source network device and the data packets received from the target network device (ie, repeatability detection). ), so as to achieve no duplication and orderly delivery of data in the process of cross-system switching.
  • the second PDCP entity in the terminal device may separately process the data packet received from the source network device and the data packet received from the target network device according to the difference of the air interface through which the data is received.
  • the terminal device can send the data packet to the second PDCP entity for PDCP processing, and the second PDCP entity can send the PDCP processed data packet to the SDAP entity in the terminal device to remove the SDAP header .
  • the SDAP entity may send the data packet with the SDAP header removed back to the second PDCP entity for deduplication processing, and finally the second PDCP entity may deliver the deduplication processing data packets to the upper layer in order.
  • the terminal device can send the data packet to the second PDCP entity for PDCP processing. Since there is no need to remove the SDAP header, the second PDCP entity can reproduce the PDCP processed data packet. Sort and de-duplicate, and then deliver the de-duplicated data packets to the upper layer in order.
  • the second PDCP entity is a dual active protocol stack (DAPS) structure
  • the second PDCP entity includes two processing units, and each processing unit is connected to the source network device and the target network device respectively.
  • DAPS dual active protocol stack
  • the first processing unit corresponds to the security configuration of the source network device
  • the second processing unit corresponds to the security configuration of the target network device
  • the second PDCP entity may perform PDCP processing on the data packet received from the source network device through the first processing unit, and perform PDCP processing on the data packet received from the target network device through the second processing unit.
  • both the first processing unit and the second processing unit mentioned in the embodiments of the present application may include one or more modules, such as modules with functions such as decryption, integrity verification, sorting, header compression and the like.
  • the functions of the first processing unit and the second processing unit may be the same or different, that is, the source network device and the target network device may be implemented by using the same or different PDCP, which is not limited in this application.
  • the SDAP header in this part of the data packet may not be removed. Instead, the terminal device itself recognizes the data packet containing the SDAP header and the data packet not containing the SDAP header received from the target network device, and then processes the received data packet containing the SDAP header and the data packet not containing the SDAP header separately.
  • the source network device may continue to send data packets to the terminal device; on the other hand, the source network device may send at least one data packet of the terminal device to the target network device, and the at least one data packet may be the source network Data packets that the device has processed PDCP, such as PDCP PDU.
  • PDCP PDU source network Data packets that the device has processed PDCP
  • the data packets sent by the source network device to the terminal device and the data packets sent by the source network device to the target network device both include the SDAP header added before the PDCP processing.
  • the target network device may receive at least one data packet of the terminal device from the source network device, and after the terminal device is connected to the target network device, send at least one data packet of the terminal device received from the source network device to the terminal device.
  • An SDAP header is included in a data packet.
  • the target network device may also receive the data packet of the terminal device from the core network, and send the data packet received from the core network to the terminal device.
  • the protocol stack of the target network device does not include the processing of the SDAP layer, and the source network device does not remove the SDAP header added before the PDCP processing when sending the PDCP-processed data packet to the target network device, therefore,
  • the data packet received from the core network sent by the target network device to the terminal device does not contain the SDAP header, but the data packet received from the source network device sent by the target network device to the terminal device contains the SDAP header.
  • the target network device can send the final identification packet to the terminal device.
  • the final identification packet is used to indicate from the source The data packet received by the network device has been sent, or it can also be understood that the data packet containing the SDAP header has been sent.
  • the target network device may send the last identification packet after sending the at least one data packet received from the source network device to the terminal device and before sending the data packet received from the core network to the terminal device.
  • the last identification packet may also be a data packet received by the target network device from the source network device and used to indicate that at least one data packet of the terminal device forwarded to the target network device has been sent. That is, after receiving the last identification packet from the source network device, the target network device may forward the last identification packet to the terminal device. After that, the target network device may send the data packet received from the core network to the terminal device.
  • the terminal device can receive data packets from the source network device and the target network device, and use the same PDCP entity to process the data packets received from the source network device and the data packets received from the target network device.
  • the terminal device can also receive the final identification packet from the target network device.
  • the second PDCP entity in the terminal device may separately process the data packet received from the source network device and the data packet received from the target network device according to the difference in the air interface through which the data is received.
  • the terminal device can send the data packet to the second PDCP entity for PDCP processing, and the second PDCP entity can send the PDCP processed data packet to the SDAP entity in the terminal device to remove the SDAP header .
  • the SDAP entity may send the data packet with the SDAP header removed back to the second PDCP entity for deduplication processing, and finally the second PDCP entity may deliver the deduplication processing data packets to the upper layer in order.
  • the terminal device can identify the data packet received from the target network device that contains the SDAP header and/or the data packet that does not contain the SDAP header according to the last identification packet received from the target network device , And deal with data packets that contain SDAP headers and data packets that do not contain SDAP headers separately. That is, after the data packet containing the SDAP header undergoes PDCP processing, the SDAP entity needs to remove the SDAP header before it can be delivered to the upper layer, and the data packet that does not contain the SDAP header undergoes PDCP processing without removing the SDAP header.
  • the terminal device may consider the data packet with the PDCP sequence number received from the target network device less than the PDCP sequence number of the last identification packet as a data packet containing the SDAP header, and the PDCP sequence number received from the target network device is greater than the PDCP sequence number of the last identification packet
  • the data packet of the serial number is a data packet that does not contain the SDAP header.
  • the terminal device can send a data packet with a PDCP sequence number less than the PDCP sequence number of the last identification packet received from the target network device to the second PDCP entity for PDCP processing, and then send it to the SDAP header to remove the SDAP header, and finally After returning to the second PDCP entity for reordering and de-duplication processing, it is delivered to the upper layer in order.
  • the terminal device can send a data packet with a PDCP sequence number greater than the PDCP sequence number of the last identified packet received from the target network device to the second PDCP entity for PDCP processing, and then directly enter the process of reordering and deduplication processing. Then it is delivered to the upper layer in order without sending to the SDAP entity to remove the SDAP header.
  • the second PDCP entity may also have a DAPS structure.
  • DAPS structure For the specific implementation manner of the second PDCP entity, refer to the introduction in the first implementation manner in this scenario, which is not repeated here.
  • the source network device may also send the PDCP sequence number corresponding to each data packet of the PDCP processed data packet together with the data packet to the target network device.
  • the source network device can also send the first PDCP sequence number assigned by the target network device to the target network device, so that the target network device can allocate the PDCP sequence number for the data packet received from the core network, thereby realizing the cross-system handover process Inheritance of the PDCP sequence numbers on the source side and the target side.
  • the source network device can send at least one data packet of the terminal device to the target network device through the downlink data forwarding tunnel corresponding to the DRB, for example, the PDCP SDU that has been processed by PDCP or the fresh received from the core network and mapped to the DRB. data.
  • the data forwarding tunnel between the source network device and the target network device can be DRB granular, that is, each DRB that needs to perform data forwarding can have a dedicated downlink data forwarding tunnel.
  • the source network device may be a network device in a communication system that adopts the second communication standard.
  • the air interface protocol stack between the network device and the terminal device is different. Including SDAP layer processing.
  • the target network device may be a network device in a communication system adopting the first communication standard.
  • the air interface protocol stack between the network device and the terminal device includes SDAP layer processing.
  • the source network device may be an access network device in a 4G communication system
  • the target network device may be an access network device in a 5G communication system.
  • the source network device can continue to send data packets to the terminal device; on the other hand, the source network device can send at least one data packet of the terminal device to the target network device, and the at least one data packet can be It is a data packet that the source network device has processed PDCP, such as PDCP SDU.
  • PDCP such as PDCP SDU.
  • the protocol stack of the source network device does not include the processing of the SDAP layer, the data packets sent by the source network device to the terminal device and the data packets sent by the source network device to the target network device do not include the SDAP header.
  • the target network device can receive at least one data packet of the terminal device from the source network device, and the at least one data packet is processed by the SDAP entity first, and the SDAP is added After the header, it is sent to the PDCP entity for PDCP processing. Then, after processing by RLC, MAC, and PHY, the target network device can send the data packet with the SDAP header added to the terminal device through the air interface.
  • the target network device can also receive the data packet of the terminal device from the core network, and send the data packet to the terminal device after processing by the SDAP entity, PDCP entity, and RLC, MAC, PHY, etc. It can be seen that in this implementation manner, the data packets sent by the target network device to the terminal device all include the SDAP header.
  • the terminal device may receive data packets from the source network device and the target network device, and use the same PDCP entity (ie, the second PDCP entity) to process the data packets received from the source network device and the data packets received from the target network device.
  • the second PDCP entity performs PDCP processing on the data packet
  • the data packet received from the source network device and the data packet received from the target network device may also be uniformly sorted and deduplicated.
  • the terminal device may separately process the data packet received from the source network device and the data packet received from the target network device according to the difference of the receiving air interface.
  • the terminal device may send the data packet to the second PDCP entity for PDCP processing, and then submit it to the upper layer.
  • the data packets after PDCP processing can be reordered and deduplicated, and then delivered to the upper layer in order.
  • the terminal device may send the data packet to the second PDCP entity for PDCP processing, and then send it to the SDAP entity to remove the SDAP header, and then submit it to the upper layer.
  • the data packets with the SDAP header removed can be reordered and deduplicated, and then delivered to the upper layer in order.
  • the terminal device after the terminal device is connected to the target network device, it can correctly receive and decode the data packet received from the source network device and the data packet received from the target network device.
  • the target network device may receive at least one data packet of the terminal device from the source network device, and perform PDCP processing on the at least one data packet, and after processing the RLC, MAC, PHY, etc., through The air interface is sent to the terminal device.
  • the target network device can also receive the data packet of the terminal device from the core network, and send the data packet to the terminal device after processing by the SDAP entity, PDCP entity, and RLC, MAC, and PHY.
  • the target network device since the target network device does not add the SDAP header to the data packet received from the source network device before sending it to the terminal device, the data packet received from the source network device sent by the target network device to the terminal device here does not contain SDAP
  • the data packet received from the core network sent by the target network device to the terminal device contains the SDAP header.
  • the target network device may also send a final identification packet to the terminal device.
  • the final identification packet is used to indicate from the source
  • the data packet received by the network device has been sent, or it can also be understood that the data packet without the SDAP header has been sent.
  • the target network device may send the last identification packet after sending the at least one data packet received from the source network device to the terminal device and before sending the data packet received from the core network to the terminal device.
  • the last identification packet may also be a data packet received by the target network device from the source network device and used to indicate that at least one data packet of the terminal device forwarded to the target network device has been sent. That is, after receiving the last identification packet from the source network device, the target network device may forward the last identification packet to the terminal device. After that, the target network device may send the data packet received from the core network to the terminal device.
  • the terminal device may receive data packets from the source network device and the target network device, and use the same PDCP entity to process the data packets received from the source network device and the data packets received from the target network device.
  • the terminal device can also receive the final identification packet from the target network device.
  • the second PDCP entity in the terminal device may separately process the data packet received from the source network device and the data packet received from the target network device according to the difference in the air interface through which the data is received.
  • the terminal device can send the data packet to the second PDCP entity for PDCP processing. Since there is no need to remove the SDAP header, after PDCP processing, the second PDCP entity can continue to perform the PDCP processing on the data packet. Reordering and deduplication processing, and then the deduplication processing data packets are delivered to the upper layer in order.
  • the terminal device can identify the data packet received from the target network device that contains the SDAP header and/or the data packet that does not contain the SDAP header according to the last identification packet received from the target network device , And deal with data packets that contain SDAP headers and data packets that do not contain SDAP headers separately. That is, after the data packet containing the SDAP header undergoes PDCP processing, the SDAP header needs to be removed from the SDAP entity before it can be delivered to the upper layer, and the data packet that does not contain the SDAP header undergoes PDCP processing without removing the SDAP header.
  • the terminal device may consider a data packet with a PDCP sequence number less than the PDCP sequence number of the last identification packet received from the target network device as a data packet that does not contain the SDAP header, and the PDCP sequence number received from the target network device is greater than the PDCP sequence number of the last identification packet.
  • the data packet of the PDCP sequence number is a data packet containing an SDAP header.
  • the terminal device can send a data packet with a PDCP sequence number less than the PDCP sequence number of the last identified packet received from the target network device to the second PDCP entity for PDCP processing, and then enter the process of reordering and deduplication processing, and then It is delivered to the upper layer in order without sending to the SDAP entity to remove the SDAP header.
  • the terminal device can send a data packet with a PDCP sequence number greater than the PDCP sequence number of the last identification packet received from the target network device to the second PDCP entity for PDCP processing, and then send it to the SDAP header to remove the SDAP header, Finally, it returns to the second PDCP entity for reordering and de-duplication, and then submits it to the upper layer in order.
  • the second PDCP entity in the terminal device may also be a DAPS structure, that is, the second PDCP entity includes a first processing unit and a second processing unit, where: The first processing unit corresponds to the security configuration of the source network device, the second processing network element corresponds to the security configuration of the target network device, and the second PDCP entity performs PDCP processing on the data packet received from the source network device through the first processing unit , PDCP processing is performed on the data packet received from the target network device through the second processing unit.
  • the first processing unit corresponds to the security configuration of the source network device
  • the second processing network element corresponds to the security configuration of the target network device
  • the second PDCP entity performs PDCP processing on the data packet received from the source network device through the first processing unit
  • PDCP processing is performed on the data packet received from the target network device through the second processing unit.
  • the source network device may also send the PDCP sequence number corresponding to each data packet of the PDCP processed data packet together with the data packet to the target network device.
  • the source network device can also send the first PDCP sequence number assigned by the target network device to the target network device, so that the target network device can allocate the PDCP sequence number for the data packet received from the core network, thereby realizing the cross-system handover process Inheritance of the PDCP sequence numbers on the source side and the target side.
  • the source network device can send at least one data packet of the terminal device to the target network device through the downlink data forwarding tunnel corresponding to the DRB, for example, a PDCP SDU that has undergone PDCP processing or is newly received from the core network and mapped to the DRB The fresh data.
  • the data forwarding tunnel between the source network device and the target network device can be DRB granular, that is, each DRB that needs to perform data forwarding can have a dedicated downlink data forwarding tunnel.
  • FIG. 10 is a schematic structural diagram of a communication device provided in an embodiment of the application.
  • the communication device 1000 includes a transceiver module 1010 and a processing module 1020.
  • the communication device can be used to implement the functions related to the source network device or the target network device in any of the foregoing method embodiments.
  • the communication device may be a network device or a chip included in the network device.
  • the transceiver module 1010 When the communication device is used as the source network device and the method embodiment shown in FIG. 2 is executed, the transceiver module 1010 is used to send a switching command to the terminal device, and the switching command is used to instruct the terminal device to switch from the communication device to the target network.
  • the communication device and the target network device adopt different wireless access technologies; the transceiver module 1010 is also used to send at least one data packet that the terminal device has not successfully received to the target network device, and at least one data packet that the terminal device has not successfully received
  • the packet includes one or more of the following data packets: data packets that have undergone PDCP processing but have not received an acknowledgement response from the terminal device, and data packets that have not undergone PDCP processing.
  • the processing module 1020 when at least one data packet that the terminal device has not successfully received includes a data packet that has undergone PDCP processing but has not received a confirmation response from the terminal device, the processing module 1020 is used for the service in the data packet The data adaptation protocol SDAP header is removed, and then the data packet with the SDAP header removed is sent to the target network device through the transceiver module 1010.
  • the processing module 1020 is configured to map the data packet to the corresponding DRB, and then transmit the data packet to the corresponding DRB through the transceiver module 1010.
  • the data packet mapped to the corresponding DRB is sent to the target network device, and the data packet does not contain the SDAP header.
  • the transceiver module 1010 is configured to send the data packet to the target Network equipment, the data packet includes the SDAP header.
  • the transceiver module 1010 is also used to send the PDCP serial number corresponding to the data packet that has undergone PDCP processing but has not received the confirmation response from the terminal device to the target network device; and/or, the transceiver module 1010 It is also used to send the first PDCP sequence number that can be allocated by the target network device to the target network device.
  • the transceiver module 1010 is configured to receive from the source network device at least one data packet that the terminal device did not successfully receive, and the terminal device did not successfully receive the data packet.
  • At least one data packet includes one or more of the following data packets: a data packet in which the source network device has performed PDCP processing but has not received a confirmation response from the terminal device, and a data packet in which the source network device has not performed PDCP processing
  • Data packet, the source network device and the communication device use different wireless access technologies, the switching command is used to instruct the terminal device to switch from the source network device to the communication device; the processing module 1020 is used to access the communication device in the terminal device Then, at least one data packet that the terminal device has not successfully received is sent to the terminal device through the transceiver module 1010.
  • the data packet received by the communication device from the source network device for which the source network device has undergone PDCP processing but has not received the confirmation response from the terminal device does not contain the service data adaptation SDAP header.
  • the data packet received by the communication device from the source network device in which the source network device has undergone PDCP processing but has not received the confirmation response from the terminal device contains the SDAP header; the transceiver module 1010 is also used to send The terminal device sends a final identification packet, which is used to indicate that the data packet containing the SDAP header is sent.
  • the transceiver module 1010 is also used to receive from the source network device the PDCP sequence number corresponding to the data packet for which the source network device has performed PDCP processing but has not received the confirmation response from the terminal device; and/or, The transceiver module 1010 receives the first PDCP serial number that can be allocated by the communication device from the source network device.
  • the processing module 1020 involved in the communication device may be implemented by a processor or processor-related circuit components, and the transceiver module 1010 may be implemented by a transceiver or transceiver-related circuit components.
  • the operation and/or function of each module in the communication device is to implement the corresponding process of the method shown in FIG. 2 or FIG.
  • FIG. 11 is a schematic diagram of another structure of a communication device provided in an embodiment of the present application.
  • the communication device 1100 may specifically be a type of network device, such as a base station, and is used to implement a function related to a source network device or a target network device in any of the foregoing method embodiments.
  • the network equipment includes: one or more radio frequency units, such as remote radio unit (RRU) 1101 and one or more baseband units (BBU) (also called digital unit, digital unit, DU) ) 1102.
  • the RRU 1101 may be called a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., and it may include at least one antenna 11011 and a radio frequency unit 11012.
  • the RRU 1101 part is mainly used for receiving and sending radio frequency signals and converting radio frequency signals and baseband signals.
  • the 1102 part of the BBU is mainly used for baseband processing, control of the base station, and so on.
  • the RRU 1101 and the BBU 1102 may be physically set together, or may be physically separated, that is, a distributed base station.
  • the BBU 11202 is the control center of the base station, and may also be called a processing unit, which is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, and spreading.
  • the BBU (processing unit) 1102 may be used to control the base station to execute the operation procedure of the source network device or the target network device in the foregoing method embodiment.
  • the BBU 1102 may be composed of one or more single boards, and multiple single boards may jointly support a radio access network with a single access indication (such as an LTE network), and may also support different access standards. Wireless access network (such as LTE network, 5G network or other networks).
  • the BBU 1102 may also include a memory 11021 and a processor 11022, where the memory 11021 is used to store necessary instructions and data.
  • the processor 11022 is used to control the base station to perform necessary actions, for example, to control the base station to perform the sending operation in the foregoing method embodiment.
  • the memory 11021 and the processor 11022 may serve one or more boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.
  • FIG. 12 is a schematic structural diagram of another communication device provided in an embodiment of the present application.
  • the communication device 1200 includes a transceiver module 1210 and a processing module 1220.
  • the communication device can be used to implement the functions related to terminal equipment in any of the foregoing method embodiments.
  • the communication device may be a terminal device, such as a handheld terminal device or a vehicle-mounted terminal device; the communication device may also be a chip included in the terminal device, or a device including the terminal device, such as various types of vehicles.
  • the transceiver module 1210 is used to receive a switching command from the source network device, and the switching command is used to instruct the communication device to switch from the source network device to the target Network equipment, the source network equipment and the target network equipment adopt different wireless access technologies; the processing module 1220 is used to access the target network equipment, and the final identification packet is received from the target network equipment through the transceiver module 1210; the processing module 1220 also uses According to the last identification packet, identify the data packet that contains the service data adaptation protocol SDAP header and/or the data packet that does not contain the SDAP header in the data packet received from the target network device.
  • the processing module 1220 is specifically configured to identify data packets that contain SDAP headers and/or data packets that do not contain SDAP headers in the data packets received from the target network device according to the PDCP sequence number corresponding to the last identified packet. Data packet with SDAP header.
  • the processing module 1220 when the processing module 1220 recognizes that the data packet received from the target network device contains the SDAP header, the processing module is also used to perform PDCP processing on the data packet through the PDCP entity, and then the data packet Sent to the SDAP entity, and the SDAP entity removes the SDAP header in the data packet.
  • the processing module 1220 recognizes that the data packet received from the target network device does not contain the SDAP header, the processing module is also used to perform PDCP processing on the data packet through the PDCP entity, but after performing PDCP processing on the data packet, it does not Then send the data packet to the SDAP entity to remove the SDAP header.
  • the processing module 1220 is further configured to send the data packet with the SDAP header removed to the upper layer through the SDAP entity; or, the processing module 1220 is also configured to receive the removed SDAP header from the SDAP entity through the PDCP entity. After the subsequent data packets, the data packets are sorted according to the PDCP sequence numbers of the data packets, and then the data packets are sent to the upper layer in sequence.
  • processing module 1220 involved in the communication device may be implemented by a processor or processor-related circuit components
  • transceiver module 1210 may be implemented by a transceiver or transceiver-related circuit components.
  • the operation and/or function of each module in the communication device is to implement the corresponding process of the method shown in FIG. 2 or FIG.
  • FIG. 13 is a schematic diagram of another structure of a communication device provided in an embodiment of the application.
  • the communication device may specifically be a terminal device. It is easy to understand and easy to illustrate.
  • the terminal device uses a mobile phone as an example.
  • the terminal device includes a processor, and may also include a memory, and of course, it may also include a radio frequency circuit, an antenna, an input and output device, and so on.
  • the processor is mainly used to process the communication protocol and communication data, and to control the terminal device, execute the software program, and process the data of the software program.
  • the memory is mainly used to store software programs and data.
  • the radio frequency circuit is mainly used for the conversion of baseband signals and radio frequency signals and the processing of radio frequency signals.
  • the antenna is mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal devices may not have input and output devices.
  • the processor When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal to the outside in the form of electromagnetic waves through the antenna.
  • the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.
  • FIG. 13 only one memory and processor are shown in FIG. 13. In an actual terminal device product, there may be one or more processors and one or more memories.
  • the memory may also be referred to as a storage medium or storage device.
  • the memory may be set independently of the processor, or may be integrated with the processor, which is not limited in the embodiment of the present application.
  • the antenna and radio frequency circuit with the transceiving function can be regarded as the transceiving unit of the terminal device
  • the processor with the processing function can be regarded as the processing unit of the terminal device.
  • the terminal device includes a transceiving unit 1310 and a processing unit 1320.
  • the transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, and so on.
  • the processing unit may also be called a processor, a processing board, a processing module, a processing device, and so on.
  • the device for implementing the receiving function in the transceiver unit 1310 can be regarded as the receiving unit, and the device for implementing the sending function in the transceiver unit 1310 as the sending unit, that is, the transceiver unit 1310 includes a receiving unit and a sending unit.
  • the transceiver unit may sometimes be referred to as a transceiver, a transceiver, or a transceiver circuit.
  • the receiving unit may sometimes be called a receiver, a receiver, or a receiving circuit.
  • the transmitting unit may sometimes be called a transmitter, a transmitter, or a transmitting circuit.
  • transceiving unit 1310 is used to perform the sending and receiving operations on the terminal device side in the foregoing method embodiment
  • processing unit 1320 is used to perform other operations on the terminal device in the foregoing method embodiment except for the transceiving operation.
  • An embodiment of the present application also provides a chip system, including: a processor, the processor is coupled with a memory, the memory is used to store a program or instruction, when the program or instruction is executed by the processor, the The chip system implements the method in any of the foregoing method embodiments.
  • processors in the chip system there may be one or more processors in the chip system.
  • the processor can be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be set on different chips.
  • the setting method of the processor is not specifically limited.
  • the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC). It can also be a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (microcontroller).
  • the controller unit, MCU may also be a programmable controller (programmable logic device, PLD) or other integrated chips.
  • each step in the foregoing method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the embodiment of the present application also provides a computer-readable storage medium, which stores computer-readable instructions, and when the computer reads and executes the computer-readable instructions, the computer is caused to execute any of the above-mentioned method embodiments In the method.
  • the embodiments of the present application also provide a computer program product.
  • the computer reads and executes the computer program product, the computer is caused to execute the method in any of the foregoing method embodiments.
  • An embodiment of the present application also provides a communication system, which includes a source network device, a target network device, and at least one terminal device described in each of the foregoing method embodiments.
  • the communication system may also include core network equipment.
  • processors mentioned in the embodiments of this application may be a central processing unit (central processing unit, CPU), or other general-purpose processors, digital signal processors (digital signal processors, DSP), and application-specific integrated circuits ( application specific integrated circuit (ASIC), ready-made programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • CPU central processing unit
  • DSP digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种切换方法及通信装置,其中方法包括:源网络设备向终端设备发送切换命令后,将终端设备未成功接收的至少一个数据包发送给目标网络设备,以便于终端设备接入目标网络设备后,目标网络设备将从源网络设备接收的该至少一个数据包发送给终端设备。由于源网络设备向目标网络设备转发的数据包中包括源网络设备已进行PDCP处理但未接收到终端设备的确认响应的数据包,因此,可有效避免跨系统切换过程中终端设备的数据丢失。

Description

一种切换方法及通信装置
相关申请的交叉引用
本申请要求在2020年02月27日提交中国国家知识产权局、申请号为202010125620.3、申请名称为“一种切换方法及通信装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域,尤其涉及一种切换方法及通信装置。
背景技术
当终端设备在不同的通信系统的覆盖区域间移动时,会发生跨系统的切换。在进行跨系统切换时,终端设备会先断开与源网络设备之间的数据传输,在接入目标网络设备后,再与目标网络设备进行数据传输。如果源网络设备与目标网络设备所处的通信系统对数据的处理不一致,在跨系统切换的过程中,可能存在终端设备的数据丢失的问题,影响用户的业务体验。
发明内容
本申请实施例提供一种切换方法及通信装置,用以避免终端设备的跨系统切换过程中的数据丢失。
第一方面,本申请实施例提供一种切换方法,该方法可由源网络设备执行,该方法包括:源网络设备向终端设备发送切换命令,该切换命令用于指示终端设备由源网络设备切换到目标网络设备,源网络设备与目标网络设备采用不同的无线接入技术;源网络设备将终端设备未成功接收的至少一个数据包发送给目标网络设备,该终端设备未成功接收的至少一个数据包包括下列数据包中的一种或多种:已进行分组数据汇聚协议PDCP处理但未接收到来自终端设备的确认响应的数据包,以及未进行PDCP处理的数据包。
采用上述技术方案,源网络设备向终端设备发送切换命令后,还可将终端设备未成功接收的至少一个数据包发送给目标网络设备,以便于终端设备接入目标网络设备后,目标网络设备可将从源网络设备接收的该至少一个数据包发送给终端设备。由于源网络设备向目标网络设备转发的数据包中包括源网络设备已进行PDCP处理但未接收到终端设备的确认响应的数据包,因此,可有效避免跨系统切换过程中终端设备的数据丢失。
在第一方面的一种可能的设计中,源网络设备与目标网络设备采用不同的无线接入技术可以体现为,终端设备与源网络设备对应的协议栈中包括SDAP层的处理,而终端设备与目标网络设备对应的协议栈中不包括SDAP层的处理。
在第一方面的一种可能的设计中,当该终端设备未成功接收的至少一个数据包包括已进行PDCP处理但未接收到来自终端设备的确认响应的数据包,源网络设备可将该数据包中的服务数据适配协议SDAP头移除,然后将移除SDAP头后的该数据包发送给目标网络设备。
在第一方面的一种可能的设计中,当该终端设备未成功接收的至少一个数据包包括未进行PDCP处理的数据包,源网络设备可将该数据包映射到对应的DRB,然后再将映射到对应的DRB的数据包发送给目标网络设备,该数据包不包含SDAP头。
采用上述技术方案,源网络设备通过对已进行PDCP处理但未接收到终端设备的确认响应的数据包移除SDAP头,对未进行PDCP处理的数据包映射到DRB后进行直接发送,可使源网络设备向目标网络设备发送的数据包中均不包括SDAP头,这样目标网络设备向终端设备转发的数据包中也不包括SDAP头。如此,可使终端设备接入目标网络设备后,能够对从目标网络设备接收的数据包进行正确的接收和解码。
在第一方面的一种可能的设计中,当该终端设备未成功接收的至少一个数据包包括已进行PDCP处理但未接收到来自终端设备的确认响应的数据包,源网络设备可将该数据包发送给目标网络设备,该数据包中包括SDAP头。
采用上述技术方案,源网络设备将已进行PDCP处理但未接收到终端设备的确认响应的数据包发送给目标网络设备前,源网络设备也可以不移除数据包中的SDAP头,而是由终端设备对从目标网络设备接收的包含SDAP头的数据包以及不包含SDAP头的数据包进行分别处理,如此,也可使终端设备能够对从目标网络设备接收的数据包进行正确的接收和解码。
在第一方面的一种可能的设计中,该方法还包括:源网络设备可将已进行PDCP处理但未接收到来自终端设备的确认响应的数据包对应的PDCP序列号发送给目标网络设备;和/或,源网络设备还可将目标网络设备可分配的第一个PDCP序列号发送给目标网络设备。
采用上述技术方案,可使得目标网络设备在为从源网络设备接收的未进行PDCP处理的数据包,以及从核心网接收的数据包分配PDCP序列号时,能够继承或延续源网络设备侧的PDCP序列号,从而支持终端设备在跨系统切换过程中根据数据包的PDCP序列号进行按序递交和去重处理。
第二方面,本申请实施例提供一种切换方法,该方法可由目标网络设备执行,该方法包括:目标网络设备从源网络设备接收终端设备未成功接收的至少一个数据包,该终端设备未成功接收的至少一个数据包包括下列数据包中的一种或多种:源网络设备已进行分组数据汇聚协议PDCP处理但未接收到来自终端设备的确认响应的数据包,以及源网络设备未进行PDCP处理的数据包,源网络设备与目标网络设备采用不同的无线接入技术;目标网络设备在终端设备接入目标网络设备后,将所述终端设备未成功接收的至少一个数据包发送给终端设备。
采用上述技术方案,目标网络设备可从源网络设备接收终端设备未成功接收的至少一个数据包,并在终端设备接入目标网络设备后,将该至少一个数据包发送给终端设备。由于该至少一个数据包中包括源网络设备已进行PDCP处理但未接收到终端设备的确认响应的数据包,因此,可有效避免跨系统切换过程中终端设备的数据丢失。
在第二方面的一种可能的设计中,源网络设备与目标网络设备采用不同的无线接入技术可以体现为,终端设备与源网络设备对应的协议栈中包括SDAP层的处理,而终端设备与目标网络设备对应的协议栈中不包括SDAP层的处理。
在第二方面的一种可能的设计中,目标网络设备从源网络设备接收的源网络设备已进行PDCP处理的数据包但未接收到来自终端设备的确认响应的数据包中不包含服务数据适配SDAP头。可选的,可以是源网络设备在向目标网络设备发送这部分数据包之前移除了 其中的SDAP头。
采用上述技术方案,由于目标网络设备向终端设备发送的源网络设备已进行PDCP处理的数据包中不包含SDAP头,因此,可使终端设备接入目标网络设备后,能够对从目标网络设备接收的数据包进行正确的接收和解码。
在第二方面的一种可能的设计中,目标网络设备从源网络设备接收的源网络设备已进行PDCP处理但未接收到来自终端设备的确认响应的数据包中包含SDAP头;该方法还包括:目标网络设备向终端设备发送最后标识包,该最后标识包用于指示包含SDAP头的数据包发送完毕。
采用上述技术方案,源网络设备也可以将已进行PDCP处理但未接收到终端设备的确认响应的数据包直接发送给目标网络设备,而不做移除SDAP头的处理。如此,目标网络设备向终端设备发送的数据包中可包括包含SDAP头的数据包和/或不包含SDAP头的数据包。通过向终端设备发送最后标识包,可使终端设备可根据该最后标识包识别从目标网络设备接收的包含SDAP头的数据包,以及不包含SDAP头的数据包,从而对包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理,使得数据包能够被正确接收和解码。
在第二方面的一种可能的设计中,该方法还包括:目标网络设备可从源网络设备接收源网络设备已进行PDCP处理但未接收到来自终端设备的确认响应的数据包对应的PDCP序列号;和/或,目标网络设备可从源网络设备接收目标网络设备可分配的第一个PDCP序列号。
采用上述技术方案,目标网络设备可继承或延续源网络设备的PDCP序列号,继续为从源网络设备接收的未进行PDCP处理的数据包,以及从核心网接收的数据包分配PDCP序列号,从而支持终端设备在跨系统切换过程中根据数据包的PDCP序列号进行按序递交和去重处理。
第三方面,本申请实施例提供一种切换方法,该方法可由终端设备执行,该方法包括:终端设备从源网络设备接收切换命令,该切换命令用于指示终端设备由源网络设备切换到目标网络设备,该源网络设备与目标网络设备采用不同的无线接入技术;终端设备接入目标网络设备,从目标网络设备接收最后标识包;终端设备根据该最后标识包,识别从目标网络设备接收的数据包中包含服务数据适配协议SDAP头的数据包和/或不包含SDAP头的数据包。
采用上述技术方案,终端设备可根据从目标网络设备接收的最后标识包,识别从目标网络设备接收的包含SDAP头的数据包和/或不包含SDAP头的数据包,进而针对包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理,从而使得数据包能够被正确接收和解码,避免跨系统切换过程中终端设备的数据丢失。
在第三方面的一种可能的设计中,终端设备可根据最后标识包对应的分组数据汇聚协议PDCP序列号,识别从目标网络设备接收到的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据包。
在第三方面的一种可能的设计中,源网络设备与目标网络设备采用不同的无线接入技术可以体现为,终端设备与源网络设备对应的协议栈中包括SDAP层的处理,而终端设备与目标网络设备对应的协议栈中不包括SDAP层的处理。
在第三方面的一种可能的设计中,当终端设备识别出从目标网络设备接收的数据包中包含SDAP头,终端设备中的PDCP实体可对该数据包进行PDCP处理,然后将该数据包 发送给终端设备中的SDAP实体,由该SDAP实体将该数据包中的SDAP头移除。当终端设备识别出从目标网络设备接收的数据包中不包含SDAP头,终端设备中的PDCP实体可对该数据包进行PDCP处理,但是在对该数据包进行PDCP处理之后,无需将该数据包再发送给SDAP实体去除SDAP头。
采用上述技术方案,终端设备中的PDCP实体递交至上层的数据包中可均不包括SDAP头,从而使得终端设备中PDCP层的上层能够对数据进行正确的接收和解码。
在第三方面的一种可能的设计中,终端设备中的SDAP实体可将移除SDAP头的该数据包发送至上层;或者,终端设备中的PDCP实体可从SDAP实体接收移除SDAP头之后的数据包,然后按照数据包的PDCP序列号对数据包进行排序后,将数据包按序发送至上层。
第四方面,本申请实施例提供一种切换方法,该方法可由源网络设备执行,该方法包括:源网络设备向终端设备发送切换命令,该切换命令指示终端设备从源网络设备切换到目标网络设备,该源网络设备与目标网络设备采用不同的无线接入技术;源网络设备继续向终端设备发送数据包,且源网络设备将终端设备的至少一个数据包发送给目标网络设备,该终端设备的至少一个数据包为源网络设备已进行分组数据汇聚协议PDCP处理的数据包;源网络设备接收到用于指示终端设备已成功接入目标网络设备的第一指示信息后,停止向终端设备发送数据包。
采用上述技术方案,源网络设备可在向终端设备发送切换命令之后,一边继续向终端设备发送数据包,另一边向目标网络设备发送已进行PDCP处理的终端设备的至少一个数据包,在从目标网络设备接收到用于指示终端设备已成功接入目标网络设备的第一指示信息后,再停止向终端设备发送数据包。如此,可使得跨系统切换过程中,终端设备与网络设备之间的连接不中断,从而提高终端设备的业务连续性。
在第四方面的一种可能的设计中,源网络设备通过一PDCP实体继续向终端设备发送数据包,且源网络设备可将经过该PDCP实体处理的终端设备的至少一个数据包发送给目标网络设备。
采用上述技术方案,源网络设备可通过同一PDCP实体一边向终端设备继续发送数据包,另一边向目标网络设备进行数据包的转发,从而避免跨系统切换过程中终端设备的数据丢失。
在第四方面的一种可能的设计中,源网络设备与目标网络设备采用不同的无线接入技术可以体现为,终端设备与源网络设备对应的协议栈中包括SDAP层的处理,而终端设备与目标网络设备对应的协议栈中不包括SDAP层的处理。
在第四方面的一种可能的设计中,源网络设备可将该终端设备的至少一个数据包中的服务数据适配协议SDAP头移除,然后将移除SDAP头之后的该至少一个数据包发送给目标网络设备。
采用上述技术方案,源网络设备向目标网络设备发送的至少一个数据包中均不包含SDAP头,这样目标网络设备向终端设备转发的至少一个数据包中也不包括SDAP头,如此,可使终端设备接入目标网络设备后,能够对从目标网络设备接收的数据包进行正确的接收和解码。
在第四方面的一种可能的设计中,源网络设备可将该终端设备的至少一个数据包发送给目标网络设备,所述数据包中包含SDAP头。
采用上述技术方案,源网络设备将终端设备的至少一个数据包发送给目标网络设备前,也可以不移除数据包中的SDAP头,而是由终端设备对从目标网络设备接收的包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理,如此,也可使终端设备能够对从目标网络设备接收的数据包进行正确的接收和解码。
在第四方面的一种可能的设计中,该方法还包括:源网络设备可将已进行PDCP处理的数据包对应的PDCP序列号发送给目标网络设备;和/或,源网络设备可将该目标网络设备可分配的第一个PDCP序列号发送给目标网络设备。
采用上述技术方案,可使得目标网络设备在为从核心网接收的数据包分配PDCP序列号时,能够继承或延续源网络设备侧的PDCP序列号,从而支持终端设备在跨系统切换过程中根据数据包的PDCP序列号进行按序递交和去重处理。
第五方面,本申请实施例提供一种切换方法,该方法可由目标网络设备执行,该方法包括:目标网络设备从源网络设备接收终端设备的至少一个数据包,该源网络设备与目标网络设备采用不同的无线接入技术;目标网络设备在终端设备接入目标网络设备后,将该至少一个数据包发送给终端设备,该至少一个数据包为源网络设备已进行分组数据汇聚协议PDCP处理的数据包;目标网络设备向源网络设备发送第一指示信息,该第一指示信息用于指示终端设备已成功接入目标网络设备。
采用上述技术方案,目标网络设备可从源网络设备接收终端设备的至少一个数据包,在终端设备接入目标网络设备后,将该至少一个数据包发送给终端设备,并向源网络设备发送用于指示终端设备已成功接入的第一指示信息。如此,可使得跨系统切换过程中,终端设备与网络设备之间的连接不中断,从而提高终端设备的业务连续性。
在第五方面的一种可能的设计中,目标网络设备可向终端设备发送第二指示信息,该第二指示信息用于指示终端设备停止从源网络设备接收数据包,从而使终端设备完成跨系统切换的过程。
在第五方面的一种可能的设计中,源网络设备与目标网络设备采用不同的无线接入技术可以体现为,终端设备与源网络设备对应的协议栈中包括SDAP层的处理,而终端设备与目标网络设备对应的协议栈中不包括SDAP层的处理。
在第五方面的一种可能的设计中,源网络设备已进行PDCP处理的数据包中不包含服务数据适配协议SDAP头。可选的,可以是源网络设备在向目标网络设备发送该已进行PDCP处理的数据包之前移除了其中的SDAP头。
采用上述技术方案,由于目标网络设备可向终端设备转发不包含SDAP头的至少一个数据包,因此,可使终端设备接入目标网络设备后,能够对从目标网络设备接收的数据包进行正确的接收和解码。
在第五方面的一种可能的设计中,源网络设备已进行PDCP处理的数据包中包含SDAP头;该方法还包括:目标网络设备向终端设备发送最后标识包,该最后标识包用于指示包含SDAP头的数据包发送完毕。
采用上述技术方案,源网络设备也可以将已进行PDCP处理的数据包直接发送给目标网络设备,而不做移除SDAP头的处理,如此,目标网络设备向终端设备发送的数据包中可包括包含SDAP头的数据包和/或不包含SDAP头的数据包,通过向终端设备发送最后标识包,可使终端设备根据该最后标识包识别从目标网络设备接收的包含SDAP头的数据包,以及不包含SDAP头的数据包,从而对包含SDAP头的数据包和不包含SDAP头的数据包 进行分别处理,使得数据包能够被正确接收和解码。
在第五方面的一种可能的设计中,该方法还包括:目标网络设备从源网络设备接收源网络设备已进行PDCP处理的数据包对应的PDCP序列号;和/或,目标网络设备从源网络设备接收目标网络设备可分配的第一个PDCP序列号。
采用上述技术方案,目标网络设备可继承或延续源网络设备的PDCP序列号,继续为从核心网接收的数据包分配PDCP序列号,从而支持终端设备在跨系统切换过程中根据数据包的PDCP序列号进行按序递交和去重处理。
第六方面,本申请实施例提供一种切换方法,该方法可由终端设备执行,该方法包括:终端设备从源网络设备接收切换命令,该切换命令指示终端设备由源网络设备切换到目标网络设备,该源网络设备与目标网络设备采用不同的无线接入技术;终端设备继续通过分组数据汇聚协议PDCP实体从源网络设备接收数据包;终端设备接入目标网络设备,并通过该PDCP实体从目标网络设备接收至少一个数据包。
采用上述技术方案,终端设备可在从源网络设备接收切换命令后,一边继续从源网络设备接收数据包,另一边接入目标网络设备,并通过同一PDCP实体从目标网络设备接收目标网络设备转发的至少一个数据包。如此,可使得跨系统切换过程中,终端设备与网络设备之间的连接不中断,从而提高终端设备的业务连续性。
在第六方面的一种可能的设计中,源网络设备与目标网络设备采用不同的无线接入技术可以体现为,终端设备与源网络设备对应的协议栈中包括SDAP层的处理,而终端设备与目标网络设备对应的协议栈中不包括SDAP层的处理。
在第六方面的一种可能的设计中,终端设备从源网络设备接收的数据包中包含服务数据适配协议SDAP头;该方法还包括:PDCP实体对从源网络设备接收的数据包进行PDCP处理,并将经过PDCP处理后的数据包发送至终端设备中的SDAP实体移除SDAP头。可选的,SDAP实体可将移除SDAP头之后的数据包发送至上层,或者PDCP实体还可从SDAP实体接收移除SDAP头之后的数据包,然后由PDCP实体将移除SDAP头之后的数据包发送至上层。如此,终端设备可对从源网络设备接收的数据包进行正确的接收和解码。
在第六方面的一种可能的设计中,终端设备从目标网络设备接收的数据包中不包含SDAP头;可选的,可以是源网络设备在向目标网络设备发送该数据包之前移除了其中的SDAP头。该方法还包括:PDCP实体对从目标网络设备接收的数据包进行PDCP处理。
采用上述技术方案,由于目标网络设备向终端设备发送的数据包中不包含SDAP头,因此,终端设备可以对从目标网络设备接收的数据包进行正确的接收和解码。
在第六方面的一种可能的设计中,终端设备从目标网络设备接收的数据包中包括包含SDAP头的数据包和/或不包含SDAP头的数据包;该方法还包括:PDCP实体从目标网络设备接收最后标识包;PDCP实体根据该最后标识包,识别从目标网络设备接收的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据包。
采用上述技术方案,源网络设备也可以将已进行PDCP处理但未接收到终端设备的确认响应的数据包直接发送给目标网络设备,而不做移除SDAP头的处理。如此,目标网络设备向终端设备发送的数据包中可包括包含SDAP头的数据包和/或不包含SDAP头的数据包,其中包含SDAP头的数据包可以是目标网络设备从源网络设备接收的数据包,不包含SDAP头的数据包可以是目标网络设备从核心网接收的数据包。通过向终端设备发送最后标识包,终端设备可根据该最后标识包识别从目标网络设备接收的包含SDAP头的数据包, 以及不包含SDAP头的数据包,从而对包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理,使得数据包能够被正确接收和解码。
在第六方面的一种可能的设计中,当终端设备识别出从目标网络设备接收的包含SDAP头的数据包,该方法还包括:PDCP实体对该数据包进行PDCP处理,并将经过PDCP处理后的数据包发送至SDAP实体移除SDAP头;PDCP实体从SDAP实体接收移除SDAP头之后的数据包。当终端设备识别出从目标网络设备接收的不包含SDAP头的数据包,该方法还包括:PDCP实体对数据包进行PDCP处理。
采用上述技术方案,终端设备对从目标网络设备接收的包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理可以为,在PDCP实体对数据包进行PDCP处理后,再将包含SDAP头的数据包发送至SDAP实体移除SDAP头。如此,可使递交至上层的数据包均不包括SDAP头,从而使得数据包均能够被正确接收和解码。
在第六方面的一种可能的设计中,PDCP实体中包括第一处理单元和第二处理单元,其中,第一处理单元与源网络设备的安全配置相对应,第二处理单元与目标网络设备的安全配置相对应;该方法还包括:PDCP实体通过第一处理单元对从源网络设备接收的数据包进行PDCP处理,通过第二处理单元对从目标网络设备接收到的数据包进行PDCP处理。
采用上述技术方案,终端设备中的PDCP实体可以为动态双栈的结构,也就是说,该PDCP实体中可包括两个处理单元,且每个处理单元分别与源网络设备和目标网络设备的安全配置相应。如此,终端设备可采用PDCP实体中的不同处理单元对从源网络设备接收的数据包以及从目标网络设备接收的数据包进行PDCP处理,从而使得从源网络设备接收的数据包以及从目标网络设备接收的数据包都能进行正常的PDCP处理,增强该切换方法的适用性,避免由于源网络设备与目标网络设备采用的PDCP的安全配置不一致,导致数据处理失败的问题。
在第六方面的一种可能的设计中,该方法还包括:PDCP实体根据数据包的PDCP序列号,对从源网络设备接收的数据包和从目标网络设备接收的数据包进行排序和/或去重处理;PDCP实体将处理后的数据包按序发送至上层。
第七方面,本申请实施例提供一种通信装置,该装置具有实现上述第一方面或第一方面的任一种可能的设计中源网络设备的功能,或具有实现上述第二方面或第二方面的任一种可能的设计中目标网络设备的功能,或具有实现上述第四方面或第四方面的任一种可能的设计中源网络设备的功能,或具有实现上述第五方面或第五方面的任一种可能的设计中目标网络设备的功能。该装置可以为网络设备,也可以为网络设备中包含的芯片。上述通信装置的功能可以通过硬件实现,也可以通过硬件执行相应的软件实现,所述硬件或软件包括一个或多个与上述功能相对应的模块或单元或手段(means)。
该装置也可以具有实现上述第四方面或第四方面的任一种可能的设计中终端设备的功能,或者具有实现上述第六方面或第六方面的任一种可能的设计中终端设备的功能,该装置可以为终端设备,也可以为终端设备中包括的芯片。上述通信装置的功能可以通过硬件实现,也可以通过硬件执行相应的软件实现,所述硬件或软件包括一个或多个与上述功能相对应的模块或单元或手段(means)。
在一种可能的设计中,该装置的结构中包括处理模块和收发模块,其中,处理模块被配置为支持该装置执行上述第一方面或第一方面的任一种设计中源网络设备相应的功能,或者执行上述第二方面或第二方面的任一种设计中目标网络设备相应的功能,或者执行上 述第四方面或第四方面的任一种可能的设计中源网络设备相应的功能,或者执行上述第五方面或第五方面的任一种可能的设计中目标网络设备相应的功能,或者执行上述第六方面或第六方面的任一种可能的设计中终端设备相应的功能,或者执行上述第七方面或第七方面的任一种可能的设计中终端设备相应的功能。收发模块用于支持该装置与其他通信设备之间的通信,例如该装置为源网络设备时,可向目标网络设备发送终端设备未成功接收的至少一个数据包。该通信装置还可以包括存储模块,存储模块与处理模块耦合,其保存有装置必要的程序指令和数据。作为一种示例,处理模块可以为处理器,通信模块可以为收发器,存储模块可以为存储器,存储器可以和处理器集成在一起,也可以和处理器分离设置,本申请并不限定。
在另一种可能的设计中,该装置的结构中包括处理器,还可以包括存储器。处理器与存储器耦合,可用于执行存储器中存储的计算机程序指令,以使装置执行上述第一方面、或第一方面的任一种可能的设计中的方法,或者执行上述第二方面或第二方面的任一种可能的设计中的方法,或者执行上述第三方面或第三方面的任一种可能的设计中的方法,或者执行上述第四方面或第四方面的任一种可能的设计中的方法,或者执行上述第五方面或第五方面的任一种可能的设计中的方法,或者执行上述第六方面或第六方面的任一种可能的设计中的方法。可选地,该装置还包括通信接口,处理器与通信接口耦合。当装置为网络设备或终端设备时,该通信接口可以是收发器或输入/输出接口;当该装置为网络设备或终端设备中包含的芯片时,该通信接口可以是芯片的输入/输出接口。可选地,收发器可以为收发电路,输入/输出接口可以是输入/输出电路。
第八方面,本申请实施例提供一种芯片系统,包括:处理器,所述处理器与存储器耦合,所述存储器用于存储程序或指令,当所述程序或指令被所述处理器执行时,使得该芯片系统实现上述第一方面或第一方面的任一种可能的设计中的方法,或实现上述第二方面或第二方面的任一种可能的设计中的方法,或实现上述第三方面或第三方面的任一种可能的设计中的方法,或实现上述第四方面或第四方面的任一种可能的设计中的方法,或实现上述第五方面或第五方面的任一种可能的设计中的方法,或实现上述第六方面或第六方面的任一种可能的设计中的方法。
可选地,该芯片系统还包括接口电路,该接口电路用于交互代码指令至所述处理器。
可选地,该芯片系统中的处理器可以为一个或多个,该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时,该处理器可以是逻辑电路、集成电路等。当通过软件实现时,该处理器可以是一个通用处理器,通过读取存储器中存储的软件代码来实现。
可选地,该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起,也可以和处理器分离设置,本申请并不限定。示例性的,存储器可以是非瞬时性处理器,例如只读存储器ROM,其可以与处理器集成在同一块芯片上,也可以分别设置在不同的芯片上,本申请对存储器的类型,以及存储器与处理器的设置方式不作具体限定。
第九方面,本申请实施例提供一种计算机可读存储介质,其上存储有计算机程序或指令,当该计算机程序或指令被执行时,使得计算机执行上述第一方面或第一方面的任一种可能的设计中的方法,或执行上述第二方面或第二方面的任一种可能的设计中的方法,或执行上述第三方面或第三方面的任一种可能的设计中的方法,或执行上述第四方面或第四方面的任一种可能的设计中的方法,或执行上述第五方面或第五方面的任一种可能的设计中的方法,或执行上述第六方面或第六方面的任一种可能的设计中的方法。
第十方面,本申请实施例提供一种计算机程序产品,当计算机读取并执行所述计算机程序产品时,使得计算机执行上述第一方面或第一方面的任一种可能的设计中的方法,或执行上述第二方面或第二方面的任一种可能的设计中的方法,或执行上述第三方面或第三方面的任一种可能的设计中的方法,或执行上述第四方面或第四方面的任一种可能的设计中的方法,或执行上述第五方面或第五方面的任一种可能的设计中的方法,或执行上述第六方面或第六方面的任一种可能的设计中的方法。
第十一方面,本申请实施例提供一种通信系统,该通信系统包括上述的源网络设备、目标网络设备和至少一个终端设备。可选的,该通信系统中还可包括核心网设备。
附图说明
图1a至图1c为本申请实施例适用的应用场景的示意图;
图2为本申请实施例提供的一种切换方法的流程示意图;
图3a为本申请实施例提供的第一通信制式的通信系统中空中接口协议栈的示意图;
图3b为本申请实施例提供的第二通信制式的通信系统中空中接口协议栈的示意图;
图4为本申请实施例提供的第一种场景中一种切换方法的第一种实现方式的示意图;
图5为本申请实施例提供的第一种场景中一种切换方法的第二种实现方式的示意图;
图6为本申请实施例提供的第二种场景中一种切换方法的实现方式的示意图;
图7为本申请实施例提供的另一种切换方法的流程示意图;
图8为本申请实施例提供的第一种场景中另一种切换方法的第一种实现方式的示意图;
图9为本申请实施例提供的第一种场景中另一种切换方法的第二种实现方式的示意图;
图10为本申请实施例提供的一种通信装置的结构示意图;
图11为本申请实施例提供的一种通信装置的另一结构示意图;
图12为本申请实施例提供的另一种通信装置的另一结构示意图;
图13为本申请实施例提供的另一种通信装置的另一结构示意图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚,下面将结合附图对本申请实施例作进一步地详细描述。
本申请实施例的技术方案可以应用于各种通信系统,例如:全球移动通信(global system for mobile communications,GSM)系统、码分多址(code division multiple access,CDMA)系统、宽带码分多址(wideband code division multiple access,WCDMA)系统、通用分组无线业务(general packet radio service,GPRS)、长期演进(long term evolution,LTE)系统、LTE频分双工(frequency division duplex,FDD)系统、LTE时分双工(time division duplex,TDD)、通用移动通信系统(universal mobile telecommunication system,UMTS)、全球互联微波接入(worldwide interoperability for microwave access,WIMAX)通信系统、第五代(5th generation,5G)通信系统或新无线(new radio,NR),或者应用于未来的通信系统或其它类似的通信系统等。
本申请实施例提供的技术方案适用于不同通信制式的通信系统共存的场景中,请参考图1a至图1c,为本申请实施例适用的应用场景的示意图,或者说本申请实施例适用的网 络架构的示意图。该网络架构中包括源网络设备、目标网络设备和终端设备,其中,源网络设备是指终端设备在切换前接入的网络设备,目标网络设备是指终端设备在切换后接入的网络设备,且源网络设备与目标网络设备采用不同的无线接入技术(radio access technology,RAT)。或者也可以理解为源网络设备和目标网络设备为不同通信制式的通信系统中的网络设备。如此,本申请实施例提供的技术方案可以支持终端设备在不同通信制式的通信系统之间进行切换。
举例来说,终端设备可以在5G通信系统与4G通信系统之间进行切换,源网络设备可以为5G通信系统中的网络设备,目标网络设备可以为4G通信系统中的网络设备。或者也可以反过来,即源网络设备可以为4G通信系统中的网络设备,目标网络设备可以为5G通信系统中的网络设备。应理解,所述5G通信系统还可以称为简称为5G系统,4G通信系统还可以称为简称为4G系统,在5G通信系统中,网络设备连接的核心网称为第五代核心网(5th generation core,5GC),在4G通信系统中,网络设备连接的核心网称为演进分组核心网(evolved packet core,EPC)。
本申请实施例可涵盖多种不同的切换场景。如图1a至图1c所示,5G通信系统的覆盖区域与4G通信系统的覆盖区域存在重叠。在图1a中,终端设备可能由于位置的移动而发生跨系统的切换,例如从5G通信系统切换到4G通信系统,或从4G通信系统切换到5G通信系统。在图1b中,终端设备还可能由于位置的移动,而发生从单连接到双连接或多连接的跨系统的切换,例如终端设备从5G通信系统的单连接,切换到同时连接5G通信系统与4G通信系统的双连接。在图1c中,由于不同的通信系统可支持的业务类型不同,终端设备可能会因所进行的业务的变化,而发生跨系统的切换,即发生接入网络的回退(fall back)。
应理解,图1a至图1c是以终端设备在5G通信系统与4G通信系统之间切换为例进行描述的,但这仅为一个示例,并不构成对本申请的限定。同样,本申请实施例中的切换场景也不限于图1a至图1c中所述的切换场景。
还应理解,所述切换可以为单连接与双连接之间的切换,也可以为单连接与多连接之间进行切换。所述双连接(dual connectivity,DC)是指终端设备同时接入到两个网络设备,其中,一个网络设备为主网络设备,另一个网络设备为辅网络设备,主网络设备也可以称为主节点(master node,MN),辅网络设备也可以称为辅节点(secondary node,SN)。多连接与此类似,是指终端设备同时接入到多个网络设备,其中,一个网络设备为主网络设备,其它的一个或多个网络设备为辅网络设备。
目前,终端设备可以支持演进的通用陆面无线接入与新空口双连接(E-UTRA NR dual connectivity,EN-DC),在EN-DC模式下,终端设备同时接入的两个网络设备中一个为4G通信系统中的网络设备,另一个为5G通信系统中的网络设备,且4G通信系统中的网络设备为主网络设备,5G通信系统中的网络设备为辅网络设备。随着系统的演进,未来终端设备也可以支持新空口与演进的通用陆面无线接入双连接(NR E-UTRA dual connectivity,NE-DC),在NE-DC模式下,终端设备同时接入的两个网络设备中一个为4G通信系统中的网络设备,另一个为5G通信系统中的网络设备,且5G通信系统中的网络设备为主网络设备,4G通信系统中的网络设备为辅网络设备。此外,终端设备还可以支持连接到5GC的演进的通用陆面无线接入与新空口双连接(Next Generation E-UTRA NR dual connectivity,NGEN-DC),以及NR与NR的双连接NR-DC。
双连接(dual connectivity,DC)中包括主小区组(master cell group,MCG)和辅小区组(secondary cell group,SCG),MCG中可以包括一个或多个载波,若包括多个载波则这些载波之间可以是载波聚合(carrier aggregation,CA),SCG中可以包括一个或多个载波,若包括多个载波则这些载波之间可以是CA。其中,主网络设备负责MCG的调度,辅网络设备负责SCG的调度。
下面对本申请实施例中的部分用语进行解释说明,以便于本领域技术人员理解。
1)终端设备,是一种具有无线收发功能的设备,可以部署在陆地上,包括室内或室外、手持、穿戴或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等。所述终端设备可以经无线接入网(radio access network,RAN)与核心网进行通信,与RAN交换语音和/或数据。所述终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、移动互联网设备(mobile internet device,MID)、可穿戴设备、虚拟现实(virtual reality,VR)终端设备、增强现实(augmented reality,AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本申请的实施例对应用场景不做限定。终端设备有时也可以称为用户设备(user equipment,UE)、移动台和远方站等,本申请的实施例对终端设备所采用的具体技术、设备形态以及名称不做限定。
作为示例而非限定,在本申请实施例中,该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备或智能穿戴式设备等,是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称,如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上,或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备,更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能,例如:智能手表或智能眼镜等,以及只专注于某一类应用功能,需要和其它设备如智能手机配合使用,如各类进行体征监测的智能手环、智能头盔、智能首饰等。
本申请实施例中的终端设备还可以是作为一个或多个部件或者单元而内置于车辆的车载模块、车载模组、车载部件、车载芯片或者车载单元,车辆通过内置的所述车载模块、车载模组、车载部件、车载芯片或者车载单元可以实施本申请的方法。
2)网络设备,也称接入网设备,是网络中用于将终端设备接入到无线网络的设备。所述网络设备可以为无线接入网中的节点,又可以称为基站,还可以称为无线接入网(radio access network,RAN)节点(或设备)。网络设备可用于将收到的空中帧与网际协议(IP)分组进行相互转换,作为终端设备与接入网的其余部分之间的路由器,其中接入网的其余部分可包括IP网络。网络设备还可协调对空口的属性管理。所述网络设备可以包括长期演进(long term evolution,LTE)系统或演进的LTE系统(LTE-Advanced,LTE-A)中的演进型基站(NodeB或eNB或e-NodeB,evolutional Node B),如传统的宏基站eNB和异构网络场景下的微基站eNB,或者也可以包括第五代移动通信技术(5th generation,5G)新无线(new radio,NR)系统中的下一代节点B(next generation node B,gNB),或者还可以包括无线网络控制器(radio network controller,RNC)、节点B(Node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、传输接 收点(transmission reception point,TRP)、家庭基站(例如,home evolved NodeB,或home Node B,HNB)、基带单元(base band unit,BBU)、基带池BBU pool,或WiFi接入点(access point,AP)等,再或者还可以包括云接入网(cloud radio access network,CloudRAN)系统中的集中式单元(centralized unit,CU)和分布式单元(distributed unit,DU),本申请实施例并不限定。在接入网设备包括CU和DU的分离部署场景中,CU支持无线资源控制(radio resource control,RRC)、分组数据汇聚协议(packet data convergence protocol,PDCP)、业务数据适配协议(service data adaptation protocol,SDAP)等协议;DU主要支持无线链路控制层(radio link control,RLC)、媒体接入控制层(media access control,MAC)和物理层协议。
3)需要说明的是,本申请实施例中的术语“系统”和“网络”可被互换使用。“多个”是指两个或两个以上,鉴于此,本申请实施例中也可以将“多个”理解为“至少两个”。“至少一个”,可理解为一个或多个,例如理解为一个、两个或更多个。例如,包括至少一个,是指包括一个、两个或更多个,而且不限制包括的是哪几个。例如,包括A、B和C中的至少一个,那么包括的可以是A、B、C,A和B,A和C,B和C,或A和B和C。同理,对于“至少一种”等描述的理解,也是类似的。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,字符“/”,如无特殊说明,一般表示前后关联对象是一种“或”的关系。
除非有相反的说明,本申请实施例提及“第一”、“第二”等序数词用于对多个对象进行区分,不用于限定多个对象的顺序、时序、优先级或者重要程度,并且“第一”、“第二”的描述也并不限定对象一定不同。
请参考图2,为本申请实施例提供的一种切换方法的流程示意图,该方法具体包括如下步骤:
步骤S201、源网络设备向终端设备发送切换命令,该切换命令用于指示终端设备由源网络设备切换到目标网络设备。
本申请实施例中,在源网络设备向终端设备发送切换命令之前,终端设备可接入源网络设备,并与源网络设备进行数据传输。
上述切换命令可以是切换命令消息或者信令,不作限定。
步骤S202、源网络设备将终端设备未成功接收的至少一个数据包发送给目标网络设备。
所述终端设备未成功接收的至少一个数据包是指,源网络设备认为终端设备未成功接收的至少一个数据包,即当前所有可能的没有被终端设备成功接收的数据包。
其中,所述终端设备未成功接收的至少一个数据包可包括:源网络设备已向终端设备发送但是还未收到来自终端设备的确认响应的数据包,以及源网络设备还未向终端设备发送的数据包。所述源网络设备已向终端设备发送但是未收到来自终端设备的确认响应的数据包可以是源网络设备已进行分组数据汇聚协议(packet data convergence protocol,PDCP)处理的数据包,如分组数据汇聚协议协议数据单元(packet data convergence protocol protocal data unit,PDCP PDU)。所述源网络设备未向终端设备发送的数据包可以包括源网络设备已进行PDCP处理的数据包,如PDCP PDU,也可以包括源网络设备还未通过PDCP层进行PDCP处理的数据包,如分组数据汇聚协议服务数据单元(packet data convergence protocol service data unit,PDCP SDU),还可以包括源网络设备从核心网设备接收的新数据 (fresh data)。
应理解,本申请实施例中,源网络设备已向终端设备发送但是还未收到来自终端设备的确认响应的数据包,并不绝对表示该数据包没有被终端设备成功接收,或者该数据包此后不会被终端设备成功接收。有可能该数据包已被终端设备成功接收,但是终端设备还未向源网络设备发送确认响应;也有可能该数据包已被终端设备成功接收,终端设备也向源网络设备发送了确认响应,但是源网络设备还未收到该确认响应;还有可能该数据包当前未被终端设备成功接收,但是在之后被终端设备成功接收,并且终端设备向源网络设备发送了该数据包对应的确认响应。
还应理解,本申请对步骤S201和步骤S202执行的先后顺序并不限定,例如先执行S201之后再执行S202,或者先执行S202之后再执行S201。
步骤S203、目标网络设备从源网络设备接收该终端设备未成功接收的至少一个数据包。
步骤S204、终端设备从源网络设备接收切换命令。
本申请实施例中,终端设备从源网络设备接收切换命令之后,可断开与源网络设备之间的连接,停止与源网络设备之间的数据传输。
步骤S205、终端设备接入目标网络设备。
本申请实施例中,终端设备可在从源网络设备接收切换命令之后,发起随机接入过程,接入目标网络设备。
可选的,在步骤S206中,目标网络设备可在终端设备接入目标网络设备后,将该终端设备未成功接收的至少一个数据包发送给终端设备。相应的,在步骤S207中,终端设备可从目标网络设备接收上述至少一个数据包。
由此可知,由于源网络设备可将当前所有可能的终端设备没有成功接收的数据包都转发给目标网络设备,由目标网络设备将这部分数据包发送给终端设备,因此,可有效避免异系统切换过程中终端设备的数据丢失,从而提高用户体验。
可选地,在本申请的一个实施方式中,步骤S202中所提及的所述终端设备未成功接收的至少一个数据包还可以按照源网络设备是否对数据包进行了PDCP处理来划分。即,步骤S202中所提及的所述终端设备未成功接收的至少一个数据包可包括下列数据包中的一种或多种:源网络设备已进行PDCP处理但未收到终端设备的确认响应的数据包,以及源网络设备未进行PDCP处理的数据包。
其中,所述源网络设备已进行PDCP处理但未收到终端设备的确认响应的数据包中可包括:源网络设备已进行PDCP处理且源网络设备已通过空中接口向终端设备发送了的数据包,以及源网络设备已进行PDCP处理但是源网络设备还没有向终端设备发送的数据包。
所述源网络设备已进行PDCP处理可以理解为,源网络设备对数据包进行了PDCP实体中全部或部分功能模块的处理,例如,为数据包分配了对应的PDCP序列号,即可以将已被分配PDCP序列号的数据包认为是已进行PDCP处理的数据包。
可选的,所述源网络设备已进行PDCP处理的数据包可以为PDCP PDU。所述源网络设备未进行PDCP处理的数据包中可包括:源网络设备还未送入PDCP层进行PDCP处理的数据包,以及源网络设备从核心网设备新接收的该终端设备的数据包(即fresh data)。
现有技术中,当终端设备进行跨系统的切换时,源网络设备并不会将已进行PDCP处理的数据包转发给目标网络设备。因此,对于这部分数据包,如果终端设备没有收到,则相当于在切换过程中丢失了。而本申请实施例中,由于源网络设备向目标网络设备转发的 至少一个数据包中可包括源网络设备已进行PDCP处理但是还未收到来自终端设备的确认响应的数据包,以及源网络设备未进行PDCP处理的数据包,因此可有效避免跨系统切换过程中终端设备的数据丢失,从而提高用户体验。
在一种应用场景中,源网络设备可以为采用第一通信制式的通信系统中的网络设备,在该第一通信制式的通信系统中,网络设备和终端设备的空中接口协议栈中包括SDAP层的处理。目标网络设备可以为采用第二通信制式的通信系统中的网络设备,在该第二通信制式的通信系统中,网络设备和终端设备的空中接口协议栈中不包括SDAP层的处理。例如,源网络设备可以为5G通信系统中的接入网设备,目标网络设备可以为4G通信系统中的接入网设备。
请参考图3a,为本申请实施例提供的第一通信制式的通信系统中网络设备和终端设备的空中接口协议栈的示意图。结合图3a,在跨系统切换前,源网络设备向终端设备发送数据的过程具体包括:源网络设备中的SDAP实体首先对从上层接收的数据包(packet)进行服务质量(quality of service,QoS)流到数据无线承载(data radio bearer,DRB)的映射,其中,DRB与PDCP实体之间是一一对应的关系,即一个DRB对应一个PDCP实体。随后,SDAP实体可以对该数据包进行其他处理,例如,若配置了SDAP头,SDAP实体可为该数据包增加SDAP头,生成SDAP PDU,生成的SDAP PDU可以作为PDCP SDU送入DRB对应的PDCP实体中进行继续处理。若没有配置SDAP头,SDAP实体可以直接将该数据包作为PDCP SDU送入DRB对应的PDCP实体进行继续处理。PDCP实体从SDAP实体接收到PDCP SDU后,可对PDCP SDU进行编号、安全保护(包括完整性保护和/或加密)、增加PDCP头等处理,生成PDCP PDU。可选的,如果需要的话,PDCP实体还可进行头压缩、路由、复制等处理,本申请并不限定。进一步地,PDCP实体生成的PDCP PDU可送入RLC,经RLC进行进一步处理后,送入MAC、PHY,最后承载在空中接口上进行传输。
相应的,终端设备在从源网络设备接收数据时可以进行反方向的对称处理,即先经PHY、MAC处理后,送入RLC,得到PDCP PDU。然后将得到的PDCP PDU送入PDCP实体进行移除PDCP头、安全处理(包括解密和/或完整性校验)、重排序/重复性检测等处理,生成PDCP SDU。生成的PDCP SDU可以作为SDAP PDU送入SDAP实体中进行处理,如果由SDAP头的话,SDAP实体需要移除SDAP头,然后通过PDCP实体对应的DRB将得到的数据包映射到QoS流,并发送到上层。
请参考图3b,为本申请实施例提供的第二通信制式的通信系统中网络设备和终端设备的空中接口协议栈的示意图。结合图3b,在跨系统切换后,目标网络设备向终端设备发送数据的过程中,由于网络设备与终端设备的协议栈中都没有配置SDAP层,上层数据可以直接送入PDCP实体进行处理。具体的,PDCP实体从上层接收到数据包后,可对数据包进行编号、头压缩、安全保护(包括完整性保护和/或加密)、增加PDCP头等处理,生成PDCP PDU。随后,生成的PDCP PDU送入RLC层继续处理,然后经过MAC和PHY处理后通过空中接口传输给终端设备。可以看出,该数据处理过程中没有SDAP处理,但PDCP处理及后续的RLC、MAC、PHY等处理均与图3a中所示的源网络设备侧的处理类似,还应注意,目标网络设备可以使用与源网络设备侧相同的PDCP(如NR PDCP),也可以使用不同的PDCP(如E-UTRA PDCP),本申请并不限定。
相应的,终端设备在从源网络设备接收数据时可以进行反方向的对称处理,即先经PHY、MAC处理后,送入RLC,得到PDCP PDU。然后将得到的PDCP PDU送入PDCP实体进行移除PDCP头、安全处理(包括解密和/或完整性校验)、重排序/重复性检测等,得到PDCP SDU,然后发送至上层。
通过图3a和图3b可以看出,由于不同的通信系统对数据的处理不一致,在步骤S202中,源网络设备向目标网络设备发送的终端设备未成功接收的至少一个数据包中可能包含SDAP头。若源网络设备直接将包含SDAP头的数据包发送给目标网络设备,由目标网络设备将这部分数据包再转发给终端设备,由于在终端设备接入目标网络设备后,与目标网络设备相匹配的空中接口的协议栈中已不包括SDAP层的处理,终端设备接收到数据包后,并不认识其中的SDAP头,无法对数据包中的SDAP头进行处理,进而会造成数据的接收和解码失败。
如图4所示,第一种可能的实现方式为,针对终端设备未成功接收的至少一个数据包中源网络设备已进行PDCP处理但还未收到来自终端设备的确认响应的数据包,源网络设备可在将该数据包发送给目标网络设备之前,将该数据包中的SDAP头移除,然后将移除SDAP头之后的数据包发送给目标网络设备,通过目标网络设备再将该数据包发送给终端设备。
考虑到源网络设备已为每个进行PDCP处理的数据包分配了对应的PDCP序列号,源网络设备可将每个已进行PDCP处理但还未收到来自终端设备的确认响应的数据包对应的PDCP序列号和数据包一起发送给目标网络设备。源网络设备还可将目标网络设备可分配的第一个PDCP序列号发送给目标网络设备,由于PDCP序列号一般是按序分配的,该目标网络设备可分配的第一个PDCP序列号可以为源网络设备已分配的PDCP序列号的下一个PDCP序列号。如此,目标网络设备可以延续或继承源网络设备侧的PDCP序列号,为源网络设备未进行PDCP处理的数据包以及目标网络设备从核心网接收的该终端设备的数据包分配PDCP序列号;相应的,终端设备从目标网络设备接收数据包时,可根据数据包对应的PDCP序列号进行按序递交和重复性检测。终端设备还可向目标网络设备发送PDCP状态报告,告知目标网络设备自己未收到的数据包。
可选的,所述源网络设备已进行PDCP处理但还未收到来自终端设备的确认响应的数据包可以为PDCP SDU,即源网络设备可将未收到来自终端设备的确认响应的PDCP SDU中的SDAP头移除,然后将移除SDAP头之后的PDCP SDU带着对应的PDCP序列号一起发送给目标网络设备,此时也可以理解为发送给目标网络设备的是SDAP SDU和PDCP序列号。通过向目标网络设备发送还未收到来自终端设备的确认响应的PDCP SDU,目标网络设备可以使用自己的PDCP对接收的数据包进行继续处理,生成PDCP PDU,例如目标网络设备可以使用自己的安全机制对接收的数据包进行加密和/或完整性保护,如图5中所示的T-加密和T-完整性保护,然后再经过RLC、MAC、PHY等处理后,通过空中接口发送给终端设备。
如此,可使得目标网络设备向终端设备发送的从源网络设备转发的数据包能够被终端设备正确接收和解码,避免由于源网络设备侧与目标网络设备侧使用的PDCP不一致,终端设备接入目标网络设备后,使用与目标网络设备相匹配的协议栈,无法对经过源网络设备的PDCP处理的数据包进行对称的PDCP处理的问题。
应理解,本申请实施例中,源网络设备可以在PDCP层移除SDAP头,也可以在SDAP 层移除SDAP头,或者也可以通过其他方式来移除SDAP头,如在协议栈中的其他层移除SDAP头,本申请并不限定。
针对终端设备未成功接收的至少一个数据包中源网络设备未进行PDCP处理的数据包,源网络设备可在将该数据包映射到对应的DRB,且不在该数据包中添加SDAP头,然后将映射到DRB的数据包发送给目标网络设备。若源网络设备已对某些数据包进行了SDAP处理,添加了SDAP头,但是还没有送入PDCP层,那么源网络设备也要将数据包中已添加的SDAP头移除,然后将移除了SDAP头的数据包发送给目标网络设备。相应的,目标网络设备接收到这部分源网络设备未进行PDCP处理后的数据包后,可使用自己的PDCP进行处理,然后再经过RLC、MAC、PHY等处理后,通过空中接口发送给终端设备。
应注意,与源网络设备已进行PDCP处理的数据包不同,这部分源网络设备未进行PDCP处理的数据包,还没有被源网络设备分配对应的PDCP序列号,因此源网络设备并不会将这部分数据包对应的PDCP序列号发送给目标网络设备。目标网络设备可自行为这部分未经源网络设备的PDCP处理的数据包分配PDCP序列号,并进行PDCP处理。例如,目标网络设备可从源网络设备接收的第一个可分配的PDCP序列号开始,为从源网络设备接收的源网络设备未进行PDCP处理的数据包分配对应的PDCP序列号。
可以看出,从目标网络设备的角度,目标网络设备从源网络设备接收的源网络设备已进行PDCP处理以及源网络设备未进行PDCP处理的数据包中均不包括SDAP头,且源网络设备向目标网络设备转发的PDCP SDU或fresh data可以由目标网络设备进行PDCP处理,因此,可使终端设备能够对从目标网络设备接收的至少一个数据包进行正确接收和解码。
第二种可能的实现方式为,如图5所示,源网络设备将该终端设备未成功接收的至少一个数据包发送给目标网络设备时,可以不做移除SDAP头的处理。也就是说,源网络设备可将终端设备未成功接收的至少一个数据包发送给目标网络设备,该终端设备未成功接收的至少一个数据包中可包括包含SDAP头的数据包和/或不包含SDAP头的数据包。其中,所述终端设备未成功接收的至少一个数据包中源网络设备已进行PDCP处理但还未收到来自终端设备的确认响应的数据包中包括在进行PDCP处理前添加的SDAP头。所述终端设备未成功接收的至少一个数据包中源网络设备未进行PDCP处理的数据包中不包括SDAP头。
目标网络设备可从源网络设备接收该终端设备未成功接收的至少一个数据包,并在终端设备接入目标网络设备后,将该终端设备未成功接收的至少一个数据包和第一最后标识包发送给终端设备,该第一最后标识包用于指示包含SDAP头的数据包发送完毕。
如此,终端设备可根据该第一最后标识包,识别从目标网络设备接收的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据包,并针对包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理。
具体的,终端设备可根据第一最后标识包的PDCP序列号,识别从目标网络设备接收的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据包。例如,当第一最后标识包是目标网络设备向终端设备发送的一个用于标识结束的空的数据包时,终端设备可认为从目标网络设备接收的PDCP序列号小于第一最后标识包的PDCP序列号的数据包中包含SDAP头,而从目标网络设备接收的PDCP序列号大于第一最后标识包的序列号的数据包中不包含SDAP头。再例如,当第一最后标识包为目标网络设备向终端设备发送的源网络 设备已进行PDCP处理但未接收到来自终端设备的确认响应的最后一个数据包时,终端设备可认为从目标网络设备接收的PDCP序列号小于第一最后标识包的PDCP序列号的数据包和第一最后标识包中包含SDAP头,而从目标网络设备接收的PDCP序列号大于第一最后标识包的序列号的数据包中不包含SDAP头。另外一种第一最后标识包的实现方式还可以为,目标网络设备向终端设备发送的一个用于标识第一个不包含SDAP头的数据包,如果该包的PDCP序列号为N,则最后一个包含SDAP包头的数据包的PDCP序列号为N-1,即PDCP序列号小于N的数据包都需要进行移除SDAP头的处理,而PDCP序列号大于等于N的数据报都不包含SDAP头。
进而,针对终端设备识别出的包含SDAP头的数据包,例如,终端设备从目标网络设备接收的PDCP序列号小于第一最后标识包的PDCP序列号的数据包,终端设备可将数据包在PDCP实体中进行PDCP处理后,再送入终端设备中的SDAP实体移除SDAP头,然后再递交至上层,以使该数据包能够被正确接收和解码。应理解,SDAP实体可以直接将移除SDAP头的数据包递交至上层,也可以将移除SDAP头的数据包再发送回PDCP实体,如图5中所示,由PDCP实体根据数据包的PDCP序列号进行重排序后,再按序递交至上层。所述上层是指终端设备建立的与目标网络设备相匹配的协议栈中PDCP层的上层,即协议栈中位于PDCP层之上的其他协议层,简称为上层(upper layer)。
需注意,在现有技术中,当进行跨系统的切换时,终端设备接收到切换命令后,释放源系统的配置和协议栈(包括PDCP实体和SDAP层),应用目标系统的配置,建立与目标站对等的协议栈。在本申请包含的方法中,进行跨系统切换时,终端设备接收到切换命令后可以不释放与源站对等的PDCP实体和/或SDAP层。终端设备基于目标系统的配置,对PDCP实体和/或SDAP层进行处理后(例如对PDCP实体进行重建立,使用目标系统的安全配置),在接入目标站后继续使用该PDCP实体和/或SDAP层接收和处理数据包。可选的,当成功接收所有包含SDAP头的数据包(例如所有PDCP序列号小于第一最后标识包的PDCP序列号的数据包)并处理完成递交给上层后,终端设备释放SDAP层。
针对终端设备识别出的不包含SDAP头的数据包,例如,终端设备从目标网络设备接收的PDCP序列号大于第一最后标识包的PDCP序列号的数据包,终端设备可将数据包在PDCP实体中进行PDCP处理后,然后进行重排序,最后按序递交至上层。
本申请实施例中描述的最后标识包也可以称为最后标识(end mark/end marker)。应理解,上述第一最后标识包可以为目标网络设备向终端设备发送的源网络设备已进行PDCP处理但未接收到来自终端设备的确认响应的最后一个数据包,这里所提及的最后一个是指该数据包的PDCP序列号是最后一个;或者,该第一最后标识包也可以是目标网络设备向终端设备发送的一个用于标识结束的空的数据包。该第一最后标识包中可包含一个标志,例如包头中的某个域被设置为特殊值,用于指示该数据包为第一最后标识包,PDCP序列号在该数据包之前的其它数据包为包含SDAP头的数据包,若收到了该数据包,可认为目标网络设备已将包含SDAP头的数据包发送完毕。
在这一实现方式中,针对源网络设备已进行PDCP处理但未接收到来自终端设备的确认响应的数据包,由于源网络设备已为这部分数据包分配了对应的PDCP序列号,源网络设备也可以在向目标网络设备发送这部分数据包时,将每个数据包对应的PDCP序列号与数据包一起发送给目标网络设备。进而,再通过目标网络设备将数据包和数据包对应的PDCP序列号再发送给终端设备,如此,可使终端设备根据数据包对应的PDCP序列号, 判断该数据包中是否包含SDAP头。
源网络设备还可将目标网络设备可分配的第一个PDCP号发送给目标网络设备,以便目标网络设备为源网络设备未进行PDCP处理的数据包,以及目标网络设备从核心网接收的该终端设备的数据包分配对应的PDCP序列号。目标网络设备分配的PDCP序列号可以延续或继承源网络设备侧分配的PDCP序列号,因此,可以支持终端设备在跨系统切换过程中进行数据包的按序递交和去重处理,以及PDCP状态报告的上报等,从而提高终端设备的业务连续性。
可选的,所述源网络设备已进行PDCP处理但还未接收到来自终端设备的确认响应的数据包可以为PDCP SDU,该PDCP SDU中包括在进行PDCP处理前添加的SDAP头。如此,目标网络设备在接收到该PDCP SDU后,可使用自己的PDCP对该PDCP SDU进行继续处理,生成PDCP PDU,然后经RLC、MAC、PHY处理后,通过空中接口发送给终端设备。
可选的,针对源网络设备未进行PDCP处理的数据包,源网络设备可以将这部分数据包直接发送给目标网络设备,由目标网络设备对这部分数据包进行PDCP处理,生成PDCP PDU,然后经RLC、MAC、PHY处理后,通过空中接口发送给终端设备。应注意,由于源网络设备并没有为这部分数据包分配对应的PDCP序列号,源网络设备也不会将这部分数据包对应的PDCP序列号发送给目标网络设备。可选的,所述源网络设备未进行PDCP处理的数据包可以为源网络设备从核心网接收的新数据(即fresh data),这些新数据中没有经过源网络设备的SDAP层的处理,因此不包括SDAP头。
需要说明的是,针对上述图4及图5所示的两种可能的实现方式,源网络设备可通过DRB对应的下行数据转发隧道向目标网络设备发送所述终端设备未成功接收的至少一个数据包,例如,还未收到来自终端设备的确认响应的PDCP SDU或是从核心网接收的并映射到DRB的新数据(fresh data)。也就是说,源网络设备与目标网络设备之间的数据转发隧道可以是DRB粒度的,即每个需要进行数据转发的DRB可以有一个专属的下行数据转发隧道。
此外,源网络设备可从核心网接收用于指示核心网停止通过源网络设备向终端设备发送数据的第二最后标识包,并将该第二最后标识包发送给目标网络设备。由此,目标网络设备可根据第二最后标识包,获知源网络设备向目标网络设备转发的所述终端设备未成功接收的至少一个标识包已发送完毕,此后,目标网络设备可向终端设备发送自己从核心网接收的数据包。
该第二最后标识包可以为核心网向源网络设备发送的该终端设备的最后一个包含有效数据的数据包,或者核心网发送的一个用于标识结束的空的数据包。该第二最后标识包中可包含一个标志,例如包头中的某个域被设置为特殊值,用以指示核心网停止通过源网络设备向终端设备发送数据。该第二最后标识包也可以为DRB粒度的,即核心网可针对一个DRB发送一个第二最后标识包。
在另一种应用场景中,源网络设备可以为采用第二通信制式的通信系统中的网络设备,在该第二通信制式的通信系统中,网络设备与终端设备的空中接口协议栈不包括SDAP层的处理。目标网络设备可以为采用第一通信制式的通信系统中的网络设备,在该第一通信制式的通信系统中,网络设备与终端设备的空中接口协议栈包括SDAP层的处理。例如, 源网络设备可以为4G通信系统中的接入网设备,目标网络设备可以为5G通信系统中的接入网设备。
在这一场景下,如图6所示,一种可能的实现方式为,源网络设备可将终端设备未成功接收的至少一个数据包发送给目标网络设备,该终端设备未成功接收的至少一个数据包中可包括如下数据包中的一种或多种:源网络设备已进行PDCP处理但未接收到来自终端设备的确认响应的数据包,以及源网络设备未进行PDCP处理的数据包。但应注意,由于源网络设备的协议栈中不包括SDAP层的处理,因此这两种数据包中均不包括SDAP头。
目标网络设备可从源网络设备接收该终端设备未成功接收的至少一个数据包,以及从核心网接收该终端设备的数据包。在终端设备接入目标网络设备后,目标网络设备可将该终端设备未成功接收的至少一个数据包和第三最后标识包发送给终端设备,该第三最后标识包用于指示不包含SDAP头的数据包已发送完毕,或者从源网络设备接收的该终端设备未成功接收的至少一个数据包已发送完毕。
可选的,目标网络设备还可从源网络设备接收第二最后标识包,该第二最后标识包用于指示核心网停止通过源网络设备向终端设备发送数据包,目标网络设备可根据该第二最后标识包,确定源网络设备向目标网络设备转发的至少一个数据包已发送完毕,第二最后标识包的具体实施方式可参考上文中的描述,在此不再赘述。目标网络设备可在接收该第二最后标识包之后,向终端设备发送从核心网接收的数据包,但应注意,由于目标网络设备的协议栈中包括SDAP层的处理,因此目标网络设备向终端设备发送的从核心网接收的数据包中包括SDAP头。
如此,终端设备可根据该第三最后标识包,识别从目标网络设备接收的数据包中不包含SDAP头的数据包和/或包含SDAP头的数据包,并针对包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理。
具体的,终端设备可根据第三最后标识包的PDCP序列号,识别从目标网络设备接收的数据包中不包含SDAP头的数据包和/或包含SDAP头的数据包。例如,当第三最后标识包是目标网络设备向终端设备发送的一个用于标识结束的空的数据包时,终端设备可认为从目标网络设备接收的PDCP序列号小于第三最后标识包的PDCP序列号的数据包中不包含SDAP头,而从目标网络设备接收的PDCP序列号大于第三最后标识包的PDCP序列号的数据包中包含SDAP头。再例如,当第三最后标识包为目标网络设备向终端设备发送的源网络设备已进行PDCP处理但未接收到来自终端设备的确认响应的最后一个数据包时,终端设备可认为从目标网络设备接收的PDCP序列号小于第三最后标识包的PDCP序列号的数据包和第三最后标识包中不包含SDAP头,而从目标网络设备接收的PDCP序列号大于第三最后标识包的序列号的数据包中包含SDAP头。另外一种第三最后标识包的实现方式还可以为,目标网络设备向终端设备发送的一个用于标识第一个包含SDAP头的数据包,如果该包的PDCP序列号为N,则最后一个不包含SDAP包头的数据包的PDCP序列号为N-1,即PDCP序列号小于N的数据包都不包含SDAP头,而PDCP序列号大于等于N的数据包都需要进行移除SDAP头的处理。
进而,针对终端设备识别出的不包含SDAP头的数据包,例如,终端设备从目标网络设备接收的PDCP序列号小于第三最后标识包的PDCP序列号的数据包,终端设备可通过PDCP实体对数据包进行PDCP处理,然后经重复性检测后按序递交至上层。
针对终端设备识别出的包含SDAP头的数据包,例如,终端设备从目标网络设备接收 的PDCP序列号大于第三最后标识包的PDCP序列号的数据包,终端设备可将该数据包在PDCP实体中进行PDCP处理后,再将该数据包送入SDAP实体中移除SDAP头,然后经重复性检测后按序递交至上层。应理解,SDAP实体可以直接将移除SDAP头的数据包递交至上层,也可以将移除SDAP头的数据包再发送给PDCP实体,由PDCP实体根据数据包的PDCP序列号对数据包进行排序后,再将数据包按序递交给上层,或者该终端设备中也可以存在一个排序模块,SDAP实体可以将移除SDAP头的数据包发送给该排序模块,由该排序模块根据数据包的PDCP序列号对数据包进行排序后,然后按序递交给上层,该排序模块可以是PDCP功能的一部分,也可以是SDAP功能的一部分,也可以是协议栈中的一个新的协议层,本申请并不限定。
需要说明的是,第三最后标识包可以为目标网络设备向终端设备发送的源网络设备已进行PDCP处理但未接收到来自终端设备的确认响应的最后一个数据包,这里所提及的最后一个是指该数据包的PDCP序列号是最后一个;或者,该第三最后标识包也可以是目标网络设备向终端设备发送的一个用于标识结束的空的数据包。该第三最后标识包中可包含一个标志,例如包头中的某个域被设置为特殊值,用于指示该数据包为第三最后标识包,PDCP序列号在该数据包之前的其它数据包为不包含SDAP头的数据包,若收到了该数据包,可认为目标网络设备已将不包含SDAP头的数据包发送完毕。
可选的,该第三最后标识包还可以是第二最后标识包,即源网络设备从核心网接收的用于指示核心网停止通过源网络设备向终端设备发送数据的最后标识包,也就是说,第三最后标识包可以与第二最后标识包是同一数据包,该第二最后标识包的具体实施方式可参考上文中的描述,在此不再赘述。
可选的,所述源网络设备已进行PDCP处理但还未接收到来自终端设备的确认响应的数据包可以为PDCP SDU,该PDCP SDU中不包含SDAP头。如此,目标网络设备在接收到该PDCP SDU后,可使用自己的PDCP对该PDCP SDU进行继续处理,生成PDCP PDU,然后经RLC、MAC、PHY处理后,通过空中接口发送给终端设备。
针对源网络设备未进行PDCP处理的数据包,源网络设备可以将这部分数据包直接发送给目标网络设备,由目标网络设备对这部分数据包进行PDCP处理,生成PDCP PDU,然后经RLC、MAC、PHY处理后,通过空中接口发送给终端设备。应注意,由于源网络设备并没有为这部分数据包分配对应的PDCP序列号,源网络设备也不会将这部分数据包对应的PDCP序列号发送给目标网络设备。可选的,所述源网络设备未进行PDCP处理的数据包可以为源网络设备从核心网接收的新数据(即fresh data),这些新数据中也不包括SDAP头。
需要说明的是,针对图6中所示的实现方式,源网络设备也可以将已进行PDCP处理但还未接收到来自终端设备的确认响应的每个数据包对应的PDCP序列号与数据包一起发送给目标网络设备。进而,通过目标网络设备将数据包和数据包对应的PDCP序列号再发送给终端设备,如此可使终端设备根据数据包对应的PDCP序列号,判断该数据包中是否包含SDAP头。
源网络设备还可将目标网络设备可分配的第一个PDCP号发送给目标网络设备,以便目标网络设备为源网络设备未进行PDCP处理的数据包,以及目标网络设备从核心网接收的该终端设备的数据包分配对应的PDCP序列号。如此,目标网络设备分配的PDCP序列号可以延续或继承源网络设备侧分配的PDCP序列号,从而可以支持终端设备在跨系统切 换过程中进行数据包的按序递交和去重处理,以及PDCP状态报告的上报等,提高终端设备的业务连续性。
此外,源网络设备还可通过DRB对应的下行数据转发隧道向目标网络设备发送所述终端设备未成功接收的至少一个数据包,例如,未收到来自终端设备的确认响应的PDCP SDU或是从核心网接收的并映射到DRB的新数据(fresh data)。也就是说,源网络设备与目标网络设备之间的数据转发隧道可以是DRB粒度的,即每个需要进行数据转发的DRB可以有一个专属的下行数据转发隧道。
请参考图7,为本申请实施例提供的另一种切换方法的流程示意图,该方法具体包括如下步骤:
步骤S701、源网络设备向终端设备发送切换命令,该切换命令用于指示终端设备由源网络设备切换到目标网络设备。可选的,该切换命令中包含无中断指示。
本申请实施例中,在源网络设备向终端设备发送切换命令之前,终端设备可接入该源网络设备,并与源网络设备进行数据传输。
上述切换命令可以是切换命令消息或者信令,不作限定。
步骤S702、源网络设备继续向终端设备发送数据包,且源网络设备将终端设备的至少一个数据包发送给目标网络设备,所述终端设备的至少一个数据包为源网络设备已进行PDCP处理的数据包。可选的,该源网络设备已进行PDCP处理的数据包可以为PDCP SDU。
本申请实施例中,源网络设备可通过源网络设备中的第一PDCP实体继续向终端设备发送数据包,且源网络设备还可向目标网络设备发送通过该第一PDCP实体处理过的该终端设备的至少一个数据包。即,源网络设备可通过同一PDCP实体向终端设备和目标网络设备发送数据包。
应注意,本申请实施例对步骤S701和S702的执行顺序并不限定,即可以先执行S701再执行S702,也可以先执行S702再执行S701。
步骤S703、目标网络设备从源网络设备接收终端设备的至少一个数据包。
本申请实施例中,目标网络设备还可从核心网接收该终端设备的数据包。
步骤S704、终端设备从源网络设备接收切换命令。
步骤S705、终端设备继续通过第二PDCP实体从源网络设备接收数据包,并接入目标网络设备。
步骤S706、目标网络设备在终端设备接入目标网络设备后,将从源网络设备接收的该终端设备的至少一个数据包发送给终端设备。
步骤S707、终端设备通过该第二PDCP实体从目标网络设备接收至少一个数据包。
本申请实施例中,终端设备接收切换命令的无中断指示后,可通过终端设备中的第二PDCP实体继续从源网络设备接收数据包,在终端设备接入目标网络设备后,终端设备还可通过该第二PDCP实体从目标网络接收至少一个数据包。即在跨系统切换的过程中,终端设备可通过同一PDCP实体从源网络设备和目标网络设备接收数据包。
步骤S708、目标网络设备向源网络设备发送第一指示信息,该第一指示信息用于指示终端设备已成功接入目标网络设备。
可选的,目标网络设备还可向终端设备发送第二指示信息,该第二指示信息用于指示终端设备停止从源网络设备接收数据包。
步骤S709、源网络设备接收到用于指示终端设备已成功接入目标网络设备的第一指示信息后,停止向终端设备发送数据包。
本申请实施例中,源网络设备还可向目标网络设备发送最后标识包,该最后标识包用于指示向目标网络设备转发的该终端设备的至少一个数据包已发送完毕。该最后标识包可以是源网络设备从核心网接收的,用于指示核心网停止通过源网络设备向终端设备发送数据的数据包。如此,目标网络设备在接收该最后标识包之后,可向终端设备发送自己从核心网接收的数据包。可选的,目标网络设备还可向终端设备发送该最后标识包,用于表示从源网络设备接收的该终端设备的数据包已发送完毕。该最后标识包的具体实施方式可参考实施例一中的第二最后标识包,在此不再赘述。
采用上述技术方案,终端设备在接收到源网络设备发送的切换命令后,并不会立即断开与源网络设备之间的连接。相反,终端设备可继续从源网络设备接收数据包,并发起随机接入过程接入目标网络设备。终端设备可在成功接入目标网络设备后,再断开与源网络设备之间的连接。相应的,源网络设备可在确定终端设备成功接入目标网络设备后,再停止向终端设备发送数据包。如此,可使得跨系统切换过程中终端设备与网络设备之间的连接不中断,从而提高终端设备的业务连续性,改善用户体验。
在一种应用场景中,源网络设备可以为采用第一通信制式的通信系统中的网络设备,在该第一通信制式的通信系统中,网络设备和终端设备的空中接口协议栈均包括SDAP层的处理。目标网络设备可以为采用第二通信制式的通信系统中的网络设备,在该第二通信制式的通信系统中,网络设备和终端设备的空中接口协议栈均不包括SDAP层的处理。例如,源网络设备可以为5G通信系统中的接入网设备,目标网络设备可以为4G通信系统中的接入网设备。
为了避免源网络设备与目标网络设备对数据的处理不一致,而导致终端设备无法对数据进行正确接收和解码的问题,在第一种可能的实现方式中,如图8所示,一方面,源网络设备可继续向终端设备发送数据包,其中,源网络设备向终端设备发送的数据包中包括在PDCP处理前添加的SDAP头;另一方面,源网络设备可将终端设备的至少一个数据包中的SDAP头移除,然后将移除了SDAP头的数据包发送给目标网络设备,所述终端设备的至少一个数据包为源网络设备已进行PDCP处理的数据包,可选的,该至少一个数据包可以为PDCP SDU。
目标网络设备可从源网络设备接收终端设备的至少一个数据包,并在终端设备接入目标网络设备后,将从源网络设备接收的该终端设备的至少一个数据包发送给终端设备。可选的,目标网络设备还可从核心网接收该终端设备的数据包,并将从核心网接收的数据包发送给终端设备。可以理解,由于目标网络设备的协议栈中不包括SDAP层的处理,且目标网络设备从源网络设备接收的数据包已移除了在进行PDCP处理前添加的SDAP头,因此,在这一场景下,目标网络设备向终端设备发送的数据包中均不包括SDAP头。
进而,终端设备可从源网络设备和目标网络设备接收数据包,并采用同一PDCP实体(即第二PDCP实体)对从源网络设备接收的数据包和从目标网络设备接收的数据包进行处理。可选的,该第二PDCP实体对数据包进行PDCP处理后,还可对从源网络设备接收的数据包以及从目标网络设备接收的数据包进行统一的排序和去重处理(即重复性检测),从而实现跨系统切换过程中数据的无重复和按序递交。
具体的,终端设备中的第二PDCP实体可根据接收数据的空口的不同,对从源网络设 备接收的数据包和从目标网络设备接收的数据包进行分别处理。对于从源网络设备接收的数据包,终端设备可将该数据包送入第二PDCP实体进行PDCP处理,第二PDCP实体可将经过PDCP处理的数据包发送至终端设备中的SDAP实体去除SDAP头。可选的,SDAP实体可将去除SDAP头的数据包再发送回第二PDCP实体进行去重处理,最后第二PDCP实体可将经过去重处理后的数据包按序递交给上层。
对于从目标网络设备接收的数据包,终端设备可将该数据包送入第二PDCP实体进行PDCP处理,由于不需要去掉SDAP头,该第二PDCP实体可将经过PDCP处理后的数据包进行重排序和去重处理,然后将经过去重处理后的数据包按序递交给上层。
可选的,该第二PDCP实体为动态双协议栈(dual active protocol stack,DAPS)的结构,该第二PDCP实体中包括两个处理单元,每个处理单元分别与源网络设备和目标网络设备的安全配置相对应,其中第一处理单元与源网络设备的安全配置相对应,也可以理解为具有与源网络设备匹配的PDCP层的功能,第二处理单元与目标网络设备的安全配置相对应,也可以理解为具有与目标网络设备匹配的PDCP层的功能。如此,第二PDCP实体可通过第一处理单元对从源网络设备接收的数据包进行PDCP处理,通过第二处理单元对从目标网络设备接收的数据包进行PDCP处理。
需要说明的是,本申请实施例中所提及的第一处理单元和第二处理单元均可包括一个或多个模块,例如具有解密、完整性验证、排序、头压缩等功能的模块。而且,第一处理单元与第二处理单元的功能可以相同或不相同,也就是说,源网络设备与目标网络设备可以采用相同或不同的PDCP实现,本申请并不限定。
在第二种可能的实现方式中,如图9所示,源网络设备将终端设备的至少一个数据包发送给目标网络设备之前,也可以不移除这部分数据包中的SDAP头。而是由终端设备自行识别从目标网络设备接收的包含SDAP头的数据包和不包含SDAP头的数据包,进而对接收的包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理。
具体的,一方面,源网络设备可继续向终端设备发送数据包,另一方面,源网络设备可将该终端设备的至少一个数据包发送给目标网络设备,该至少一个数据包可以为源网络设备已进行PDCP处理的数据包,例如PDCP PDU。但应注意,源网络设备向终端设备发送的数据包以及源网络设备向目标网络设备发送的数据包中均包括在进行PDCP处理前添加的SDAP头。
目标网络设备可从源网络设备接收终端设备的至少一个数据包,并在终端设备接入目标网络设备后,将从源网络设备接收的该终端设备的至少一个数据包发送给终端设备,该至少一个数据包中包括SDAP头。可选的,目标网络设备还可从核心网接收该终端设备的数据包,并将从核心网接收的数据包发送给终端设备。可以理解,由于目标网络设备的协议栈中不包括SDAP层的处理,且源网络设备向目标网络设备发送已进行PDCP处理的数据包时未移除在进行PDCP处理前添加的SDAP头,因此,目标网络设备向终端设备发送的从核心网接收的数据包中不包含SDAP头,但是目标网络设备向终端设备发送的从源网络设备接收的数据包中包含SDAP头。
为了便于终端设备识别从目标网络设备接收的包含SDAP头的数据包和/或不包含SDAP头的数据包,目标网络设备可将最后标识包发送给终端设备,该最后标识包用于指示从源网络设备接收的数据包已发送完毕,或者也可以理解为包含SDAP头的数据包已发送完毕。可选的,目标网络设备可在向终端设备发送从源网络设备接收的至少一个数据包 之后,且向终端设备发送从核心网接收的数据包之前,发送该最后标识包。该最后标识包还可以为目标网络设备从源网络设备接收的用于指示向目标网络设备转发的该终端设备的至少一个数据包已发送完毕的数据包。即,目标网络设备可从源网络设备接收该最后标识包后,向终端设备转发该最后标识包,在此之后,目标网络设备可向终端设备发送从核心网接收的数据包。
类似的,终端设备可从源网络设备和目标网络设备接收数据包,并采用同一PDCP实体对从源网络设备接收的数据包和从目标网络设备接收的数据包进行处理。终端设备还可从目标网络设备接收最后标识包。
具体的,终端设备中的第二PDCP实体可根据接收数据的空口的不同,对从源网络设备接收的数据包和从目标网络设备接收的数据包进行分别处理。对于从源网络设备接收的数据包,终端设备可将该数据包送入第二PDCP实体进行PDCP处理,第二PDCP实体可将经过PDCP处理的数据包发送至终端设备中的SDAP实体去除SDAP头。SDAP实体可将去除SDAP头的数据包再发送回第二PDCP实体进行去重处理,最后第二PDCP实体可将经过去重处理后的数据包按序递交给上层。
对于从目标网络设备接收的数据包,终端设备可根据从目标网络设备接收的最后标识包,识别从目标网络设备接收的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据包,并针对包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理。即,包含SDAP头的数据包在进行PDCP处理后,还需要在SDAP实体去除SDAP头之后,才可递交至上层,而不包含SDAP头的数据包在进行PDCP处理后,无需去除SDAP头。
例如,终端设备可认为从目标网络设备接收的PDCP序列号小于最后标识包的PDCP序列号的数据包为包含SDAP头的数据包,而从目标网络设备接收的PDCP序列号大于最后标识包的PDCP序列号的数据包为不包含SDAP头的数据包。如此,终端设备可将从目标网络设备接收的PDCP序列号小于最后标识包的PDCP序列号的数据包,送入第二PDCP实体中进行PDCP处理,然后再送入SDAP头中移除SDAP头,最后返回第二PDCP实体进行重排序和去重处理后,按序递交给上层。相应的,终端设备可将从目标网络设备接收的PDCP序列号大于最后标识包的PDCP序列号的数据包,送入第二PDCP实体进行PDCP处理后,直接进入重排序和去重处理的流程,然后按序递交给上层,而无需发送到SDAP实体中去除SDAP头。
可选的,该第二PDCP实体也可以为DAPS的结构,第二PDCP实体的具体实施方式可参考该场景下第一种实现方式中的介绍,这里不再赘述。
需要说明的是,针对该场景下上述两种可能的实现方式,源网络设备还可将已进行PDCP处理的数据包的每个数据包对应的PDCP序列号与数据包一起发送给目标网络设备。此外,源网络设备还可将目标网络设备分配的第一个PDCP序列号发送给目标网络设备,以使目标网络设备为从核心网接收的数据包分配PDCP序列号,从而实现跨系统切换过程中源侧与目标侧的PDCP序列号的继承。
源网络设备可通过DRB对应的下行数据转发隧道向目标网络设备发送所述终端设备的至少一个数据包,例如,已进行PDCP处理的PDCP SDU或是新从核心网接收的并映射到DRB的fresh data。也就是说,源网络设备与目标网络设备之间的数据转发隧道可以是DRB粒度的,即每个需要进行数据转发的DRB可以有一个专属的下行数据转发隧道。
在另一种应用场景中,源网络设备可以为采用第二通信制式的通信系统中的网络设备, 在该第二通信制式的通信系统中,网络设备与终端设备之间的空中接口协议栈不包括SDAP层的处理。目标网络设备可以为采用第一通信制式的通信系统中的网络设备,在该第一通信制式的通信系统中,网络设备与终端设备之间的空中接口协议栈包括SDAP层的处理。例如,源网络设备可以为4G通信系统中的接入网设备,目标网络设备可以为5G通信系统中的接入网设备。
在这一场景下,一方面,源网络设备可继续向终端设备发送数据包,另一方面,源网络设备可将该终端设备的至少一个数据包发送给目标网络设备,该至少一个数据包可以为源网络设备已进行PDCP处理的数据包,例如PDCP SDU。但应注意,由于源网络设备的协议栈中不包括SDAP层的处理,源网络设备向终端设备发送的数据包以及源网络设备向目标网络设备发送的数据包中均不包括SDAP头。
与实施例一类似,在第一种可能的实现方式中,目标网络设备可从源网络设备接收该终端设备的至少一个数据包,并将该至少一个数据包先经过SDAP实体的处理,添加SDAP头后,送入PDCP实体中进行PDCP处理。然后,再经过RLC、MAC、PHY的处理后,目标网络设备可将添加SDAP头后的数据包通过空中接口发送给终端设备。目标网络设备还可从核心网接收该终端设备的数据包,并在经过SDAP实体、PDCP实体的处理,以及RLC、MAC、PHY等处理后,将数据包发送给终端设备。可以看出,在这一实现方式中,目标网络设备向终端设备发送的数据包中都包括SDAP头。
进而,终端设备可从源网络设备和目标网络设备接收数据包,并采用同一PDCP实体(即第二PDCP实体)对从源网络设备接收的数据包和从目标网络设备接收的数据包进行处理。可选的,该第二PDCP实体对数据包进行PDCP处理后,还可对从源网络设备接收的数据包以及从目标网络设备接收的数据包进行统一的排序和去重处理。
具体的,终端设备可根据接收空口的不同,对从源网络设备接收的数据包和从目标网络设备接收的数据包进行分别处理。对于从源网络设备接收的数据包,终端设备可将该数据包送入第二PDCP实体进行PDCP处理后,递交至上层。可选的,可以将进行PDCP处理后的数据包再经过重排序和去重处理后,按序递交至上层。
对于从目标网络设备接收的数据包,终端设备可将该数据包送入第二PDCP实体进行PDCP处理,然后送入SDAP实体中进行移除SDAP头后,递交至上层。可选的,可以将移除SDAP头后的数据包再经过重排序和去重处理后,按序递交至上层。
如此,可使终端设备接入目标网络设备后,能够对从源网络设备接收的数据包以及从目标网络设备接收的数据包进行正确的接收和解码。
在第二种可能的实现方式中,目标网络设备可从源网络设备接收该终端设备的至少一个数据包,并将该至少一个数据包进行PDCP处理,以及RLC、MAC、PHY等处理后,通过空中接口发送给终端设备。目标网络设备还可从核心网接收该终端设备的数据包,并在经过SDAP实体、PDCP实体的处理,以及RLC、MAC、PHY的处理之后,将数据包发送给终端设备。应注意,由于目标网络设备没有对从源网络设备接收的数据包添加SDAP头后再发送给终端设备,因此,这里目标网络设备向终端设备发送的从源网络设备接收的数据包中不包含SDAP头,而目标网络设备向终端设备发送的从核心网接收的数据包中包含SDAP头。
为了使终端设备识别从目标网络设备接收的包含SDAP头的数据包和/或不包含SDAP头的数据包,目标网络设备还可向终端设备发送最后标识包,该最后标识包用于指示从源 网络设备接收的数据包已发送完毕,或者也可以理解为不包含SDAP头的数据包已发送完毕。可选的,目标网络设备可在向终端设备发送从源网络设备接收的至少一个数据包之后,且向终端设备发送从核心网接收的数据包之前,发送该最后标识包。可选的,该最后标识包还可以为目标网络设备从源网络设备接收的用于指示向目标网络设备转发的该终端设备的至少一个数据包已发送完毕的数据包。即,目标网络设备可从源网络设备接收该最后标识包后,向终端设备转发该最后标识包,在此之后,目标网络设备可向终端设备发送从核心网接收的数据包。
进而,终端设备可从源网络设备和目标网络设备接收数据包,并采用同一PDCP实体对从源网络设备接收的数据包和从目标网络设备接收的数据包进行处理。终端设备还可从目标网络设备接收最后标识包。
具体的,终端设备中的第二PDCP实体可根据接收数据的空口的不同,对从源网络设备接收的数据包和从目标网络设备接收的数据包进行分别处理。对于从源网络设备接收的数据包,终端设备可将该数据包送入第二PDCP实体进行PDCP处理,由于不需要去除SDAP头,经过PDCP处理后,第二PDCP实体可继续对该数据包进行重排序和去重处理,然后将去重处理后的数据包按序递交给上层。
对于从目标网络设备接收的数据包,终端设备可根据从目标网络设备接收的最后标识包,识别从目标网络设备接收的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据包,并针对包含SDAP头的数据包和不包含SDAP头的数据包进行分别处理。即,包含SDAP头的数据包在进行PDCP处理后,还需要在SDAP实体去除SDAP头,才可递交至上层,而不包含SDAP头的数据包在进行PDCP处理后,无需去除SDAP头。
例如,终端设备可认为从目标网络设备接收的PDCP序列号小于最后标识包的PDCP序列号的数据包为不包含SDAP头的数据包,而从目标网络设备接收的PDCP序列号大于最后标识包的PDCP序列号的数据包为包含SDAP头的数据包。如此,终端设备可将从目标网络设备接收的PDCP序列号小于最后标识包的PDCP序列号的数据包,送入第二PDCP实体中进行PDCP处理,然后进入重排序和去重处理的流程,再按序递交给上层,而无需发送到SDAP实体中去除SDAP头。相应的,终端设备可将从目标网络设备接收的PDCP序列号大于最后标识包的PDCP序列号的数据包,送入第二PDCP实体中进行PDCP处理,然后再送入SDAP头中移除SDAP头,最后返回第二PDCP实体进行重排序和去重处理后,再按序递交给上层。
需要说明的是,针对该场景下两种可能的实现方式,终端设备中的第二PDCP实体也可以为DAPS的结构,即第二PDCP实体中包括第一处理单元和第二处理单元,其中,第一处理单元与源网络设备的安全配置相对应,第二处理网元与目标网络设备的安全配置相对应,第二PDCP实体通过第一处理单元对从源网络设备接收的数据包进行PDCP处理,通过第二处理单元对从目标网络设备接收的数据包进行PDCP处理。第一处理单元和第二处理单元的具体实施方式请参考上文中的描述,在此不再赘述。
源网络设备还可将已进行PDCP处理的数据包的每个数据包对应的PDCP序列号与数据包一起发送给目标网络设备。此外,源网络设备还可将目标网络设备分配的第一个PDCP序列号发送给目标网络设备,以使目标网络设备为从核心网接收的数据包分配PDCP序列号,从而实现跨系统切换过程中源侧与目标侧的PDCP序列号的继承。
此外,源网络设备可通过DRB对应的下行数据转发隧道向目标网络设备发送所述终 端设备的至少一个数据包,例如,已进行PDCP处理的PDCP SDU或是新从核心网接收的并映射到DRB的fresh data。也就是说,源网络设备与目标网络设备之间的数据转发隧道可以是DRB粒度的,即每个需要进行数据转发的DRB可以有一个专属的下行数据转发隧道。
本申请实施例提供一种通信装置,请参阅图10,为本申请实施例提供的一种通信装置的结构示意图,该通信装置1000包括:收发模块1010和处理模块1020。该通信装置可用于实现上述任一方法实施例中涉及源网络设备或目标网络设备的功能。例如,该通信装置可以为网络设备或网络设备中包含的芯片。
当该通信装置作为源网络设备,执行图2中所示的方法实施例时,收发模块1010,用于向终端设备发送切换命令,该切换命令用于指示终端设备由该通信装置切换到目标网络设备,该通信装置与目标网络设备采用不同的无线接入技术;收发模块1010还用于将终端设备未成功接收的至少一个数据包发送给目标网络设备,该终端设备未成功接收的至少一个数据包包括下列数据包中的一种或多种:已进行分组数据汇聚协议PDCP处理但未接收到来自终端设备的确认响应的数据包,以及未进行PDCP处理的数据包。
在一种可能的设计中,当终端设备未成功接收的至少一个数据包包括已进行PDCP处理但未接收到来自终端设备的确认响应的数据包,处理模块1020,用于该数据包中的服务数据适配协议SDAP头移除,然后通过收发模块1010将移除SDAP头后的数据包发送给目标网络设备。
在一种可能的设计中,当终端设备未成功接收的至少一个数据包包括未进行PDCP处理的数据包,处理模块1020,用于将该数据包映射到对应的DRB,然后通过收发模块1010将映射到对应的DRB的数据包发送给目标网络设备,该数据包不包含SDAP头。
在一种可能的设计中,当终端设备未成功接收的至少一个数据包包括已进行PDCP处理但未接收到来自终端设备的确认响应的数据包,收发模块1010用于将该数据包发送给目标网络设备,该数据包中包括SDAP头。
在一种可能的设计中,收发模块1010还用于将已进行PDCP处理但未接收到来自终端设备的确认响应的数据包对应的PDCP序列号发送给目标网络设备;和/或,收发模块1010还用于将目标网络设备可分配的第一个PDCP序列号发送给目标网络设备。
当该通信装置作为目标网络设备,执行图2中所示的方法实施例时,收发模块1010,用于从源网络设备接收终端设备未成功接收的至少一个数据包,该终端设备未成功接收的至少一个数据包包括下列数据包中的一种或多种:源网络设备已进行分组数据汇聚协议PDCP处理但未接收到来自终端设备的确认响应的数据包,以及源网络设备未进行PDCP处理的数据包,源网络设备与该通信装置采用不同的无线接入技术,该切换命令用于指示终端设备由源网络设备切换到该通信装置;处理模块1020,用于在终端设备接入该通信装置后,通过收发模块1010将述终端设备未成功接收的至少一个数据包发送给终端设备。
在一种可能的设计中,该通信装置从源网络设备接收的源网络设备已进行PDCP处理的数据包但未接收到来自终端设备的确认响应的数据包中不包含服务数据适配SDAP头。
在一种可能的设计中,该通信装置从源网络设备接收的源网络设备已进行PDCP处理但未接收到来自终端设备的确认响应的数据包中包含SDAP头;收发模块1010,还用于向终端设备发送最后标识包,该最后标识包用于指示包含SDAP头的数据包发送完毕。
在一种可能的设计中,收发模块1010,还用于从源网络设备接收源网络设备已进行PDCP处理但未接收到来自终端设备的确认响应的数据包对应的PDCP序列号;和/或,收发模块1010,从源网络设备接收该通信装置可分配的第一个PDCP序列号。
该通信装置中涉及的处理模块1020可以由处理器或处理器相关电路组件实现,收发模块1010可以由收发器或收发器相关电路组件实现。该通信装置中的各个模块的操作和/或功能分别为了实现图2或图7中所示方法的相应流程,为了简洁,在此不再赘述。
请参阅图11,为本申请实施例中提供的一种通信装置的另一结构示意图。该通信装置1100可具体为一种网络设备,例如基站,用于实现上述任一方法实施例中涉及源网络设备或目标网络设备的功能。
该网络设备包括:一个或多个射频单元,如远端射频单元(remote radio unit,RRU)1101和一个或多个基带单元(baseband unit,BBU)(也可称为数字单元,digital unit,DU)1102。所述RRU 1101可以称为收发单元、收发机、收发电路、或者收发器等等,其可以包括至少一个天线11011和射频单元11012。所述RRU 1101部分主要用于射频信号的收发以及射频信号与基带信号的转换。所述BBU 1102部分主要用于进行基带处理,对基站进行控制等。所述RRU 1101与BBU 1102可以是物理上设置在一起,也可以物理上分离设置的,即分布式基站。
所述BBU 11202为基站的控制中心,也可以称为处理单元,主要用于完成基带处理功能,如信道编码,复用,调制,扩频等等。例如所述BBU(处理单元)1102可以用于控制基站执行上述方法实施例中关于源网络设备或目标网络设备的操作流程。
在一个示例中,所述BBU 1102可以由一个或多个单板构成,多个单板可以共同支持单一接入指示的无线接入网(如LTE网),也可以分别支持不同接入制式的无线接入网(如LTE网,5G网或其他网)。所述BBU 1102还可以包括存储器11021和处理器11022,所述存储器11021用于存储必要的指令和数据。所述处理器11022用于控制基站进行必要的动作,例如用于控制基站执行上述方法实施例中发送操作。所述存储器11021和处理器11022可以服务于一个或多个单板。也就是说,可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
本申请实施例提供另一种通信装置,请参阅图12,为本申请实施例提供的另一种通信装置的结构示意图,该通信装置1200包括:收发模块1210和处理模块1220。该通信装置可用于实现上述任一方法实施例中涉及终端设备的功能。例如,该通信装置可以是终端设备,例如手持终端设备或车载终端设备;该通信装置还可以是终端设备中包括的芯片,或者包括终端设备的装置,如各种类型的车辆等。
当该通信装置作为终端设备,执行图2中所示的方法实施例时,收发模块1210,用于从源网络设备接收切换命令,该切换命令用于指示该通信装置由源网络设备切换到目标网络设备,该源网络设备与目标网络设备采用不同的无线接入技术;处理模块1220,用于接入目标网络设备,通过收发模块1210从目标网络设备接收最后标识包;处理模块1220,还用于根据最后标识包,识别从目标网络设备接收的数据包中包含服务数据适配协议SDAP头的数据包和/或不包含SDAP头的数据包。
在一种可能的设计中,处理模块1220具体用于根据最后标识包对应的分组数据汇聚协议PDCP序列号,识别从目标网络设备接收到的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据包。
在一种可能的设计中,当处理模块1220识别出从目标网络设备接收的数据包中包含SDAP头,处理模块还用于,通过PDCP实体可对该数据包进行PDCP处理,然后将该数据包发送给SDAP实体,由SDAP实体将该数据包中的SDAP头移除。当处理模块1220识别出从目标网络设备接收的数据包中不包含SDAP头,处理模块还用于,通过PDCP实体可对该数据包进行PDCP处理,但是在对该数据包进行PDCP处理之后,不再将该数据包再发送给SDAP实体去除SDAP头。
在一种可能的设计中,处理模块1220还用于,通过SDAP实体将移除SDAP头的数据包发送至上层;或者,处理模块1220还用于,通过PDCP实体从SDAP实体接收移除SDAP头之后的数据包,然后按照数据包的PDCP序列号对数据包进行排序后,将数据包按序发送至上层。
应理解,该通信装置中涉及的处理模块1220可以由处理器或处理器相关电路组件实现,收发模块1210可以由收发器或收发器相关电路组件实现。该通信装置中的各个模块的操作和/或功能分别为了实现图2或图7中所示方法的相应流程,为了简洁,在此不再赘述。
请参阅图13,为本申请实施例中提供的一种通信装置的另一结构示意图。该通信装置具体可为一种终端设备。便于理解和图示方便,在图13中,终端设备以手机作为例子。如图13所示,终端设备包括处理器,还可以包括存储器,当然,也还可以包括射频电路、天线以及输入输出装置等。处理器主要用于对通信协议以及通信数据进行处理,以及对终端设备进行控制,执行软件程序,处理软件程序的数据等。存储器主要用于存储软件程序和数据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置,例如触摸屏、显示屏,键盘等主要用于接收用户输入的数据以及对用户输出数据。需要说明的是,有些种类的终端设备可以不具有输入输出装置。
当需要发送数据时,处理器对待发送的数据进行基带处理后,输出基带信号至射频电路,射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时,射频电路通过天线接收到射频信号,将射频信号转换为基带信号,并将基带信号输出至处理器,处理器将基带信号转换为数据并对该数据进行处理。为便于说明,图13中仅示出了一个存储器和处理器。在实际的终端设备产品中,可以存在一个或多个处理器和一个或多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以是独立于处理器设置,也可以是与处理器集成在一起,本申请实施例对此不做限制。
在本申请实施例中,可以将具有收发功能的天线和射频电路视为终端设备的收发单元,将具有处理功能的处理器视为终端设备的处理单元。如图13所示,终端设备包括收发单元1310和处理单元1320。收发单元也可以称为收发器、收发机、收发装置等。处理单元也可以称为处理器,处理单板,处理模块、处理装置等。可选的,可以将收发单元1310中用于实现接收功能的器件视为接收单元,将收发单元1310中用于实现发送功能的器件视为发送单元,即收发单元1310包括接收单元和发送单元。收发单元有时也可以称为收发机、收发器、或收发电路等。接收单元有时也可以称为接收机、接收器、或接收电路等。发送单元有时也可以称为发射机、发射器或者发射电路等。应理解,收发单元1310用于执行上述方法实施例中终端设备侧的发送操作和接收操作,处理单元1320用于执行上述 方法实施例中终端设备上除了收发操作之外的其他操作。
本申请实施例还提供一种芯片系统,包括:处理器,所述处理器与存储器耦合,所述存储器用于存储程序或指令,当所述程序或指令被所述处理器执行时,使得该芯片系统实现上述任一方法实施例中的方法。
可选地,该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时,该处理器可以是逻辑电路、集成电路等。当通过软件实现时,该处理器可以是一个通用处理器,通过读取存储器中存储的软件代码来实现。
可选地,该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起,也可以和处理器分离设置,本申请并不限定。示例性的,存储器可以是非瞬时性处理器,例如只读存储器ROM,其可以与处理器集成在同一块芯片上,也可以分别设置在不同的芯片上,本申请对存储器的类型,以及存储器与处理器的设置方式不作具体限定。
示例性的,该芯片系统可以是现场可编程门阵列(field programmable gate array,FPGA),可以是专用集成芯片(application specific integrated circuit,ASIC),还可以是系统芯片(system on chip,SoC),还可以是中央处理器(central processor unit,CPU),还可以是网络处理器(network processor,NP),还可以是数字信号处理电路(digital signal processor,DSP),还可以是微控制器(micro controller unit,MCU),还可以是可编程控制器(programmable logic device,PLD)或其他集成芯片。
应理解,上述方法实施例中的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例还提供一种计算机可读存储介质,所述计算机存储介质中存储有计算机可读指令,当计算机读取并执行所述计算机可读指令时,使得计算机执行上述任一方法实施例中的方法。
本申请实施例还提供一种计算机程序产品,当计算机读取并执行所述计算机程序产品时,使得计算机执行上述任一方法实施例中的方法。
本申请实施例还提供一种通信系统,该通信系统包括源网络设备、目标网络设备和至少一个上述各方法实施例中所述的终端设备。可选的,该通信系统中还可包括核心网设备。
应理解,本申请实施例中提及的处理器可以是中央处理单元(central processing unit,CPU),还可以是其他通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现成可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解,本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存 取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。
需要说明的是,当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时,存储器(存储模块)集成在处理器中。
应注意,本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本发明实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应所述以权利要求的保护范围为准。

Claims (42)

  1. 一种切换方法,其特征在于,所述方法包括:
    源网络设备向终端设备发送切换命令,所述切换命令用于指示所述终端设备由所述源网络设备切换到目标网络设备,所述源网络设备与所述目标网络设备采用不同的无线接入技术;
    所述源网络设备将所述终端设备未成功接收的至少一个数据包发送给所述目标网络设备,所述终端设备未成功接收的至少一个数据包包括下列数据包中的一种或多种:已进行分组数据汇聚协议PDCP处理但未接收到来自所述终端设备的确认响应的数据包,以及未进行PDCP处理的数据包。
  2. 根据权利要求1所述的方法,其特征在于,所述源网络设备与所述目标网络设备采用不同的无线接入技术,包括:
    所述终端设备与所述源网络设备对应的协议栈中包括服务数据适配协议SDAP层的处理,而所述终端设备与所述目标网络设备对应的协议栈中不包括SDAP层的处理。
  3. 根据权利要求1或2所述的方法,其特征在于,当所述终端设备未成功接收的至少一个数据包包括所述已进行PDCP处理但未接收到来自所述终端设备的确认响应的数据包,所述方法还包括:
    所述源网络设备将所述数据包中的SDAP头移除;
    所述源网络设备将所述终端设备未成功接收的至少一个数据包发送给所述目标网络设备,包括:
    所述源网络设备将移除SDAP头后的所述数据包发送给所述目标网络设备。
  4. 根据权利要求1至3中任一项所述的方法,其特征在于,当所述终端设备未成功接收的至少一个数据包包括所述未进行PDCP处理的数据包,所述方法还包括:
    所述源网络设备将所述数据包映射到对应的数据无线承载DRB;
    所述源网络设备将所述终端设备未成功接收的至少一个数据包发送给所述目标网络设备,包括:
    所述源网络设备将映射到对应的DRB的所述数据包发送给所述目标网络设备,所述数据包不包含SDAP头。
  5. 根据权利要求1或2所述的方法,其特征在于,当所述终端设备未成功接收的至少一个数据包包括所述已进行PDCP处理但未接收到来自所述终端设备的确认响应的数据包,所述源网络设备将所述终端设备未成功接收的至少一个数据包发送给所述目标网络设备,包括:
    所述源网络设备将所述数据包发送给所述目标网络设备,所述数据包中包括SDAP头。
  6. 根据权利要求1至5中任一项所述的方法,其特征在于,所述方法还包括:
    所述源网络设备将所述已进行PDCP处理但未接收到来自所述终端设备的确认响应的数据包对应的PDCP序列号发送给所述目标网络设备;和/或,
    所述源网络设备将所述目标网络设备可分配的第一个PDCP序列号发送给所述目标网络设备。
  7. 一种切换方法,其特征在于,所述方法包括:
    目标网络设备从源网络设备接收终端设备未成功接收的至少一个数据包,所述终端设 备未成功接收的至少一个数据包包括下列数据包中的一种或多种:所述源网络设备已进行分组数据汇聚协议PDCP处理但未接收到来自所述终端设备的确认响应的数据包,以及所述源网络设备未进行PDCP处理的数据包,所述源网络设备与所述目标网络设备采用不同的无线接入技术;
    所述目标网络设备在所述终端设备接入所述目标网络设备后,将所述终端设备未成功接收的至少一个数据包发送给所述终端设备。
  8. 根据权利要求7所述的方法,其特征在于,所述源网络设备与所述目标网络设备采用不同的无线接入技术,包括:
    所述终端设备与所述源网络设备对应的协议栈中包括服务数据适配协议SDAP层的处理,而所述终端设备与所述目标网络设备对应的协议栈中不包括SDAP层的处理。
  9. 根据权利要求7或8所述的方法,其特征在于,所述目标网络设备从所述源网络设备接收的所述源网络设备已进行PDCP处理的数据包但未接收到来自所述终端设备的确认响应的数据包中不包含SDAP头。
  10. 根据权利要求7或8所述的方法,其特征在于,目标网络设备从所述源网络设备接收的所述源网络设备已进行PDCP处理但未接收到来自所述终端设备的确认响应的数据包中包含SDAP头;
    所述方法还包括:
    所述目标网络设备向所述终端设备发送最后标识包,所述最后标识包用于指示包含SDAP头的数据包发送完毕。
  11. 根据权利要求7至10中任一项所述的方法,其特征在于,所述方法还包括:
    所述目标网络设备从所述源网络设备接收所述源网络设备已进行PDCP处理但未接收到来自所述终端设备的确认响应的数据包对应的PDCP序列号;和/或,
    所述目标网络设备从所述源网络设备接收所述目标网络设备可分配的第一个PDCP序列号。
  12. 一种切换方法,其特征在于,所述方法包括:
    终端设备从源网络设备接收切换命令,所述切换命令用于指示所述终端设备由所述源网络设备切换到目标网络设备,所述源网络设备与所述目标网络设备采用不同的无线接入技术;
    所述终端设备接入所述目标网络设备,从所述目标网络设备接收最后标识包;
    所述终端设备根据所述最后标识包,识别从所述目标网络设备接收到的数据包中包含服务数据适配协议SDAP头的数据包和/或不包含SDAP头的数据包。
  13. 根据权利要求12所述的方法,其特征在于,所述源网络设备与所述目标网络设备采用不同的无线接入技术,包括:
    所述终端设备与所述源网络设备对应的协议栈中包括SDAP层的处理,而所述终端设备与所述目标网络设备对应的协议栈中不包括SDAP层的处理。
  14. 根据权利要求12或13所述的方法,其特征在于,所述终端设备根据所述最后标识包,识别从所述目标网络设备接收到的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据包,包括:
    所述终端设备根据所述第一最后标识包对应的分组数据汇聚协议PDCP序列号,识别从所述目标网络设备接收到的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据 包。
  15. 根据权利要求12至14中任一项所述的方法,其特征在于,当所述终端设备识别出从所述目标网络设备接收的数据包中包含SDAP头,所述方法还包括:
    所述终端设备中的PDCP实体对所述数据包进行PDCP处理后,将所述数据包发送给所述终端设备中的SDAP实体,所述SDAP实体将所述数据包中的SDAP头移除。
  16. 根据权利要求15所述的方法,其特征在于,所述方法还包括:
    所述SDAP实体将所述移除SDAP头之后的数据包发送至上层;或者,
    所述PDCP实体从所述SDAP实体接收所述移除SDAP头后的数据包,按照数据包的PDCP序列号对数据包进行排序后,将数据包按序发送至上层。
  17. 一种切换方法,其特征在于,所述方法包括:
    源网络设备向终端设备发送切换命令,所述切换命令指示所述终端设备从所述源网络设备切换到目标网络设备,所述源网络设备与所述目标网络设备采用不同的无线接入技术;
    所述源网络设备继续向所述终端设备发送数据包,且所述源网络设备将所述终端设备的至少一个数据包发送给所述目标网络设备,所述终端设备的至少一个数据包为所述源网络设备已进行分组数据汇聚协议PDCP处理的数据包;
    所述源网络设备接收到用于指示所述终端设备已成功接入所述目标网络设备的第一指示信息后,停止向所述终端设备发送数据包。
  18. 根据权利要求17所述的方法,其特征在于,所述源网络设备与所述目标网络设备采用不同的无线接入技术,包括:
    所述终端设备与所述源网络设备对应的协议栈中包括服务数据适配协议SDAP层的处理,而所述终端设备与所述目标网络设备对应的协议栈中不包括SDAP层的处理。
  19. 根据权利要求17或18所述的方法,其特征在于,所述方法包括:
    所述源网络设备通过PDCP实体继续向所述终端设备发送数据包;
    所述源网络设备将经过所述PDCP实体处理的所述终端设备的至少一个数据包发送给所述目标网络设备。
  20. 根据权利要求17至19中任一项所述的方法,其特征在于,所述方法还包括:
    所述源网络设备将所述终端设备的至少一个数据包中的SDAP头移除;
    所述源网络设备将所述终端设备的至少一个数据包发送给所述目标网络设备,包括:
    所述源网络设备将移除SDAP头之后的所述至少一个数据包发送给所述目标网络设备。
  21. 根据权利要求17至19中任一项所述的方法,其特征在于,所述源网络设备将所述终端设备的至少一个数据包发送给所述目标网络设备,包括:
    所述源网络设备将所述终端设备的至少一个数据包发送给所述目标网络设备,所述数据包中包含SDAP头。
  22. 根据权利要求17至21中任一项所述的方法,其特征在于,所述方法还包括:
    所述源网络设备将所述已进行PDCP处理的数据包对应的PDCP序列号发送给所述目标网络设备;和/或,
    所述源网络设备将所述目标网络设备可分配的第一个PDCP序列号发送给所述目标网络设备。
  23. 一种切换方法,其特征在于,所述方法包括:
    目标网络设备从源网络设备接收终端设备的至少一个数据包,所述源网络设备与所述 目标网络设备采用不同的无线接入技术;
    所述目标网络设备在所述终端设备接入所述目标网络设备后,将所述至少一个数据包发送给所述终端设备,所述至少一个数据包为所述源网络设备已进行分组数据汇聚协议PDCP处理的数据包;
    所述目标网络设备向所述源网络设备发送第一指示信息,所述第一指示信息用于指示所述终端设备已成功接入所述目标网络设备。
  24. 根据权利要求23所述的方法,其特征在于,所述源网络设备与所述目标网络设备采用不同的无线接入技术,包括:
    所述终端设备与所述源网络设备对应的协议栈中包括服务数据适配协议SDAP层的处理,而所述终端设备与所述目标网络设备对应的协议栈中不包括SDAP层的处理。
  25. 根据权利要求23或24所述的方法,其特征在于,所述方法还包括:
    所述目标网络设备向所述终端设备发送第二指示信息,所述第二指示信息用于指示所述终端设备停止从所述源网络设备接收数据包。
  26. 根据权利要求23至25中任一项所述的方法,其特征在于,所述源网络设备已进行PDCP处理的数据包中不包含SDAP头。
  27. 根据权利要求23至25中任一项所述的方法,其特征在于,所述源网络设备已进行PDCP处理的数据包中包含SDAP头;
    所述方法还包括:
    所述目标网络设备向所述终端设备发送最后标识包,所述最后标识包用于指示包含SDAP头的数据包发送完毕。
  28. 根据权利要求23至27中任一项所述的方法,其特征在于,所述方法还包括:
    所述目标网络设备从所述源网络设备接收所述源网络设备已进行PDCP处理的数据包对应的PDCP序列号;和/或,
    所述目标网络设备从所述源网络设备接收所述目标网络设备可分配的第一个PDCP序列号。
  29. 一种切换方法,其特征在于,所述方法包括:
    终端设备从源网络设备接收切换命令,所述切换命令指示所述终端设备由所述源网络设备切换到目标网络设备,所述源网络设备与所述目标网络设备采用不同的无线接入技术;
    所述终端设备继续通过分组数据汇聚协议PDCP实体从所述源网络设备接收数据包;
    所述终端设备接入所述目标网络设备,并通过所述PDCP实体从所述目标网络设备接收至少一个数据包。
  30. 根据权利要求29所述的方法,其特征在于,所述源网络设备与所述目标网络设备采用不同的无线接入技术,包括:
    所述终端设备与所述源网络设备对应的协议栈中包括服务数据适配协议SDAP层的处理,而所述终端设备与所述目标网络设备对应的协议栈中不包括SDAP层的处理。
  31. 根据权利要求29或30所述的方法,其特征在于,所述终端设备从所述源网络设备接收的数据包中包含SDAP头;所述方法还包括:
    所述PDCP实体对从所述源网络设备接收的数据包进行PDCP处理,并将经过PDCP处理后的数据包发送至所述终端设备中的SDAP实体移除SDAP头。
  32. 根据权利要求29至31中任一项所述的方法,其特征在于,所述终端设备从所述 目标网络设备接收的数据包中不包含SDAP头;所述方法还包括:
    所述PDCP实体对从所述目标网络设备接收的数据包进行PDCP处理。
  33. 根据权利要求29至31中任一项所述的方法,其特征在于,所述终端设备从所述目标网络设备接收的数据包中包括包含SDAP头的数据包和/或不包含SDAP头的数据包;
    所述方法还包括:
    所述PDCP实体从所述目标网络设备接收最后标识包;
    所述PDCP实体根据所述最后标识包,识别从所述目标网络设备接收的数据包中包含SDAP头的数据包和/或不包含SDAP头的数据包。
  34. 根据权利要求33所述的方法,其特征在于,当所述终端设备识别出从所述目标网络设备接收的包含SDAP头的数据包,所述方法还包括:
    所述PDCP实体对所述数据包进行PDCP处理,并将经过PDCP处理后的所述数据包发送至SDAP实体移除SDAP头;
    所述PDCP实体从所述SDAP实体接收移除SDAP头之后的所述数据包;
    当所述终端设备识别出从所述目标网络设备接收的不包含SDAP头的数据包,所述方法还包括:
    所述PDCP实体对所述数据包进行PDCP处理。
  35. 根据权利要求29至34中任一项所述的方法,其特征在于,所述PDCP实体中包括第一处理单元和第二处理单元,所述第一处理单元与所述源网络设备的安全配置对应,所述第二处理单元与所述目标网络设备的安全配置对应;
    所述方法还包括:
    所述PDCP实体通过所述第一处理单元对从所述源网络设备接收的数据包进行PDCP处理,通过所述第二处理单元对从所述目标网络设备接收到的数据包进行PDCP处理。
  36. 根据权利要求29至35中任一项所述的方法,其特征在于,所述方法还包括:
    所述PDCP实体根据数据包的PDCP序列号,对从所述源网络设备接收的数据包和从所述目标网络设备接收的数据包进行排序和/或去重处理;
    所述PDCP实体将处理后的数据包按序发送至上层。
  37. 一种通信装置,其特征在于,所述装置包括用于执行如权利要求1至6中任一项所述的方法的各步骤的单元,或者包括用于执行如权利要求7至11中任一项所述的方法的各步骤的单元,或者包括用于执行如权利要求12至16中任一项所述的方法的各步骤的单元,或者包括用于执行如权利要求17至22中任一项所述的方法的各步骤的单元,或者包括用于执行如权利要求23至28中任一项所述的方法的各步骤的单元,或者包括用于执行如权利要求29至36中任一项所述的方法的各步骤的单元。
  38. 一种通信装置,其特征在于,所述装置包括至少一个处理器,所述至少一个处理器与至少一个存储器耦合:
    所述至少一个处理器,用于执行所述至少一个存储器中存储的计算机程序或指令,以使得所述装置执行如权利要求1至6中任一项所述的方法,或者使得所述装置执行如权利要求7至11中任一项所述的方法,或者使得所述装置执行如权利要求12至16中任一项所述的方法,或者使得所述装置执行如权利要求17至22中任一项所述的方法,或者使得所述装置执行如权利要求23至28中任一项所述的方法,或者使得所述装置执行如权利要求29至36中任一项所述的方法。
  39. 一种计算机可读存储介质,其特征在于,用于存储指令,当所述指令被执行时,使如权利要求1至6中任一项所述的方法被实现,或者使如权利要求7至11中任一项所述的方法被实现,或者使如权利要求12至16中任一项所述的方法被实现,或者使如权利要求17至22中任一项所述的方法被实现,或者使如权利要求23至28中任一项所述的方法被实现,或者使如权利要求29至36中任一项所述的方法被实现。
  40. 一种通信装置,其特征在于,包括处理器和接口电路;
    所述接口电路,用于交互代码指令至所述处理器;
    所述处理器用于运行所述代码指令以执行如权利要求1至6中任一项所述的方法,或者所述处理器用于运行所述代码指令以执行如权利要求7至11中任一项所述的方法,或者所述处理器用于运行所述代码指令以执行如权利要求12至16中任一项所述的方法,或者所述处理器用于运行所述代码指令以执行如权利要求17至22中任一项所述的方法,或者所述处理器用于运行所述代码指令以执行如权利要求23至28中任一项所述的方法,或者所述处理器用于运行所述代码指令以执行如权利要求29至36中任一项所述的方法。
  41. 一种计算机程序产品,其特征在于,当计算机读取并执行所述计算机程序产品时,使得计算机执行如权利要求1至6中任一项所述的方法,或者执行如权利要求7至11中任一项所述的方法,或者执行如权利要求12至16中任一项所述的方法,或者执行如权利要求17至22中任一项所述的方法,或者执行如权利要求23至28中任一项所述的方法,或者执行如权利要求29至36中任一项所述的方法。
  42. 一种通信系统,其特征在于,所述系统包括源网络设备、目标网络设备和终端设备;
    其中,所述源网络设备用于执行如权利要求1至6中任一项所述的方法,所述目标网络设备用于执行如权利要求7至11中任一项所述的方法,所述终端设备用于执行如权利要求12至16中任一项所述的方法;或者,
    所述源网络设备用于执行如权利要求17至22中任一项所述的方法,所述目标网络设备用于执行如权利要求23至28中任一项所述的方法,所述终端设备用于执行如权利要求29至36中任一项所述的方法。
PCT/CN2021/074503 2020-02-27 2021-01-29 一种切换方法及通信装置 WO2021169732A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21760714.2A EP4087318A4 (en) 2020-02-27 2021-01-29 SWITCHING METHOD AND COMMUNICATION APPARATUS
US17/893,858 US20220408319A1 (en) 2020-02-27 2022-08-23 Handover method and communication apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010125620.3A CN113316202A (zh) 2020-02-27 2020-02-27 一种切换方法及通信装置
CN202010125620.3 2020-02-27

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/893,858 Continuation US20220408319A1 (en) 2020-02-27 2022-08-23 Handover method and communication apparatus

Publications (1)

Publication Number Publication Date
WO2021169732A1 true WO2021169732A1 (zh) 2021-09-02

Family

ID=77370476

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/074503 WO2021169732A1 (zh) 2020-02-27 2021-01-29 一种切换方法及通信装置

Country Status (4)

Country Link
US (1) US20220408319A1 (zh)
EP (1) EP4087318A4 (zh)
CN (1) CN113316202A (zh)
WO (1) WO2021169732A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117528639A (zh) * 2022-07-30 2024-02-06 华为技术有限公司 一种通信方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047967A (zh) * 2006-03-30 2007-10-03 华为技术有限公司 在切换过程中处理数据的方法及装置
US20080219275A1 (en) * 2007-03-05 2008-09-11 Nokia Corporation Apparatus, method and computer program product providing neighbor discovery, handover procedure and relay zone configuration for relay stations in a multi-hop network
CN103313325A (zh) * 2012-03-09 2013-09-18 中兴通讯股份有限公司 切换方法及装置、数据处理方法及装置
CN108112041A (zh) * 2016-11-24 2018-06-01 中国移动通信有限公司研究院 一种切换方法、源基站、目标基站及终端
CN109982360A (zh) * 2017-12-27 2019-07-05 华为技术有限公司 通信方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108882334B (zh) * 2017-08-11 2019-11-05 华为技术有限公司 一种数据传输方法、核心网用户面设备和源基站
WO2019237364A1 (zh) * 2018-06-15 2019-12-19 Oppo广东移动通信有限公司 数据按序递交的方法、网络设备及终端设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047967A (zh) * 2006-03-30 2007-10-03 华为技术有限公司 在切换过程中处理数据的方法及装置
US20080219275A1 (en) * 2007-03-05 2008-09-11 Nokia Corporation Apparatus, method and computer program product providing neighbor discovery, handover procedure and relay zone configuration for relay stations in a multi-hop network
CN103313325A (zh) * 2012-03-09 2013-09-18 中兴通讯股份有限公司 切换方法及装置、数据处理方法及装置
CN108112041A (zh) * 2016-11-24 2018-06-01 中国移动通信有限公司研究院 一种切换方法、源基站、目标基站及终端
CN109982360A (zh) * 2017-12-27 2019-07-05 华为技术有限公司 通信方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4087318A4 *

Also Published As

Publication number Publication date
EP4087318A4 (en) 2023-06-14
EP4087318A1 (en) 2022-11-09
CN113316202A (zh) 2021-08-27
US20220408319A1 (en) 2022-12-22

Similar Documents

Publication Publication Date Title
US11968633B2 (en) Relay communication method and apparatus
US11246074B2 (en) Communication method and communications apparatus
CN110603896B (zh) 新型无线电接入技术中的pdcp重复和数据恢复的处理
CN109151918B (zh) 切换控制方法及装置
CN110636575B (zh) 一种切换方法及装置
KR102420332B1 (ko) 데이터 전송 방법, 단말 기기 및 네트워크 기기
US11711731B2 (en) Data transmission method and apparatus
WO2018127220A1 (zh) 一种数据转发方法及装置
WO2021185350A1 (zh) 一种通信方法、接入网设备、终端设备和核心网设备
WO2019095114A1 (zh) 处理无线链路失败的方法、终端设备和网络设备
US20210144801A1 (en) Wireless communication method, communication device, chip, and communication system
WO2021185058A1 (zh) 一种中继通信方法及相关设备
US11894974B2 (en) Network switching method, network node, chip and communication system
WO2021169732A1 (zh) 一种切换方法及通信装置
WO2020147056A1 (zh) 用于复制数据传输的方法和设备
WO2021127943A1 (zh) 无线通信方法和终端设备
WO2020029838A1 (zh) 一种配置载波的方法及设备
WO2022141332A1 (zh) 一种通信方法及装置
WO2024066882A1 (zh) 控制面信令传输方法、装置及存储介质
WO2024011463A1 (zh) 一种处理数据的方法及装置、通信设备
WO2021160057A1 (zh) 系统间切换方法和通信装置
WO2020029074A1 (zh) 无线通信方法、通信设备、芯片和通信系统
WO2020124540A1 (zh) 一种数据包重排序方法、电子设备及存储介质
CN115623469A (zh) 一种网络编码功能的配置方法以及相关装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21760714

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021760714

Country of ref document: EP

Effective date: 20220805

NENP Non-entry into the national phase

Ref country code: DE