WO2018141241A1 - 设备切换方法及设备、承载配置方法及设备、通信系统 - Google Patents

设备切换方法及设备、承载配置方法及设备、通信系统 Download PDF

Info

Publication number
WO2018141241A1
WO2018141241A1 PCT/CN2018/074601 CN2018074601W WO2018141241A1 WO 2018141241 A1 WO2018141241 A1 WO 2018141241A1 CN 2018074601 W CN2018074601 W CN 2018074601W WO 2018141241 A1 WO2018141241 A1 WO 2018141241A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
network device
pdcp
bearer
length
Prior art date
Application number
PCT/CN2018/074601
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 华为技术有限公司
Publication of WO2018141241A1 publication Critical patent/WO2018141241A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a device switching method and device, a bearer configuration method and device, and a communication system.
  • the LTE communication system includes terminal equipment and access network equipment.
  • the terminal device establishes a first bearer with the first access network device, and the terminal device communicates with the first access network device by using the first bearer.
  • the first access network device indicates that the terminal device is the first bearer configuration data convergence protocol (English: Packet Data Convergence Protocol; PDCP) serial number (English: Sequence Number; referred to as: SN) length (that is, the number of bits in the SN).
  • PDCP Packet Data Convergence Protocol
  • SN Sequence Number
  • the terminal device needs to switch from the first access network device to the second access network device, the first access network device sends a handover request message to the second access network device, where the handover request message includes the PDCP of the first bearer configuration.
  • the SN length the second access network device determines, according to the handover request message, whether it can support the PDCP SN length of the first bearer configuration.
  • the second access network device determines that the PDCP SN length of the first bearer configuration cannot be supported, the second access network device triggers the terminal device to perform full configuration switching by using the first access network device, and performs full configuration switching on the terminal device.
  • the terminal device establishes a second bearer with the second access network device, and configures a PDCP SN length that the second access network device can support for the second bearer, and deletes the cached data of the terminal device.
  • the cached data on the terminal device includes data that has been sent by the terminal device and is not confirmed to be successfully transmitted.
  • the terminal device deletes the cached data of the terminal device during the process of performing the full configuration switch. Therefore, when the terminal device is switched from the first access network device to the second access network device, the terminal device may be The loss of data sent successfully and not confirmed.
  • the present invention provides a device switching method and device, a bearer configuration method, a device, and a communication system, which can solve the problem that the data that has been sent by the terminal device and that is not confirmed to be successfully transmitted is lost.
  • the technical solution is as follows:
  • the first aspect provides a device switching method, where the method includes: the first access network device sends a handover request message to the second access network device, where the handover request message includes: a first lossless handover identifier; Receiving, by the first access network device, a handover confirmation message sent by the second access network device, where the handover confirmation message includes a transparent container information element and a second lossless handover identifier located outside the transparent container information element, where the transparent
  • the container information element includes a third lossless handover identifier; the first access network device sends the transparent container information element as a handover command to the terminal device; wherein, the first lossless handover identifier, the second lossless handover identifier, and the third lossless The handover identifier is used to indicate that there is no data loss handover.
  • the lossless transmission identifier is included in the handover request received by the second access network device, the handover confirmation message received by the first access network device, and the transparent container information element received by the terminal device, and the lossless transmission identifier is used to indicate Switching with no data loss is performed. Therefore, when the terminal device is switched from the first access network device to the second access network device, full configuration switching is prevented, and the occurrence of cache data loss is prevented.
  • the handover request message further includes: first configuration information used to indicate a length of a current packet data convergence protocol (PDCP) sequence number SN of the first bearer
  • the handover confirmation message further includes: Whether the access network device can support the capability information of the current PDCP SN length of the first bearer, and when the capability information indicates that the second access network device cannot support the current PDCP SN length, the handover confirms
  • the message further includes: second configuration information indicating a length of the target PDCP SN allocated by the second access network device to the second bearer; wherein the first bearer is the terminal device and the first access A bearer between the network devices, where the second bearer is a bearer between the terminal device and the second access network device.
  • the method further includes: the capability information in the handover confirmation message indicates the second
  • the first access network device forwards to the second access network device: the first PDCP service in the cached data of the first access network device
  • the data unit SDU, the PDCP SN in the first PDCP SDU is less than or equal to the maximum PDCP SN corresponding to the target PDCP SN length.
  • the first access network device When the second access network device cannot support the current PDCP SN of the first bearer, the first access network device sends the first PDCP SDU that can be identified by the second access network device to the second access network device, preventing the first The loss of a PDCP SDU.
  • the method further includes: when the capability information in the handover confirmation message indicates that the second access network device cannot support the current PDCP SN length, the first access network device according to the The target PDCP SN length constructs a reception status element of the uplink PDCP SDU; the first access network device forwards the reception status element of the uplink PDCP SDU to the second access network device. Since the second access network device cannot support the current PSCP SN length of the first bearer, the first access network device needs to construct the receiving status element of the uplink PDCP SDU according to the target PDCP SN length that the second access network device can support.
  • the method further includes: the first access network device sends a configuration message to the terminal device, where
  • the configuration message includes: the first access network device is a first PDCP SN length allocated by the first access network device and the first bearer that the terminal device has established.
  • the first access network device can send a configuration message to the terminal device to instruct the terminal device to reconfigure the first PDCP SN length for the established first bearer. That is, the PDCP SN length of the bearer configuration that has been established in the present application can be adjusted.
  • the terminal device sends less data to the first access network device, the first access network device configures the PDCP for the first bearer.
  • the length of the SN is reduced, thereby reducing the length of the PDCP SN in the PDCP SDU sent by the terminal device, and reducing the waste of the bit.
  • the PDCP SN length of the first bearer includes: an uplink PDCP SN length and a downlink PDCP SN length.
  • the uplink PDCP SN length in the PDCP SN length of the first bearer is equal to the downlink PDPC SN length, or the uplink PDCP SN length in the PDPC SN length of the first bearer is different from the downlink PDPC SN length.
  • the first access network device can allocate a first PDCP SN length (that is, a downlink PDCP SN length or a downlink PDCP SN length) to the first bearer, and send a configuration message including the first PDCP SN length to the terminal device, where the terminal The device configures a first PDCP SN length for the first bearer according to the configuration message.
  • the configuration message includes a PDCP SN length
  • the length of the PDCP SN may be the same as the uplink PDCP SN length and the downlink PDCP SN length of the first bearer allocated by the first access network device, or the length of the PDCP SN is An uplink PDCP SN length or a downlink PDCP SN length allocated by the access network device to the first bearer.
  • the terminal device or the first access network device when the terminal device or the first access network device has less data to be transmitted, a shorter PDCP SN length (requiring a small number of bits) can distinguish less data, but currently, the terminal device or the An access network device still allocates a fixed-length (relatively long) PDCP SN for each data (requiring more bits). Therefore, the PDCP SN in the PDCP SDU is longer, and the bits of the PDCP SN need to be occupied. A large number, resulting in the waste of bits.
  • the terminal device or the first access network device When the terminal device or the first access network device has more data to be sent, the terminal device or the first access network device still allocates a fixed length (relatively short) PDCP SN for each data, and the fixed length can only A part of the data to be sent is distinguished. Therefore, the terminal device or the first access network device can only transmit a part of data to be transmitted during a data transmission process, and the efficiency of the data transmission cannot meet the requirement.
  • the access network device can send a configuration message to the terminal device to instruct the terminal device to reconfigure the length of the first PDCP SN for the first bearer that has been established, and adjust the length of the PDCP SN of the first bearer.
  • the terminal device can transmit data by reconfiguring the first bearer after the length of the PDCP SN.
  • the uplink PDCP SN length and the downlink PDCP SN length allocated by the access network device to the first bearer can satisfy the situation that the data packet is more and less, thereby avoiding the waste of the bit in the PDCP SN when the data packet is small. And when there are many data packets, the data transmission efficiency is low.
  • the configuration message further includes validation information, where the validation information is used to indicate a target count value.
  • the validation information includes at least one of a PDCP SN, a start frame number HFN, and a count value.
  • the first access network device is further configured to instruct the terminal device to turn off the count value, the cutoff count value is located after the target count value, and there are multiple count values between the target count value, and the count value maintained by the terminal device becomes When the count value is off, the terminal device can reconfigure the original PDCP SN length for the first bearer.
  • a second aspect provides a device switching method, where the method includes: receiving, by a terminal device, a handover command sent by a first access network device, where the handover command is a transparent container information element in a handover confirmation message, and the transparent container information
  • the element includes a third lossless handover identifier, the first lossless handover identifier, the second lossless handover identifier, and the third lossless handover identifier are used to indicate that no data loss is performed; the terminal device is in the first according to the handover command There is no data loss switching between the access network device and the second access network device.
  • the transparent container information element further includes: capability information indicating whether the second access network device can support the current PDCP SN length of the first bearer, and indicating the second access network a second configuration information that is allocated to the target PDCP SN of the second bearer, where the first bearer is a bearer between the terminal device and the first access network device, and the second bearer is the terminal a bearer between the device and the second access network device; the terminal device performs no data loss switching between the first access network device and the second access network device according to the handover command,
  • the method includes: when the capability information in the transparent container information element indicates that the second access network device cannot support the current PDCP SN length, the terminal device configures the target PDCP SN length for the second bearer; Transmitting, by the terminal device, a second PDCP SDU in the cached data of the terminal device to the second access network device, where a PDCP SN in the second PDCP SDU is less than or equal to a length of the target PDCP SN Maximum
  • the terminal device can only configure the target PDCP SN length for the second bearer, and only the second PDCP SDU with the smaller PDCP SN length can
  • the second bearer transmits and can be identified by the second access device, preventing the loss of the second PDCP SDU.
  • the terminal device performs data lossless switching between the first access network device and the second access network device according to the handover command, and further includes: in the transparent container information element When the capability information indicates that the second access network device cannot support the current PDCP SN length, the terminal device constructs a reception status report of the downlink PDCP SDU according to the target PDCP SN length; The second access network device sends a reception status report of the downlink PDCP SDU.
  • the transparent container information element further includes: capability information indicating whether the second access network device can support the current PDCP SN length of the first bearer, and indicating the second access network a second configuration information that is allocated to the target PDCP SN of the second bearer, where the first bearer is a bearer between the terminal device and the first access network device, and the second bearer is the terminal a bearer between the device and the second access network device; the terminal device performs no data loss switching between the first access network device and the second access network device according to the handover command,
  • the method includes: when the capability information in the transparent container information element indicates that the second access network device can support the current PDCP SN length, the terminal device configures the current PDCP SN length for the second bearer;
  • the terminal device sends a PDCP SDU to which the PDCP SN has been allocated in the cache data of the terminal device to the second access network device; and successfully confirms that the PDCP SDU of the PDCP SN has been allocated in the cache data of the
  • the terminal device After access to said second network device, the terminal device is the target of the second bearer configuration PDCP SN length. That is, when the second access network device can support the current PDCP SN length of the first bearer, the terminal device transmits the PDCP SDU with the allocated PDCP SN in the cached data to the second access network device, and the second access network The device can recognize the received PDCP SDU and prevent the loss of the PDCP SDU of the allocated PDCP SN in the buffered data of the terminal device.
  • the terminal device performs data lossless switching between the first access network device and the second access network device according to the handover command, and further includes: in the transparent container information element When the capability information indicates that the second access network device is capable of supporting the current PDCP SN length, the terminal device constructs a reception status report of the downlink PDCP SDU according to the current PDCP SN length; The second access network device sends a reception status report of the downlink PDCP SDU.
  • the method further includes: receiving, by the terminal device, a configuration message sent by the first access network device, where the configuration message is The first access network device is a first PDCP SN length allocated by the first access network device and the first bearer that has been established by the terminal device, and the terminal device is configured according to the configuration message.
  • the first bearer reconfigures the first PDCP SN length.
  • the PDCP SN length of the first bearer includes: an uplink PDCP SN length and a downlink PDCP SN length.
  • the method before the receiving, by the terminal device, the configuration message sent by the first access network device, the method further includes: acquiring, by the terminal device, at least one trigger condition related to a PDCP SDU in flight,
  • the in-flight PDCP SDU is an uplink PDCP SDU that has been sent by the terminal device and has not been successfully sent;
  • the terminal device determines whether the number of PDCP SDUs in flight meets any of the trigger conditions;
  • the terminal device sends a feedback message to the first access network device.
  • the first PDCP SN length (uplink PDCP SN length) allocated by the first access network device for the first bearer is positively correlated with the uplink throughput of the terminal device, and the uplink throughput of the terminal device and the in-flight packet of the terminal device
  • the number is positively correlated. That is, when the number of data packets in flight is large, the uplink throughput of the terminal device is large. In this case, in order to improve the efficiency of transmitting the data packet by the terminal device, the first access network device allocates the uplink to the first bearer.
  • the PDCP SN has a large length, enabling the terminal device to transmit more data packets at a time. When the number of data packets in flight is small, the uplink throughput of the terminal device is small.
  • the first access network device is allocated to the first bearer.
  • the uplink PDCP SN has a small length, reducing the waste of bits in the PDCP SN in the data packet.
  • the at least one triggering condition includes at least one of the following triggering conditions: the number of in-flight PDCP SDUs of the terminal device is less than a first threshold; the number of in-flight PDCP SDUs of the terminal device Greater than the second threshold.
  • the configuration message further includes the validation information, where the validation information is used to indicate the target count value, and the terminal device reconfigures the first PDCP SN for the first bearer according to the configuration message.
  • the length includes: when the count value maintained by the terminal device is changed to the target count value, the terminal device reconfigures the first PDCP SN length for the first bearer according to the configuration information; or When the count value maintained by the terminal device is changed to the next count value of the target count value, the terminal device reconfigures the first PDCP SN length for the first bearer according to the configuration information.
  • the terminal device After receiving the configuration message, the terminal device determines the first PDCP SN and the target count value according to the configuration message, and reconfigures the first PDCP SN for the first bearer when the count value maintained by the terminal device is changed to the target count value.
  • the length that is, the uplink PDCP SN length of the first bearer is changed to the first PDCP SN length.
  • the terminal device determines the first PDCP SN and the target count value according to the configuration message, and is first when the count value maintained by the terminal device is changed to the next count value of the target count value.
  • the bearer reconfigures the first PDCP SN length, that is, changes the uplink PDCP SN length of the first bearer to the first PDCP SN length.
  • the validation information includes at least one of a PDCP SN, a start frame number HFN, and a count value.
  • a third aspect provides a device switching method, where the method includes: a second access network device receives a handover request message sent by a first access network device, where the handover request message includes: a first lossless handover identifier, where Transmitting, by the second access network device, a handover confirmation message to the first access network device according to the handover request message, where the handover confirmation message includes a transparent container information element and a second outside the transparent container information element And the transparent container information element includes a third lossless handover identifier; wherein the first lossless handover identifier, the second lossless handover identifier, and the third lossless handover identifier are used to indicate that the handover without data loss is performed.
  • the handover request message further includes: first configuration information that is used to indicate a current PDCP SN length of the first bearer
  • the handover confirmation message further includes: The capability information of the current PDCP SN length is supported, and when the capability information indicates that the second access network device cannot support the current PDCP SN length, the handover confirmation message further includes: The second configuration information that is allocated by the second access network device to the target PDCP SN length of the second bearer, where the first bearer is a bearer between the terminal device and the first access network device, where the The second bearer is a bearer between the terminal device and the second access network device.
  • the method further includes: receiving, by the second access network device The first PDCP SDU in the cache data of the first access network device forwarded by the first access network device, the PDCP SN in the first PDCP SDU is less than or equal to the maximum corresponding to the target PDCP SN length PDCP SN.
  • the method further includes: receiving, by the second access network device a receiving status element of the uplink PDCP SDU forwarded by the first access network device, and a receiving status element of the uplink PDCP SDU is configured according to the target PDCP SN length.
  • the method further includes: receiving, by the second access network device a second PDCP SDU in the buffered data of the terminal device that is sent by the terminal device, and a PDCP SN in the second PDCP SDU is less than or equal to a maximum PDCP SN corresponding to the target PDCP SN length.
  • the method further includes: receiving, by the second access network device a receiving status report of the downlink PDCP SDU sent by the terminal device, where the receiving status report of the downlink PDCP SDU is configured according to the target PDCP SN length.
  • the method further includes: receiving, by the second access network device The PDCP SDU of the PDCP SN has been allocated in the cache data of the terminal device sent by the terminal device.
  • the method further includes: receiving, by the second access network device a receiving status report of the downlink PDCP SDU sent by the terminal device, where the receiving status report of the downlink PDCP SDU is constructed according to the current PDCP SN length.
  • the fourth aspect provides a bearer configuration method, where the method includes: the first access network device sends a configuration message to the terminal device, where the configuration message includes: the first access network device is the first interface The first PDCP SN length allocated by the network device and the first bearer that has been established by the terminal device.
  • the first access network device can send a configuration message to the terminal device to instruct the terminal device to reconfigure the first PDCP SN length for the established first bearer. That is, the PDCP SN length of the bearer configuration that has been established in the present application can be adjusted.
  • the terminal device sends less data to the first access network device
  • the first access network device configures the PDCP for the first bearer.
  • the length of the SN is reduced, thereby reducing the length of the PDCP SN in the PDCP SDU sent by the terminal device, and reducing the waste of the bit.
  • the PDCP SN length of the first bearer includes: an uplink PDCP SN length and a downlink PDCP SN length.
  • the configuration message further includes validation information, where the validation information is used to indicate a target count value.
  • the validation information includes at least one of a PDCP SN, a start frame number HFN, and a count value.
  • a fifth aspect provides a bearer configuration method, where the method includes: receiving, by a terminal device, a configuration message sent by a first access network device, where the configuration message includes: the first access network device is the first The first PDCP SN length allocated by the access network device and the first bearer that has been established by the terminal device; the terminal device reconfigures the first PDCP SN length for the first bearer according to the configuration message.
  • the PDCP SN length of the first bearer includes: an uplink PDCP SN length and a downlink PDCP SN length.
  • the method before the receiving, by the terminal device, the configuration message sent by the first access network device, the method further includes: acquiring, by the terminal device, at least one trigger condition related to a PDCP SDU in flight,
  • the in-flight PDCP SDU is an uplink PDCP SDU that has been sent by the terminal device and has not been successfully sent;
  • the terminal device determines whether the number of PDCP SDUs in flight meets any of the trigger conditions;
  • the terminal device sends a feedback message to the first access network device.
  • the at least one triggering condition includes at least one of the following triggering conditions: the number of in-flight PDCP SDUs of the terminal device is less than a first threshold; the number of in-flight PDCP SDUs of the terminal device Greater than the second threshold.
  • the configuration message further includes the validation information, where the validation information is used to indicate the target count value, and the terminal device reconfigures the first PDCP SN for the first bearer according to the configuration message.
  • the length includes: when the count value maintained by the terminal device is changed to the target count value, the terminal device reconfigures the first PDCP SN length for the first bearer according to the configuration information; or When the count value maintained by the terminal device is changed to the next count value of the target count value, the terminal device reconfigures the first PDCP SN length for the first bearer according to the configuration information.
  • the validation information includes at least one of a PDCP SN, a start frame number HFN, and a count value.
  • the sixth aspect provides a switching device, where the switching device includes at least one module, and the at least one module is used to implement the device switching method provided by the foregoing first aspect or any of the foregoing aspects.
  • the seventh aspect provides a switching device, where the switching device includes at least one module, and the at least one module is configured to implement the device switching method provided by any of the foregoing second aspect or the second aspect.
  • the eighth aspect provides a switching device, where the switching device includes at least one module, and the at least one module is used to implement the device switching method provided by any of the foregoing third aspect or the third aspect.
  • the ninth aspect provides a bearer configuration device, where the bearer configuration device includes at least one module, and the at least one module is configured to implement the bearer configuration method provided by any of the foregoing fourth aspect or the fourth aspect.
  • the tenth aspect provides a bearer configuration device, where the bearer configuration device includes at least one module, and the at least one module is configured to implement the bearer configuration method provided by any of the foregoing fifth or fifth aspects.
  • a network access device comprising: at least one transmitter, at least one receiver, at least one processor, at least one network interface, a memory, and at least one bus, a memory and a network interface Connected to the processor by a bus; the processor is configured to execute the instructions stored in the memory; the processor is implemented by executing the instruction: the device switching method provided by any one of the foregoing first aspect or the first aspect Or the device switching method provided by any one of the foregoing third aspect or the third aspect.
  • a terminal device includes: at least one transmitter, at least one receiver, at least one processor, at least one network interface, and a memory, and the memory and the network interface are respectively connected to the processor;
  • the device is configured to execute the instructions stored in the memory; the processor implements the device switching method provided by any one of the possible implementations of the second aspect or the second aspect.
  • a network access device comprising: at least one transmitter, at least one receiver, at least one processor, at least one network interface, a memory, a memory and a network interface, respectively, and a processor Connected; the processor is configured to execute the instructions stored in the memory; the processor implements the load configuration method provided by any one of the possible implementations of the fourth aspect or the fourth aspect.
  • a terminal device comprising: at least one transmitter, at least one receiver, at least one processor, at least one network interface, a memory, and a memory and a network interface respectively connected to the processor;
  • the processor is configured to execute the instructions stored in the memory; the processor implements the load configuration method provided by any one of the possible implementations of the fifth aspect or the fifth aspect.
  • a communications system comprising: a first access network device, a terminal device, and a second access network device, wherein the first access network device is the sixth aspect
  • the switching device is the switching device according to the seventh aspect; the second access network device is the switching device according to the eighth aspect.
  • the first access network device and the second access network device are different, and the first access network device and the second access network device are the network access device according to the eleventh aspect, and the terminal device is The terminal device described in the twelve aspects.
  • a communication system includes: a first access network device and a terminal device, where the first access network device is the switching device according to the ninth aspect; the terminal device The switching device of the tenth aspect.
  • the first access network device is the access network device according to the thirteenth aspect
  • the terminal device is the terminal device according to the fourteenth aspect.
  • a computer readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the first aspect, The method of the second aspect, the third aspect, the fourth aspect or the fifth aspect.
  • the lossless transmission identifier is included in the handover request received by the second access network device, the handover confirmation message received by the first access network device, and the transparent container information element received by the terminal device, and the lossless transmission identifier is used to indicate Switching with no data loss is performed. Therefore, when the terminal device is switched from the first access network device to the second access network device, full configuration switching is prevented, and the occurrence of cache data loss is prevented.
  • the first access network device can send a configuration message to the terminal device to instruct the terminal device to reconfigure the first PDCP SN length for the established first bearer. That is, the PDCP SN length of the bearer configuration that has been established in the present application can be adjusted.
  • the terminal device sends less data to the first access network device
  • the first access network device configures the PDCP for the first bearer. The length of the SN is reduced, thereby reducing the length of the PDCP SN in the PDCP SDU sent by the terminal device, and reducing the waste of the bit.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of another communication system according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a user plane protocol stack of a communication device according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of an application scenario of a device switching method according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of an application scenario of another device switching method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of an application scenario of another device switching method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of an access network device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of a method for device switching according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a count value according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a handover confirmation message according to an embodiment of the present disclosure.
  • FIG. 12 is a flowchart of a method for forwarding cache data by a first access network device according to an embodiment of the present disclosure
  • FIG. 13 is a flowchart of a method for a terminal device to perform handover according to an embodiment of the present invention
  • FIG. 14 is a schematic structural diagram of a first switching device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a second switching device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a third switching device according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of a fourth switching device according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram of a fifth switching device according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic structural diagram of a sixth switching device according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic structural diagram of a seventh switching device according to an embodiment of the present disclosure.
  • FIG. 21 is a schematic structural diagram of an eighth switching device according to an embodiment of the present disclosure.
  • FIG. 22 is a schematic structural diagram of a ninth switching device according to an embodiment of the present disclosure.
  • FIG. 23 is a schematic structural diagram of a tenth switching device according to an embodiment of the present disclosure.
  • FIG. 24 is a schematic structural diagram of a switch device according to an eleventh embodiment of the present disclosure.
  • FIG. 25 is a schematic structural diagram of a twelfth switching device according to an embodiment of the present disclosure.
  • FIG. 26 is a schematic structural diagram of a thirteenth switching device according to an embodiment of the present disclosure.
  • FIG. 27 is a schematic structural diagram of a fourteenth switching device according to an embodiment of the present disclosure.
  • FIG. 28 is a schematic structural diagram of a bearer configuration device according to an embodiment of the present disclosure.
  • FIG. 29 is a schematic structural diagram of another bearer configuration device according to an embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of a communication system A according to an embodiment of the present invention.
  • the communication system A includes a terminal device 10, a first access network device 111, and a second access network device 112.
  • the terminal device 10 is capable of establishing a bearer with each access network device (the terminal device 10 and the first access network device 111 are configured with a bearer in FIG. 1), and can communicate with the access network device through the established bearer.
  • the access network device accesses the core network (not shown in Figure 1).
  • the access network device is a base station, such as an evolved base station (English: Evolved NodeB; eNB for short) or a new air interface base station (English: New Radio NodeB; NR-NB for short), and the terminal device 10 is a mobile phone, and the data is carried as data.
  • Radio bearer English: Data Radio Bearer; referred to as: DRB.
  • the NR-NB may also be referred to as gNB (base station in the fifth generation mobile communication technology system).
  • FIG. 2 is a schematic structural diagram of another communication system B according to an embodiment of the present invention.
  • the communication system B includes a terminal device 10 and a first access network device 111.
  • the terminal device 10 can establish a bearer with the first access network device 111, and can communicate with the access network device through the established bearer, and the first access network device accesses the core network (not shown in FIG. 1).
  • the first access network device is a base station, such as an eNB or an NR-NB
  • the terminal device 10 is a mobile phone
  • the bearer is a DRB.
  • FIG. 3 is a schematic diagram of a user plane protocol stack of a communication device according to an embodiment of the present invention.
  • the communication device is a terminal device or an access network device.
  • the user plane protocol stack of the communication device includes: PDCP, Radio link control (English: Radio Link Control; RLC for short), multiple access control (English: Multiple Access Control; MAC), physical layer protocol (English: physical; abbreviation: PHY) four-layer protocol.
  • the working mode of the RLC is the confirmation mode (English: Acknowledged Mode; abbreviation: AM).
  • the bearer established by the terminal device and the access network device is established by the entity of the PDCP layer and the entity of the RLC layer.
  • FIG. 4 is a schematic diagram of an application scenario of a device switching method according to an embodiment of the present invention.
  • the terminal device 10 when the terminal device 10 establishes a first bearer with the first access network device 111, and passes through the first access network.
  • the terminal device 10 communicates with the core network (Evolved Packet Core; EPC) 2, the terminal device 10 can also cut off the first bearer established with the currently connected first access network device 111, and the second access
  • the network device 112 establishes a second bearer, which in turn communicates with the core network 2 via the second access network device 112.
  • EPC Evolved Packet Core
  • the first bearer and the first The second bearer is a bearer.
  • FIG. 5 is a schematic diagram of a scenario in which a secondary cell group change (SCG change) is performed in a secondary device of a terminal device according to an embodiment of the present invention. As shown in FIG. 5, when the terminal device 10 and the first device are shown in FIG.
  • SCG change secondary cell group change
  • the access network device 111 is configured with a first bearer, and the terminal device 10 passes the S1-C interface on the first access network device 111 (a communication interface defined in the LTE protocol, that is, a data radio bearer (English: Signal) Radio Bearer; abbreviated as: SRB))
  • SRB Data Radio Bearer
  • the terminal device 10 is also capable of switching the S1-U interface from the first access network device 111 to the second access network device 112.
  • DRB Data Radio Bearer
  • the terminal device 10 and the first access network device 111 establish a first bearer, and a second The access network device 112 is configured with a second bearer, and the terminal device 10 transmits signaling through the S1-C interface of the first access network device 111 to the core network 2 and through the S1-U interface of the second access network device 112. Data is transmitted with the core network 2.
  • FIG. 6 is a schematic diagram of another SCG change scenario according to an embodiment of the present invention.
  • the terminal device 10 and the third access network device 113 establish a third bearer
  • the first access network device 111 is established.
  • the terminal device 10 communicates with the core network 2 through the S1-C interface on the third access network device 113, and communicates with the core network 2 through the S1-U interface of the first access network device 111.
  • the terminal device 10 is also capable of switching the S1-U interface from the first access network device 111 to the second access network device 112.
  • the terminal device 10 and the third access network device establish a third bearer, and
  • the second access network device 112 is configured with a second bearer, and the terminal device 10 transmits signaling to the core network 2 through the S1-C interface of the third access network device 113, and passes through the S1 of the second access network device 112.
  • the -U interface is transmitted with the core network 2.
  • the DRBs of the terminal device 10 are all switched from the first access network device 111 to the second access network device 112.
  • the first access network device 111 and the second access network device 112 are both NR-NB, or the first access network device 111 and the second access network device 112, and one access network device is NR. -NB, another access network device is an eNB.
  • the access network device instructs the terminal device to configure the PDCP SN length for the bearer.
  • the terminal device needs to send the uplink data
  • the terminal device allocates different PDCP SNs for the uplink data to be sent according to the PDCP SN length of the bearer configuration, and obtains multiple uplink PDCP service data units (English: Service Data Unit; SDU for short)
  • the length of the PDCP SN allocated by the terminal device to the data is equal to the PDCP SN length (eg, 12 bits) of the bearer being configured.
  • each PDCP SDU includes a PDCP SN and a data part, and each PDCP SN has a length of 12 bits, but the PDCP SNs in different PDCP SDUs are different from each other.
  • the terminal device sends a PDCP SDU to the access network device by using the bearer, and after receiving the PDCP SDU, the access network device parses the PDCP SDU to determine the PDCP SN and the data portion in each uplink PDCP SDU, and then according to The size of the PDCP SN in multiple PDCP SDUs determines the ordering of the data portions in the PDCP SDU.
  • the terminal device receives the downlink PDCP SDU sent by the access network device, the terminal device parses the received downlink PDCP SDU according to the PDCP SN length of the bearer configuration.
  • FIG. 7 is a schematic structural diagram of an access network device 70 according to an embodiment of the present invention.
  • the access network device 70 is the first access network device in the communication system A shown in FIG. 1, the second access network device in the communication system A shown in FIG. 1, or the communication system B shown in FIG.
  • the access network device 70 is configured to perform some of the methods provided by the embodiment shown in FIG. Referring to FIG. 7, the access network device 70 includes a processor 710 and a transmitter 720, and the processor 710 and the transmitter 720 are connected by a bus 730.
  • Processor 710 includes one or more processing cores.
  • the processor 710 executes various functional applications and data processing by running software programs and units.
  • the access network device 70 further includes: a memory 740, a network interface 750, and a receiver 760.
  • the memory 740, the network interface 750, and the receiver 760 are processed by the bus 730 and the transmitter 720, respectively.
  • the device 710 is connected.
  • the network interface 750 is used by the network interface 750 to communicate with other storage devices or access network devices.
  • the network interface 750 is optional.
  • the access network device 70 can communicate with other storage devices or access network devices through the transmitter 720 and the receiver 760. Therefore, the access network device 70 can be absent.
  • the network interface is not limited in this embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a terminal device 80 according to an embodiment of the present invention.
  • the terminal device 80 is a terminal device in the communication system A shown in FIG. 1 or the communication system B shown in FIG. 2, and the terminal device 80 is used to execute part of the method provided in the embodiment shown in FIG.
  • the access network device diagram 80 includes a processor 810 and a transmitter map 820.
  • the processor 810 and the transmitter map 820 are coupled by a bus map 830.
  • Processor 810 includes one or more processing cores.
  • the processor 810 executes various functional applications and data processing by running software programs and units.
  • the terminal device 80 further includes a memory map 840, a network interface map 850, and a receiver map 860.
  • the memory map 840, the network interface map 850, and the receiver map 860 respectively pass through the bus map 830. Connected to transmitter map 820 and processor 810.
  • the network interface diagram 850 is used to communicate with other storage devices or access network devices.
  • the network interface diagram 850 is optional.
  • the terminal device diagram 80 can communicate with other storage devices or access network devices through the transmitter map 820 and the receiver map 860. Therefore, the terminal device does not have any picture 80.
  • the network interface is not limited in this embodiment of the present invention.
  • FIG. 9 is a flowchart of a method for device switching according to an embodiment of the present invention.
  • the device switching method is used in the communication system A shown in FIG. 1 , and the device switching method is also used in FIG. 4 , FIG. 5 or FIG. 6 .
  • the application scenario shown in Figure 9, the device switching method includes:
  • Step 901 The first access network device sends a configuration message to the terminal device, where the configuration message includes a first PDCP SN length.
  • the terminal device and the first access network device have established the first bearer, and when the first bearer is established, the first access network device has instructed the terminal device to configure the PDCP SN length for the first bearer.
  • the first access network device can also send a configuration message to the terminal device to indicate that the terminal device reconfigures the first PDCP SN length for the established first bearer.
  • the configuration message includes the first PDCP SN length that the first access network device re-configured for the first bearer.
  • the PDCP SN length of the first bearer includes: an uplink PDCP SN length and a downlink PDCP SN length.
  • the length of the first PDCP SN is the length of the uplink PDCP SN allocated by the first access network device for the first bearer, and the length of the downlink PDCP SN allocated by the first access network device for the first bearer, that is, the first connection
  • the network device allocates the first PDCP SN length for the uplink PDCP SN length and the downlink PDCP SN length of the first bearer.
  • the first PDCP SN length in the configuration message is used to indicate a PDCP SN length.
  • the first PDCP SN length in the configuration message is used to indicate two different PDCP SN lengths (that is, an uplink PDCP SN length and a downlink PDCP SN length), where the two different PDCP SN lengths are respectively
  • the access network device is configured with the uplink PDCP SN length and the downlink PDCP SN length configured for the first bearer.
  • the first access network device is capable of transmitting, to the terminal device, at least one trigger condition associated with the in-flight PDCP SDU, such that the terminal device acquires the at least one trigger condition associated with the in-flight PDCP SDU .
  • the terminal device determines that the current scenario meets one of the at least one triggering condition, the terminal device sends a feedback message to the first access network device, so that the first access network device is the first bearer according to the feedback message.
  • the uplink PDCP SN length is allocated, and then a configuration message is sent to the terminal device.
  • the first access network device can store the corresponding relationship between multiple triggering conditions and multiple PDCP SN lengths.
  • the first access network device can receive the feedback message according to the feedback message. Determining the trigger condition that the PDCP SDU in flight meets, and in the corresponding relationship between the multiple trigger conditions and the multiple PDCP SN lengths, the PDCP SDU length corresponding to the trigger condition that the PDCP SDU in the flight meets is allocated as the first bearer. Uplink PDCP SDU length (the first PDCP SN length in the configuration message is used to indicate the allocated uplink PDCP SN length).
  • the terminal device after the RLC layer adopts the AM mode, after the terminal device sends the uplink PDCP SDU to the first access network device, if the first access network device receives the uplink PDCP SDU, the first access network The device sends a status report to the terminal device through the RLC layer, and the terminal device can determine whether the uplink PDCP SDU is successfully sent by using the status report, where the terminal device has sent to the first access network device and the first access network device does not acknowledge.
  • the uplink PDCP SDU that is successfully transmitted is: the in-flight PDCP SDU of the terminal device.
  • the at least one triggering condition includes at least one of the following triggering conditions: the number of in-flight PDCP SDUs of the terminal device is less than a first threshold; and the number of in-flight PDCP SDUs of the terminal device is greater than a second threshold, The first threshold and the second threshold are both the number of PDCP SDUs.
  • the terminal device can compare the number of in-flight PDCP SDUs of the terminal device (or the number of in-flight PDCP SDUs of the terminal device in the preset time period) with the first threshold and the second threshold to determine in real time to determine Whether the number of PDCP SDUs in flight (or the number of in-flight PDCP SDUs of the terminal device in a preset time period) is less than a first threshold or greater than a second threshold, thereby determining the number of PDCP SDUs in flight A trigger condition of at least one trigger condition is met. Once the number of in-flight PDCP SDUs meets a certain trigger condition, the terminal device can send a feedback message to the first access network device.
  • the feedback message includes: the number of in-flight PDCP SDUs that satisfy the certain trigger condition, or the identifier of the certain trigger condition.
  • the at least one trigger condition includes at least one of the following trigger conditions: the data volume of the PDCP SDU in the flight of the terminal device is less than a third threshold; the data volume of the PDCP SDU in the flight of the terminal device is greater than the fourth threshold,
  • the third threshold and the fourth threshold are both data quantities of the PDCP SDU.
  • the terminal device needs to compare the data amount of the PDCP SDU in flight of the terminal device (or the data amount of the PDCP SDU in flight in the preset time period) with the third threshold and the fourth threshold to determine in real time to determine Whether the data amount of the PDCP SDU in flight (or the amount of data of the PDCP SDU in flight during the preset time period of the terminal device) satisfies any trigger condition, once the data amount of the PDCP SDU in flight satisfies a certain trigger condition
  • the terminal device sends a feedback message to the first access network device, where the feedback message includes: an amount of data of the in-flight PDCP SDU that satisfies the certain trigger condition, or an identifier of the certain trigger condition.
  • the data volume of the PDCP SDU in the embodiment of the present invention refers to the number of bytes of the PDCP SDU.
  • the first access network device is also capable of allocating a downlink PDCP SN length for the first bearer.
  • the first access network device can self-count the downlink throughput of the first bearer, for example, by counting the number of data packets or the amount of data in the flight of the first access network device, determining the downlink throughput of the first bearer. If the downlink throughput is larger, the downlink PDCP SN length of the first bearer needs to be re-allocated to ensure that the downlink PDCP SN length of the first bearer is increased when the downlink throughput is large. When the downlink throughput is small, the downlink PDCP SN length of the first bearer is reduced.
  • the uplink PDCP SN length indicated by the first PDCP SN length allocated by the first access network device for the first bearer is positively correlated with the uplink throughput
  • the indicated downlink PDCP SN length is positively correlated with the downlink throughput
  • the uplink throughput is The number of in-flight data packets of the terminal device is positively correlated
  • the downlink throughput is positively correlated with the number of in-flight data packets of the first access network device. That is, when the number of in-flight data packets of the terminal device is large, the uplink throughput of the terminal device is large.
  • the first access network device is allocated to the first device.
  • the length of the uplink PDCP SN carried by the bearer is large, so that the terminal device can send more data packets at a time.
  • the uplink throughput of the terminal device is small.
  • the first access network device allocates to the first The length of a bearer's uplink PDCP SN is small, reducing the waste of bits in the PDCP SN in the data packet.
  • the downlink throughput of the first access network device is large.
  • the downlink PDCP SN allocated by the access network device to the first bearer has a large length, so that the first access network device can send more data packets at a time.
  • the downlink throughput of the first access network device is small.
  • the downlink PDCP SN allocated by the access network device to the first bearer is of a small length, reducing the waste of bits in the PDCP SN in the data packet.
  • the terminal device or the first access network device when the terminal device or the first access network device has less data to be transmitted, a shorter PDCP SN length (requiring a small number of bits) can distinguish less data, but currently, the terminal device or the An access network device still allocates a fixed-length (relatively long) PDCP SN for each data (requiring more bits). Therefore, the PDCP SN in the PDCP SDU is longer, and the bits of the PDCP SN need to be occupied. A large number, resulting in the waste of bits.
  • the terminal device or the first access network device When the terminal device or the first access network device has more data to be sent, the terminal device or the first access network device still allocates a fixed length (relatively short) PDCP SN for each data, and the fixed length can only A part of the data to be sent is distinguished. Therefore, the terminal device or the first access network device can only transmit a part of data to be transmitted during a data transmission process, and the efficiency of the data transmission cannot meet the requirement.
  • the access network device can send a configuration message to the terminal device to instruct the terminal device to reconfigure the length of the first PDCP SN for the first bearer that has been established, and adjust the length of the PDCP SN of the first bearer.
  • the terminal device can transmit data by reconfiguring the first bearer after the length of the PDCP SN.
  • the uplink PDCP SN length and the downlink PDCP SN length allocated by the access network device to the first bearer can satisfy the situation that the data packet is more and less, thereby avoiding the waste of the bit in the PDCP SN when the data packet is small. And when there are many data packets, the data transmission efficiency is low.
  • Step 902 The terminal device reconfigures the PDCP SN length of the first bearer to the first PDCP SN length according to the configuration message.
  • the terminal device and the first access network device respectively maintain a count value (English: COUNT), and under normal circumstances, the count value maintained by the terminal device is equal to the count value maintained by the first access network device, that is, The count value maintained by the terminal device is synchronized with the count value maintained by the first access network device.
  • the count value is composed of a PDCP SN and a start frame number (English: Hyper Frame Number; HFN for short), that is, the high bit of the count value is HFN, and the low bit of the count value is PDCP SN.
  • each count value corresponds to one PDCP SN and one HFN.
  • the configuration message sent by the first access network device further includes the validity information of the first PDCP SN, where the validation information is used to indicate the target count value, and the validation information includes at least one of a PDCP SN, an HFN, and a count value.
  • the effective information includes the PDCP SN
  • the target count value indicated by the validation information is a count value corresponding to the PDCP SN
  • the validation information includes the HFN
  • the target count value indicated by the validation information is: the HFN and the PDCP SN are The count value at 0; when the effective information includes the count value, the target count value indicated by the validation information is the count value in the validation information.
  • the terminal device After receiving the configuration message, the terminal device can determine the first PDCP SN and the target count value according to the configuration message, and reconfigure the first PDCP for the first bearer when the count value maintained by the terminal device is changed to the target count value. SN length.
  • the terminal device can determine the first PDCP SN and the target count value according to the configuration message, and when the count value maintained by the terminal device is changed to the next count value of the target count value, A bearer reconfigures the first PDCP SN length.
  • the first access network device is further configured to instruct the terminal device to turn off the count value, the cutoff count value is located after the target count value, and there are multiple count values between the target count value, and the count value maintained by the terminal device becomes When the count value is off, the terminal device can reconfigure the original (that is, the first bearer configuration before step 902) PDCP SN length for the first bearer.
  • Step 903 The first access network device sends a handover request message to the second access network device, where the handover request message includes the first lossless handover identifier.
  • the first access network device When the terminal device establishes a bearer (such as a first bearer) with the first access network device, and communicates through the established bearer, the first access network device can switch with the second access network device.
  • the first access network device is configured to generate a handover request message, where the handover request message includes: a first lossless handover identifier and first configuration information, where the first configuration information is used to indicate a current PDCP SN length of the first bearer. .
  • the first lossless handover identifier, the second lossless handover identifier, and the third lossless handover identifier are used to indicate that no data loss is performed, and after the second access network device receives the first lossless handover identifier, even if the second access network
  • the device cannot support the current PDCP SN length of the first bearer, and the second access network device cannot trigger the terminal device to perform the full configuration switch in the related art, but performs step 904 in the embodiment of the present invention.
  • the current PDCP SN length of the first bearer indicated by the first configuration information is one PDCP SN length, that is, the current uplink PDCP SN length of the first bearer is the same as the current downlink PDCP SN length; or the current PDCP SN length.
  • the two PDCP SN lengths are respectively the current uplink PDCP SN length and the current downlink PDCP SN length, and the current uplink PDCP SN length is different from the current downlink PDCP SN length.
  • a case where the current PDCP SN length is one PDCP SN length is taken as an example for description.
  • Step 904 The second access network device sends a handover confirmation message to the first access network device according to the handover request message, where the handover confirmation message includes a transparent container information element and a second lossless handover identifier outside the transparent container information element, and the transparent container
  • the information element includes a third lossless handover identifier.
  • the second access network device After the second access network device receives the handover request message sent by the first access network device, if the second access network device allows access to the terminal device, the second access network device can access the first access network device.
  • Send a handover confirmation message For example, as shown in FIG. 11, the handover confirmation message includes: capability information, a transparent container information element, and a second lossless handover identifier located outside the transparent container information element, and the transparent container information element includes: capability information, second configuration information. And a third lossless switching identifier.
  • the capability information is used to indicate whether the second access network device can support the current PDCP SN length of the first bearer, and when the capability information indicates that the second access network device cannot support the current PDCP SN length of the first bearer,
  • the handover confirmation message further includes: second configuration information indicating a length of the target PDCP SN allocated by the second access network device to the second bearer.
  • the target PDCP SN length is a PDCP SN length that the second access network device can support
  • the second bearer is a bearer between the terminal device and the second access network device.
  • the second access network device can determine whether it can support the current uplink PDCP SN length and the current downlink PDCP SN length.
  • the capability information is used to indicate whether the second access network device can support the current uplink PDCP of the first bearer.
  • the SN length and the current downlink PDCP SN length of the first bearer is used to indicate whether the second access network device can support the current uplink PDCP of the first
  • Step 905 The first access network device sends a handover command to the terminal device, where the handover command is a transparent container information element in the handover confirmation message.
  • the first access network device After the first access network device parses the handover confirmation message to obtain the transparent container information element, the first access network device does not parse the transparent container information element, but directly sends the transparent container information element as a handover command to the terminal device.
  • Step 906 The first access network device forwards the cache data of the first access network device to the second access network device according to the handover confirmation message.
  • the cached data on the first access network device includes: a downlink PDCP SDU that has been sent by the first access network device and has not been successfully sent, a downlink PDCP SDU that has been allocated a PDCP SN and is not transmitted, and downlink new data that is not allocated a PDCP SN. And an uplink PDCP SDU that is sent by the terminal device and has not been uploaded to the core network.
  • step 906 includes:
  • Step 9061 The first access network device determines, according to the capability information in the handover confirmation message, whether the second access network device can support the current PDCP SN length of the first bearer. If the second access network device can support the current PDCP SN length of the first bearer, step 9062 is performed; if the second access network device cannot support the current PDCP SN length of the first bearer, step 9063 is performed.
  • the first access network device first parses the handover confirmation message, and obtains capability information, a transparent container information element, and a second lossless handover identifier, and determines, according to the capability information, whether the second access network device can support the first The current PDCP SN length carried.
  • the capability information is 1 or 0.
  • the first access network device determines that the second access network device can support the current PDCP SN length of the first bearer.
  • the capability information is 0, The first access network device determines that the second access network device cannot support the current PDCP SN length of the first bearer.
  • the capability information is true (English: true) or false (English: false), and true corresponds to the first access network device determining that the second access network device can support the current PDCP SN length of the first bearer, and corresponding to false The first access network device determines that the second access network device cannot support the current PDCP SN length of the first bearer.
  • the second access network device can determine that it can support the PDCP SN of the first bearer. That is, as long as the PDCP SN length used by the current bearer is within the PDPC SN length set that the second access network device can support, it is considered that the second access network device can support the PDCP SN length of the first bearer.
  • Step 9062 The first access network device forwards the buffer data of the first access network device to the second access network device, and the receiving status element of the uplink PDCP SDU constructed according to the current PDCP SN length of the first bearer.
  • the first access network device determines that the second access network device can support the current PDCP SN length of the first bearer
  • the first access network device can forward the cached data of the first access network device to the second access Network access equipment.
  • the second access network device can determine the first bearer according to the first configuration information, because the first configuration information is included in the handover request message sent by the first access network device to the second access network device in step 903.
  • the current PDCP SN length and after receiving the buffered data, can parse the received cached data according to the current PDCP SN length of the first bearer in the first configuration information.
  • the first access network device can also construct an uplink PDCP SDU according to the current PDCP SN length of the first bearer (that is, the terminal device sends the A reception status element of the PDCP SDU) and transmitting the reception status element to the second access network device.
  • Step 9063 The first access network device forwards, to the second access network device, a first PDCP SDU in the cached data of the first access network device, and a receiving status element of the uplink PDCP SDU configured according to the target PDCP SN length, where The PDCP SN in the first PDCP SDU is less than or equal to the maximum PDCP SN corresponding to the target PDCP SN length.
  • the first access network device can determine the first PDCP SDU in the cached data of the first access network device. It should be noted that the first PDCP SDU is the cached data of the first access network device, and the PDCP SN is less than or equal to the maximum PDCP SN corresponding to the target PDCP SN length.
  • the embodiment of the present invention interprets the maximum PDCP SN corresponding to the target PDCP SN by using the target PDCP SN length of 2:
  • the target PDCP SN length is 2
  • the PDCP SN corresponding to the target PDCP SN length includes the following binary digits: 00, 01, 10, and 11, wherein the maximum PDCP SN corresponding to the target PDCP SN length is a binary number 11.
  • the first access network device cancels the highest n-bit of the PDCP SN in each first PDCP SDU, and obtains the first PDCP SN after canceling the n-bit, where n is the current PDCP SN length and target of the first bearer. The difference in PDCP SN length. Finally, the first access network device forwards the first PDCP SN after canceling n bits to the second access device.
  • the first access network device needs to construct a receiving state element of the uplink PDCP SDU according to the target PDCP SN length, and the receiving state is The element is sent to the second access network device.
  • the data other than the first PDCP SN in the cache data of the first access network device includes: a PDCP SDU to which the PDCP SN has been allocated and downlink new data to which the PDCP SN is not allocated.
  • the first access network device is further capable of canceling the PDCP SN in the PDCP SDU to which the PDCP SN has been allocated, obtaining the data portion in the PDCP SDU of the allocated PDCP SN, and obtaining the obtained data portion and the unassigned PDCP SN.
  • the new data is forwarded together to the second access network device.
  • the second access network device can determine whether the second access network device can support the current uplink PDCP of the first bearer. SN length and current downlink PDCP SN length, the capability information is used to indicate whether the second access network device can support the current uplink PDCP SN length of the first bearer and whether the second access network device can support the current downlink PDCP of the first bearer SN length. Since the cached data that the first access network device needs to forward to the second access network device includes both uplink data and downlink data, the first access network device forwards the cached data to the second access network device in step 906.
  • the first access network device can separately transmit the uplink data and the downlink data in the cached data, that is, perform the method shown in step 9061 to step 9063 for the uplink data in the cached data, for the downlink data in the cached data.
  • the method shown in steps 9061 to 9063 is performed.
  • Step 907 The terminal device performs no data loss switching between the first access network device and the second access network device according to the handover command.
  • step 907 includes:
  • Step 9071 The terminal device determines, according to the capability information in the handover command, whether the second access network device can support the current PDCP SN length of the first bearer. If the second access network device can support the current PDCP SN length of the first bearer, Then, step 9072 is performed; if the second access network device cannot support the current PDCP SN length of the first bearer, step 9075 is performed.
  • the terminal device first parses the handover command, obtains the capability information, the second configuration information, and the third lossless handover identifier, and determines, according to the capability information, whether the second access network device can support the current PDCP SN length of the first bearer. .
  • Step 9072 The terminal device and the second access network device establish a second bearer configured with a first PDCP SN length. Go to step 9073.
  • the terminal device can establish a second bearer with the second access network device, and configure the current bearer's current PDCP SN for the second bearer. length.
  • Step 9073 The terminal device sends, to the second access network device, a PDCP SDU to which the PDCP SN has been allocated in the buffer data of the terminal device, and a reception status report of the downlink PDCP SDU configured according to the PDCP SN length of the first bearer. Go to step 9074.
  • the cached data in the terminal device includes: an uplink PDCP SDU that the terminal device has sent and has not confirmed the successful transmission, an uplink PDCP SDU that has been allocated the PDCP SN and is not transmitted, and uplink new data that is not allocated the PDCP SN.
  • the terminal device can forward the PDCP SDUs of the allocated buffered data of the terminal device to the second access network device.
  • the second access network device can receive the first configuration information in the handover request message sent by the first access network device to the second access network device in step 903.
  • the SDU of the PDCP SN in the current PDCP SN length parsing cache data of the first bearer in the configuration information is obtained, and the data part in the SDU is obtained.
  • the first access network device forwards the receiving status element of the uplink PDCP SDU to the second access network device, and after step 906, the second access network device can further parse the uplink PDCP.
  • the receiving status element of the SDU obtains the receiving status report of the uplink PDCP SDU, and sends the receiving status report of the uplink PDCP SDU to the terminal device.
  • the terminal device is further configured to determine, according to the receiving status report of the uplink PDCP SDU sent by the second access network device, the uplink PDCP SDU that has been sent and confirmed to be successfully sent, and the terminal device sends the buffer to the second access network device.
  • the terminal device When the uplink PDCP SDU of the allocated PDCP SN in the data is transmitted, only the PDCP SN that has been allocated the PDCP SN and not transmitted and the uplink PDCP SDU that has been sent and not successfully transmitted are transmitted, and the retransmission of the PDCP SDU is reduced. If the terminal device does not receive the reception status report of the uplink PDCP SDU sent by the second access network device, the terminal device can send all PDCP SDUs of the allocated PDCP SN in the buffer data of the terminal device to the second access network. device.
  • the terminal device can also construct the downlink PDCP SDU according to the current PDCP SN length of the first bearer in step 9073 (that is, the original first connection) The receiving status report of the downlink PDCP SDU sent by the network access device, and sending the receiving status report to the second access network device.
  • Step 9074 After confirming that the PDCP SDUs of the PDCP SN that have been allocated in the buffered data of the terminal device are successfully sent to the second access network device, the terminal device configures the target PDCP SN length for the second bearer.
  • the terminal device After confirming that the PDCP SDUs of the PDCP SN that have been allocated in the buffered data of the terminal device are successfully sent to the second access network device, the terminal device can reconfigure the target PDCP SN length for the second bearer. Then, the PDCP SN can be allocated to the new data on the terminal device according to the target PDCP SN length to obtain the PDCP SDU, and the PDCP SDU is sent to the second access network device by using the second bearer configured with the target PDCP SN length.
  • the terminal device can determine, according to the receiving status report of the uplink PDCP SDU sent by the second access access network device, whether the PDCP SDUs of the allocated PDCP SN in the buffer data of the terminal device are successfully sent to the second access network device.
  • the terminal device is further configured to receive the handover count value sent by the second access access network device, and is the second bearer when the count value maintained by the terminal device becomes the handover count value. Configure the target PDCP SN length.
  • Step 9075 The terminal device and the second access network device establish a second bearer configured with a target PDCP SN length. Go to step 9076.
  • the terminal device When the terminal device confirms that the second access network device cannot support the current PDCP SN length of the first bearer, the terminal device can establish a second bearer with the second access network device, and configure the second access network device for the second bearer.
  • the target PDCP SN that can be supported.
  • Step 9076 The terminal device forwards, to the second access network device, the second PDCP SDU in the buffer data of the terminal device, and the receiving status element of the downlink PDCP SDU configured according to the target PDCP SN length, where the PDCP in the second PDCP SDU The SN is less than or equal to the maximum PDCP SN corresponding to the target PDCP SN length.
  • the cached data in the terminal device includes: an uplink PDCP SDU that the terminal device has sent and has not confirmed the successful transmission, an uplink PDCP SDU that has been allocated the PDCP SN and is not transmitted, and uplink new data that is not allocated the PDCP SN.
  • the terminal device determines the second PDCP SDU in the cached data of the terminal device, and the second PDCP SDU is the terminal device.
  • the PDCP SN is less than or equal to the PDCP SDU of the largest PDCP SN corresponding to the target PDCP SN length.
  • the terminal device cancels the highest n-bit of the PDCP SN in each second PDCP SDU, and obtains the second PDCP SN after canceling the n-bit, where n is the current PDCP SN length of the first bearer and the target PDCP SN length. difference.
  • the terminal device sends the second PDCP SN after canceling n bits to the second access device.
  • the terminal device since the second access network device cannot support the current PDCP SN length of the first bearer, the terminal device needs to construct a receiving status report of the downlink PDCP SDU according to the target PDCP SN length, that is, the first lost SN.
  • the length of the :first missing sn;FMS) is the target PDCP SN length
  • the length of the bit mask (English:bitmask) is also the target PDCP SN length
  • the receiving status report is sent to the second access network device.
  • the data other than the second PDCP SN in the buffer data of the terminal device may include: a PDCP SDU to which the PDCP SN has been allocated and uplink new data to which the PDCP SN is not allocated.
  • the terminal device is further configured to cancel the PDCP SN in the uplink PDCP SDU of the allocated PDCP SN, obtain the data part in the uplink PDCP SDU of the allocated PDCP SN, and obtain the uplink of the obtained data part and the unassigned PDCP SN.
  • the new data is sent together as new data to the second access network device (eg, the PDCP SN is allocated for the new data according to the target PDCP SN length, the uplink PDCP SDU is obtained, and the uplink PDCP SDU is sent to the second access network device).
  • the second access network device eg, the PDCP SN is allocated for the new data according to the target PDCP SN length, the uplink PDCP SDU is obtained, and the uplink PDCP SDU is sent to the second access network device.
  • the first access network device when the terminal device establishes the first bearer with the first access network device, the first access network device can instruct the terminal device to reconfigure the PDCP SN for the first bearer. length. After the second device is established by the terminal device and the second access network device, the second access network device can also instruct the terminal device to reconfigure the PDCP SN length for the second bearer, and the process of the configuration is referred to. Step 901 to step 902.
  • the handover request received by the second access network device, the handover confirmation message received by the first access network device, and the transparent container information received by the terminal device are Each element includes a lossless transmission identifier, and the lossless transmission identifier is used to indicate that no data loss is performed, so that full configuration is prevented when the terminal device is switched from the first access network device to the second access network device. Switching prevents the occurrence of cache data loss.
  • FIG. 14 is a schematic structural diagram of a first type of switching device 140 according to an embodiment of the present invention.
  • the switching device 140 is the first access network device in FIG. 1. As shown in FIG. 14, the switching device 140 includes:
  • the first sending module 1401 is configured to send a handover request message to the second access network device, where the handover request message includes: a first lossless handover identifier;
  • the receiving module 1402 is configured to receive a handover confirmation message sent by the second access network device, where the handover confirmation message includes a transparent container information element and a second lossless handover identifier located outside the transparent container information element, where the transparent container information element includes a third lossless handover Identification
  • the second sending module 1403 is configured to send the transparent container information element as a handover command to the terminal device;
  • the first lossless handover identifier, the second lossless handover identifier, and the third lossless handover identifier are used to indicate that the handover without data loss is performed.
  • the handover request message further includes: first configuration information used to indicate a current PDCP SN length of the first bearer;
  • the handover confirmation message further includes: capability information indicating whether the second access network device can support the current PDCP SN length of the first bearer, and switching when the capability information indicates that the second access network device cannot support the current PDCP SN length.
  • the acknowledgement message further includes: second configuration information indicating a length of the target PDCP SN allocated by the second access network device to the second bearer;
  • the first bearer is a bearer between the terminal device and the first access network device
  • the second bearer is a bearer between the terminal device and the second access network device.
  • FIG. 15 is a schematic structural diagram of a second type of switching device 140 according to an embodiment of the present invention. As shown in FIG. 15, the switching device 140 further includes:
  • the first forwarding module 1404 is configured to: when the capability information in the handover confirmation message indicates that the second access network device cannot support the current PDCP SN length, forward the data to the second access network device: the cache data of the first access network device.
  • the first PDCP service data unit SDU, the PDCP SN in the first PDCP SDU is less than or equal to the maximum PDCP SN corresponding to the target PDCP SN length.
  • FIG. 16 is a schematic structural diagram of a third type of switching device 140 according to an embodiment of the present invention. As shown in FIG. 16, the switching device 140 further includes:
  • the constructing module 1405 is configured to construct a receiving state element of the uplink PDCP SDU according to the target PDCP SN length when the capability information in the handover confirm message indicates that the second access network device cannot support the current PDCP SN length;
  • the second forwarding module 1406 is configured to forward the receiving status element of the uplink PDCP SDU to the second access network device.
  • FIG. 17 is a schematic structural diagram of a fourth switching device 140 according to an embodiment of the present invention. As shown in FIG. 17, the switching device 140 further includes:
  • the third sending module 1407 is configured to send a configuration message to the terminal device, where the configuration message includes: the first access network device is a first PDCP SN length allocated by the first access network device and the first bearer that the terminal device has established.
  • the PDCP SN length of the first bearer includes: an uplink PDCP SN length and a downlink PDCP SN length.
  • the configuration message further includes an effective information, where the effective information is used to indicate a target count value.
  • the validation information includes at least one of a PDCP SN, a start frame number HFN, and a count value.
  • the handover confirmation message sent by the second access network device of the first sending module box, the handover confirmation message received by the receiving module, and the second sending module are sent to the terminal device.
  • the transparent container information element includes a lossless transmission identifier, and the lossless transmission identifier is used to indicate that the data loss is not performed, so that when the terminal device is switched from the first access network device to the second access network device, Perform a full configuration switch to prevent cache data loss.
  • FIG. 18 is a schematic structural diagram of a fifth type of switching device according to an embodiment of the present invention.
  • the switching device 180 is the terminal device in FIG. 1. As shown in FIG. 18, the switching device 180 includes:
  • the first receiving module 1801 is configured to receive a handover command sent by the first access network device, where the handover command is a transparent container information element in the handover confirmation message, the transparent container information element includes a third lossless handover identifier, and the first lossless handover identifier, The second lossless handover identifier and the third lossless handover identifier are used to indicate that the handover without data loss is performed;
  • the switching module 1802 is configured to perform data lossless switching between the first access network device and the second access network device according to the handover command.
  • the transparent container information element further includes: capability information indicating whether the second access network device can support the current PDCP SN length of the first bearer, and indicating that the second access network device is allocated to the second bearer
  • capability information indicating whether the second access network device can support the current PDCP SN length of the first bearer, and indicating that the second access network device is allocated to the second bearer
  • the second configuration information of the target PDCP SN length, the first bearer is a bearer between the terminal device and the first access network device, and the second bearer is a bearer between the terminal device and the second access network device;
  • the switching module 1802 is further configured to: when the capability information in the transparent container information element indicates that the second access network device cannot support the current PDCP SN length, configure the target PDCP SN length for the second bearer;
  • the second access network device Sending, to the second access network device, the second PDCP SDU in the buffered data of the terminal device, where the PDCP SN in the second PDCP SDU is less than or equal to the maximum PDCP SN corresponding to the target PDCP SN length.
  • the switching module 1802 is further configured to:
  • the capability information in the transparent container information element indicates that the second access network device cannot support the current PDCP SN length, construct a reception status report of the downlink PDCP SDU according to the target PDCP SN length;
  • the transparent container information element further includes: capability information indicating whether the second access network device can support the current PDCP SN length of the first bearer, and indicating that the second access network device is allocated to the second bearer
  • capability information indicating whether the second access network device can support the current PDCP SN length of the first bearer, and indicating that the second access network device is allocated to the second bearer
  • the second configuration information of the target PDCP SN length, the first bearer is a bearer between the terminal device and the first access network device, and the second bearer is a bearer between the terminal device and the second access network device
  • the switching module 1802 Also used for:
  • the capability information in the transparent container information element indicates that the second access network device can support the current PDCP SN length, configure the current PDCP SN length for the second bearer;
  • the target PDCP SN length is configured for the second bearer.
  • the switching module 1802 is further configured to:
  • the capability information in the transparent container information element indicates that the second access network device can support the current PDCP SN length
  • FIG. 19 is a schematic structural diagram of a sixth type of switching device according to an embodiment of the present invention. As shown in FIG. 19, the switching device 180 further includes:
  • the second receiving module 1803 is configured to receive a configuration message sent by the first access network device, where the configuration message includes: the first access network device is the first allocated by the first access network device and the first bearer that the terminal device has established. PDCP SN length;
  • the reconfiguration module 1804 is configured to: the terminal device reconfigures the first PDCP SN length for the first bearer according to the configuration message.
  • the PDCP SN length of the first bearer includes: an uplink PDCP SN length and a downlink PDCP SN length.
  • FIG. 20 is a schematic structural diagram of a seventh type of switching device according to an embodiment of the present invention. As shown in FIG. 20, the switching device 180 further includes:
  • the obtaining module 1805 is configured to acquire at least one trigger condition related to the PDCP SDU in flight, where the PDCP SDU in the flight is an uplink PDCP SDU that has been sent by the terminal device and is not confirmed to be successfully sent;
  • the determining module 1806 is configured to determine whether the number of PDCP SDUs in flight meets any trigger condition
  • the sending module 1807 is configured to send a feedback message to the first access network device when the number of the PDCP SDUs in flight meets a certain trigger condition.
  • the at least one trigger condition includes at least one of the following trigger conditions:
  • the number of PDCP SDUs in flight of the terminal device is less than a first threshold
  • the number of in-flight PDCP SDUs of the terminal device is greater than a second threshold.
  • the configuration message further includes an effective information, where the effective information is used to indicate a target count value, and the reconfiguration module 1804 is further configured to:
  • the first PDCP SN length is configured for the first bearer according to the configuration information
  • the first PDCP SN length is configured for the first bearer according to the configuration information.
  • the validation information includes at least one of a PDCP SN, a start frame number HFN, and a count value.
  • the switching command received by the first receiving module is a transparent container information element in the switching confirmation message
  • the transparent container information element includes a lossless transmission identifier
  • the The lossless transmission identifier is used to indicate that the data loss is not performed, so that the full configuration switching is prevented when the terminal device is switched from the first access network device to the second access network device, thereby preventing the occurrence of the cache data loss.
  • FIG. 21 is a schematic structural diagram of an eighth switching device according to an embodiment of the present disclosure.
  • the switching device 210 is the second access network device in FIG. 1. As shown in FIG. 21, the switching device 210 includes:
  • the first receiving module 2101 is configured to receive a handover request message sent by the first access network device, where the handover request message includes: a first lossless handover identifier;
  • the sending module 2102 is configured to send, according to the handover request message, a handover confirmation message to the first access network device, where the handover confirmation message includes a transparent container information element and a second lossless handover identifier located outside the transparent container information element, where the transparent container information element includes Third lossless switching identifier;
  • the first lossless handover identifier, the second lossless handover identifier, and the third lossless handover identifier are used to indicate that the handover without data loss is performed.
  • the handover request message further includes: first configuration information used to indicate a current PDCP SN length of the first bearer;
  • the handover confirmation message further includes: capability information indicating whether the second access network device can support the current PDCP SN length, and when the capability information indicates that the second access network device cannot support the current PDCP SN length, the handover confirmation message further includes : second configuration information for indicating a length of the target PDCP SN allocated by the second access network device to the second bearer;
  • the first bearer is a bearer between the terminal device and the first access network device
  • the second bearer is a bearer between the terminal device and the second access network device.
  • FIG. 22 is a schematic structural diagram of a ninth switching device according to an embodiment of the present disclosure. As shown in FIG. 22, the switching device 210 further includes:
  • the second receiving module 2103 is configured to receive, by the first access network device, a first PDCP SDU in the cached data of the first access network device, where the PDCP SN in the first PDCP SDU is less than or equal to the target PDCP SN length. Corresponding maximum PDCP SN.
  • FIG. 23 is a schematic structural diagram of a tenth type of switching device according to an embodiment of the present invention. As shown in FIG. 23, on the basis of FIG. 22, the switching device 210 further includes:
  • the third receiving module 2104 is configured to receive a receiving status element of the uplink PDCP SDU forwarded by the first access network device, where the receiving status element of the uplink PDCP SDU is configured according to the target PDCP SN length.
  • FIG. 24 is a schematic structural diagram of a switch device according to an eleventh embodiment of the present invention. As shown in FIG. 24, on the basis of FIG. 23, the switch device 210 further includes:
  • the fourth receiving module 2105 is configured to receive a second PDCP SDU in the buffered data of the terminal device that is sent by the terminal device, where the PDCP SN in the second PDCP SDU is less than or equal to the maximum PDCP SN corresponding to the target PDCP SN length.
  • FIG. 25 is a schematic structural diagram of a twelfth type of switching device according to an embodiment of the present invention. As shown in FIG. 25, the switching device 210 further includes:
  • the fifth receiving module 2106 is configured to receive a receiving status report of the downlink PDCP SDU sent by the terminal device, where the receiving status report of the downlink PDCP SDU is configured according to the target PDCP SN length.
  • FIG. 26 is a schematic structural diagram of a thirteenth switching device according to an embodiment of the present invention. As shown in FIG. 26, on the basis of FIG. 21, the switching device 210 further includes:
  • the sixth receiving module 2107 is configured to receive a PDCP SDU that has been allocated a PDCP SN in the cache data of the terminal device that is sent by the terminal device.
  • FIG. 27 is a schematic structural diagram of a fourteenth type of switching device according to an embodiment of the present invention. As shown in FIG. 27, the switching device 210 further includes:
  • the seventh receiving module 2108 is configured to receive a receiving status report of the downlink PDCP SDU sent by the terminal device, where the receiving status report of the downlink PDCP SDU is configured according to the current PDCP SN length.
  • the handover request message received by the first receiving module and the handover request message sent by the sending module both include a lossless handover identifier, and the lossless transmission identifier is used to indicate that no data is performed.
  • the switching of the loss prevents the full configuration switching when the terminal device is switched from the first access network device to the second access network device, thereby preventing the occurrence of cache data loss.
  • FIG. 28 is a schematic structural diagram of a bearer configuration device according to an embodiment of the present invention.
  • the bearer configuration device 280 is a first access network device in the communication system B shown in FIG. 2, and the bearer configuration is as shown in FIG. Device 280 includes:
  • the sending module 2801 is configured to send a configuration message to the terminal device, where the configuration message includes: the first access network device is a first PDCP SN length allocated by the first access network device and the first bearer that the terminal device has established.
  • the sending module can send a configuration message to the terminal device to instruct the terminal device to reconfigure the first PDCP SN length for the established first bearer. That is, the PDCP SN length of the bearer configuration that has been established in the embodiment of the present invention can be adjusted.
  • the first access network device has a shorter configuration for the first bearer. The length of the PDCP SN, thereby reducing the length of the PDCP SN in the PDCP SDU sent by the terminal device, and reducing the waste of the bit.
  • FIG. 29 is a schematic structural diagram of another bearer configuration device according to an embodiment of the present disclosure.
  • the bearer configuration device 290 is a terminal device in the communication system B shown in FIG. 2. As shown in FIG. 29, the bearer configuration device 290 includes :
  • the receiving module 2901 is configured to receive a configuration message sent by the first access network device, where the configuration message includes: the first access network device is a first PDCP SN allocated by the first access network device and the first bearer established by the terminal device. length;
  • the reconfiguration module 2902 is configured to reconfigure the first PDCP SN length for the first bearer according to the configuration message.
  • the receiving module can receive the first access network device to send a configuration message to the terminal device, and the reconfiguration module can perform the first bearer according to the configuration message.
  • Reconfigure the first PDCP SN length That is, the PDCP SN length of the bearer configuration that has been established in the embodiment of the present invention can be adjusted.
  • the first access network device has a shorter configuration for the first bearer. The length of the PDCP SN, thereby reducing the length of the PDCP SN in the PDCP SDU sent by the terminal device, and reducing the waste of the bit.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product comprising one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a readable storage medium of a computer or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data
  • the center transmits to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state hard disk) or the like.
  • the embodiment of the method provided by the embodiment of the present invention can refer to the corresponding device embodiment, which is not limited by the embodiment of the present invention.
  • the sequence of the steps of the method embodiments of the present invention can be appropriately adjusted, and the steps can be correspondingly increased or decreased according to the situation. Any person skilled in the art can easily think of the technical scope disclosed in the embodiments of the present invention. The method of the change should be included in the scope of protection of the embodiments of the present invention, and therefore will not be described again.
  • the program can be stored in a computer readable storage medium.
  • the storage medium mentioned is a read only memory, a magnetic disk or an optical disk or the like.

Abstract

本申请公开了一种设备切换方法及设备、承载配置方法及设备、通信系统，属于通信技术领域。所述方法包括：第一接入网设备向第二接入网设备发送切换请求消息，切换请求消息包括：第一无损切换标识；第一接入网设备接收第二接入网设备发送的切换确认消息，切换确认消息包括透明容器信息元素和位于透明容器信息元素外的第二无损切换标识，透明容器信息元素包括第三无损切换标识；第一接入网设备将透明容器信息元素作为切换命令发送给终端设备；其中，无损切换标识用于指示进行无数据损失的切换。本申请解决了切换过程中网络设备和终端设备已发送且未确认发送成功的数据会丢失的问题，即防止了缓存数据丢失的情况发生，本申请用于通信系统。

Description

设备切换方法及设备、承载配置方法及设备、通信系统
本申请要求于2017年2月3日提交中国专利局、申请号为201710063477.8、发明名称为“设备切换方法及设备、承载配置方法及设备、通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种设备切换方法及设备、承载配置方法及设备、通信系统。
背景技术
随着通信技术的发展，长期演进(英文：Long Time Evolution；简称：LTE)通信系统得到了广泛的应用，LTE通信系统包括终端设备和接入网设备。
目前，终端设备与第一接入网设备建立第一承载，终端设备通过第一承载与第一接入网设备通信。终端设备在与第一接入网设备建立第一承载时，第一接入网设备指示终端设备为第一承载配置数据汇聚协议(英文：Packet Data Convergence Protocol；简称：PDCP)序列号(英文：Sequence Number；简称：SN)长度(也即SN的比特位数)。当终端设备需要从第一接入网设备切换至第二接入网设备时，第一接入网设备向第二接入网设备发送切换请求消息，该切换请求消息包括第一承载配置的PDCP SN长度，第二接入网设备根据该切换请求消息判断自己是否能够支持第一承载配置的PDCP SN长度。在第二接入网设备确定自己无法支持第一承载配置的PDCP SN长度时，第二接入网设备通过第一接入网设备触发终端设备进行全配置切换，在终端设备进行全配置切换的过程中，终端设备与第二接入网设备建立第二承载，并为第二承载配置第二接入网设备能够支持的PDCP SN长度，以及将终端设备的缓存数据进行删除。需要说明的是，终端设备上的缓存数据包括终端设备的已发送且未确认发送成功的数据。
由于终端设备在进行全配置切换的过程中，会删除终端设备的缓存数据，因此，在终端设备由第一接入网设备切换至第二接入网设备的过程中，会导致终端设备的已发送且未确认发送成功的数据的丢失。
发明内容
本申请提供了一种设备切换方法及设备、承载配置方法及设备、通信系统，能够解决终端设备的已发送且未确认发送成功的数据会丢失的问题。所述技术方案如下：
第一方面，提供了一种设备切换方法，所述方法包括：第一接入网设备向第二接入网设备发送切换请求消息，所述切换请求消息包括：第一无损切换标识；所述第一接入网设备接收所述第二接入网设备发送的切换确认消息，所述切换确认消息包括透明容器信息元素和位于所述透明容器信息元素外的第二无损切换标识，所述透明容器信息元素包括第三无损切换标识；所述第一接入网设备将所述透明容器信息元素作为切换命令发送给终端设备；其中，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数 据损失的切换。由于第二接入网设备接收到的切换请求、第一接入网设备接收到的切换确认消息以及终端设备接收到的透明容器信息元素中均包含无损传输标识，且该无损传输标识用于指示进行无数据损失的切换，所以，防止了在终端设备由第一接入网设备切换至第二接入网设备时，进行全配置切换，防止了缓存数据丢失的情况发生。
可选的，所述切换请求消息还包括：用于指示第一承载的当前包数据汇聚协议PDCP序列号SN长度的第一配置信息；所述切换确认消息还包括：用于指示所述第二接入网设备能否支持所述第一承载的当前PDCP SN长度的能力信息，且当所述能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述切换确认消息还包括：用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息；其中，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载。
可选的，在所述第一接入网设备接收所述第二接入网设备发送的切换确认消息之后，所述方法还包括：在所述切换确认消息中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述第一接入网设备向所述第二接入网设备转发：所述第一接入网设备的缓存数据中的第一PDCP服务数据单元SDU，第一PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。在第二接入网设备无法支持第一承载的当前PDCP SN时，第一接入网设备将第二接入网设备能够识别的第一PDCP SDU发送至第二接入网设备，防止了第一PDCP SDU的丢失。
可选的，所述方法还包括：在所述切换确认消息中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述第一接入网设备根据所述目标PDCP SN长度构造上行PDCP SDU的接收状态元素；所述第一接入网设备向所述第二接入网设备转发所述上行PDCP SDU的接收状态元素。由于第二接入网设备无法支持第一承载的当前PSCP SN长度，因此，第一接入网设备需要根据第二接入网设备能够支持的目标PDCP SN长度构造上行PDCP SDU的接收状态元素。
可选的，在所述第一接入网设备向第二接入网设备发送切换请求消息之前，所述方法还包括：所述第一接入网设备向所述终端设备发送配置消息，所述配置消息包括：所述第一接入网设备为所述第一接入网设备与所述终端设备已建立的第一承载分配的第一PDCP SN长度。由于第一接入网设备能够向终端设备发送配置消息，以指示终端设备对已建立的第一承载重配置第一PDCP SN长度。也即，本申请中已建立的承载配置的PDCP SN长度能够调整，当终端设备向第一接入网设备发送的数据较少时，第一接入网设备为第一承载配置较短的PDCP SN长度，从而减少终端设备发送的PDCP SDU中PDCP SN的长度，减少对比特位的浪费。
可选的，第一承载的PDCP SN长度包括：上行PDCP SN长度和下行PDCP SN长度。
需要说明的是，第一承载的PDCP SN长度中的上行PDCP SN长度与下行PDPC SN长度相等，或者，第一承载的PDPC SN长度中的上行PDCP SN长度与下行PDPC SN长度不等。第一接入网设备能够为第一承载分配第一PDCP SN长度(也即下行PDCP SN长度或下行PDCP SN长度)，并将包括该第一PDCP SN长度的配置消息发送至终端设备，由终端设备根据该配置消息为第一承载配置第一PDCP SN长度。进一步的，配置消息包括一个 PDCP SN长度，该一个PDCP SN长度可以同时为第一接入网设备分配给第一承载的上行PDCP SN长度和下行PDCP SN长度，或者，该一个PDCP SN长度为第一接入网设备分配给第一承载的上行PDCP SN长度或下行PDCP SN长度。
相关技术中，当终端设备或第一接入网设备待发送的数据较少时，较短的PDCP SN长度(需要少量的比特位)就能够区分较少的数据，但是目前，终端设备或第一接入网设备仍然为每个数据分配固定长度(相对较长)的PDCP SN(需要较多的比特位)，因此，PDCP SDU中的PDCP SN较长，PDCP SN需要占用的比特位的个数较多，造成了比特位的浪费。当终端设备或第一接入网设备待发送的数据较多时，由于终端设备或第一接入网设备仍然为每个数据分配固定长度(相对较短)的PDCP SN，且该固定长度仅仅能够区分一部分待发送的数据，因此，终端设备或第一接入网设备在一次数据传输过程中，仅仅能够传输一部分待发送的数据，数据传输的效率无法满足需要。
而本发明实施例中，接入网设备能够根据向终端设备发送配置消息，以指示终端设备对已建立的第一承载重配置第一PDCP SN长度，对第一承载的PDCP SN长度进行调整，终端设备能够通过重配置PDCP SN长度后的第一承载发送数据。且接入网设备分配给第一承载的上行PDCP SN长度和下行PDCP SN长度均能够满足数据包较多和较少的情况，从而避免了在数据包较少时PDCP SN中比特位的浪费，以及在数据包较多时，数据传输效率较低的情况。
可选的，所述配置消息还包括生效信息，所述生效信息用于指示目标计数值。可选的，所述生效信息包括：PDCP SN、起始帧号HFN和计数值中的至少一个。
进一步的，第一接入网设备还能够指示终端设备截止计数值，该截止计数值位于目标计数值之后，且与目标计数值之间存在多个计数值，当终端设备维护的计数值变为该截止计数值时，终端设备能够重新为第一承载配置原先的PDCP SN长度。
第二方面，提供了种设备切换方法，所述方法包括：终端设备接收第一接入网设备发送的切换命令，所述切换命令为切换确认消息中的透明容器信息元素，所述透明容器信息元素包括第三无损切换标识，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换；所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换。
可选的，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换，包括：在所述透明容器信息元素中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述终端设备为所述第二承载配置所述目标PDCP SN长度；所述终端设备向所述第二接入网设备发送所述终端设备的缓存数据中的第二PDCP SDU，所述第二PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。也即，在第二接入网设备无法支持第一承载的当前PDCP SN长度时，终端设备只能够为第二承载配置目标PDCP SN长度，且只有PDCP SN长度较小的第二PDCP SDU能够在 第二承载上传输，且能够被第二接入设备识别，防止了第二PDCP SDU的丢失。
可选的，所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换，还包括：在所述透明容器信息元素中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述终端设备根据所述目标PDCP SN长度构造下行PDCP SDU的接收状态报告；所述终端设备向所述第二接入网设备发送所述下行PDCP SDU的接收状态报告。
可选的，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换，包括：在所述透明容器信息元素中的能力信息指示所述第二接入网设备能够支持所述当前PDCP SN长度时，所述终端设备为所述第二承载配置所述当前PDCP SN长度；所述终端设备向所述第二接入网设备发送所述终端设备的缓存数据中已分配PDCP SN的PDCP SDU；在确认所述终端设备的缓存数据中已分配PDCP SN的PDCP SDU均成功发送至所述第二接入网设备后，所述终端设备为所述第二承载配置所述目标PDCP SN长度。也即，在第二接入网设备能够支持第一承载的当前PDCP SN长度时，终端设备将缓存数据中已分配PDCP SN的PDCP SDU传输至第二接入网设备，且第二接入网设备能够识别接收到的PDCP SDU，防止了终端设备的缓存数据中已分配PDCP SN的PDCP SDU的丢失。
可选的，所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换，还包括：在所述透明容器信息元素中的能力信息指示所述第二接入网设备能够支持所述当前PDCP SN长度时，所述终端设备根据所述当前PDCP SN长度构造下行PDCP SDU的接收状态报告；所述终端设备向所述第二接入网设备发送所述下行PDCP SDU的接收状态报告。
可选的，在所述终端设备接收第一接入网设备发送的切换命令之前，所述方法还包括：所述终端设备接收所述第一接入网设备发送的配置消息，所述配置消息包括：所述第一接入网设备为所述第一接入网设备与所述终端设备已建立的第一承载分配的第一PDCP SN长度；所述终端设备根据所述配置消息，为所述第一承载重配置所述第一PDCP SN长度。
可选的，第一承载的PDCP SN长度包括：上行PDCP SN长度和下行PDCP SN长度。
可选的，在所述终端设备接收所述第一接入网设备发送的配置消息之前，所述方法还包括：所述终端设备获取与飞行中的PDCP SDU相关的至少一个触发条件，所述飞行中的PDCP SDU为所述终端设备已发送且未确认发送成功的上行PDCP SDU；所述终端设备判断所述飞行中的PDCP SDU的个数是否满足任一所述触发条件；当所述飞行中的PDCP SDU的个数满足某一触发条件时，所述终端设备向所述第一接入网设备发送反馈消息。
第一接入网设备为第一承载分配的第一PDCP SN长度(上行PDCP SN长度)与终端设备的上行吞吐量正相关，且终端设备的上行吞吐量与终端设备的飞行中的数据包的个数正相关。也即，当飞行中的数据包的个数较大时，终端设备的上行吞吐量较大，此时为了提高终端设备发送数据包的效率，第一接入网设备分配给第一承载的上行PDCP SN长度较 大，使得终端设备能够一次发送较多的数据包。当飞行中的数据包的个数较小时，终端设备的上行吞吐量较小，此时为了避免发送的数据包中PDCP SN中比特位的浪费，第一接入网设备分配给第一承载的上行PDCP SN长度较小，减少对数据包中PDCP SN中比特位的浪费。
可选的，所述至少一个触发条件包括以下触发条件中的至少一个：所述终端设备的飞行中的PDCP SDU的个数小于第一阈值；所述终端设备的飞行中的PDCP SDU的个数大于第二阈值。
可选的，所述配置消息还包括生效信息，所述生效信息用于指示目标计数值计数值，所述终端设备根据所述配置消息，为所述第一承载重配置所述第一PDCP SN长度，包括：当所述终端设备维护的计数值变更为所述目标计数值时，所述终端设备根据所述配置信息为所述第一承载重配置所述第一PDCP SN长度；或者，当所述终端设备维护的计数值变更为所述目标计数值的下一计数值时，所述终端设备根据所述配置信息为所述第一承载重配置所述第一PDCP SN长度。终端设备在接收到配置消息后，终端设备根据该配置消息确定第一PDCP SN和目标计数值，并在终端设备维护的计数值变更为目标计数值时，为第一承载重配置第一PDCP SN长度，也即将第一承载的上行PDCP SN长度更改为第一PDCP SN长度。或者，终端设备在接收到配置消息后，终端设备根据该配置消息确定第一PDCP SN和目标计数值，并在终端设备维护的计数值变更为目标计数值的下一个计数值时，为第一承载重配置第一PDCP SN长度，也即将第一承载的上行PDCP SN长度更改为第一PDCP SN长度。
可选的，所述生效信息包括：PDCP SN、起始帧号HFN和计数值中的至少一个。
第三方面，提供了一种设备切换方法，所述方法包括：第二接入网设备接收第一接入网设备发送的切换请求消息，所述切换请求消息包括：第一无损切换标识，所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息，所述切换确认消息包括透明容器信息元素和位于所述透明容器信息元素外的第二无损切换标识，所述透明容器信息元素包括第三无损切换标识；其中，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换。
可选的，所述切换请求消息还包括：用于指示第一承载的当前PDCP SN长度的第一配置信息；所述切换确认消息还包括：用于指示所述第二接入网设备能否支持所述当前PDCP SN长度的能力信息，且当所述能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述切换确认消息还包括：用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息；其中，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载。
可选的，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：所述第二接入网设备接收所述第一接入网设备转发的：所述第一接入网设备的缓存数据中的第一PDCP SDU，第一PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
可选的，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：所述第二接入网设备接收所述第一接入网设备转发 的上行PDCP SDU的接收状态元素，所述上行PDCP SDU的接收状态元素是根据所述目标PDCP SN长度构造的。
可选的，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：所述第二接入网设备接收所述终端设备发送的所述终端设备的缓存数据中的第二PDCP SDU，所述第二PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
可选的，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：所述第二接入网设备接收所述终端设备发送的下行PDCP SDU的接收状态报告，所述下行PDCP SDU的接收状态报告是根据所述目标PDCP SN长度构造的。
可选的，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：所述第二接入网设备接收所述终端设备发送的所述终端设备的缓存数据中已分配PDCP SN的PDCP SDU。
可选的，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：所述第二接入网设备接收所述终端设备发送的下行PDCP SDU的接收状态报告，所述下行PDCP SDU的接收状态报告是根据所述当前PDCP SN长度构造的。
第四方面，提供了一种承载配置方法，所述方法包括：第一接入网设备向终端设备发送配置消息，所述配置消息包括：所述第一接入网设备为所述第一接入网设备与所述终端设备已建立的第一承载分配的第一PDCP SN长度。由于第一接入网设备能够向终端设备发送配置消息，以指示终端设备对已建立的第一承载重配置第一PDCP SN长度。也即，本申请中已建立的承载配置的PDCP SN长度能够调整，当终端设备向第一接入网设备发送的数据较少时，第一接入网设备为第一承载配置较短的PDCP SN长度，从而减少终端设备发送的PDCP SDU中PDCP SN的长度，减少对比特位的浪费。
可选的，第一承载的PDCP SN长度包括：上行PDCP SN长度和下行PDCP SN长度。
可选的，所述配置消息还包括生效信息，所述生效信息用于指示目标计数值。
可选的，所述生效信息包括：PDCP SN、起始帧号HFN和计数值中的至少一个。
第五方面，提供了一种承载配置方法，所述方法包括：终端设备接收第一接入网设备发送的配置消息，所述配置消息包括：所述第一接入网设备为所述第一接入网设备与所述终端设备已建立的第一承载分配的第一PDCP SN长度；所述终端设备根据所述配置消息，为所述第一承载重配置第一PDCP SN长度。
可选的，第一承载的PDCP SN长度包括：上行PDCP SN长度和下行PDCP SN长度。
可选的，在所述终端设备接收所述第一接入网设备发送的配置消息之前，所述方法还包括：所述终端设备获取与飞行中的PDCP SDU相关的至少一个触发条件，所述飞行中的PDCP SDU为所述终端设备已发送且未确认发送成功的上行PDCP SDU；所述终端设备判断所述飞行中的PDCP SDU的个数是否满足任一所述触发条件；当所述飞行中的PDCP SDU的个数满足某一触发条件时，所述终端设备向所述第一接入网设备发送反馈消息。
可选的，所述至少一个触发条件包括以下触发条件中的至少一个：所述终端设备的飞 行中的PDCP SDU的个数小于第一阈值；所述终端设备的飞行中的PDCP SDU的个数大于第二阈值。
可选的，所述配置消息还包括生效信息，所述生效信息用于指示目标计数值计数值，所述终端设备根据所述配置消息，为所述第一承载重配置所述第一PDCP SN长度，包括：当所述终端设备维护的计数值变更为所述目标计数值时，所述终端设备根据所述配置信息为所述第一承载重配置所述第一PDCP SN长度；或者，当所述终端设备维护的计数值变更为所述目标计数值的下一计数值时，所述终端设备根据所述配置信息为所述第一承载重配置所述第一PDCP SN长度。
可选的，所述生效信息包括：PDCP SN、起始帧号HFN和计数值中的至少一个。
第六方面，提供一种切换设备，该切换设备包括至少一个模块，该至少一个模块用于实现上述第一方面或第一方面的任一可选方式所提供的设备切换方法。
第七方面，提供了一种切换设备，该切换设备包括至少一个模块，该至少一个模块用于实现上述第二方面或第二方面的任一可选方式所提供的设备切换方法。
第八方面，提供了一种切换设备，该切换设备包括至少一个模块，该至少一个模块用于实现上述第三方面或第三方面的任一可选方式所提供的设备切换方法。
第九方面，提供了一种承载配置设备，该承载配置设备包括至少一个模块，该至少一个模块用于实现上述第四方面或第四方面的任一可选方式所提供的承载配置方法。
第十方面，提供了一种承载配置设备，该承载配置设备包括至少一个模块，该至少一个模块用于实现上述第五方面或第五方面的任一可选方式所提供的承载配置方法。
第十一方面，提供一种网络接入设备，该网络接入设备包括：至少一个发射机、至少一个接收机、至少一个处理器、至少一个网络接口、存储器以及至少一个总线，存储器与网络接口分别通过总线与处理器相连；处理器被配置为执行存储器中存储的指令；处理器通过执行指令来实现：上述第一方面或第一方面中任意一种可能的实现方式所提供的设备切换方法，或者，上述第三方面或第三方面中任意一种可能的实现方式所提供的设备切换方法。
第十二方面，提供一种终端设备，该终端杆设备包括：至少一个发射机、至少一个接收机、至少一个处理器、至少一个网络接口、存储器，存储器与网络接口分别与处理器相连；处理器被配置为执行存储器中存储的指令；处理器通过执行指令来实现：上述第二方面或第二方面中任意一种可能的实现方式所提供的设备切换方法。
第十三方面，提供一种网络接入设备，该网络接入设备包括：至少一个发射机、至少一个接收机、至少一个处理器、至少一个网络接口、存储器，存储器与网络接口分别与处理器相连；处理器被配置为执行存储器中存储的指令；处理器通过执行指令来实现：上述第四方面或第四方面中任意一种可能的实现方式所提供的承载配置方法。
第十四方面，提供一种终端设备，该终端杆设备包括：至少一个发射机、至少一个接收机、至少一个处理器、至少一个网络接口、存储器，存储器与网络接口分别与处理器相连；处理器被配置为执行存储器中存储的指令；处理器通过执行指令来实现：上述第五方面或第五方面中任意一种可能的实现方式所提供的承载配置方法。
第十五方面，提供了一种通信系统，所述通信系统包括：第一接入网设备、终端设备 和第二接入网设备，所述第一接入网设备为第六方面所述的切换设备；所述终端设备为第七方面所述的切换设备；所述第二接入网设备为第八方面所述的切换设备。或者，第一接入网设备和第二接入网设备不同，且第一接入网设备和第二接入网设备均为如第十一方面所述的网络接入设备，终端设备为第十二方面所述的终端设备。
第十六方面，提供了一种通信系统，所述通信系统包括：第一接入网设备和终端设备，所述第一接入网设备为第九方面所述的切换设备；所述终端设备为第十方面所述的切换设备。或者，所述第一接入网设备为第十三方面所述的接入网设备，所述终端设备为第十四方面所述的终端设备。
第十七方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当所述计算机可读存储介质在计算机上运行时，使得计算机执行上述第一方面、第二方面、第三方面、第四方面或第五方面所述的方法。
本申请提供的技术方案带来的有益效果是：
由于第二接入网设备接收到的切换请求、第一接入网设备接收到的切换确认消息以及终端设备接收到的透明容器信息元素中均包含无损传输标识，且该无损传输标识用于指示进行无数据损失的切换，所以，防止了在终端设备由第一接入网设备切换至第二接入网设备时，进行全配置切换，防止了缓存数据丢失的情况发生。
另外，由于第一接入网设备能够向终端设备发送配置消息，以指示终端设备对已建立的第一承载重配置第一PDCP SN长度。也即，本申请中已建立的承载配置的PDCP SN长度能够调整，当终端设备向第一接入网设备发送的数据较少时，第一接入网设备为第一承载配置较短的PDCP SN长度，从而减少终端设备发送的PDCP SDU中PDCP SN的长度，减少对比特位的浪费。
附图说明
图1为本发明实施例提供的一种通信系统的结构示意图；
图2为本发明实施例提供的另一种通信系统的结构示意图；
图3为本发明实施例提供的一种通信设备的用户面协议栈示意图；
图4为本发明实施例提供的一种设备切换方法的应用场景示意图；
图5为本发明实施例提供的另一种设备切换方法的应用场景示意图；
图6为本发明实施例提供的又一种设备切换方法的应用场景示意图；
图7为本发明实施例提供的一种接入网设备的结构示意图；
图8为本发明实施例提供的一种终端设备的结构示意图；
图9为本发明实施例提供的一种设备切换方法的方法流程图；
图10为本发明实施例提供的一种计数值的结构示意图；
图11为本发明实施例提供的一种切换确认消息的结构示意图；
图12为本发明实施例提供的一种第一接入网设备转发缓存数据的方法流程图；
图13为本发明实施例提供的一种终端设备进行切换的方法流程图；
图14为本发明实施例提供的第一种切换设备的结构示意图；
图15为本发明实施例提供的第二种切换设备的结构示意图；
图16为本发明实施例提供的第三种切换设备的结构示意图；
图17为本发明实施例提供的第四种切换设备的结构示意图；
图18为本发明实施例提供的第五种切换设备的结构示意图；
图19为本发明实施例提供的第六种切换设备的结构示意图；
图20为本发明实施例提供的第七种切换设备的结构示意图；
图21为本发明实施例提供的第八种切换设备的结构示意图；
图22为本发明实施例提供的第九种切换设备的结构示意图；
图23为本发明实施例提供的第十种切换设备的结构示意图；
图24为本发明实施例提供的第十一种切换设备的结构示意图；
图25为本发明实施例提供的第十二种切换设备的结构示意图；
图26为本发明实施例提供的第十三种切换设备的结构示意图；
图27为本发明实施例提供的第十四种切换设备的结构示意图；
图28为本发明实施例提供的一种承载配置设备的结构示意图；
图29为本发明实施例提供的另一种承载配置设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
图1为本发明实施例提供的一种通信系统A的结构示意图，如图1所示，该通信系统A包括终端设备10、第一接入网设备111和第二接入网设备112。终端设备10能够与每个接入网设备建立承载(图1中示出了终端设备10与第一接入网设备111建立有承载)，并能够通过建立的承载与接入网设备进行通信，接入网设备接入核心网(图1中未示出)。示例的，接入网设备为基站，如演进型基站(英文：EvolvedNodeB；简称：eNB)或新空口基站(英文：New Radio NodeB；简称：NR-NB)，终端设备10为手机，承载为数据无线承载(英文：Data Radio Bearer；简称：DRB)。需要说明的是，NR-NB也可以称为gNB(第五代移动通信技术系统中的基站)。
图2为本发明实施例提供的另一种通信系统B的结构示意图，如图2所示，该通信系统B包括终端设备10和第一接入网设备111。终端设备10能够与第一接入网设备111建立承载，并能够通过建立的承载与接入网设备进行通信，第一接入网设备接入核心网(图1中未示出)。示例的，第一接入网设备为基站，如eNB或NR-NB，终端设备10为手机，承载为DRB。
图3为本发明实施例提供的一种通信设备的用户面协议栈示意图，该通信设备为终端设备或接入网设备，如图3所示，该通信设备的用户面协议栈包括：PDCP、无线链路控制(英文：Radio Link Control；简称：RLC)、多址接入控制(英文：Multiple Access Control；简称：MAC)、物理层协议(英文：physical；简称：PHY)四层协议。其中，RLC的工作模式为确认模式(英文：Acknowledged Mode；简称：AM)。终端设备与接入网设备建立的承载是通过PDCP层的实体和RLC层的实体建立的。
图4为本发明实施例提供的一种设备切换方法的应用场景示意图，如图4所示，当终端设备10在与第一接入网设备111建立第一承载，并通过第一接入网设备111与核心网(英文：Evolved Packet Core；简称：EPC)2进行通信时，终端设备10还能够切断与当前连接的第一接入网设备111建立的第一承载，并与第二接入网设备112建立第二承载，进而通过第二接入网设备112与核心网2进行通信。可选的，当切换后的承载(第二承载)的编号(英文：identification；简称：ID)相对于切换前的承载(第一承载)的ID没有发生变化时，可以认为第一承载与第二承载是一个承载。
图5为本发明实施例提供的一种终端设备辅小区改变辅小区组改变(英文：Secondary Cell Group change；简称：SCG change)的场景示意图，如图5所示，当终端设备10与第一接入网设备111建立有第一承载，且终端设备10通过该第一接入网设备111上的S1-C接口(LTE协议中定义的一种通信接口，也即数据无线承载(英文：Signal Radio Bearer；简称：SRB))与S1-U接口(LTE协议中定义的一种通信接口，也即数据无线承载(英文：Data Radio Bearer；简称：DRB))与核心网2通信时，终端设备10还能够将S1-U接口从该第一接入网设备111切换至第二接入网设备112，此时，终端设备10与第一接入网设备111建立有第一承载，与第二接入网设备112建立有第二承载，且终端设备10通过第一接入网设备111的S1-C接口与核心网2传输信令，并通过第二接入网设备112的S1-U接口与核心网2传输数据。
图6为本发明实施例提供的另一种SCG change场景示意图，如图6所示，当终端设备10与第三接入网设备113建立有第三承载，与第一接入网设备111建立有第一承载，且终端设备10通过第三接入网设备113上的S1-C接口与核心网2通信，并通过第一接入网设备111的S1-U接口与核心网2通信时，终端设备10还能够将S1-U接口从该第一接入网设备111切换至第二接入网设备112，此时，终端设备10与第三接入网设备建立有第三承载，与第二接入网设备112建立有第二承载，且终端设备10通过该第三接入网设备113的S1-C接口与核心网2传输信令，并通过该第二接入网设备112的S1-U接口与核心网2传输。
也即，在图4、图5或图6所示的应用场景中，终端设备10的DRB均从第一接入网设备111切换至第二接入网设备112。可选的，第一接入网设备111和第二接入网设备112同时为NR-NB，或者第一接入网设备111与第二接入网设备112中，一个接入网设备为NR-NB，另一个接入网设备为eNB。
示例的，终端设备在与接入网设备建立承载时，接入网设备会指示终端设备为承载配置PDCP SN长度。当终端设备需要发送上行数据时，终端设备根据承载配置的PDCP SN长度，为待发送的上行数据分别分配不同的PDCP SN，得到多个上行PDCP服务数据单元(英文：Service Data Unit；简称：SDU)，且终端设备分配给数据的PDCP SN的长度等于该承载被配置的PDCP SN长度(如12个比特位)。示例的，每个PDCP SDU包括PDCP SN和数据部分，每个PDCP SN的长度均为12比特位，但不同的PDCP SDU中的PDCP SN互不相同。然后，终端设备就通过该承载向接入网设备发送PDCP SDU，接入网设备在接收到PDCP SDU后，对PDCP SDU进行解析，确定每个上行PDCP SDU中的PDCP SN和数据部分，进而根据多个PDCP SDU中PDCP SN的大小，确定PDCP SDU中数据部分的排序。当终端设备接收到接入网设备发送的下行PDCP SDU时，终端设备根据承载配置的PDCP  SN长度，解析接收到的下行PDCP SDU。
请参考图7，其示出了本发明实施例提供的一种接入网设备70的结构示意图。该接入网设备70为图1所示的通信系统A中的第一接入网设备、图1所示的通信系统A中的第二接入网设备或者图2所示的通信系统B中的第一接入网设备。该接入网设备70用于执行图9所示实施例提供的部分方法。参见图7，该接入网设备70包括：处理器710和发射机720，处理器710和发射机720通过总线730连接。
处理器710包括一个或者一个以上处理核心。处理器710通过运行软件程序以及单元，从而执行各种功能应用以及数据处理。
可选地，如图7所示，该接入网设备70还包括：存储器740、网络接口750和接收机760，存储器740、网络接口750、接收机760分别通过总线730与发射机720和处理器710连接。
其中，网络接口750为多个，该网络接口750用于该接入网设备70与其它存储设备或者接入网设备进行通信。其中，网络接口750是可选地，实际应用中，接入网设备70能够通过发射机720和接收机760与其它存储设备或者接入网设备进行通信，所以，接入网设备70中能够没有网络接口，本发明实施例对此不作限定。
请参考图8，其示出了本发明实施例提供的一种终端设备80的结构示意图。该终端设备80为图1所示的通信系统A或者图2所示的通信系统B中的终端设备，该终端设备80用于执行图9所示实施例提供的部分方法。参见图8，该接入网设备图80包括：处理器810和发射机图820，处理器810和发射机图820通过总线图830连接。
处理器810包括一个或者一个以上处理核心。处理器810通过运行软件程序以及单元，从而执行各种功能应用以及数据处理。
可选地，如图8所示，该终端设备图80还包括：存储器图840、网络接口图850和接收机图860，存储器图840、网络接口图850、接收机图860分别通过总线图830与发射机图820和处理器810连接。
其中，网络接口图850为多个，该网络接口图850用于该终端设备图80与其它存储设备或者接入网设备进行通信。其中，网络接口图850是可选地，实际应用中，终端设备图80能够通过发射机图820和接收机图860与其它存储设备或者接入网设备进行通信，所以，终端设备图80中没有网络接口，本发明实施例对此不作限定。
图9为本发明实施例提供的一种设备切换方法的方法流程图，该设备切换方法用于如图1所示的通信系统A，该设备切换方法也用于图4、图5或图6所示的应用场景，如图9所示，该设备切换方法包括：
步骤901、第一接入网设备向终端设备发送配置消息，配置消息包括第一PDCP SN长度。
在步骤901之前，终端设备与第一接入网设备已经建立有第一承载，且在建立第一承载时，第一接入网设备已经指示终端设备为第一承载配置PDCP SN长度。在步骤901中， 在建立第一承载后，第一接入网设备还能够根据需要，向终端设备发送配置消息，以指示终端设备对已建立的第一承载重新配置第一PDCP SN长度。
示例的，配置消息包括第一接入网设备重新为第一承载配置的第一PDCP SN长度，需要说明的是，该第一承载的PDCP SN长度包括：上行PDCP SN长度和下行PDCP SN长度。该第一PDCP SN长度既为第一接入网设备为第一承载分配的上行PDCP SN长度，也为第一接入网设备为第一承载分配的下行PDCP SN长度，也即，第一接入网设备为第一承载的上行PDCP SN长度和下行PDCP SN长度同时分配第一PDCP SN长度，此时该配置消息中的第一PDCP SN长度用于指示一个PDCP SN长度。可选的，该配置消息中的第一PDCP SN长度用于指示两个不同的PDCP SN长度(也即上行PDCP SN长度和下行PDCP SN长度)，该两个不同的PDCP SN长度分别为第一接入网上设备为第一承载配置的上行PDCP SN长度和下行PDCP SN长度。
下面将对第一接入网设备确定为第一承载分配的上行PDCP SN长度和下行PDCP SN长度的过程进行解释说明：
一方面，在步骤901之前，第一接入网设备能够向终端设备发送与飞行中的PDCP SDU相关的至少一个触发条件，使得终端设备获取到该与飞行中的PDCP SDU相关的至少一个触发条件。当终端设备确定当前场景满足至少一个触发条件中的某一触发条件时，终端设备就向第一接入网设备发送反馈消息，以便于第一接入网设备根据该反馈消息，为第一承载分配上行PDCP SN长度，进而向终端设备发送配置消息。示例的，第一接入网设备上能够存储有多个触发条件与多个PDCP SN长度的对应关系，第一接入网设备在接收到反馈消息后，第一接入网设备能够根据反馈消息确定飞行中的PDCP SDU满足的触发条件，进而将多个触发条件与多个PDCP SN长度的对应关系中，飞行中的PDCP SDU满足的触发条件所对应的PDCP SDU长度作为为第一承载分配的上行PDCP SDU长度(配置消息中的第一PDCP SN长度用于指示该分配的上行PDCP SN长度)。
需要说明的是，在RLC层采用AM模式条件下，终端设备在向第一接入网设备发送上行PDCP SDU后，若第一接入网设备接收到该上行PDCP SDU，则第一接入网设备会向终端设备通过RLC层进行状态报告，终端设备通过该状态报告能够确定该上行PDCP SDU是否发送成功，其中，终端设备已向第一接入网设备发送且第一接入网设备未确认发送成功的上行PDCP SDU为：终端设备的飞行中的PDCP SDU。
可选的，该至少一个触发条件包括以下触发条件中的至少一个：终端设备的飞行中的PDCP SDU的个数小于第一阈值；终端设备的飞行中的PDCP SDU的个数大于第二阈值，其中，第一阈值和第二阈值均为PDCP SDU的个数。终端设备能够实时的将终端设备的飞行中的PDCP SDU的个数(或者终端设备在预设时间段内的飞行中的PDCP SDU的个数)与第一阈值和第二阈值进行比较，以确定飞行中的PDCP SDU的个数(或者终端设备在预设时间段内的飞行中的PDCP SDU的个数)是否小于第一阈值，或者大于第二阈值，进而确定飞行中的PDCP SDU的个数满足至少一个触发条件中的某一触发条件。一旦飞行中的PDCP SDU的个数满足某一触发条件时，终端设备就能够向第一接入网设备发送反馈消息。该反馈消息包括：满足该某一触发条件的飞行中的PDCP SDU的个数，或者，该某一触发条件的标识。
可选的，该至少一个触发条件包括以下触发条件中的至少一个：终端设备的飞行中的PDCP SDU的数据量小于第三阈值；终端设备的飞行中的PDCP SDU的数据量大于第四阈值，其中，第三阈值和第四阈值均为PDCP SDU的数据量。终端设备需要实时的将终端设备的飞行中的PDCP SDU的数据量(或者终端设备在预设时间段内的飞行中的PDCP SDU的数据量)与第三阈值和第四阈值进行比较，以确定飞行中的PDCP SDU的数据量(或者终端设备在预设时间段内的飞行中的PDCP SDU的数据量)是否满足任一触发条件，一旦飞行中的PDCP SDU的数据量满足某一触发条件时，终端设备就向第一接入网设备发送反馈消息，该反馈消息包括：满足该某一触发条件的飞行中的PDCP SDU的数据量，或者，该某一触发条件的标识。需要说明的是，本发明实施例中的PDCP SDU的数据量指的是PDCP SDU的字节数。
另一方面，第一接入网设备还能够为第一承载分配下行PDCP SN长度。示例的，第一接入网设备能够自行统计第一承载的下行吞吐量，如通过统计第一接入网设备的飞行中的数据包的个数或数据量，确定第一承载的下行吞吐量较大或较小，并根据第一承载的下行吞吐量确定是否需要为第一承载重新分配下行PDCP SN长度，以保证在下行吞吐量较大时，将第一承载的下行PDCP SN长度调大，在下行吞吐量较小时，将第一承载的下行PDCP SN长度调小。
第一接入网设备为第一承载分配的第一PDCP SN长度所指示的上行PDCP SN长度与上行吞吐量正相关，所指示的下行PDCP SN长度与下行吞吐量正相关，且上行吞吐量与终端设备的飞行中的数据包的个数正相关，下行吞吐量与第一接入网设备的飞行中的数据包的个数正相关。也即，当终端设备的飞行中的数据包的个数较大时，终端设备的上行吞吐量较大，此时为了提高终端设备发送数据包的效率，第一接入网设备分配给第一承载的上行PDCP SN长度较大，使得终端设备能够一次发送较多的数据包。当终端设备的飞行中的数据包的个数较小时，终端设备的上行吞吐量较小，此时为了避免发送的数据包中PDCP SN中比特位的浪费，第一接入网设备分配给第一承载的上行PDCP SN长度较小，减少对数据包中PDCP SN中比特位的浪费。当第一接入网设备的飞行中的数据包的个数较大时，第一接入网设备的下行吞吐量较大，此时为了提高第一接入网设备发送数据包的效率，第一接入网设备分配给第一承载的下行PDCP SN长度较大，使得第一接入网设备能够一次发送较多的数据包。当第一接入网设备的飞行中的数据包的个数较小时，第一接入网设备的下行吞吐量较小，此时为了避免发送的数据包中PDCP SN中比特位的浪费，第一接入网设备分配给第一承载的下行PDCP SN长度较小，减少对数据包中PDCP SN中比特位的浪费。
相关技术中，当终端设备或第一接入网设备待发送的数据较少时，较短的PDCP SN长度(需要少量的比特位)就能够区分较少的数据，但是目前，终端设备或第一接入网设备仍然为每个数据分配固定长度(相对较长)的PDCP SN(需要较多的比特位)，因此，PDCP SDU中的PDCP SN较长，PDCP SN需要占用的比特位的个数较多，造成了比特位的浪费。当终端设备或第一接入网设备待发送的数据较多时，由于终端设备或第一接入网设备仍然为每个数据分配固定长度(相对较短)的PDCP SN，且该固定长度仅仅能够区分一部分待发送的数据，因此，终端设备或第一接入网设备在一次数据传输过程中，仅仅能够传输一部分待发送的数据，数据传输的效率无法满足需要。
而本发明实施例中，接入网设备能够根据向终端设备发送配置消息，以指示终端设备对已建立的第一承载重配置第一PDCP SN长度，对第一承载的PDCP SN长度进行调整，终端设备能够通过重配置PDCP SN长度后的第一承载发送数据。且接入网设备分配给第一承载的上行PDCP SN长度和下行PDCP SN长度均能够满足数据包较多和较少的情况，从而避免了在数据包较少时PDCP SN中比特位的浪费，以及在数据包较多时，数据传输效率较低的情况。
步骤902、终端设备根据配置消息，将第一承载的PDCP SN长度重配置为第一PDCP SN长度。
需要说明的是，终端设备与第一接入网设备分别维护一个计数值(英文：COUNT)，且正常情况下，终端设备维护的计数值等于第一接入网设备维护的计数值，也即终端设备维护的计数值与第一接入网设备维护的计数值同步。如图10所示，计数值由PDCP SN和起始帧号(英文：Hyper Frame Number；简称：HFN)组成，也即，计数值的高位为HFN，计数值的低位为PDCP SN。其中，每个计数值对应一个PDCP SN以及一个HFN。
可选的，第一接入网设备发送的配置消息还包括第一PDCP SN的生效信息，生效信息用于指示目标计数值，如生效信息包括：PDCP SN、HFN和计数值中的至少一个。当生效信息包括PDCP SN时，该生效信息所指示的目标计数值为该PDCP SN对应的计数值；当生效信息包括HFN时，该生效信息所指示的目标计数值为：该HFN和PDCP SN为0时的计数值；当生效信息包括计数值时，该生效信息所指示的目标计数值为该生效信息中的计数值。
终端设备在接收到配置消息后，终端设备能够根据该配置消息确定第一PDCP SN和目标计数值，并在终端设备维护的计数值变更为目标计数值时，为第一承载重配置第一PDCP SN长度。或者，终端设备在接收到配置消息后，终端设备能够根据该配置消息确定第一PDCP SN和目标计数值，并在终端设备维护的计数值变更为目标计数值的下一个计数值时，为第一承载重配置第一PDCP SN长度。
进一步的，第一接入网设备还能够指示终端设备截止计数值，该截止计数值位于目标计数值之后，且与目标计数值之间存在多个计数值，当终端设备维护的计数值变为该截止计数值时，终端设备能够重新为第一承载配置原先的(也即步骤902之前第一承载配置的)PDCP SN长度。
步骤903、第一接入网设备向第二接入网设备发送切换请求消息，切换请求消息包括第一无损切换标识。
在终端设备与第一接入网设备建立有承载(如第一承载)，并通过建立的承载进行通信时，第一接入网设备能够与第二接入网设备进行切换。在步骤903中，第一接入网设备能够生成切换请求消息，该切换请求消息包括：第一无损切换标识和第一配置信息，该第一配置信息用于指示第一承载的当前PDCP SN长度。第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换，当第二接入网设备接收到该第一无损切换标识后，即使第二接入网设备无法支持第一承载的当前PDCP SN长度，第二接入网设备也无法触发终端设备进行相关技术中的全配置切换，而是要执行本发明实施例中的步骤904。
需要说明的是，该第一配置信息所指示的第一承载的当前PDCP SN长度为一个PDCP SN长度，即第一承载的当前上行PDCP SN长度与当前下行PDCP SN长度相同；或者当前PDCP SN长度包括两个PDCP SN长度，分别为当前上行PDCP SN长度和当前下行PDCP SN长度，该当前上行PDCP SN长度和当前下行PDCP SN长度不同。示例的，本发明实施例中以当前PDCP SN长度为一个PDCP SN长度的情况为例进行说明。
步骤904、第二接入网设备根据切换请求消息，向第一接入网设备发送切换确认消息，切换确认消息包括透明容器信息元素和位于透明容器信息元素外的第二无损切换标识，透明容器信息元素包括第三无损切换标识。
第二接入网设备在接收到第一接入网设备发送的切换请求消息后，若第二接入网设备允许接入终端设备，则第二接入网设备能够向第一接入网设备发送切换确认消息。示例的，如图11所示，该切换确认消息包括：能力信息、透明容器信息元素和位于透明容器信息元素外的第二无损切换标识，且透明容器信息元素包括：能力信息、第二配置信息和第三无损切换标识。
其中，该能力信息用于指示第二接入网设备能否支持第一承载的当前PDCP SN长度，且当能力信息指示第二接入网设备无法支持第一承载的当前PDCP SN长度时，该切换确认消息还包括：用于指示第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息。当然，目标PDCP SN长度为第二接入网设备能够支持的PDCP SN长度，该第二承载为终端设备与第二接入网设备之间的承载。第二接入网设备能够分别判断自己能否支持当前上行PDCP SN长度与当前下行PDCP SN长度，此时，能力信息用于指示第二接入网设备分别能否支持第一承载的当前上行PDCP SN长度以及第一承载的当前下行PDCP SN长度。
步骤905、第一接入网设备向终端设备发送切换命令，切换命令为切换确认消息中的透明容器信息元素。
第一接入网设备在解析切换确认消息得到透明容器信息元素后，第一接入网设备并不解析该透明容器信息元素，而是直接将该透明容器信息元素作为切换命令发送给终端设备。
步骤906、第一接入网设备根据切换确认消息，向所述第二接入网设备转发第一接入网设备的缓存数据。
第一接入网设备上的缓存数据包括：第一接入网设备已发送且未确认发送成功的下行PDCP SDU、已分配PDCP SN且未发送的下行PDCP SDU、未分配PDCP SN的下行新数据以及终端设备发送的还未上传至核心网的上行PDCP SDU。如图12所示，步骤906包括：
步骤9061、第一接入网设备根据切换确认消息中的能力信息，判断第二接入网设备能否支持第一承载的当前PDCP SN长度。若第二接入网设备能够支持第一承载的当前PDCP SN长度，则执行步骤9062；若第二接入网设备无法支持第一承载的当前PDCP SN长度，则执行步骤9063。
在步骤9061中，第一接入网设备首先解析该切换确认消息，得到能力信息、透明容器信息元素和第二无损切换标识，并根据该能力信息确定第二接入网设备能否支持第一承载的当前PDCP SN长度。可选的，该能力信息为1或0，当能力信息为1时，第一接入网设备确定第二接入网设备能够支持第一承载的当前PDCP SN长度，当能力信息为0时，第一 接入网设备确定第二接入网设备无法支持第一承载的当前PDCP SN长度。可选的，该能力信息为真(英文：true)或假(英文：false)，true对应第一接入网设备确定第二接入网设备能够支持第一承载的当前PDCP SN长度，false对应第一接入网设备确定第二接入网设备无法支持第一承载的当前PDCP SN长度。
需要说明的是，当第二接入网设备能够支持的PDCP SN长度为10比特位和15个比特位，若第一承载的当前PDCP SN长度为11比特位时，第二接入网设备无法支持该第一承载的PDCP SN长度；若第一承载的PDCP SN长度为10比特位，则第二接入网设备能够确定自己能够支持第一承载的PDCP SN。也即，只要当前承载使用的PDCP SN长度在第二接入网设备能够支持的PDPC SN长度集合内，就认为第二接入网设备能够支持第一承载的PDCP SN长度。
步骤9062、第一接入网设备向第二接入网设备转发第一接入网设备的缓存数据，以及根据第一承载的当前PDCP SN长度构造的上行PDCP SDU的接收状态元素。
在第一接入网设备确定第二接入网设备能够支持第一承载的当前PDCP SN长度时，该第一接入网设备能够将第一接入网设备的缓存数据均转发至第二接入网设备。且由于在步骤903中第一接入网设备向第二接入网设备发送的切换请求消息中包含第一配置信息，所以，第二接入网设备能够根据该第一配置信息确定第一承载的当前PDCP SN长度，并在接收到缓存数据后，能够根据第一配置信息中的第一承载的当前PDCP SN长度解析接收到的缓存数据。
另外，由于第二接入网设备能够支持第一承载的当前PDCP SN长度，所以，第一接入网设备还能够根据第一承载的当前PDCP SN长度构造上行PDCP SDU(也即终端设备发送的PDCP SDU)的接收状态元素，并将该接收状态元素发送至第二接入网设备。
步骤9063、第一接入网设备向第二接入网设备转发第一接入网设备的缓存数据中的第一PDCP SDU，以及根据目标PDCP SN长度构造的上行PDCP SDU的接收状态元素，其中，第一PDCP SDU中的PDCP SN小于或等于目标PDCP SN长度所对应的最大PDCP SN。
在第一接入网设备确定第二接入网设备无法支持第一承载的当前PDCP SN长度时，该第一接入网设备能够在第一接入网设备的缓存数据中确定第一PDCP SDU，需要说明的是，第一PDCP SDU为第一接入网设备的缓存数据中，PDCP SN小于或等于目标PDCP SN长度所对应的最大PDCP SN。本发明实施例在此以目标PDCP SN长度为2，对目标PDCP SN对应的最大PDCP SN进行解释说明：当目标PDCP SN长度为2时，目标PDCP SN长度所对应的PDCP SN包括以下二进制数字：00、01、10和11，其中，目标PDCP SN长度所对应的最大PDCP SN为二进制数字11。
然后，第一接入网设备将每个第一PDCP SDU中的PDCP SN的最高n位取消，得到取消n位后的第一PDCP SN，其中，n为第一承载的当前PDCP SN长度与目标PDCP SN长度的差。最后，第一接入网设备将取消n位后的第一PDCP SN转发至第二接入设备。另外，由于第二接入网设备无法支持第一承载的当前PDCP SN长度，因此，该第一接入网设备需要根据该目标PDCP SN长度构造上行PDCP SDU的接收状态元素，并将该接收状态元素发送至第二接入网设备。
第一接入网设备的缓存数据中除第一PDCP SN之外的其他数据包括：已分配PDCP SN 的PDCP SDU以及未分配PDCP SN的下行新数据。在步骤9063中，第一接入网设备还能够取消已分配PDCP SN的PDCP SDU中的PDCP SN，得到已分配PDCP SN的PDCP SDU中的数据部分，并将得到的数据部分与未分配PDCP SN的新数据一起转发至第二接入网设备。
需要说明的是，当第一承载的当前上行PDCP SN长度和当前下行PDCP SN长度不同时，第二接入网设备能够分别判断该第二接入网设备能否支持第一承载的当前上行PDCP SN长度和当前下行PDCP SN长度，能力信息用于指示该第二接入网设备能否支持第一承载的当前上行PDCP SN长度以及第二接入网设备能否支持第一承载的当前下行PDCP SN长度。由于第一接入网设备需要向第二接入网设备转发的缓存数据同时包括上行数据和下行数据，因此，在步骤906中第一接入网设备在向第二接入网设备转发缓存数据时，第一接入网设备能够将缓存数据中的上行数据和下行数据分别传输，也即，针对缓存数据中的上行数据执行步骤9061至步骤9063所示的方法，针对缓存数据中的下行数据执行步骤9061至步骤9063所示的方法。
步骤907、终端设备根据切换命令，在第一接入网设备与第二接入网设备之间进行无数据损失的切换。
可选的，如图13所示，步骤907包括：
步骤9071、终端设备根据切换命令中的能力信息，判断第二接入网设备能否支持第一承载的当前PDCP SN长度；若第二接入网设备能够支持第一承载的当前PDCP SN长度，则执行步骤9072；若第二接入网设备无法支持第一承载的当前PDCP SN长度，则执行步骤9075。
在步骤9071中，终端设备首先解析切换命令，得到能力信息、第二配置信息和第三无损切换标识，并根据该能力信息确定第二接入网设备能否支持第一承载的当前PDCP SN长度。
步骤9072、终端设备与第二接入网设备建立配置有第一PDCP SN长度的第二承载。执行步骤9073。
若能力信息指示第二接入网设备能够支持第一承载的当前PDCP SN长度，则终端设备能够与第二接入网设备建立第二承载，并为第二承载配置第一承载的当前PDCP SN长度。
步骤9073、终端设备向第二接入网设备发送终端设备的缓存数据中已分配PDCP SN的PDCP SDU，以及根据第一承载的PDCP SN长度构造的下行PDCP SDU的接收状态报告。执行步骤9074。
终端设备中的缓存数据包括：终端设备已发送且未确认发送成功的上行PDCP SDU、已分配PDCP SN且未发送的上行PDCP SDU以及未分配PDCP SN的上行新数据。终端设备能够将终端设备的缓存数据中已分配PDCP SN的PDCP SDU均转发至第二接入网设备。且由于在步骤903中第一接入网设备向第二接入网设备发送的切换请求消息中包含第一配置信息，所以，第二接入网设备在接收到缓存数据后，能够根据第一配置信息中的第一承载的当前PDCP SN长度解析缓存数据中已分配PDCP SN的SDU，得到SDU中的数据部分。
需要说明的是，在步骤906中，第一接入网设备将上行PDCP SDU的接收状态元素转发至第二接入网设备，在步骤906之后，第二接入网设备还能够解析该上行PDCP SDU的 接收状态元素，得到上行PDCP SDU的接收状态报告，并将上行PDCP SDU的接收状态报告发送至终端设备。在步骤9073中，终端设备还能够根据第二接入网设备发送的上行PDCP SDU的接收状态报告，确定已发送且确认发送成功的上行PDCP SDU，终端设备在向第二接入网设备发送缓存数据中的已分配PDCP SN的上行PDCP SDU时，仅仅发送已分配PDCP SN且未发送的PDCP SN和已发送且未确认发送成功的上行PDCP SDU，减少PDCP SDU的重传。如果终端设备始终未接收到第二接入网设备发送的上行PDCP SDU的接收状态报告，则终端设备能够将终端设备的缓存数据中的所有已分配PDCP SN的PDCP SDU发送至第二接入网设备。
另外，由于第二接入网设备能够支持第一承载的当前PDCP SN长度，所以，在步骤9073中终端设备还能够根据第一承载的当前PDCP SN长度构造下行PDCP SDU(也即原先第一接入网设备发送的下行PDCP SDU)的接收状态报告，并将该接收状态报告发送至第二接入网设备。
步骤9074、在确认终端设备的缓存数据中已分配PDCP SN的PDCP SDU均成功发送至第二接入网设备后，终端设备为第二承载配置目标PDCP SN长度。
在确认终端设备的缓存数据中已分配PDCP SN的PDCP SDU均成功发送至第二接入网设备后，终端设备能够重新为第二承载配置目标PDCP SN长度。然后，就能够根据目标PDCP SN长度为终端设备上的新数据分配PDCP SN，得到PDCP SDU，并通过配置有目标PDCP SN长度的第二承载，向第二接入网设备发送PDCP SDU。
示例的，终端设备能够根据第二接入接入网设备发送的上行PDCP SDU的接收状态报告，确定终端设备的缓存数据中已分配PDCP SN的PDCP SDU是否均成功发送至第二接入网设备，可选的，在步骤9075中，终端设备还能够接收第二接入接入网设备发送的切换计数值，并在该终端设备维护的计数值变为该切换计数值时，为第二承载配置目标PDCP SN长度。
步骤9075、终端设备与第二接入网设备建立配置有目标PDCP SN长度的第二承载。执行步骤9076。
终端设备在确认第二接入网设备无法支持第一承载的当前PDCP SN长度时，终端设备能够与第二接入网设备建立第二承载，并为该第二承载配置第二接入网设备能够支持的目标PDCP SN。
步骤9076、终端设备向第二接入网设备转发终端设备的缓存数据中的第二PDCP SDU，以及根据目标PDCP SN长度构造的下行PDCP SDU的接收状态元素，其中，第二PDCP SDU中的PDCP SN小于或等于目标PDCP SN长度所对应的最大PDCP SN。
终端设备中的缓存数据包括：终端设备已发送且未确认发送成功的上行PDCP SDU、已分配PDCP SN且未发送的上行PDCP SDU以及未分配PDCP SN的上行新数据。
在终端设备确定第二接入网设备无法支持第一承载的当前PDCP SN长度时，该终端设备在终端设备的缓存数据中确定第二PDCP SDU，需要说明的是，第二PDCP SDU为终端设备的缓存数据中，PDCP SN小于或等于目标PDCP SN长度所对应的最大PDCP SN的PDCP SDU。然后，终端设备将每个第二PDCP SDU中的PDCP SN的最高n位取消，得到取消n位后的第二PDCP SN，其中，n为第一承载的当前PDCP SN长度与目标PDCP SN 长度的差。最后，终端设备将取消n位后的第二PDCP SN发送至第二接入设备。
另外，由于第二接入网设备无法支持第一承载的当前PDCP SN长度，因此，终端设备需要根据该目标PDCP SN长度构造下行PDCP SDU的接收状态报告，也即第一个丢失的SN(英文：first missing sn；简称：FMS)的长度为目标PDCP SN长度，位掩码(英文：bitmask)的长度也为目标PDCP SN长度，并将该接收状态报告发送至第二接入网设备。
终端设备的缓存数据中除第二PDCP SN之外的其他数据，可能包括：已分配PDCP SN的PDCP SDU以及未分配PDCP SN的上行新数据。在步骤9076中，终端设备还能够取消已分配PDCP SN的上行PDCP SDU中的PDCP SN，得到已分配PDCP SN的上行PDCP SDU中的数据部分，并将得到的数据部分与未分配PDCP SN的上行新数据一起作为新数据向第二接入网设备发送(如根据目标PDCP SN长度为新数据分配PDCP SN，得到上行PDCP SDU，并向第二接入网设备发送上行PDCP SDU)。
需要说明的是，本发明实施例的步骤901至902中，在终端设备与第一接入网设备建立第一承载时，第一接入网设备能够指示终端设备为第一承载重新配置PDCP SN长度。在步骤907之后，终端设备与第二接入网设备建立有第二承载后，该第二接入网设备也能够指示终端设备为第二承载重新配置PDCP SN长度，且该配置的过程请参考步骤901至步骤902。
综上所述，由于本发明实施例提供的设备切换方法中，第二接入网设备接收到的切换请求、第一接入网设备接收到的切换确认消息以及终端设备接收到的透明容器信息元素中均包含无损传输标识，且该无损传输标识用于指示进行无数据损失的切换，所以，防止了在终端设备由第一接入网设备切换至第二接入网设备时，进行全配置切换，防止了缓存数据丢失的情况发生。
图14为本发明实施例提供的第一种切换设备140的结构示意图，该切换设备140为图1中的第一接入网设备，如图14所示，该切换设备140包括：
第一发送模块1401，用于向第二接入网设备发送切换请求消息，切换请求消息包括：第一无损切换标识；
接收模块1402，用于接收第二接入网设备发送的切换确认消息，切换确认消息包括透明容器信息元素和位于透明容器信息元素外的第二无损切换标识，透明容器信息元素包括第三无损切换标识；
第二发送模块1403，用于将透明容器信息元素作为切换命令发送给终端设备；
其中，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换。
可选的，切换请求消息还包括：用于指示第一承载的当前PDCP SN长度的第一配置信息；
切换确认消息还包括：用于指示第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，且当能力信息指示第二接入网设备无法支持当前PDCP SN长度时，切换确认消息还包括：用于指示第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息；
其中，第一承载为终端设备与第一接入网设备之间的承载，第二承载为终端设备与第二接入网设备之间的承载。
图15为本发明实施例提供的第二种切换设备140的结构示意图，如图15所示，在图14的基础上，该切换设备140还包括：
第一转发模块1404，用于在切换确认消息中的能力信息指示第二接入网设备无法支持当前PDCP SN长度时，向第二接入网设备转发：第一接入网设备的缓存数据中的第一PDCP服务数据单元SDU，第一PDCP SDU中的PDCP SN小于或等于目标PDCP SN长度所对应的最大PDCP SN。
图16为本发明实施例提供的第三种切换设备140的结构示意图，如图16所示，在图15的基础上，该切换设备140还包括：
构造模块1405，用于在切换确认消息中的能力信息指示第二接入网设备无法支持当前PDCP SN长度时，根据目标PDCP SN长度构造上行PDCP SDU的接收状态元素；
第二转发模块1406，用于向第二接入网设备转发上行PDCP SDU的接收状态元素。
图17为本发明实施例提供的第四种切换设备140的结构示意图，如图17所示，在图14的基础上，该切换设备140还包括：
第三发送模块1407，用于向终端设备发送配置消息，配置消息包括：第一接入网设备为第一接入网设备与终端设备已建立的第一承载分配的第一PDCP SN长度。
可选的，第一承载的PDCP SN长度包括：上行PDCP SN长度和下行PDCP SN长度。
可选的，配置消息还包括生效信息，生效信息用于指示目标计数值。
可选的，生效信息包括：PDCP SN、起始帧号HFN和计数值中的至少一个。
综上所述，由于本发明实施例提供的切换设备中，第一发送模块箱第二接入网设备发送的切换确认消息、接收模块接收到的切换确认消息以及第二发送模块发送至终端设备的透明容器信息元素中均包含无损传输标识，且无损传输标识用于指示进行无数据损失的切换，所以，防止了在终端设备由第一接入网设备切换至第二接入网设备时，进行全配置切换，防止了缓存数据丢失的情况发生。
图18为本发明实施例提供的第五种切换设备的结构示意图，该切换设备180为图1中的终端设备，如图18所示，切换设备180包括：
第一接收模块1801，用于接收第一接入网设备发送的切换命令，切换命令为切换确认消息中的透明容器信息元素，透明容器信息元素包括第三无损切换标识，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换；
切换模块1802，用于根据切换命令，在第一接入网设备与第二接入网设备之间进行无数据损失的切换。
可选的，透明容器信息元素还包括：用于指示第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，第一承载为终端设备与第一接入网设备之间的承载，第二承载为终端设备与第二接入网设备之间的承载；
切换模块1802还用于：在透明容器信息元素中的能力信息指示第二接入网设备无法支 持当前PDCP SN长度时，为第二承载配置目标PDCP SN长度；
向第二接入网设备发送终端设备的缓存数据中的第二PDCP SDU，第二PDCP SDU中的PDCP SN小于或等于目标PDCP SN长度所对应的最大PDCP SN。
可选的，切换模块1802还用于：
在透明容器信息元素中的能力信息指示第二接入网设备无法支持当前PDCP SN长度时，根据目标PDCP SN长度构造下行PDCP SDU的接收状态报告；
向第二接入网设备发送下行PDCP SDU的接收状态报告。
可选的，透明容器信息元素还包括：用于指示第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，第一承载为终端设备与第一接入网设备之间的承载，第二承载为终端设备与第二接入网设备之间的承载，切换模块1802还用于：
在透明容器信息元素中的能力信息指示第二接入网设备能够支持当前PDCP SN长度时，为第二承载配置当前PDCP SN长度；
向第二接入网设备发送终端设备的缓存数据中已分配PDCP SN的PDCP SDU；
在确认终端设备的缓存数据中已分配PDCP SN的PDCP SDU均成功发送至第二接入网设备后，为第二承载配置目标PDCP SN长度。
可选的，切换模块1802还用于：
在透明容器信息元素中的能力信息指示第二接入网设备能够支持当前PDCP SN长度时，根据当前PDCP SN长度构造下行PDCP SDU的接收状态报告；
向第二接入网设备发送下行PDCP SDU的接收状态报告。
图19为本发明实施例提供的第六种切换设备的结构示意图，如图19所示，在图18的基础上，该切换设备180还包括：
第二接收模块1803，用于接收第一接入网设备发送的配置消息，配置消息包括：第一接入网设备为第一接入网设备与终端设备已建立的第一承载分配的第一PDCP SN长度；
重配置模块1804，用于终端设备根据配置消息，为第一承载重配置第一PDCP SN长度。
可选的，第一承载的PDCP SN长度包括：上行PDCP SN长度和下行PDCP SN长度。
图20为本发明实施例提供的第七种切换设备的结构示意图，如图20所示，在图19的基础上，该切换设备180还包括：
获取模块1805，用于获取与飞行中的PDCP SDU相关的至少一个触发条件，飞行中的PDCP SDU为终端设备已发送且未确认发送成功的上行PDCP SDU；
判断模块1806，用于判断飞行中的PDCP SDU的个数是否满足任一触发条件；
发送模块1807，用于在飞行中的PDCP SDU的个数满足某一触发条件时，向第一接入网设备发送反馈消息。
可选的，至少一个触发条件包括以下触发条件中的至少一个：
终端设备的飞行中的PDCP SDU的个数小于第一阈值；
终端设备的飞行中的PDCP SDU的个数大于第二阈值。
可选的，配置消息还包括生效信息，生效信息用于指示目标计数值计数值，重配置模块1804还用于：
在终端设备维护的计数值变更为目标计数值时，根据配置信息为第一承载重配置第一PDCP SN长度；
或者，在终端设备维护的计数值变更为目标计数值的下一计数值时，根据配置信息为第一承载重配置第一PDCP SN长度。
可选的，生效信息包括：PDCP SN、起始帧号HFN和计数值中的至少一个。
综上所述，由于本发明实施例提供的切换设备中，第一接收模块接收到的切换命令为切换确认消息中的透明容器信息元素，且该透明容器信息元素中包含无损传输标识，且该无损传输标识用于指示进行无数据损失的切换，所以，防止了在终端设备由第一接入网设备切换至第二接入网设备时，进行全配置切换，防止了缓存数据丢失的情况发生。
图21为本发明实施例提供的第八种切换设备的结构示意图，该切换设备210为图1中的第二接入网设备，如图21所示，切换设备210包括：
第一接收模块2101，用于接收第一接入网设备发送的切换请求消息，切换请求消息包括：第一无损切换标识；
发送模块2102，用于根据切换请求消息，向第一接入网设备发送切换确认消息，切换确认消息包括透明容器信息元素和位于透明容器信息元素外的第二无损切换标识，透明容器信息元素包括第三无损切换标识；
其中，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换。
可选的，切换请求消息还包括：用于指示第一承载的当前PDCP SN长度的第一配置信息；
切换确认消息还包括：用于指示第二接入网设备能否支持当前PDCP SN长度的能力信息，且当能力信息指示第二接入网设备无法支持当前PDCP SN长度时，切换确认消息还包括：用于指示第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息；
其中，第一承载为终端设备与第一接入网设备之间的承载，第二承载为终端设备与第二接入网设备之间的承载。
图22为本发明实施例提供的第九种切换设备的结构示意图，如图22所示，在图21的基础上，该切换设备210还包括：
第二接收模块2103，用于接收第一接入网设备转发的：第一接入网设备的缓存数据中的第一PDCP SDU，第一PDCP SDU中的PDCP SN小于或等于目标PDCP SN长度所对应的最大PDCP SN。
图23为本发明实施例提供的第十种切换设备的结构示意图，如图23所示，在图22的基础上，该切换设备210还包括：
第三接收模块2104，用于接收第一接入网设备转发的上行PDCP SDU的接收状态元素，上行PDCP SDU的接收状态元素是根据目标PDCP SN长度构造的。
图24为本发明实施例提供的第十一种切换设备的结构示意图，如图24所示，在图23的基础上，该切换设备210还包括：
第四接收模块2105，用于接收终端设备发送的终端设备的缓存数据中的第二PDCP  SDU，第二PDCP SDU中的PDCP SN小于或等于目标PDCP SN长度所对应的最大PDCP SN。
图25为本发明实施例提供的第十二种切换设备的结构示意图，如图25所示，在图24的基础上，该切换设备210还包括：
第五接收模块2106，用于接收终端设备发送的下行PDCP SDU的接收状态报告，下行PDCP SDU的接收状态报告是根据目标PDCP SN长度构造的。
图26为本发明实施例提供的第十三种切换设备的结构示意图，如图26所示，在图21的基础上，该切换设备210还包括：
第六接收模块2107，用于接收终端设备发送的终端设备的缓存数据中已分配PDCP SN的PDCP SDU。
图27为本发明实施例提供的第十四种切换设备的结构示意图，如图27所示，在图26的基础上，该切换设备210还包括：
第七接收模块2108，用于接收终端设备发送的下行PDCP SDU的接收状态报告，下行PDCP SDU的接收状态报告是根据当前PDCP SN长度构造的。
综上所述，由于本发明实施例提供的切换设备中，第一接收模块接收到的切换请求消息和发送模块发送的切换请求消息均包括无损切换标识，且无损传输标识用于指示进行无数据损失的切换，所以，防止了在终端设备由第一接入网设备切换至第二接入网设备时，进行全配置切换，防止了缓存数据丢失的情况发生。
图28为本发明实施例提供的一种承载配置设备的结构示意图，该承载配置设备280为图2所示的通信系统B中的第一接入网设备，如图28所示，该承载配置设备280包括：
发送模块2801，用于向终端设备发送配置消息，配置消息包括：第一接入网设备为第一接入网设备与终端设备已建立的第一承载分配的第一PDCP SN长度。
综上所述，由于本发明实施例提供的承载配置设备中，发送模块能够向终端设备发送配置消息，以指示终端设备对已建立的第一承载重配置第一PDCP SN长度。也即，本发明实施例中已建立的承载配置的PDCP SN长度能够调整，当终端设备向第一接入网设备发送的数据较少时，第一接入网设备为第一承载配置较短的PDCP SN长度，从而减少终端设备发送的PDCP SDU中PDCP SN的长度，减少对比特位的浪费。
图29为本发明实施例提供的另一种承载配置设备的结构示意图，该承载配置设备290为图2所示的通信系统B中的终端设备，如图29所示，该承载配置设备290包括：
接收模块2901，用于接收第一接入网设备发送的配置消息，配置消息包括：第一接入网设备为第一接入网设备与终端设备已建立的第一承载分配的第一PDCP SN长度；
重配置模块2902，用于根据配置消息，为第一承载重配置第一PDCP SN长度。
综上所述，由于本发明实施例提供的承载配置设备中，接收模块能够接收第一接入网设备向终端设备发送配置消息，重配置模块能够根据该配置消息，对已建立的第一承载重配置第一PDCP SN长度。也即，本发明实施例中已建立的承载配置的PDCP SN长度能够调整，当终端设备向第一接入网设备发送的数据较少时，第一接入网设备为第一承载配置 较短的PDCP SN长度，从而减少终端设备发送的PDCP SDU中PDCP SN的长度，减少对比特位的浪费。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现，所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机的可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)，或者半导体介质(例如固态硬盘)等。
需要说明的是，本发明实施例提供的方法实施例能够与相应的设备实施例相互参考，本发明实施例对此不做限定。本发明实施例提供的方法实施例步骤的先后顺序能够进行适当调整，步骤也能够根据情况进行相应增减，任何熟悉本技术领域的技术人员在本发明实施例揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本发明实施例的保护范围之内，因此不再赘述。
本领域普通技术人员能够理解实现上述实施例的全部或部分步骤能够通过硬件来完成，也能够通过程序来指令相关的硬件完成，所述的程序能够存储于一种计算机可读存储介质中，上述提到的存储介质是只读存储器，磁盘或光盘等。
以上所述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (37)

  1. 一种设备切换方法，其特征在于，所述方法包括：
    第一接入网设备向第二接入网设备发送切换请求消息，所述切换请求消息包括：第一无损切换标识；
    所述第一接入网设备接收所述第二接入网设备发送的切换确认消息，所述切换确认消息包括透明容器信息元素和位于所述透明容器信息元素外的第二无损切换标识，所述透明容器信息元素包括第三无损切换标识；
    所述第一接入网设备将所述透明容器信息元素作为切换命令发送给终端设备；
    其中，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换。
  2. 根据权利要求1所述的方法，其特征在于，
    所述切换请求消息还包括：用于指示第一承载的当前包数据汇聚协议PDCP序列号SN长度的第一配置信息；
    所述切换确认消息还包括：用于指示所述第二接入网设备能否支持所述第一承载的当前PDCP SN长度的能力信息，且当所述能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述切换确认消息还包括：用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息；
    其中，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载。
  3. 根据权利要求2所述的方法，其特征在于，在所述第一接入网设备接收所述第二接入网设备发送的切换确认消息之后，所述方法还包括：
    在所述切换确认消息中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述第一接入网设备向所述第二接入网设备转发：所述第一接入网设备的缓存数据中的第一PDCP服务数据单元SDU，第一PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
  4. 根据权利要求2或3所述的方法，其特征在于，在所述第一接入网设备接收所述第二接入网设备发送的切换确认消息之后，所述方法还包括：
    在所述切换确认消息中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述第一接入网设备根据所述目标PDCP SN长度构造上行PDCP SDU的接收状态元素；
    所述第一接入网设备向所述第二接入网设备转发所述上行PDCP SDU的接收状态元素。
  5. 一种设备切换方法，其特征在于，所述方法包括：
    终端设备接收第一接入网设备发送的切换命令，所述切换命令为切换确认消息中的透明容器信息元素，所述透明容器信息元素包括第三无损切换标识，第一无损切换标识、第二无 损切换标识和第三无损切换标识用于指示进行无数据损失的切换；
    所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换。
  6. 根据权利要求5所述的方法，其特征在于，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；
    所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换，包括：
    在所述透明容器信息元素中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述终端设备为所述第二承载配置所述目标PDCP SN长度；
    所述终端设备向所述第二接入网设备发送所述终端设备的缓存数据中的第二PDCP SDU，所述第二PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
  7. 根据权利要求5或6所述的方法，其特征在于，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；
    所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换，包括：
    在所述透明容器信息元素中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述终端设备根据所述目标PDCP SN长度构造下行PDCP SDU的接收状态报告；
    所述终端设备向所述第二接入网设备发送所述下行PDCP SDU的接收状态报告。
  8. 根据权利要求5至7任一所述的方法，其特征在于，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；
    所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换，包括：
    在所述透明容器信息元素中的能力信息指示所述第二接入网设备能够支持所述当前PDCP SN长度时，所述终端设备为所述第二承载配置所述当前PDCP SN长度；
    所述终端设备向所述第二接入网设备发送所述终端设备的缓存数据中已分配PDCP SN 的PDCP SDU；
    在确认所述终端设备的缓存数据中已分配PDCP SN的PDCP SDU均成功发送至所述第二接入网设备后，所述终端设备为所述第二承载配置所述目标PDCP SN长度。
  9. 根据权利要求5至8任一所述的方法，其特征在于，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；
    所述终端设备根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换，包括：
    在所述透明容器信息元素中的能力信息指示所述第二接入网设备能够支持所述当前PDCP SN长度时，所述终端设备根据所述当前PDCP SN长度构造下行PDCP SDU的接收状态报告；
    所述终端设备向所述第二接入网设备发送所述下行PDCP SDU的接收状态报告。
  10. 一种设备切换方法，其特征在于，所述方法包括：
    第二接入网设备接收第一接入网设备发送的切换请求消息，所述切换请求消息包括：第一无损切换标识；
    所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息，所述切换确认消息包括透明容器信息元素和位于所述透明容器信息元素外的第二无损切换标识，所述透明容器信息元素包括第三无损切换标识；
    其中，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换。
  11. 根据权利要求10所述的方法，其特征在于，
    所述切换请求消息还包括：用于指示第一承载的当前PDCP SN长度的第一配置信息；
    所述切换确认消息还包括：用于指示所述第二接入网设备能否支持所述当前PDCP SN长度的能力信息，且当所述能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述切换确认消息还包括：用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息；
    其中，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载。
  12. 根据权利要求11所述的方法，其特征在于，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：
    所述第二接入网设备接收所述第一接入网设备转发的：所述第一接入网设备的缓存数据中的第一PDCP SDU，第一PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
  13. 根据权利要求11或12所述的方法，其特征在于，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：
    所述第二接入网设备接收所述第一接入网设备转发的上行PDCP SDU的接收状态元素，所述上行PDCP SDU的接收状态元素是根据所述目标PDCP SN长度构造的。
  14. 根据权利要求11至13任一所述的方法，其特征在于，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：
    所述第二接入网设备接收所述终端设备发送的所述终端设备的缓存数据中的第二PDCP SDU，所述第二PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
  15. 根据权利要求11至14任一所述的方法，其特征在于，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：
    所述第二接入网设备接收所述终端设备发送的下行PDCP SDU的接收状态报告，所述下行PDCP SDU的接收状态报告是根据所述目标PDCP SN长度构造的。
  16. 根据权利要求11至15任一所述的方法，其特征在于，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：
    所述第二接入网设备接收所述终端设备发送的所述终端设备的缓存数据中已分配PDCP SN的PDCP SDU。
  17. 根据权利要求11至16任一所述的方法，其特征在于，在所述第二接入网设备根据所述切换请求消息，向所述第一接入网设备发送切换确认消息之后，所述方法还包括：
    所述第二接入网设备接收所述终端设备发送的下行PDCP SDU的接收状态报告，所述下行PDCP SDU的接收状态报告是根据所述当前PDCP SN长度构造的。
  18. 一种切换设备，其特征在于，所述切换设备包括：
    第一发送模块，用于向第二接入网设备发送切换请求消息，所述切换请求消息包括：第一无损切换标识；
    接收模块，用于接收所述第二接入网设备发送的切换确认消息，所述切换确认消息包括透明容器信息元素和位于所述透明容器信息元素外的第二无损切换标识，所述透明容器信息元素包括第三无损切换标识；
    第二发送模块，用于将所述透明容器信息元素作为切换命令发送给终端设备；
    其中，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换。
  19. 根据权利要求18所述的切换设备，其特征在于，
    所述切换请求消息还包括：用于指示第一承载的当前包数据汇聚协议PDCP序列号SN 长度的第一配置信息；
    所述切换确认消息还包括：用于指示所述第二接入网设备能否支持所述第一承载的当前PDCP SN长度的能力信息，且当所述能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述切换确认消息还包括：用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息；
    其中，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载。
  20. 根据权利要求19所述的切换设备，其特征在于，所述切换设备还包括：
    第一转发模块，用于在所述切换确认消息中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，向所述第二接入网设备转发：所述第一接入网设备的缓存数据中的第一PDCP服务数据单元SDU，第一PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
  21. 根据权利要求19或20所述的切换设备，其特征在于，所述切换设备还包括：
    构造模块，用于在所述切换确认消息中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，根据所述目标PDCP SN长度构造上行PDCP SDU的接收状态元素；
    第二转发模块，用于向所述第二接入网设备转发所述上行PDCP SDU的接收状态元素。
  22. 一种切换设备，其特征在于，所述切换设备包括：
    第一接收模块，用于接收第一接入网设备发送的切换命令，所述切换命令为切换确认消息中的透明容器信息元素，所述透明容器信息元素包括第三无损切换标识，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换；
    切换模块，用于根据所述切换命令，在所述第一接入网设备与第二接入网设备之间进行无数据损失的切换。
  23. 根据权利要求22所述的切换设备，其特征在于，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；
    所述切换模块还用于：
    在所述透明容器信息元素中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，为所述第二承载配置所述目标PDCP SN长度；
    向所述第二接入网设备发送所述终端设备的缓存数据中的第二PDCP SDU，所述第二PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
  24. 根据权利要求22或23所述的切换设备，其特征在于，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及 用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；所述切换模块还用于：
    在所述透明容器信息元素中的能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，根据所述目标PDCP SN长度构造下行PDCP SDU的接收状态报告；
    向所述第二接入网设备发送所述下行PDCP SDU的接收状态报告。
  25. 根据权利要求22至24任一所述的切换设备，其特征在于，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；所述切换模块还用于：
    在所述透明容器信息元素中的能力信息指示所述第二接入网设备能够支持所述当前PDCP SN长度时，为所述第二承载配置所述当前PDCP SN长度；
    向所述第二接入网设备发送所述终端设备的缓存数据中已分配PDCP SN的PDCP SDU；
    在确认所述终端设备的缓存数据中已分配PDCP SN的PDCP SDU均成功发送至所述第二接入网设备后，为所述第二承载配置所述目标PDCP SN长度。
  26. 根据权利要求22至25任一所述的切换设备，其特征在于，所述透明容器信息元素还包括：用于指示所述第二接入网设备能否支持第一承载的当前PDCP SN长度的能力信息，以及用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载；所述切换模块还用于：
    在所述透明容器信息元素中的能力信息指示所述第二接入网设备能够支持所述当前PDCP SN长度时，根据所述当前PDCP SN长度构造下行PDCP SDU的接收状态报告；
    向所述第二接入网设备发送所述下行PDCP SDU的接收状态报告。
  27. 一种切换设备，其特征在于，所述切换设备包括：
    第一接收模块，用于接收第一接入网设备发送的切换请求消息，所述切换请求消息包括：第一无损切换标识；
    发送模块，用于根据所述切换请求消息，向所述第一接入网设备发送切换确认消息，所述切换确认消息包括透明容器信息元素和位于所述透明容器信息元素外的第二无损切换标识，所述透明容器信息元素包括第三无损切换标识；
    其中，第一无损切换标识、第二无损切换标识和第三无损切换标识用于指示进行无数据损失的切换。
  28. 根据权利要求27所述的切换设备，其特征在于，
    所述切换请求消息还包括：用于指示第一承载的当前PDCP SN长度的第一配置信息；
    所述切换确认消息还包括：用于指示所述第二接入网设备能否支持所述当前PDCP SN长 度的能力信息，且当所述能力信息指示所述第二接入网设备无法支持所述当前PDCP SN长度时，所述切换确认消息还包括：用于指示所述第二接入网设备分配给第二承载的目标PDCP SN长度的第二配置信息；
    其中，所述第一承载为所述终端设备与所述第一接入网设备之间的承载，所述第二承载为所述终端设备与所述第二接入网设备之间的承载。
  29. 根据权利要求28所述的切换设备，其特征在于，所述切换设备还包括：
    第二接收模块，用于接收所述第一接入网设备转发的：所述第一接入网设备的缓存数据中的第一PDCP SDU，第一PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
  30. 根据权利要求28或29所述的切换设备，其特征在于，所述切换设备还包括：
    第三接收模块，用于接收所述第一接入网设备转发的上行PDCP SDU的接收状态元素，所述上行PDCP SDU的接收状态元素是根据所述目标PDCP SN长度构造的。
  31. 根据权利要求28至30任一所述的切换设备，其特征在于，所述切换设备还包括：
    第四接收模块，用于接收所述终端设备发送的所述终端设备的缓存数据中的第二PDCP SDU，所述第二PDCP SDU中的PDCP SN小于或等于所述目标PDCP SN长度所对应的最大PDCP SN。
  32. 根据权利要求28至31任一所述的切换设备，其特征在于，所述切换设备还包括：
    第五接收模块，用于接收所述终端设备发送的下行PDCP SDU的接收状态报告，所述下行PDCP SDU的接收状态报告是根据所述目标PDCP SN长度构造的。
  33. 根据权利要求28至32任一所述的切换设备，其特征在于，所述切换设备还包括：
    第六接收模块，用于接收所述终端设备发送的所述终端设备的缓存数据中已分配PDCP SN的PDCP SDU。
  34. 根据权利要求28至33任一所述的切换设备，其特征在于，所述切换设备还包括：
    第七接收模块，用于接收所述终端设备发送的下行PDCP SDU的接收状态报告，所述下行PDCP SDU的接收状态报告是根据所述当前PDCP SN长度构造的。
  35. 一种通信系统，其特征在于，所述通信系统包括：
    第一接入网设备、终端设备和第二接入网设备，
    所述第一接入网设备为权利要求18至21任一所述的切换设备；
    所述终端设备为权利要求22至26任一所述的切换设备；
    所述第二接入网设备为权利要求27至34任一所述的切换设备。
  36. 一种切换设备，其特征在于，所述切换设备包括处理器，所述处理器用于与存储器 耦合，并读取存储器中的指令并根据所述指令执行如权利要求1-17中任一项所述的方法。
  37. 一种可读存储介质，其特征在于，所述可读存储介质中存储程序，所述程序在执行时，权1至17中任一项所述的方法步骤被执行。
PCT/CN2018/074601 2017-02-03 2018-01-30 设备切换方法及设备、承载配置方法及设备、通信系统 WO2018141241A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710063477.8 2017-02-03
CN201710063477.8A CN108391297B (zh) 2017-02-03 2017-02-03 设备切换方法及设备、承载配置方法及设备、通信系统

Publications (1)

Publication Number Publication Date
WO2018141241A1 true WO2018141241A1 (zh) 2018-08-09

Family

ID=63040268

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/074601 WO2018141241A1 (zh) 2017-02-03 2018-01-30 设备切换方法及设备、承载配置方法及设备、通信系统

Country Status (2)

Country Link
CN (1) CN108391297B (zh)
WO (1) WO2018141241A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021022527A1 (en) * 2019-08-07 2021-02-11 Nec Corporation Simultaneous connectivity based handover

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020087457A1 (zh) * 2018-11-01 2020-05-07 Oppo广东移动通信有限公司 数据的传输方法及终端
KR20220002597A (ko) * 2019-04-30 2022-01-06 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 셀 핸드오버 방법 및 기기

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011017849A1 (zh) * 2009-08-14 2011-02-17 华为技术有限公司 数据处理方法和装置
CN102438284A (zh) * 2011-12-12 2012-05-02 大唐移动通信设备有限公司 一种基于基站内小区切换的数据倒换方法及装置
CN103533586A (zh) * 2012-07-03 2014-01-22 电信科学技术研究院 切换过程中的信令交互及层重建的方法和设备
US20140254551A1 (en) * 2013-03-11 2014-09-11 Qualcomm Incorporated Method and apparatus for media access control -based fast cell switching for high-speed packet access

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997988A (zh) * 2009-08-18 2011-03-30 中兴通讯股份有限公司 一种彩铃设置方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011017849A1 (zh) * 2009-08-14 2011-02-17 华为技术有限公司 数据处理方法和装置
CN102438284A (zh) * 2011-12-12 2012-05-02 大唐移动通信设备有限公司 一种基于基站内小区切换的数据倒换方法及装置
CN103533586A (zh) * 2012-07-03 2014-01-22 电信科学技术研究院 切换过程中的信令交互及层重建的方法和设备
US20140254551A1 (en) * 2013-03-11 2014-09-11 Qualcomm Incorporated Method and apparatus for media access control -based fast cell switching for high-speed packet access

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021022527A1 (en) * 2019-08-07 2021-02-11 Nec Corporation Simultaneous connectivity based handover

Also Published As

Publication number Publication date
CN108391297B (zh) 2021-02-09
CN108391297A (zh) 2018-08-10

Similar Documents

Publication Publication Date Title
US11540349B2 (en) Data transmission method, access network device, terminal, and communications system
JP6945659B2 (ja) 情報処理方法および関連装置
US20190274075A1 (en) Handover processing method and base station
JP4536976B2 (ja) 移動通信システムにおいて高信頼リンクを提供する技術
WO2019242748A1 (zh) 信息传输方法及装置
US20200112885A1 (en) Handover control method and apparatus
EP2484146B1 (en) Method of controlling data flow in wireless communication system
US20220070748A1 (en) Data transmission method and related device
CN111148163B (zh) 通信方法及装置
WO2019242749A1 (zh) 一种切换方法及装置
CN111490942A (zh) 封包路由方法与通信系统
WO2018141241A1 (zh) 设备切换方法及设备、承载配置方法及设备、通信系统
CN110972215B (zh) 一种切换方法及基站
US20230141231A1 (en) Mobile Edge Computing Processing Method and Related Device
WO2018202133A1 (zh) 数据处理方法及设备
KR102459063B1 (ko) 전송 장치 및 전송 장치에서 통신을 처리하기 위해 수행되는 방법
WO2020030176A1 (zh) 数据传输的方法和设备
JP2023062123A (ja) 無線通信装置、無線通信方法、及び無線通信システム
US20210385031A1 (en) Data retransmission indication and processing method and device
WO2020088177A1 (zh) 一种通信方法、移动性管理实体、用户设备及服务网关
WO2018228545A1 (zh) 信息处理方法以及相关装置
CN112470527B (zh) 一种数据传输方法及装置
US11968633B2 (en) Relay communication method and apparatus
WO2024032352A1 (zh) 数据处理方法及装置
WO2023011111A1 (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: 18748149

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18748149

Country of ref document: EP

Kind code of ref document: A1