WO2021127940A1 - 切换方法、切换处理方法、通信系统及存储介质 - Google Patents

切换方法、切换处理方法、通信系统及存储介质 Download PDF

Info

Publication number
WO2021127940A1
WO2021127940A1 PCT/CN2019/127655 CN2019127655W WO2021127940A1 WO 2021127940 A1 WO2021127940 A1 WO 2021127940A1 CN 2019127655 W CN2019127655 W CN 2019127655W WO 2021127940 A1 WO2021127940 A1 WO 2021127940A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
network device
user equipment
convergence protocol
packet data
Prior art date
Application number
PCT/CN2019/127655
Other languages
English (en)
French (fr)
Inventor
尤心
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201980100520.0A priority Critical patent/CN114424622B/zh
Priority to PCT/CN2019/127655 priority patent/WO2021127940A1/zh
Publication of WO2021127940A1 publication Critical patent/WO2021127940A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H04W36/185—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection using make before break

Definitions

  • This application relates to the field of communications, and specifically, to a switching method, a switching processing method, a communication system, and a storage medium.
  • the dual active protocol stack (Dual Active Protocol Stack, referred to as DAPS) optimization for reducing the interruption time during handover is proposed
  • the main idea of the method is that during the handover, the user equipment (User Equipment, referred to as UE) will simultaneously maintain the protocol stacks of the source cell and the target cell.
  • DAPS switching supports DAPS per Data Wireless Bearer (DRB), which means that during the switching process, some DRBs will maintain a dual active stack, while DRB switching without DAPS will follow the current switching process.
  • DRB Data Wireless Bearer
  • the Packet Data Convergence Protocol (PDCP) and Radio Link Control (RLC) entities corresponding to the DRB will be rebuilt to the target side after receiving the handover command.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • this topic includes Long Term Evolution (LTE for short) and New Radio (NR for short).
  • the NR system supports the handover process of connected UEs.
  • the system When a user who is using network services moves from one cell to another, or due to wireless transmission traffic load adjustment, activation operation and maintenance, equipment failure, etc., in order to ensure the continuity of communication and the quality of service, the system must transfer the user to The communication link with the original cell is transferred to the new cell, that is, the handover process is performed.
  • the UE After the UE fails to perform the DAPS handover, it can return to the connection of the source cell. For those DRBs that are not configured with DAPS, the source cell side does not retain its corresponding protocol stack, and the problem of data transmission interruption may occur.
  • the embodiments of the present application provide a switching method, a switching processing method, a communication system, and a storage medium.
  • the technical problem of data transmission interruption may occur after the UE fails to perform the DAPS handover, for the DRB that is not configured with DAPS, because the source cell does not retain the corresponding protocol stack.
  • a handover method including: a UE receives a handover command, where the handover command is used to instruct the UE to perform DAPS-based handover; the UE will correspond to the PDCP entity corresponding to the DRB not configured with DAPS And the RLC entity is rebuilt to the target access network device; the UE initiates random access to the target access network device based on the handover command.
  • the UE in the case that the UE fails to randomly access the target access network device, for the DRB configured with DAPS, the UE reconfigures the PDCP entity of the DRB to the normal PDCP entity, and releases the RLC corresponding to the DRB on the target side entity.
  • the above method further includes: in the case that the UE fails to randomly access the target access network device, for the DRB not configured with DAPS, the UE reestablishes the PDCP entity corresponding to the DRB and the RLC entity corresponding to the PDCP entity to the source connection Network access equipment; or the UE establishes corresponding PDCP and RLC entities based on the reserved PDCP and RLC entity configuration information of the source access network equipment.
  • the handover command carries DRB indication information for instructing DAPS handover.
  • the above method further includes: for the DRB that has been configured with DAPS, the UE reconfigures the PDCP entity of the DRB to the PDCP entity of the dual active data protocol, and establishes the RLC entity corresponding to the PDCP entity.
  • a handover processing method which includes: when the UE fails to randomly access the target access network device, for the DRB not configured with DAPS, the UE changes the PDCP entity corresponding to the DRB And the RLC entity corresponding to the PDCP entity is rebuilt to the source access network device; or the UE establishes the corresponding PDCP and RLC entities based on the reserved PDCP and RLC entity configuration information of the source access network device.
  • a handover method including: a UE receives a handover command, where the handover command is used to instruct the UE to perform DAPS-based handover; the UE will correspond to a DRB not configured with DAPS
  • the PDCP entity and the RLC entity are re-established to the target access network device, and the source access network device retains the configuration information of the PDCP entity and the RLC entity; the UE initiates random access to the target access network device, and when the random access fails, the UE Reconnect the source access network device based on the configuration information.
  • a handover method including: in the case that the UE handover fails, the source access network device obtains the configuration information of the PDCP entity corresponding to the DRB and the RLC entity, wherein the handover The command is used to instruct the UE to perform DAPS-based handover on the DRB; the source access network device establishes the corresponding PDCP and RLC entities based on the obtained configuration information of the PDCP and RLC entities, and establishes a connection with the UE through the DRB.
  • the source access network device obtains the configuration information of the PDCP entity and RLC entity corresponding to the DRB, including: after the source access network device forwards the handover command to the UE, the source access network device retains the current PDCP entity and RLC The configuration information of the entity; when the UE handover fails, the source access network device determines the PDCP entity corresponding to the DRB and the configuration information of the RLC entity based on the current PDCP entity and the configuration information of the RLC entity, where the handover command is used to instruct the UE Perform DAPS-based handover on the DRB; or, the source access network device receives the PDCP entity corresponding to the DRB and the configuration information of the RLC entity from the target access network device, where the PDCP entity corresponding to the DRB received from the target access network device and
  • the configuration information of the RLC entity is that when the source access network device receives the handover command, the source access network device has forwarded the data to the target access network device.
  • the above method further includes: in the case that the source access network device receives the handover command, the source access network device has forwarded the designated data to the target access network device, and after the user equipment handover fails, the source access network device The network device receives the designated data sent by the target access network device; or the source access network device continues to retain the designated data after forwarding the designated data to the target access network device.
  • the aforementioned designated data includes at least downlink data and sequence numbers for which correct feedback has not been received.
  • the above configuration information includes at least one of the following: serial number allocation status, counter maintenance status, reordering window parameters, reordering window parameters, reordering window variables, reordering window variables, timer-related configurations, and compression/decompression-related configurations .
  • a switching device applied to user equipment including: a communication unit for receiving a switching command, where the switching command is used to instruct the user equipment to perform switching based on the dual activation protocol stack
  • the processing unit is used to reconstruct the packet data convergence protocol entity and the radio link control entity corresponding to the data radio bearer to the target access network device for the data radio bearer that is not configured with the dual activation protocol stack; and to connect to the target based on the handover command
  • the connected device initiates random access.
  • the processing unit is further configured to reconfigure the packet data convergence protocol entity of the data radio bearer to the data radio bearer configured with the dual activation protocol stack in the case that the user equipment fails to randomly access the target access network device Standard normal PDCP entity, and release the radio link control entity corresponding to the target access network device and the data radio bearer.
  • the processing unit is further configured to perform the following operation: when the user equipment fails to randomly access the target access network device, for the data radio bearer that is not configured with the dual activation protocol stack, the data radio bears the corresponding packet data
  • the convergence protocol entity and the radio link control entity corresponding to the packet data convergence protocol entity are reconstructed to the source access network device; or, based on the reserved packet data convergence protocol of the source access network device and the configuration information of the wireless link control entity The corresponding packet data convergence protocol and radio link control entity.
  • the above-mentioned handover command carries indication information of DRB for instructing DAPS handover.
  • the foregoing processing unit is further configured to perform the following operations: for the data radio bearer that has been configured with the dual activation protocol stack, reconfigure the packet data convergence protocol entity of the data radio bearer to the packet data convergence protocol of the dual activation data protocol Entity, and establish a radio link control entity corresponding to the packet data convergence protocol entity.
  • a UE including: the above-mentioned handover device.
  • a UE including: a signal transceiving circuit for receiving a handover command, where the handover command is used to instruct the UE to perform DAPS-based handover; Configure the DRB of DAPS, rebuild the PDCP entity and RLC entity corresponding to the DRB to the target access network device; and initiate random access to the target access network device.
  • the above-mentioned processor is further configured to reconfigure the PDCP entity of the DRB to the standard normal PDCP entity for the DRB configured with DAPS when the user random access fails, and release the RLC entity corresponding to the DRB on the target side.
  • the above-mentioned processor is further configured to, for a DRB not configured with DAPS, reconstruct the PDCP entity corresponding to the DRB and the RLC entity corresponding to the PDCP entity to the source access network device when the random access of the UE fails; or, The corresponding PDCP and RLC entities are established based on the reserved configuration information of the PDCP and RLC entities of the source access network device.
  • a switching device which is applied to a source access network device, and the switching device includes: an acquisition module for acquiring data radio bearer correspondence when the user equipment fails to switch The configuration information of the packet data convergence protocol entity and the wireless link control entity; the establishment module is used to establish the corresponding packet data convergence protocol and wireless link based on the obtained configuration information of the packet data convergence protocol and the wireless link control entity Controlling the entity, and establishing a connection with the user equipment through the data radio bearer.
  • the acquisition module includes: a first access module, configured to retain the configuration information of the current packet data convergence protocol entity and the radio link control entity after the source access network device forwards the handover command to the user equipment;
  • the configuration information of the packet data convergence protocol entity and the radio link control entity corresponding to the data radio bearer is determined based on the configuration information of the current packet data convergence protocol entity and the radio link control entity, where the switch command is used To instruct the user equipment to perform handover based on the dual activation protocol stack on the data radio bearer;
  • the second access module is used to receive the configuration of the packet data convergence protocol entity and the radio link control entity corresponding to the data radio bearer from the target access network device Information, where the configuration information of the packet data convergence protocol entity and the radio link control entity corresponding to the data radio bearer received from the target access network device is that when the source access network device receives the handover command, the source access network device has forwarded it The data is given to the target access network device.
  • the above device is also used to perform the following processing: in the case that the source access network device receives the handover command, the source access network device has forwarded the designated data to the target access network device, and after the user equipment fails to switch, the source access network device The network access device receives the designated data sent by the target access network device; or the source access network device continues to retain the designated data after forwarding the designated data to the target access network device.
  • the aforementioned designated data includes at least downlink data and sequence numbers for which correct feedback has not been received.
  • an access network device including: the above-mentioned switching device.
  • a communication system includes: a UE, a target access network device, and a source access network device; wherein, the source access network device is used to connect the target access network
  • the handover command of the device is forwarded to the UE, where the handover command is used to instruct the UE to perform DAPS-based handover; the UE is used to disconnect the source access network device when receiving the handover command, and check the unconfigured DAPS In the DRB, the PDCP entity and the RLC entity corresponding to the DRB are reconstructed to the target access network device to initiate random access to the target access network device based on the handover command.
  • a computer-readable storage medium for storing a computer program that enables a computer to execute the switching method described above.
  • a computer program product including computer program instructions, which cause a computer to execute the switching method described above.
  • the UE when the UE receives the handover command, it rebuilds the PDCP entity and RLC entity corresponding to the DRB not configured with DAPS to the target access network device. Therefore, when the handover fails, the UE switches back to the source After accessing the network equipment, the transmission of non-DAPS HO (Handover) DRB can be continued, which solves the problem that in related technologies, after the UE fails to perform DAPS handover, for the DRB that is not configured with DAPS, because the source cell does not retain the corresponding protocol stack, There may be technical problems with interruption of data transmission.
  • HO Heandover
  • Fig. 1 is a schematic diagram of a handover procedure based on an Xn interface according to an embodiment of the present application
  • Fig. 2 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • Fig. 3 is a schematic flowchart of a handover method according to an embodiment of the present application.
  • Fig. 4 is a schematic flowchart of a handover processing method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another handover method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another handover method according to an embodiment of the present application.
  • Fig. 7 is a schematic structural diagram of a user equipment according to an embodiment of the present application.
  • Fig. 8 is a schematic structural diagram of a switching device according to an embodiment of the present application.
  • Fig. 9 is a schematic structural diagram of another switching device according to an embodiment of the present application.
  • Handover preparation including measurement control and reporting, handover request and confirmation.
  • the handover confirmation message contains the handover command generated by the target cell.
  • the source cell does not allow any modification to the handover command generated by the target cell, and directly forwards the handover command to the UE.
  • the UE immediately executes the handover process after receiving the handover command, that is, the UE disconnects the source cell and connects to the target cell (such as performing random access, sending Radio Resource Control (RRC)).
  • RRC Radio Resource Control
  • the handover is completed Message to the target base station, etc.).
  • the target cell and the access and mobility management function (Access and Mobility on Management Function, abbreviated as AMF) and the user plane function (User Plane Function, abbreviated as UPF) execute path switch (Path Switch, abbreviated as PS) )
  • AMF Access and Mobility on Management Function
  • UPF User Plane Function
  • PS path switch
  • the UE context includes but is not limited to UE security information (for example, UE Security Capabilities), UE capability information, Protocol Data Unit (PDU) session information, etc. .
  • the UE when the handover fails, the UE will switch back to the source base station. However, because the source base station does not retain its corresponding protocol stack, the problem of data transmission interruption may occur. Regarding this problem, in the embodiment of this application, the UE rebuilds the PDCP and RLC entities corresponding to the DRB not configured with DAPS to the target base station, so that when the handover fails, the source base station can be based on the above-mentioned PDCP entity and RLC entity related configuration Re-access the UE to avoid interruption of data transmission.
  • the UE rebuilds the PDCP and RLC entities corresponding to the DRB not configured with DAPS to the target base station, so that when the handover fails, the source base station can be based on the above-mentioned PDCP entity and RLC entity related configuration Re-access the UE to avoid interruption of data transmission.
  • Fig. 2 is a schematic structural diagram of a communication system according to an embodiment of the present application; as shown in Fig. 4, the communication system includes: a user equipment 20, a target access network device 22, and a source access network device 24; among them:
  • the source access network device 24 is configured to forward a handover command of the target access network device to the user equipment, where the handover command is used to instruct the user equipment to perform handover based on the dual activation protocol stack;
  • the user equipment 20 is configured to disconnect the connection with the source access network device 24 when receiving the handover command, and rebuild the PDCP entity and the RLC entity corresponding to the DRB to the target radio bearer for the data radio bearer that is not configured with the dual activation protocol stack
  • the access network device 22 is used to initiate random access to the target access network device 22.
  • the user equipment 20 is also used to reconfigure the PDCP entity of the DRB to the normal PDCP entity for the DRB configured with DAPS in the case of failure to randomly access the target access network device, and release The RLC entity corresponding to the target access network device and the DRB.
  • the user equipment 20 is also used to, in the case where the random access to the target access network device fails, for the DRB not configured with DAPS, the PDCP entity corresponding to the DRB and the RLC entity corresponding to the PDCP entity The entity is rebuilt to the source access network device; or, the corresponding PDCP and RLC entities are established based on the reserved PDCP and RLC entity configuration information of the source access network device.
  • the source access network equipment includes but is not limited to: a source base station; the target access network equipment includes but is not limited to: a target base station.
  • the embodiment of the present application provides an embodiment of a switching method. It should be noted that the steps shown in the flowchart of the accompanying drawings can be performed on a computer such as a set of computer-executable instructions. It is executed in the system, and although the logical sequence is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than here.
  • Fig. 3 is a schematic flowchart of a handover method according to an embodiment of the present application. As shown in Fig. 1, the method includes the following steps:
  • Step S302 The target access network device sends a handover command to the source access network device, where the handover command is used to instruct the user equipment to perform DAPS-based handover.
  • Step S304 the source access network device forwards the handover command to the user equipment, and the user equipment receives the handover command;
  • the UE receives a handover command, the handover command instructs the UE to perform DAPS handover, and the handover command indicates a DRB for DAPS handover.
  • step S306 the user equipment reconstructs the PDCP entity and the RLC entity corresponding to the DRB not configured with DAPS to the target access network device.
  • Step S308 The user equipment initiates random access to the target access network device.
  • step of forwarding the handover command by the source access network device in steps S302 and S304 is optional, that is, when the UE has received the handover command, the above steps may not be performed.
  • synchronizing the UE to the target access network device includes the UE initiating random access to the target access network device, while the UE maintains radio link management (Radio Link Management, RLM for short) of the source access network device.
  • RLM Radio Link Management
  • the source access network device when the PDCP entity and the RLC entity corresponding to the data radio bearer not configured with DAPS are rebuilt to the target access network device, the source access network device retains the configuration information of the PDCP entity and the RLC entity.
  • the above-mentioned configuration information includes at least one of the following: serial number allocation status, counter maintenance status, reordering window and or reorganization window parameters and variables, timer-related configuration, and compression and decompression-related configuration.
  • the user equipment when the user equipment fails to randomly access the target access network device, for the data radio bearer configured with DAPS, the user equipment reconfigures the PDCP entity of the data radio bearer to the normal PDCP entity and releases it.
  • the user equipment when the user equipment fails to randomly access the target access network device, for a data radio bearer that is not configured with DAPS, the user equipment assigns the PDCP entity corresponding to the data radio bearer and the PDCP entity corresponding to the data radio bearer
  • the RLC entity is rebuilt to the source access network device; or the user equipment establishes the corresponding PDCP and RLC entities based on the reserved PDCP and RLC entity configuration information of the source access network device.
  • the source access network device when the source access network device receives the handover command, the source access network device has forwarded the designated data to the target access network device. After the user equipment handover fails, the target access network device The network device forwards the designated data to the source access network device again; or the source access network device continues to retain the designated data after forwarding the designated data to the target access network device.
  • the above-mentioned designated data includes at least downlink data and sequence numbers that have not received correct feedback.
  • the aforementioned handover command carries DRB indication information for instructing DAPS handover.
  • the UE can determine the DRB used for DAPS handover based on the indication information.
  • the user equipment reconfigures the PDCP entity of the data radio bearer to the PDCP entity of the dual active data protocol, and establishes the RLC entity corresponding to the PDCP entity.
  • the embodiment of the present application also provides another handover processing method. As shown in FIG. 4, the method includes:
  • Step S402 the user equipment fails to randomly access the target access network equipment
  • Step S404 For the data radio bearer that is not configured with DAPS, the user equipment reconstructs the PDCP entity corresponding to the DRB and the RLC entity corresponding to the PDCP entity to the source access network device;
  • Step S406 The user equipment establishes corresponding PDCP and RLC entities based on the reserved PDCP and RLC entity configuration information of the source access network device.
  • steps S404 and S406 are two parallel steps, that is, they are two independent steps, and there is no sequential relationship.
  • Using the above processing steps can also solve the technical problem of data transmission interruption in related technologies after the UE fails to perform the DAPS handover, for the DRB not configured with DAPS, because the source cell does not retain the corresponding protocol stack.
  • Fig. 5 is a schematic flowchart of another handover method according to an embodiment of the present application. As shown in Fig. 5, the method includes the following steps:
  • Step S502 The target access network device sends a handover command to the source access network device, where the handover command is used to instruct the user equipment to perform DAPS-based handover.
  • Step S506 the user equipment rebuilds the PDCP entity and the RLC entity corresponding to the data radio bearer not configured with DAPS to the target access network device, and the source access network device retains the configuration information of the PDCP entity and the RLC entity;
  • step S508 the user equipment initiates random access to the target access network device, and when the random access fails, the UE re-accesses the source access network device based on the above configuration information.
  • Fig. 6 is a schematic flowchart of another handover method according to an embodiment of the present application. As shown in Fig. 6, the method includes the following steps:
  • Step S602 In the case that the user equipment fails to switch, the source access network device obtains the PDCP entity corresponding to the DRB and the configuration information of the RLC entity, where the switch command is used to instruct the user equipment to perform DAPS-based switch on the DRB.
  • Step S604 The source access network device establishes corresponding PDP and RLC entities based on the acquired configuration information of the PDCP and RLC entities, and establishes a connection with the user equipment through the DRB.
  • the source access network device may obtain the configuration information of the PDCP entity and the RLC entity corresponding to the data radio bearer in the following manner: After the source access network device forwards the handover command to the user equipment, the source access network device forwards the handover command to the user equipment.
  • the network device retains the current PDCP entity and RLC entity configuration information; when the user equipment fails to switch, the source access network device determines the PDCP entity and RLC entity corresponding to the data radio bearer based on the current PDCP entity and RLC entity configuration information
  • the configuration information of the data radio bearer where the handover command is used to instruct the user equipment to perform DAPS-based handover of the data radio bearer; or the source access network device receives the configuration of the PDCP entity and the RLC entity corresponding to the data radio bearer from the target access network device Information, where the configuration information of the PDCP entity and RLC entity corresponding to the data radio bearer received from the target access network device is that when the source access network device receives the handover command, the source access network device has forwarded the data to the target access ⁇ Net equipment.
  • the source access network device receives the handover command, the source access network device has forwarded the specified data to the target access network device. After the user equipment fails to switch, the source access network device receives the transmission from the target access network device. Or, the source access network device continues to retain the specified data after forwarding the specified data to the target access network device.
  • the above-mentioned designated data includes at least downlink data and sequence numbers that have not received correct feedback.
  • the configuration information includes at least one of the following: serial number allocation status, counter maintenance status, reordering window parameters, reordering window parameters, reordering window variables, restructuring window variables, timer-related configuration, and compression Unzip the relevant configuration.
  • Using the above processing steps can also solve the technical problem of data transmission interruption in related technologies after the UE fails to perform the DAPS handover, for the DRB not configured with DAPS, because the source cell does not retain the corresponding protocol stack.
  • Fig. 7 is a schematic structural diagram of a user equipment according to an embodiment of the present application. As shown in Fig. 7, the user equipment 7 includes:
  • Signal transceiving circuit 70 for receiving a switching command, wherein the switching command is used to instruct the user equipment to perform DAPS-based switching.
  • the processor 72 is configured to reconstruct the PDCP entity and the RLC entity corresponding to the data radio bearer to the target access network device for the data radio bearer that is not configured with DAPS; and initiate random access to the target access network device.
  • the user equipment may further include a memory 74.
  • the above-mentioned processor 72 is further configured to reconfigure the PDCP entity of the data radio bearer to the standard normal PDCP entity for the data radio bearer configured with DAPS when the user random access fails, and release the target The RLC entity corresponding to the data radio bearer on the side.
  • the reconfiguration content includes but is not limited to: releasing the target side header compression, de-header compression, and encryption/decryption functions.
  • the above-mentioned processor 72 is further configured to, when the user equipment fails random access, for the DRB not configured with DAPS, re-establish the PDCP entity corresponding to the DRB and the RLC entity corresponding to the PDCP entity to the source connection.
  • Network access equipment or, establish corresponding PDCP and RLC entities based on the reserved configuration information of the PDCP and RLC entities of the source access network equipment.
  • the above-mentioned processor 72 is also configured to, when the user equipment fails random access, if a handover command is received, the source access network device has forwarded data to the target access network device, and the UE HOF Afterwards, the target access network device should forward the forwarded data to the source access network device again.
  • the data includes the downlink data and the SN number that have not received correct feedback.
  • the embodiment of the present application also provides a switching device, which is applied to user equipment.
  • the switching device includes:
  • the communication unit 80 is used to receive a handover command, where the handover command is used to instruct the user equipment to perform DAPS-based handover; the communication unit 80 can be implemented by a signal transceiving circuit as shown in FIG. 7, of course, it can also be represented as a Software program module.
  • the processing unit 82 is configured to reconstruct the PDCP entity and the RLC entity corresponding to the DRB to the target access network device for the DRB that is not configured with DAPS; and initiate random access to the target access network device based on the handover command.
  • the processing unit 82 can be implemented by the processor 72 shown in FIG. 7, of course, it can also be represented as a software program module.
  • the UE when the UE fails in random access, it can use different solutions to switch back to the source base station for different situations, for example:
  • the processing unit 82 is further configured to reconfigure the PDCP entity of the DRB to a standard normal PDCP entity for the DRB configured with DAPS when the UE fails to randomly access the target access network device, and release the target access network device and the DRB The corresponding RLC entity.
  • the processing unit 82 is further configured to perform the following operations: when the user equipment fails to randomly access the target access network device, for the DRB not configured with DAPS, the PDCP entity corresponding to the DRB and the RLC entity corresponding to the PDCP entity The entity is rebuilt to the source access network device; or, the corresponding PDCP and RLC entities are established based on the reserved PDCP and RLC entity configuration information of the source access network device.
  • the above switching command carries DRB indication information for instructing DAPS switching.
  • the processing unit 82 is further configured to perform the following operations: For the DRB that has been configured with DAPS, reconfigure the PDCP entity of the DRB to the PDCP entity of the dual active data protocol, and establish a correspondence with the PDCP entity The RLC entity.
  • the embodiment of the present application also provides a user equipment, and the user equipment includes but is not limited to the switching apparatus in the embodiment shown in FIG. 8.
  • An embodiment of the present application also provides a switching device, which is applied to a source access network device. As shown in FIG. 9, the switching device includes:
  • the obtaining module 90 is configured to obtain the configuration information of the PDCP entity corresponding to the DRB and the RLC entity when the user equipment fails to switch;
  • the establishment module 92 is configured to establish corresponding PDCP and RLC entities based on the obtained configuration information of the PDCP and RLC entities, and establish a connection with the user equipment through the DRB.
  • the obtaining module 90 includes:
  • the first access module 900 is configured to retain the configuration information of the current PDCP entity and RLC entity after the source access network device forwards the handover command to the user equipment; when the user equipment fails to switch, based on the current PDCP entity and RLC entity
  • the configuration information of the entity determines the PDCP entity corresponding to the DRB and the configuration information of the RLC entity, where the handover command is used to instruct the user equipment to perform DAPS-based handover on the DRB;
  • the second access module 902 is configured to receive configuration information of the PDCP entity and RLC entity corresponding to the DRB from the target access network device, where the configuration information of the PDCP entity and RLC entity corresponding to the DRB received from the target access network device is When the source access network device receives the handover command, the source access network device has forwarded the data to the target access network device.
  • the acquiring module 900 is further configured to perform the following processing procedure: when the source access network device receives the handover command, the source access network device has forwarded the designated data to the target access network device, and the user equipment After the handover fails, the source access network device receives the designated data sent by the target access network device; or the source access network device continues to retain the designated data after forwarding the designated data to the target access network device.
  • the designated data includes at least downlink data and sequence numbers that have not received correct feedback.
  • An embodiment of the present application also provides an access network device, including: the switching device described in FIG. 9.
  • the embodiment of the present application also provides a computer-readable storage medium for storing a computer program that enables a computer to execute the switching method described above. For example, the following method may be executed: receiving a switching command, wherein the switching The command is used to instruct the UE to perform DAPS-based handover; rebuild the PDCP entity and RLC entity corresponding to the DRB not configured with DAPS to the target access network device; and initiate random access to the target access network device based on the handover command.
  • the embodiments of the present application also provide a computer program product, including computer program instructions, which cause a computer to execute the switching method described above.
  • the disclosed technical content can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units may be a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, units or modules, and may be in electrical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes. .

Abstract

本申请公开了一种切换方法、切换处理方法、通信系统及存储介质。其中，该方法包括：用户设备接收切换命令，其中，该切换命令用于指示用户设备执行基于双激活协议栈的切换；用户设备将与未配置双激活协议栈的数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体重建至目标接入网设备；用户设备基于切换命令向目标接入网设备发起随机接入。

Description

切换方法、切换处理方法、通信系统及存储介质 技术领域
本申请涉及通信领域，具体而言，涉及一种切换方法、切换处理方法、通信系统及存储介质。
背景技术
目前，在第三代合作伙伴计划(3rd Generation Partnership Project，简称为3GPP)移动性增强课题中，提出了对于切换时减小中断时间的双激活协议栈(Dual Active Protocol Stack，简称为DAPS)优化方法，主要思想是在切换期间用户设备(User Equipment，简称为UE)会同时保持源小区和目标小区的协议栈。并且DAPS切换支持per数据无线承载(Data Wireless Bearer，简称为DRB)的DAPS，也就是说切换过程中，一部分DRB会保持双激活栈，而未配置DAPS的DRB切换时会效仿现在的切换流程，该DRB对应的分组数据汇聚协议(Packet Data Convergence Protocol，简称为PDCP)和无线链路控制(Radio Link Control，简称为RLC)实体会在收到切换命令后重建至目标侧。其中，该课题包括长期演进(Long Term Evolution，简称为LTE)和新无线(New Radio，简称为NR)。
在进行切换时，与LTE系统相似，NR系统支持连接态UE的切换过程。当正在使用网络服务的用户从一个小区移动到另一个小区，或由于无线传输业务负荷量调整、激活操作维护、设备故障等原因，为了保证通信的连续性和服务的质量，系统要将该用户与原小区的通信链路转移到新的小区上，即执行切换过程。
UE执行DAPS切换失败后可以回到源小区的连接，对于那些未配置DAPS的DRB，源小区侧未保留其对应的协议栈，可能会出现数据传输中断的问题。
针对上述的问题，目前尚未提出有效的解决方案。
发明内容
本申请实施例提供了一种切换方法、切换处理方法、通信系统及存储介质。以至少解决相关技术中，在UE执行DAPS切换失败后，对于未配置DAPS的DRB，由于源小区未保留对应的协议栈，可能会出现数据传输中断的技术问题。
根据本申请实施例的一个方面，提供了一种切换方法，包括：UE接收切换命令，其中，该切换命令用于指示UE执行基于DAPS的切换；UE将与未配置DAPS的DRB 对应的PDCP实体以及RLC实体重建至目标接入网设备；UE基于切换命令向目标接入网设备发起随机接入。
可选地，在UE随机接入目标接入网设备失败的情况下，对于配置了DAPS的DRB，UE重配DRB的PDCP实体至标准(normal)PDCP实体，并释放目标侧与DRB对应的RLC实体。
可选地，上述方法还包括：在UE随机接入目标接入网设备失败的情况下，对于未配置DAPS的DRB，UE将DRB对应的PDCP实体以及与PDCP实体对应的RLC实体重建至源接入网设备；或者UE基于保留的源接入网设备的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体。
可选地，切换命令中携带有用于指示DAPS切换的DRB的指示信息。
可选地，上述方法还包括：对已经配置了DAPS的DRB，UE将DRB的PDCP实体重配为双激活数据协议的PDCP实体，并建立与PDCP实体对应的RLC实体。
根据本申请实施例的另一方面，还提供了一种切换处理方法，包括：在UE随机接入目标接入网设备失败的情况下，对于未配置DAPS的DRB，UE将DRB对应的PDCP实体以及与PDCP实体对应的RLC实体重建至源接入网设备；或者UE基于保留的源接入网设备的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体。
根据本申请实施例的又一方面，还提供了一种切换方法，包括：UE接收切换命令，其中，该切换命令用于指示UE执行基于DAPS的切换；UE将与未配置DAPS的DRB对应的PDCP实体以及RLC实体重建至目标接入网设备，并且，源接入网设备保留PDCP实体以及RLC实体的配置信息；UE对目标接入网设备发起随机接入，在随机接入失败时，UE基于配置信息重新接入源接入网设备。
根据本申请实施例的又一方面，还提供了一种切换方法，包括：在UE切换失败的情况下，源接入网设备获取DRB对应的PDCP实体以及RLC实体的配置信息，其中，该切换命令用于指示UE对DRB执行基于DAPS的切换；源接入网设备基于获取的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体，并通过DRB建立与UE的连接。
可选地，源接入网设备获取DRB对应的PDCP实体以及RLC实体的配置信息，包括：在源接入网设备将切换命令转发至UE后，源接入网设备保留当前的PDCP实体以及RLC实体的配置信息；在UE切换失败时，源接入网设备基于当前的PDCP实体以及RLC实体的配置信息确定与DRB对应的PDCP实体以及RLC实体的配置信息，其中，该切换命令用于指示UE对DRB执行基于DAPS的切换；或者，源接入网设备从目标接入网设备接收DRB对应的PDCP实体以及RLC实体的配置信息，其中，从 目标接入网设备接收的DRB对应的PDCP实体以及RLC实体的配置信息为源接入网设备接收到切换命令时，源接入网设备已经转发了数据给目标接入网设备。
可选地，上述方法还包括：在源接入网设备收到切换命令的情况下，源接入网设备已经转发了指定数据给目标接入网设备，在用户设备切换失败后，源接入网设备接收目标接入网设备发送的指定数据；或者，源接入网设备在转发指定数据给目标接入网设备后，继续保留指定数据。
可选地，上述指定数据中至少包括未收到正确反馈的下行数据以及序列号。
可选地，上述配置信息包括以下至少之一：序列号分配状态、计数器维护状态、重排序窗口参数、重组窗口参数、重排序窗口变量、重组窗口变量、计时器相关配置和压缩解压缩相关配置。
根据本申请实施例的又一方面，提供了一种切换装置，应用于用户设备，包括：通信单元，用于接收切换命令，其中，切换命令用于指示用户设备执行基于双激活协议栈的切换；处理单元，用于对未配置双激活协议栈的数据无线承载，将数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体重建至目标接入网设备；以及基于切换命令向目标接入网设备发起随机接入。
可选地，处理单元，还用于在用户设备随机接入目标接入网设备失败的情况下，对于配置了双激活协议栈的数据无线承载，重配数据无线承载的分组数据汇聚协议实体至标准normal PDCP实体，并释放目标接入网设备与数据无线承载对应的无线链路控制实体。
可选地，处理单元，还用于执行以下操作：在用户设备随机接入目标接入网设备失败的情况下，对于未配置双激活协议栈的数据无线承载，将数据无线承载对应的分组数据汇聚协议实体以及与分组数据汇聚协议实体对应的无线链路控制实体重建至源接入网设备；或者，基于保留的源接入网设备的分组数据汇聚协议和无线链路控制实体的配置信息建立相应的分组数据汇聚协议和无线链路控制实体。
可选地，上述切换命令中携带有用于指示DAPS切换的DRB的指示信息。
可选地，上述处理单元，还用于执行以下操作：对已经配置了双激活协议栈的数据无线承载，将数据无线承载的分组数据汇聚协议实体重配为双激活数据协议的分组数据汇聚协议实体，并建立与分组数据汇聚协议实体对应的无线链路控制实体。
根据本申请实施例的又一方面，提供了一种UE，包括：以上所述的切换装置。
根据本申请实施例的又一方面，提供了一种UE，包括：信号收发电路，用于接收切换命令，其中，该切换命令用于指示UE执行基于DAPS的切换；处理器，用于对 未配置DAPS的DRB，将DRB对应的PDCP实体以及RLC实体重建至目标接入网设备；以及对目标接入网设备发起随机接入。
可选地，上述处理器，还用于在用户随机接入失败时，对于配置了DAPS的DRB，重配DRB的PDCP实体至标准normal PDCP实体，并释放目标侧与DRB对应的RLC实体。
可选地，上述处理器，还用于在UE随机接入失败时，对于未配置DAPS的DRB，将DRB对应的PDCP实体以及与PDCP实体对应的RLC实体重建至源接入网设备；或者，基于保留的源接入网设备的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体。
根据本申请实施例的再一方面，提供了一种切换装置，应用于源接入网设备中，上述切换装置包括：获取模块，用于在用户设备切换失败的情况下，获取数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息；建立模块，用于基于获取的所述分组数据汇聚协议和无线链路控制实体的配置信息建立相应的分组数据汇聚协议和无线链路控制实体，并通过所述数据无线承载建立与所述用户设备的连接。
可选地，获取模块包括：第一接入模块，用于在源接入网设备将切换命令转发至用户设备后，保留当前的分组数据汇聚协议实体以及无线链路控制实体的配置信息；在用户设备切换失败时，基于当前的分组数据汇聚协议实体以及无线链路控制实体的配置信息确定与数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息，其中，切换命令用于指示用户设备对数据无线承载执行基于双激活协议栈的切换；第二接入模块，用于从目标接入网设备接收数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息，其中，从目标接入网设备接收的数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息为源接入网设备接收到切换命令时，源接入网设备已经转发了数据给目标接入网设备。
上述装置还用于执行以下处理过程：在源接入网设备收到切换命令的情况下，源接入网设备已经转发了指定数据给目标接入网设备，在用户设备切换失败后，源接入网设备接收目标接入网设备发送的指定数据；或者，源接入网设备在转发指定数据给目标接入网设备后，继续保留指定数据。
可选地，上述指定数据中至少包括未收到正确反馈的下行数据以及序列号。
根据本申请实施例的又一方面，提供了一种接入网设备，包括：以上所述的切换装置。
根据本申请实施例的又一方面，提供了一种通信系统，该系统包括：UE、目标接入网设备和源接入网设备；其中，源接入网设备，用于将目标接入网设备的切换命令转发至UE，其中，该切换命令用于指示UE执行基于DAPS的切换；UE，用于在接收到切换命令时，断开与源接入网设备的连接，并对未配置DAPS的DRB，将DRB对应的PDCP实体以及RLC实体重建至目标接入网设备，以基于切换命令向目标接入网设备发起随机接入。
根据本申请实施例的又一方面，提供了一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行以上所述的切换方法。
根据本申请实施例的又一方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行以上所述的切换方法。
在本申请实施例中，由于UE在接收到切换命令时，将未配置DAPS的DRB对应的PDCP实体以及RLC实体重建至目标接入网设备，因此，在切换失败时，UE在切换回到源接入网设备后可以继续non-DAPS HO(Handover)DRB的传输，从而解决了相关技术中，在UE执行DAPS切换失败后，对于未配置DAPS的DRB，由于源小区未保留对应的协议栈，可能会出现数据传输中断的技术问题。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是根据本申请实施例的一种基于Xn接口的切换流程的示意图；
图2是根据本申请实施例的一种通信系统的结构示意图；
图3是根据本申请实施例的一种切换方法的流程示意图；
图4是根据本申请实施例的一种切换处理方法的流程示意图；
图5是根据本申请实施例的另一种切换方法的流程示意图；
图6是根据本申请实施例的另一种切换方法的流程示意图；
图7是根据本申请实施例的一种用户设备的结构示意图；
图8是根据本申请实施例的一种切换装置的结构示意图；
图9是根据本申请实施例的另一种切换装置的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本申请方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分的实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
相关技术中，在UE进行Xn切换(其中，Xn接口为接入网之间的接口)时，其大概过程如图1所示，整个切换过程分为以下三个阶段(基于Xn接口的切换流程如图1所示)：
(1)切换准备：包括测量控制和汇报，切换请求以及确认。在切换确认消息中包含目标小区生成的切换命令，源小区不允许对目标小区生成的切换命令进行任何修改，直接将切换命令转发给UE。
(2)切换执行：UE在收到切换命令后立即执行切换过程，即UE断开源小区并与目标小区连接(如执行随机接入，发送无线资源控制(Radio Resource Control，简称为RRC)切换完成消息给目标基站等)。
(3)切换完成：目标小区与接入和移动管理功能(Access and Mobility on Management Function，简称为AMF)和用户面功能(User Plane Function，简称为UPF)执行路径切换(Path Switch，简称为PS)，释放源基站的UE的上下文，该UE的上下文包括但不限于UE的安全信息(例如，UE Security Capabilities)、UE的能力信息、协议数据单元(Protocol Data Unit，简称为PDU)会话信息等。
但是，在切换失败时，UE会切换回源基站，但是，由于源基站未保留其对应的协议栈，可能会出现数据传输中断的问题。对于该问题，本申请实施例中，UE将与未配置DAPS的DRB对应的PDCP和RLC实体重建至目标基站，这样，在切换失败时， 源基站便可以基于上述PDCP实体和RLC实体的相关配置重新接入UE，从而避免数据传输中断。以下结合实施例详细说明。
图2是根据本申请实施例的一种通信系统的结构示意图；如图4所示，该通信系统包括：用户设备20、目标接入网设备22和源接入网设备24；其中：
源接入网设备24，用于将目标接入网设备的切换命令转发至用户设备，其中，该切换命令用于指示用户设备执行基于双激活协议栈的切换；
用户设备20，用于在接收到切换命令时，断开与源接入网设备24的连接，并对未配置双激活协议栈的数据无线承载，将DRB对应的PDCP实体以及RLC实体重建至目标接入网设备22，以对目标接入网设备22发起随机接入。
在本申请的一些实施例中，用户设备20，还用于在随机接入目标接入网设备失败的情况下，对于配置了DAPS的DRB，重配DRB的PDCP实体至normal PDCP实体，并释放目标接入网设备与DRB对应的RLC实体。
在本申请的一些实施例中，用户设备20，还用于在随机接入目标接入网设备失败的情况下，对于未配置DAPS的DRB，将DRB对应的PDCP实体以及与PDCP实体对应的RLC实体重建至源接入网设备；或者，基于保留的源接入网设备的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体。
需要说明的是，源接入网设备包括但不限于：源基站；目标接入网设备包括但不限于：目标基站。
在图2所示的运行环境下，本申请实施例提供了一种切换方法的实施例，需要说明的是，在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
图3是根据本申请实施例的一种切换方法的流程示意图，如图1所示，该方法包括如下步骤：
步骤S302，目标接入网设备发送切换命令至源接入网设备，其中，该切换命令用于指示用户设备执行基于DAPS的切换。
步骤S304，源接入网设备转发切换命令至用户设备，用户设备接收切换命令；
具体地，UE接收切换命令，该切换命令指示UE执行DAPS的切换，且该切换命令中指示了用于DAPS切换的DRB。
步骤S306，用户设备将与未配置DAPS的DRB对应的PDCP实体以及RLC实体 重建至目标接入网设备。
步骤S308，用户设备对目标接入网设备发起随机接入。
需要说明的是，步骤S302和S304中的源接入网设备转发切换命令的步骤是可选的，即在UE已经接收到切换命令的情况下，可以不用执行上述步骤。
具体地，UE同步至目标接入网设备，包括UE向目标接入网设备发起随机接入，同时UE保持对源接入网设备的无线链路管理(Radio Link Management，简称为RLM)。
在本申请一些实施例中，将与未配置DAPS的数据无线承载对应的PDCP实体以及RLC实体重建至目标接入网设备时，源接入网设备保留PDCP实体以及RLC实体的配置信息。采用上述手段，可以避免UE切换失败，在切换回源接入网设备时出现数据传输中断的问题。
在本申请一些实施例中，上述配置信息包括以下至少之一：序列号分配状态、计数器维护状态、重排序窗口和或重组窗口参数以及变量、计时器相关配置、压缩解压缩相关配置。
在本申请一些实施例中，在用户设备随机接入目标接入网设备失败的情况下，对于配置了DAPS的数据无线承载，用户设备重配数据无线承载的PDCP实体至normal PDCP实体，并释放目标侧与数据无线承载对应的RLC实体。
在本申请的一些实施例中，在用户设备随机接入目标接入网设备失败的情况下，对于未配置DAPS的数据无线承载，用户设备将数据无线承载对应的PDCP实体以及与PDCP实体对应的RLC实体重建至源接入网设备；或者用户设备基于保留的源接入网设备的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体。
在本申请的一些实施例中，在源接入网设备收到切换命令的情况下，源接入网设备已经转发了指定数据给目标接入网设备，在用户设备切换失败后，目标接入网设备将指定数据再次转发给源接入网设备；或者，源接入网设备在转发指定数据给目标接入网设备后，继续保留指定数据。
其中，上述指定数据中至少包括未收到正确反馈的下行数据以及序列号。
在本申请的一些实施例中，上述切换命令中携带有用于指示DAPS切换的DRB的指示信息，这样，UE便可以基于该指示信息确定用于进行DAPS切换的DRB。
在本申请一些实施例中，对已经配置了DAPS的数据无线承载，用户设备将数据无线承载的PDCP实体重配为双激活数据协议的PDCP实体，并建立与PDCP实体对应的RLC实体。
本申请实施例还提供了另外一种切换处理方法，如图4所示，该方法包括：
步骤S402，用户设备随机接入目标接入网设备失败；
步骤S404，对于未配置DAPS的数据无线承载，用户设备将DRB对应的PDCP实体以及与PDCP实体对应的RLC实体重建至源接入网设备；
步骤S406，用户设备基于保留的源接入网设备的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体。
需要说明的是，步骤S404和S406是两个并列的步骤，即两者是两个独立的步骤，并不存在先后关系。
还需要说明的是，图4所示实施例的优选实施方式可以参见图2-3中的相关描述，此处不再赘述。
采用上述处理步骤，同样可以解决相关技术中，在UE执行DAPS切换失败后，对于未配置DAPS的DRB，由于源小区未保留对应的协议栈，可能会出现数据传输中断的技术问题。
图5是根据本申请实施例的另一种切换方法的流程示意图，如图5所示，该方法包括如下步骤：
步骤S502，目标接入网设备发送切换命令至源接入网设备，其中，该切换命令用于指示用户设备执行基于DAPS的切换。
步骤S506，用户设备将与未配置DAPS的数据无线承载对应的PDCP实体以及RLC实体重建至目标接入网设备，并且，源接入网设备保留PDCP实体以及RLC实体的配置信息；
步骤S508，用户设备对目标接入网设备发起随机接入，在随机接入失败时，UE基于上述配置信息重新接入源接入网设备。
需要说明的是，图5所示实施例的优选实施方式可以参见图2-3中的相关描述，此处不再赘述。
图6是根据本申请实施例的另一种切换方法的流程示意图，如图6所示，该方法包括如下步骤：
步骤S602，在用户设备切换失败的情况下，源接入网设备获取DRB对应的PDCP实体以及RLC实体的配置信息，其中，该切换命令用于指示用户设备对DRB执行基于DAPS的切换。
步骤S604，源接入网设备基于获取的PDCP和RLC实体的配置信息建立相应的PDP和RLC实体，并通过DRB建立与用户设备的连接。
在本申请一些实施例中，源接入网设备可以通过以下方式获取数据无线承载对应的PDCP实体以及RLC实体的配置信息：在源接入网设备将切换命令转发至用户设备后，源接入网设备保留当前的PDCP实体以及RLC实体的配置信息；在用户设备切换失败时，源接入网设备基于当前的PDCP实体以及RLC实体的配置信息中确定与数据无线承载对应的PDCP实体以及RLC实体的配置信息，其中，该切换命令用于指示用户设备对数据无线承载执行基于DAPS的切换；或者，源接入网设备从目标接入网设备接收数据无线承载对应的PDCP实体以及RLC实体的配置信息，其中，从目标接入网设备接收的数据无线承载对应的PDCP实体以及RLC实体的配置信息为源接入网设备接收到切换命令时，源接入网设备已经转发了数据给目标接入网设备。
在源接入网设备收到切换命令的情况下，源接入网设备已经转发了指定数据给目标接入网设备，在用户设备切换失败后，源接入网设备接收目标接入网设备发送的指定数据；或者，源接入网设备在转发指定数据给目标接入网设备后，继续保留指定数据。
其中，上述指定数据中至少包括未收到正确反馈的下行数据以及序列号。
在本申请的一些实施例中，配置信息包括以下至少之一：序列号分配状态、计数器维护状态、重排序窗口参数、重组窗口参数、重排序窗口变量、重组窗口变量、计时器相关配置和压缩解压缩相关配置。
需要说明的是，图6所示实施例的优选实施方式可以参见图2-3中的相关描述，此处不再赘述。
采用上述处理步骤，同样可以解决相关技术中，在UE执行DAPS切换失败后，对于未配置DAPS的DRB，由于源小区未保留对应的协议栈，可能会出现数据传输中断的技术问题。
图7是根据本申请实施例的一种用户设备的结构示意图，如图7所示，该用户设备7包括：
信号收发电路70，用于接收切换命令，其中，该切换命令用于指示用户设备执行基于DAPS的切换.
处理器72，用于对未配置DAPS的数据无线承载，将数据无线承载对应的PDCP实体以及RLC实体重建至目标接入网设备；以及对目标接入网设备发起随机接入。
在一些实施例中，用户设备还可以包括存储器74。
在本申请一些实施例中，上述处理器72，还用于在用户随机接入失败时，对于配置了DAPS的数据无线承载，重配数据无线承载的PDCP实体至标准normal PDCP实体，并释放目标侧与数据无线承载对应的RLC实体。
具体地，重配内容包括但不仅限于：释放目标侧头压缩、解头压缩及加密/解密功能。
在本申请一些实施例中，上述处理器72，还用于在用户设备随机接入失败时，对于未配置DAPS的DRB，将DRB对应的PDCP实体以及与PDCP实体对应的RLC实体重建至源接入网设备；或者，基于保留的源接入网设备的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体。
在本申请一些实施例中，上述处理器72，还用于在用户设备随机接入失败时，若收到切换命令时候，源接入网设备已经转发了数据给目标接入网设备，UE HOF后目标接入网设备应将转发数据再次转发给源接入网设备，数据包括了未收到正确反馈的下行数据以及SN号。
本申请实施例还提供一种切换装置，应用于用户设备，如图8所示，该切换装置包括：
通信单元80，用于接收切换命令，其中，切换命令用于指示用户设备执行基于DAPS的切换；通信单元80可以通过如图7中所述的信号收发电路实现，当然，其也可以表现为一个软件程序模块。
处理单元82，用于对未配置DAPS的DRB，将DRB对应的PDCP实体以及RLC实体重建至目标接入网设备；以及基于切换命令向目标接入网设备发起随机接入。该处理单元82可以通过图7中所示的处理器72实现，当然其也可以表现为一个软件程序模块。
在本申请的一些实施例中，UE在随机接入失败时，可以针对不同的情况采用不同的方案切换回源基站，例如：
处理单元82，还用于在UE随机接入目标接入网设备失败的情况下，对于配置了DAPS的DRB，重配DRB的PDCP实体至标准normal PDCP实体，并释放目标接入网设备与DRB对应的RLC实体。
又例如，处理单元82，还用于执行以下操作：在用户设备随机接入目标接入网设备失败的情况下，对于未配置DAPS的DRB，将DRB对应的PDCP实体以及与PDCP实体对应的RLC实体重建至源接入网设备；或者，基于保留的源接入网设备的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体。
其中，上述切换命令中携带有用于指示DAPS切换的DRB的指示信息。
在本申请的一些实施例中，处理单元82，还用于执行以下操作：对已经配置了DAPS的DRB，将DRB的PDCP实体重配为双激活数据协议的PDCP实体，并建立与PDCP实体对应的RLC实体。
本申请实施例还提供一种用户设备，该用户设备包括但不限于图8所示实施例中的切换装置。
本申请实施例还提供一种切换装置，应用于源接入网设备中，如图9所示，该切换装置包括：
获取模块90，用于在用户设备切换失败的情况下，获取DRB对应的PDCP实体以及RLC实体的配置信息；
建立模块92，用于基于获取的PDCP和RLC实体的配置信息建立相应的PDCP和RLC实体，并通过DRB建立与用户设备的连接。
在本申请的一些实施例中，获取模块90包括：
第一接入模块900，用于在源接入网设备将切换命令转发至用户设备后，保留当前的PDCP实体以及RLC实体的配置信息；在用户设备切换失败时，基于当前的PDCP实体以及RLC实体的配置信息确定与DRB对应的PDCP实体以及RLC实体的配置信息，其中，切换命令用于指示用户设备对DRB执行基于DAPS的切换；
第二接入模块902，用于从目标接入网设备接收DRB对应的PDCP实体以及RLC实体的配置信息，其中，从目标接入网设备接收的DRB对应的PDCP实体以及RLC实体的配置信息为源接入网设备接收到切换命令时，源接入网设备已经转发了数据给目标接入网设备。
可选地，获取模块900，还用于执行以下处理过程：在源接入网设备收到切换命令的情况下，源接入网设备已经转发了指定数据给目标接入网设备，在用户设备切换失败后，源接入网设备接收目标接入网设备发送的指定数据；或者，源接入网设备在转发指定数据给目标接入网设备后，继续保留指定数据。其中，指定数据中至少包括未收到正确反馈的下行数据以及序列号。
本申请实施例还提供一种接入网设备，包括：图9所述的切换装置。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行以上所述的切换方法，例如，可以执行以下方法：接收切换命令，其中，该切换命令用于指示UE执行基于DAPS的切换；将与未配置DAPS的 DRB对应的PDCP实体以及RLC实体重建至目标接入网设备；基于切换命令向目标接入网设备发起随机接入。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行以上所述的切换方法。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
在本申请的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的技术内容，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，可以为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅是本申请的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本申请的保护范围。

Claims (27)

  1. 一种切换方法，其特征在于，包括：
    用户设备接收切换命令，其中，所述切换命令用于指示所述用户设备执行基于双激活协议栈的切换；
    所述用户设备将与未配置双激活协议栈的数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体重建至目标接入网设备；
    所述用户设备基于所述切换命令向所述目标接入网设备发起随机接入。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述用户设备随机接入所述目标接入网设备失败的情况下，对于配置了双激活协议栈的数据无线承载，所述用户设备重配所述数据无线承载的分组数据汇聚协议实体至标准分组数据汇聚协议实体，并释放目标接入网设备与所述数据无线承载对应的无线链路控制实体。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述用户设备随机接入所述目标接入网设备失败的情况下，对于未配置双激活协议栈的数据无线承载，所述用户设备将所述数据无线承载对应的分组数据汇聚协议实体以及与所述分组数据汇聚协议实体对应的无线链路控制实体重建至源接入网设备；或者
    所述用户设备基于保留的源接入网设备的所述分组数据汇聚协议和无线链路控制实体的配置信息建立相应的分组数据汇聚协议和无线链路控制实体。
  4. 根据权利要求1所述的方法，其特征在于，所述切换命令中携带有用于指示DAPS切换的DRB的指示信息。
  5. 根据权利要求1至4中任意一项所述的方法，其特征在于，所述方法还包括：对已经配置了双激活协议栈的数据无线承载，所述用户设备将所述数据无线承载的分组数据汇聚协议实体重配为双激活数据协议的分组数据汇聚协议实体，并建立与所述分组数据汇聚协议实体对应的无线链路控制实体。
  6. 一种切换处理方法，其特征在于，包括：
    在用户设备随机接入目标接入网设备失败的情况下，
    对于未配置双激活协议栈的数据无线承载，所述用户设备将所述数据无线承载对应的分组数据汇聚协议实体以及与所述分组数据汇聚协议实体对应的无线链路控制实体重建至源接入网设备；或者
    所述用户设备基于保留的源接入网设备的所述分组数据汇聚协议和无线链路控制实体的配置信息建立相应的分组数据汇聚协议和无线链路控制实体。
  7. 一种切换方法，其特征在于，包括：
    在用户设备切换失败的情况下，源接入网设备获取数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息；
    所述源接入网设备基于获取的所述分组数据汇聚协议和无线链路控制实体的配置信息建立相应的分组数据汇聚协议和无线链路控制实体，并通过所述数据无线承载建立与所述用户设备的连接。
  8. 根据权利要求7所述的方法，其特征在于，源接入网设备获取数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息，包括：
    在源接入网设备将切换命令转发至用户设备后，所述源接入网设备保留当前的分组数据汇聚协议实体以及无线链路控制实体的配置信息；在所述用户设备切换失败时，所述源接入网设备基于所述当前的分组数据汇聚协议实体以及无线链路控制实体的配置信息确定与所述数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息，其中，所述切换命令用于指示所述用户设备对所述数据无线承载执行基于双激活协议栈的切换；或者，
    所述源接入网设备从目标接入网设备接收所述数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息，其中，从所述目标接入网设备接收的数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息为所述源接入网设备接收到所述切换命令时，所述源接入网设备已经转发了数据给目标接入网设备。
  9. 根据权利要求7所述的方法，其特征在于，所述方法还包括：在所述源接入网设备收到切换命令的情况下，所述源接入网设备已经转发了指定数据给目标接入网设备，在所述用户设备切换失败后，所述源接入网设备接收所述目标接入网设备发送的所述指定数据；或者，所述源接入网设备在转发所述指定数据给目标接入网设备后，继续保留所述指定数据。
  10. 根据权利要求9所述的方法，其特征在于，所述指定数据中至少包括未收到正确反馈的下行数据以及序列号。
  11. 根据权利要求7所述的方法，其特征在于，所述配置信息包括以下至少之一：序列号分配状态、计数器维护状态、重排序窗口参数、重组窗口参数、重排序窗口变量、重组窗口变量、计时器相关配置和压缩解压缩相关配置。
  12. 一种切换装置，应用于用户设备，其特征在于，包括：
    通信单元，用于接收切换命令，其中，所述切换命令用于指示所述用户设备执行基于双激活协议栈的切换；
    处理单元，用于对未配置双激活协议栈的数据无线承载，将所述数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体重建至目标接入网设备；以及基于所述切换命令向所述目标接入网设备发起随机接入。
  13. 根据权利要求12所述的装置，其特征在于，所述处理单元，还用于在所述用户设备随机接入所述目标接入网设备失败的情况下，对于配置了双激活协议栈的数据无线承载，重配所述数据无线承载的分组数据汇聚协议实体至标准normal PDCP实体，并释放目标接入网设备与所述数据无线承载对应的无线链路控制实体。
  14. 根据权利要求12所述的装置，其特征在于，所述处理单元，还用于执行以下操作：
    在所述用户设备随机接入所述目标接入网设备失败的情况下，对于未配置双激活协议栈的数据无线承载，将所述数据无线承载对应的分组数据汇聚协议实体以及与所述分组数据汇聚协议实体对应的无线链路控制实体重建至源接入网设备；或者，基于保留的源接入网设备的所述分组数据汇聚协议和无线链路控制实体的配置信息建立相应的分组数据汇聚协议和无线链路控制实体。
  15. 根据权利要求12所述的装置，其特征在于，所述切换命令中携带有用于指示DAPS切换的DRB的指示信息。
  16. 根据权利要求12至15中任意一项所述的装置，其特征在于，所述处理单元，还用于执行以下操作：对已经配置了双激活协议栈的数据无线承载，将所述数据无线承载的分组数据汇聚协议实体重配为双激活数据协议的分组数据汇聚协议实体，并建立与所述分组数据汇聚协议实体对应的无线链路控制实体。
  17. 一种用户设备，其特征在于，包括：权利要求12至16中任意一项所述的切换装置。
  18. 一种切换装置，应用于源接入网设备中，其特征在于，包括：
    获取模块，用于在用户设备切换失败的情况下，获取数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息；
    建立模块，用于基于获取的所述分组数据汇聚协议和无线链路控制实体的配置信息建立相应的分组数据汇聚协议和无线链路控制实体，并通过所述数据无线承载建立与所述用户设备的连接。
  19. 根据权利要求18所述的装置，其特征在于，所述获取模块包括：
    第一接入模块，用于在源接入网设备将切换命令转发至用户设备后，保留当前的分组数据汇聚协议实体以及无线链路控制实体的配置信息；在所述用户设备切换失败时，基于所述当前的分组数据汇聚协议实体以及无线链路控制实体的配置信息确定与所述数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息，其中，所述切换命令用于指示所述用户设备对所述数据无线承载执行基于双激活协议栈的切换；
    第二接入模块，用于从目标接入网设备接收所述数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息，其中，从所述目标接入网设备接收的数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体的配置信息为所述源接入网设备接收到所述切换命令时，所述源接入网设备已经转发了数据给目标接入网设备。
  20. 根据权利要求18所述的装置，其特征在于，所述获取模块，还用于执行以下处理过程：在所述源接入网设备收到切换命令的情况下，所述源接入网设备已经转发了指定数据给目标接入网设备，在所述用户设备切换失败后，所述源接入网设备接收所述目标接入网设备发送的所述指定数据；或者，所述源接入网设备在转发所述指定数据给目标接入网设备后，继续保留所述指定数据。
  21. 根据权利要求20所述的装置，其特征在于，所述指定数据中至少包括未收到正确反馈的下行数据以及序列号。
  22. 一种接入网设备，其特征在于，包括：权利要求18至21中任意一项所述的切换装置。
  23. 一种通信系统，其特征在于，包括：用户设备、目标接入网设备和源接入网设备；其中，
    所述源接入网设备，用于将目标接入网设备的切换命令转发至所述用户设备，其中，所述切换命令用于指示所述用户设备执行基于双激活协议栈的切换；
    所述用户设备，用于在接收到所述切换命令时，断开与所述源接入网设备的连接，并对未配置双激活协议栈的数据无线承载，将所述数据无线承载对应的分组数据汇聚协议实体以及无线链路控制实体重建至目标接入网设备，以基于所述切换命令向所述目标接入网设备发起随机接入。
  24. 根据权利要求23所述的通信系统，其特征在于，所述用户设备，还用于在随机接入所述目标接入网设备失败的情况下，对于配置了双激活协议栈的数据无线承载， 重配所述数据无线承载的分组数据汇聚协议实体至标准分组数据汇聚协议实体，并释放目标接入网设备与所述数据无线承载对应的无线链路控制实体。
  25. 根据权利要求24所述的通信系统，其特征在于，所述用户设备，还用于在随机接入所述目标接入网设备失败的情况下，对于未配置双激活协议栈的数据无线承载，将所述数据无线承载对应的分组数据汇聚协议实体以及与所述分组数据汇聚协议实体对应的无线链路控制实体重建至源接入网设备；或者，基于保留的源接入网设备的所述分组数据汇聚协议和无线链路控制实体的配置信息建立相应的分组数据汇聚协议和无线链路控制实体。
  26. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至5中任意一项所述的切换方法；或者执行权利要求7至11中任意一项所述的切换方法。
  27. 一种计算机程序产品，其特征在于，包括计算机程序指令，所述计算机程序指令使得计算机执行如权利要求1至5中任一项所述的切换方法；或者执行权利要求7至11中任意一项所述的切换方法。
PCT/CN2019/127655 2019-12-23 2019-12-23 切换方法、切换处理方法、通信系统及存储介质 WO2021127940A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201980100520.0A CN114424622B (zh) 2019-12-23 2019-12-23 切换方法、切换处理方法、通信系统及存储介质
PCT/CN2019/127655 WO2021127940A1 (zh) 2019-12-23 2019-12-23 切换方法、切换处理方法、通信系统及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/127655 WO2021127940A1 (zh) 2019-12-23 2019-12-23 切换方法、切换处理方法、通信系统及存储介质

Publications (1)

Publication Number Publication Date
WO2021127940A1 true WO2021127940A1 (zh) 2021-07-01

Family

ID=76573488

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/127655 WO2021127940A1 (zh) 2019-12-23 2019-12-23 切换方法、切换处理方法、通信系统及存储介质

Country Status (2)

Country Link
CN (1) CN114424622B (zh)
WO (1) WO2021127940A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115038132B (zh) * 2022-08-15 2022-11-22 武汉世炬信息技术有限公司 基站的daps切换方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016021820A1 (en) * 2014-08-08 2016-02-11 Lg Electronics Inc. Method for processing a packet data convergence protocol re-ordering function at a user equipment in a dual connectivity system and device therefor
WO2017138978A1 (en) * 2016-02-12 2017-08-17 Intel IP Corporation Systems and methods for reducing interruptions in data transmissions due to handover operations
CN107409336A (zh) * 2015-03-04 2017-11-28 高通股份有限公司 双链路切换
WO2018203702A1 (en) * 2017-05-05 2018-11-08 Samsung Electronics Co., Ltd. Method and apparatus for coordination of rrc configurations between interworking nodes in dual connectivity
CN108924947A (zh) * 2017-03-21 2018-11-30 中兴通讯股份有限公司 一种确定无线承载方式的方法及装置
CN110063086A (zh) * 2017-10-02 2019-07-26 联发科技（新加坡）私人有限公司 利用上行链路切换的数据恢复方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8059595B2 (en) * 2007-04-06 2011-11-15 Qualcomm Incorporated Handoff of data attachment point
US10333664B1 (en) * 2016-09-19 2019-06-25 Sprint Spectrum L.P. Systems and methods for dynamically selecting wireless devices for uplink (UL) multiple-input-multiple-output (MIMO) pairing

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016021820A1 (en) * 2014-08-08 2016-02-11 Lg Electronics Inc. Method for processing a packet data convergence protocol re-ordering function at a user equipment in a dual connectivity system and device therefor
CN107409336A (zh) * 2015-03-04 2017-11-28 高通股份有限公司 双链路切换
WO2017138978A1 (en) * 2016-02-12 2017-08-17 Intel IP Corporation Systems and methods for reducing interruptions in data transmissions due to handover operations
CN108924947A (zh) * 2017-03-21 2018-11-30 中兴通讯股份有限公司 一种确定无线承载方式的方法及装置
WO2018203702A1 (en) * 2017-05-05 2018-11-08 Samsung Electronics Co., Ltd. Method and apparatus for coordination of rrc configurations between interworking nodes in dual connectivity
CN110063086A (zh) * 2017-10-02 2019-07-26 联发科技（新加坡）私人有限公司 利用上行链路切换的数据恢复方法

Also Published As

Publication number Publication date
CN114424622A (zh) 2022-04-29
CN114424622B (zh) 2024-02-23

Similar Documents

Publication Publication Date Title
US10750414B2 (en) System and method for handovers in a dual connectivity communications system
CN107690162B (zh) 小区连接失败的处理方法及装置
TWI757778B (zh) 減少行動中斷之方法和使用者設備
EP3764693B1 (en) Handover method and apparatus
CN102215485B (zh) 多载波通信系统中保证多载波切换或重建安全性的方法
WO2020151653A1 (zh) 由用户设备执行的切换方法以及用户设备
JP6637617B2 (ja) 通信方法、ネットワーク側デバイス、およびユーザ端末
US11412563B2 (en) Multi-connectivity communication method and device
US20110117905A1 (en) LTE RRC connection re-establishment requesting method, cause value setting method and terminal
WO2018127219A1 (zh) 一种减少中断时延的方法、装置及用户设备
US11765627B2 (en) Sequence number transfer for radio bearers
WO2014101171A1 (zh) 连接失败恢复方法、装置和系统
WO2021227881A1 (zh) 无线链路失败恢复方法及对应的用户设备
US20210385905A1 (en) Entity Establishment Processing Method and Apparatus
CN113678568A (zh) 管理mcg快速恢复
CN111757348A (zh) 一种通信方法及装置
WO2021127940A1 (zh) 切换方法、切换处理方法、通信系统及存储介质
WO2021129018A1 (zh) 网络连接的重建立方法及装置、存储介质、电子装置
WO2022120744A1 (zh) 数据传输处理方法及相关装置
KR20230009939A (ko) 마스터 셀 그룹 실패의 이벤트에서의 통신 관리
WO2022222687A1 (zh) 一种信息配置方法以及相关设备
US20240137786A1 (en) Multi-connectivity communication method and apparatus
WO2023078340A1 (zh) 一种无线通信链路失败处理方法及装置
WO2019233419A1 (zh) Rrc连接重建立方法及终端
CN117136581A (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: 19957997

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: 19957997

Country of ref document: EP

Kind code of ref document: A1