IP Library › Granted Patent US 12,477,592
Granted Patent B2
US 12,477,592 · App. 17/212,720 · Granted Nov 18, 2025

Method for dual connectivity handover, terminal, and network device

Inventors: Yue Ma (Chang'an Dongguan, CN); Yumin Wu (Chang'an Dongguan, CN)
Assignee: VIVO MOBILE COMMUNICATION CO., LTD.
H04W76/10H04W36/083H04W36/0069
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,477,592
App. No.
17/212,720
Granted
Nov 18, 2025
Kind
B2
Abstract

This disclosure discloses a method for dual connectivity handover, a terminal, and a network device. The method includes: receiving a handover command sent from a source node, where the handover command carries dual connectivity DC configuration information for the source node and a target node, and single connectivity SC configuration information for the target node; when the DC configuration information is supported, establishing dual connectivity with the source node and the target node based on the DC configuration information; and based on the SC configuration information, disconnecting the connection with the source node in the dual connectivity and maintaining a single connection with the target node.

Claims (68)

1 . A method for dual connectivity handover from a source node to a target node, applied to a terminal side and comprising:

receiving, by the terminal side not in dual connectivity, a handover command sent from the source node, wherein the handover command carries both dual connectivity DC configuration information for establishing a dual connectivity with the source node and the target node and single connectivity SC configuration information for establishing a single connectivity with the target node;

determining, by the terminal side not in dual connectivity, whether the DC configuration information is supported by the terminal side;

in case that the DC configuration information is supported by the terminal side, establishing, by the terminal side not in dual connectivity, dual connectivity with the source node and the target node based on the DC configuration information; and

based on the SC configuration information, disconnecting, by the terminal side in the established dual connectivity with the source node and the target node, the connection with the source node in the dual connectivity and maintaining a single connection with the target node;

wherein after the step of receiving, by the terminal side not in dual connectivity, a handover command sent from a source node, the method further comprises:

sending, by the terminal side, first confirmation information to the source node based on the handover command, wherein the first confirmation information is used to confirm at least one of the following:

whether the SC configuration information is valid,

whether the SC configuration information is applied.

2 . The method for dual connectivity handover according to claim 1 , wherein after the step of receiving, by the terminal side not in dual connectivity, a handover command sent from a source node, the method further comprises:

in case that the DC configuration information is not supported by the terminal side, sending, by the terminal side not in dual connectivity, to the source node a rejection message indicating that the DC configuration information is rejected, so that the source node performs, based on the rejection message, a procedure for single connectivity handover.

3 . The method for dual connectivity handover according to claim 1 ,

wherein the first confirmation information is further used to confirm at least one of the following:

whether the handover command is received,

whether the DC configuration information is valid,

whether the dual connectivity is established.

4 . The method for dual connectivity handover according to claim 1 , wherein after the step of establishing, by the terminal side not in dual connectivity, dual connectivity with the source node and the target node based on the DC configuration information, the method further comprises:

sending, by the terminal side in the established dual connectivity with the source node and the target node, second confirmation information indicating that the dual connectivity has been established to the source node and/or the target node.

5 . The method for dual connectivity handover according to claim 1 , wherein after the step of based on the SC configuration information, disconnecting, by the terminal side in the established dual connectivity with the source node and the target node, the connection with the source node in the dual connectivity and maintaining a single connection with the target node, the method further comprises:

sending, by the terminal side, a handover completed message to the target node, wherein the handover completed message is used to indicate at least one of the following:

the SC configuration information has been applied, and

handover completed.

6 . The method for dual connectivity handover according to claim 1 , wherein the handover command is carried in a radio resource control RRC reconfiguration message, and the RRC reconfiguration message has a first transaction identifier.

7 . The method for dual connectivity handover according to claim 6 , wherein the DC configuration information and/or the SC configuration information have/has a second transaction identifier, the second transaction identifier being different from the first transaction identifier.

8 . A terminal, wherein the terminal comprises a processor, a memory, and a computer program stored in the memory and running on the processor, wherein when the computer program is executed by the processor, a method for dual connectivity handover from a source node to a target node is implemented, and the method comprises:

receiving, by the terminal not in dual connectivity, a handover command sent from the source node, wherein the handover command carries both dual connectivity DC configuration information for establishing a dual connectivity with the source node and the target node and single connectivity SC configuration information for establishing a single connectivity with the target node;

determining, by the terminal not in dual connectivity, whether the DC configuration information is supported by the terminal;

in case that the DC configuration information is supported by the terminal, establishing, by the terminal not in dual connectivity, dual connectivity with the source node and the target node based on the DC configuration information; and

based on the SC configuration information, disconnecting, by the terminal in the established dual connectivity with the source node and the target node, the connection with the source node in the dual connectivity and maintaining a single connection with the target node;

wherein after the step of receiving, by the terminal side not in dual connectivity, a handover command sent from a source node, the method further comprises:

sending, by the terminal side, first confirmation information to the source node based on the handover command, wherein the first confirmation information is used to confirm at least one of the following:

whether the SC configuration information is valid,

whether the SC configuration information is applied.

9 . The terminal according to claim 8 , wherein after the step of receiving, by the terminal not in dual connectivity, a handover command sent from a source node, the method further comprises:

in case that the DC configuration information is not supported by the terminal, sending, by the terminal not in dual connectivity, to the source node a rejection message indicating that the DC configuration information is rejected, so that the source node performs, based on the rejection message, a procedure for single connectivity handover.

10 . The terminal according to claim 8 ,

wherein the first confirmation information is further used to confirm at least one of the following:

whether the handover command is received,

whether the DC configuration information is valid,

whether the dual connectivity is established.

11 . A method for dual connectivity handover from a source node to a target node, applied to a network device, wherein the network device is the source node, and the method comprises:

sending, by the source node, a handover command to a terminal not in dual connectivity, wherein the handover command carries both dual connectivity DC configuration information for establishing a dual connectivity with the source node and the target node and single connectivity SC configuration information for establishing a single connectivity with the target node;

wherein after the step of sending, by the source node, a handover command to a terminal not in dual connectivity, the method further comprises:

receiving, by the source node, first confirmation information sent from the terminal, wherein the first confirmation information is used to confirm at least one of the following:

whether the SC configuration information is valid,

whether the SC configuration information is applied.

12 . The method for dual connectivity handover according to claim 11 , wherein before the step of sending, by the source node, a handover command to a terminal not in dual connectivity, the method further comprises:

sending, by the source node, a handover request to the target node, wherein the handover request carries configuration information for the source node in single connectivity and configuration information for the source node in dual connectivity; and

receiving, by the source node, a handover request response fed back from the target node, wherein the handover request response carries the DC configuration information and the SC configuration information.

13 . The method for dual connectivity handover according to claim 11 , wherein after the step of sending, by the source node, a handover command to a terminal not in dual connectivity, the method further comprises:

receiving, by the source node, a rejection message sent from the terminal not in dual connectivity, wherein the rejection message is used to indicate that the terminal rejects the DC configuration information; and

based on the rejection message, performing, by the source node, a procedure for single connectivity handover.

14 . The method for dual connectivity handover according to claim 11 ,

wherein the first confirmation information is further used to confirm at least one of the following:

whether the handover command is received,

whether the DC configuration information is valid,

whether the dual connectivity is established.

15 . The method for dual connectivity handover according to claim 14 , wherein after the step of receiving, by the source node, first confirmation information sent from the terminal, the method further comprises:

sending, by the source node, a first handover confirmation message to the target node; and

receiving, by the source node, a second handover confirmation message fed back from the target node based on the first handover confirmation message.

16 . The method for dual connectivity handover according to claim 11 , wherein after the step of sending, by the source node, a handover command to a terminal not in dual connectivity, the method further comprises:

receiving, by the source node, from the terminal or the target node, second confirmation information that is used to indicate that the dual connectivity has been established.

17 . A network device, wherein the network device comprises a processor, a memory, and a computer program stored in the memory and running on the processor, wherein when the computer program is executed by the processor, the steps of the method for dual connectivity handover according to claim 11 are implemented.

18 . The network device according to claim 17 , wherein before the step of sending, by the source node, a handover command to a terminal not in dual connectivity, the method further comprises:

sending, by the source node, a handover request to the target node, wherein the handover request carries configuration information for the source node in single connectivity and configuration information for the source node in dual connectivity; and

receiving, by the source node, a handover request response fed back from the target node, wherein the handover request response carries the DC configuration information and the SC configuration information.

19 . A non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for dual connectivity handover according to claim 1 are implemented.

20 . A non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for dual connectivity handover according to claim 11 are implemented.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 26, 2021
From: MA, YUE; WU, YUMIN
To: VIVO MOBILE COMMUNICATION CO.,LTD.
Reel/Frame 055739/0736 →
Priority Claims (1)
CN 201811134407.8 · Sep 27, 2018 · national
Continuity (2)
Continuation PCTCN2019106672 · Sep 19, 2019
Related Publication 20210211951A1 · Jul 8, 2021
References Cited (37)
US 20120224561A1 · Fang et al. · 2012 [cited by applicant]
US 20140370897A1 · Vesterinen et al. · 2014 [cited by applicant]
US 20150045035A1 · Nigam et al. · 2015 [cited by applicant]
US 20160037579A1 · Jung · 2016 [cited by examiner]
US 20160323926A1 · Gao et al. · 2016 [cited by applicant]
US 20160337254A1 · Karaki · 2016 [cited by examiner]
US 20170012887A1 · Ohta · 2017 [cited by examiner]
US 20170181044A1 · Wen et al. · 2017 [cited by applicant]
US 20170289879A1 · Wang et al. · 2017 [cited by applicant]
US 20180035344A1 · Wang · 2018 [cited by applicant]
US 20180220336A1 · Hong et al. · 2018 [cited by applicant]
US 20190215734A1 · Selvaganapathy · 2019 [cited by examiner]
US 20200351722A1 · Yang · 2020 [cited by examiner]
CN 1882176A · 2006 [cited by applicant]
CN 1997220A · 2007 [cited by applicant]
CN 104301955A · 2015 [cited by applicant]
CN 104735638A · 2015 [cited by applicant]
CN 104822169A · 2015 [cited by applicant]
CN 105992292A · 2016 [cited by applicant]
CN 107690163A · 2018 [cited by applicant]
CN 107852653A · 2018 [cited by applicant]
CN 108112041A · 2018 [cited by applicant]
EP 3879880A1 · 2021 [cited by applicant]
WO 2014056163A1 · 2014 [cited by applicant]
WO 2016087104A1 · 2016 [cited by applicant]
WO 2019192150A1 · 2019 [cited by applicant]
Extended European Search Report dated Oct. 22, 2021 as received in Application No. 19867838.5. [cited by applicant]
Japanese Office Action dated Apr. 18, 2022 as received in application No. 2021-517644. [cited by applicant]
“DC based NR scheme for Oms interruption handover” 3GPP TSG-RAN WG2 #101 R2-1802473 Athens, Greece, Feb. 26-Mar. 2, 2018 Revision of R2-1800550, Huawei, HiSilicon. [cited by applicant]
“NR 0ms Interruption HO” 3GPP TSG-RAN WG2 Meeting #101 R2-1803662 Athens, Greece, Feb. 26-Mar. 2, 2018, Qualcomm Incorporated. [cited by applicant]
Ericsson, “0 ms interruption support during handover procedure in NR,” 3GPP TSG-RAN WG2 NR AH#2, R2-1706625, pp. 1-8, (Jun. 29, 2017). [cited by applicant]
Huawei et al., “DC based NR scheme for Oms interruption handover,” 3GPP TSG-RAN WG2 #99, R2-1708877, pp. 1-7, (Aug. 25, 2017). [cited by applicant]
ZTE, “Further Consideration on MR-DC Mobility Procedures,” 3GPP TSG RAN WG3#1801ad-hoc, R3-180014, pp. 1-12 (Jan. 26, 2018). [cited by applicant]
Intel Corporation, “New WID: NR mobility enhancements,” 3GPP TSG RAN Meeting #80, RP-181433, pp. 1-5, (May 21-25, 2018). [cited by applicant]
Vivo, “Signalling procedure on DC handover in EUTRAN,” 3GPP TSG-RAN WG2 Meeting #103 bis, R2-1814192, pp. 1-4 (Oct. 12, 2018). [cited by applicant]
Written Opinion of the International Searching Authority dated Apr. 8, 2021 as received in Application No. PCT/CN2019/106672. [cited by applicant]
CN Office Action dated Aug. 14, 2020 as received in Application No. 201811134407.8. [cited by applicant]