IP Library Granted Patent US 12,295,061
Granted Patent B2
US 12,295,061 · App. 17/810,716 · Granted May 6, 2025

Enhanced make-before-break handover

Inventors: Karthika Paladugu (San Diego, CA); Gavin Bernard Horn (La Jolla, CA); Prashanth Haridas Hande (San Diego, CA); Keiichi Kubota (Tokyo, JP); Prasad Reddy Kadiri (San Diego, CA); Alberto Rico Alvarino (San Diego, CA); Masato Kitazoe (Tokyo, JP); Umesh Phuyal (San Diego, CA); Supratik Bhattacharjee (San Diego, CA)
Assignee: QUALCOMM Incorporated
H04W76/27H04W12/033H04W12/04H04W12/106
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,295,061
App. No.
17/810,716
Granted
May 6, 2025
Kind
B2
Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment concurrently communicates with a source base station (BS) and a target BS on a connection with the source BS and a connection with the target BS as part of a make-before-break (MBB) handover procedure; and performs a common packet data convergence protocol (PDCP) function for the connection with the source BS and the connection with the target BS before the connection with the source BS is released as part of the MBB handover procedure. Numerous other aspects are provided.

Claims (107)

1. A source network entity, comprising:

one or more memories; and

one or more processors, coupled to the one or more memories, configured to:

receive, from a user equipment (UE), capability information indicating that the UE supports intra-frequency make-before-break (MBB) handover;

communicate, as part of a MBB handover procedure, with the UE on a connection between the UE and the source network entity;

transmit or receive a packet data convergence protocol (PDCP) sequence number (SN) status transfer; and

cease, as part of the MBB handover procedure, the connection between the UE and the source network entity.

2. The source network entity of claim 1 , wherein the one or more processors are further configured to:

exchange, with a target network entity, information regarding a time division multiplexing (TDM) pattern for the UE.

3. The source network entity of claim 2 , wherein the information regarding the TDM pattern is exchanged via an X2 interface.

4. The source network entity of claim 1 , wherein the MBB handover procedure is configured based at least in part on a capability of the UE.

5. The source network entity of claim 1 , wherein the intra-frequency MBB handover is associated with a constraint on at least one of:

a maximum number of carriers,

a maximum number of physical resource blocks, or

a maximum bandwidth.

6. The source network entity of claim 1 , wherein the capability information further indicates one or more constraints that the UE has in supporting the intra-frequency MBB handover.

7. The source network entity of claim 1 , wherein the MBB handover procedure is an asynchronous intra-frequency MBB handover procedure.

8. The source network entity of claim 1 , wherein the capability information further indicates that the UE supports inter-frequency MBB handover.

9. The source network entity of claim 1 , wherein the one or more processors are further configured to:

receive, from the UE, a measurement report that indicates that a handover is to be performed from the source network entity to a target network entity.

10. The source network entity of claim 1 , wherein the one or more processors are further configured to:

provide a handover request to a target network entity; and

receive a handover acknowledgment (ACK) from the target network entity.

11. The source network entity of claim 1 , wherein the one or more processors are further configured to:

communicate with a target network entity to determine a handover configuration for the UE.

12. The source network entity of claim 11 , wherein, to communicate with the UE, the one or more processors are further configured to:

provide the handover configuration to the UE.

13. The source network entity of claim 11 , wherein the handover configuration includes a configuration for the MBB handover procedure.

14. The source network entity of claim 10 , wherein, to cease the connection with the UE, the one or more processors are further configured to:

provide, to the UE, an instruction to release the connection between the UE and the source network entity.

15. A method of wireless communication performed by an apparatus of a source network entity, comprising:

receiving, from a user equipment (UE), capability information indicating that the UE supports intra-frequency make-before-break (MBB) handover;

communicating, as part of a MBB handover procedure, with the UE on a connection between the UE and the source network entity;

transmitting or receiving a packet data convergence protocol (PDCP) sequence number (SN) status transfer; and

ceasing, as part of the MBB handover procedure, the connection between the UE and the source network entity.

16. The method of claim 15 , further comprising:

exchanging, with a target network entity, information regarding a time division multiplexing (TDM) pattern for the UE, wherein the information regarding the TDM pattern is exchanged via an X2 interface.

17. The method of claim 15 , wherein the MBB handover procedure is configured based at least in part on a capability of the UE.

18. The method of claim 15 , wherein the intra-frequency MBB handover is associated with a constraint on at least one of:

a maximum number of carriers,

a maximum number of physical resource blocks, or

a maximum bandwidth.

19. The method of claim 15 , wherein the capability information further indicates one or more constraints that the UE has in supporting the intra-frequency MBB handover.

20. The method of claim 15 , wherein the MBB handover procedure is an asynchronous intra-frequency MBB handover procedure.

21. The method of claim 15 , wherein the capability information further indicates that the UE supports inter-frequency MBB handover.

22. The method of claim 15 , further comprising:

receiving, from the UE, a measurement report that indicates that a handover is to be performed from the source network entity to a target network entity.

23. The method of claim 15 , further comprising:

providing a handover request to a target network entity; and

receiving a handover acknowledgment (ACK) from the target network entity.

24. The method of claim 15 , further comprising:

communicating with a target network entity to determine a handover configuration for the UE.

25. The method of claim 24 , wherein communicating with the UE comprises:

providing the handover configuration to the UE.

26. The method of claim 24 , wherein the handover configuration includes a configuration for the MBB handover procedure.

27. The method of claim 15 , wherein ceasing the connection with the UE comprises:

providing, to the UE, an instruction to release the connection between the UE and the source network entity.

28. An apparatus, comprising:

means for receiving, from a user equipment (UE), capability information indicating that the UE supports intra-frequency make-before-break (MBB) handover;

means for communicating, as part of a MBB handover procedure, with the UE on a connection between the UE and the apparatus;

means for transmitting or receiving a packet data convergence protocol (PDCP) sequence number (SN) status transfer; and

means for ceasing, as part of the MBB handover procedure, the connection between the UE and the apparatus.

29. The source network entity of claim 1 , wherein the PDCP SN status transfer comprises a downlink PDCP SN for data units transmitted by a target network entity.

30. The source network entity of claim 1 , wherein, to transmit or receive the PDCP SN status transfer, the one or more processors are configured to:

receive the PDCP SN status transfer as part of the UE performing a common PDCP function.

31. The source network entity of claim 1 , wherein the PDCP SN status transfer provides continuity for radio link control acknowledged-mode and unacknowledged-mode data units that are transmitted on the connection between the UE and the source network entity or on a connection with a target network entity.

32. The source network entity of claim 1 , wherein the one or more processors are further configured to:

reserve a set of PDCP SNs to finish transmitting downlink traffic to the UE.

33. The source network entity of claim 32 , wherein the set of PDCP SNs includes a PDCP SN of the PDCP SN status transfer.

34. The source network entity of claim 1 , wherein, to transmit or receive the PDCP SN status transfer, the one or more processors are configured to:

transmit the PDCP SN status transfer to a target network entity.

35. A user equipment (UE), comprising:

one or more memories; and

one or more processors communicatively coupled to the one or more memories, configured to:

provide, to a source network entity, capability information indicating that the UE supports intra-frequency make-before-break (MBB) handover;

communicate, as part of a MBB handover procedure, with the source network entity on a connection with the source network entity;

perform a packet data convergence protocol (PDCP) function with the source network entity; and

release, as part of the MBB handover procedure, the connection with the source network entity.

36. The UE of claim 35 , wherein the MBB handover procedure is configured based at least in part on a capability of the UE.

37. The UE of claim 35 , wherein the intra-frequency MBB handover is associated with a constraint on at least one of:

a maximum number of carriers,

a maximum number of physical resource blocks, or

a maximum bandwidth.

38. The UE of claim 35 , wherein the capability information further indicates one or more constraints that the UE has in supporting the intra-frequency MBB handover.

39. The UE of claim 35 , wherein the MBB handover procedure is an asynchronous intra-frequency MBB handover procedure.

40. The UE of claim 35 , wherein the capability information further indicates that the UE supports inter-frequency MBB handover.

41. The UE of claim 35 , wherein the one or more processors are further configured to:

transmit, to the source network entity, a measurement report that indicates that a handover is to be performed from the source network entity to a target network entity.

42. The UE of claim 35 , wherein the one or more processors are further configured to:

receive an instruction to release the connection between the UE and the source network entity.

43. A method of wireless communication performed by a user equipment (UE), comprising:

providing, to a source network entity, capability information indicating that the UE supports intra-frequency make-before-break (MBB) handover;

communicating, as part of a MBB handover procedure, with the source network entity on a connection with the source network entity;

performing a packet data convergence protocol (PDCP) function with the source network entity; and

releasing, as part of the MBB handover procedure, the connection with the source network entity.

44. The method of claim 43 , wherein the MBB handover procedure is configured based at least in part on a capability of the UE.

45. The method of claim 43 , wherein the intra-frequency MBB handover is associated with a constraint on at least one of:

a maximum number of carriers,

a maximum number of physical resource blocks, or

a maximum bandwidth.

46. The method of claim 43 , wherein the capability information further indicates one or more constraints that the UE has in supporting the intra-frequency MBB handover.

47. The method of claim 43 , wherein the MBB handover procedure is an asynchronous intra-frequency MBB handover procedure.

48. The method of claim 43 , wherein the capability information further indicates that the UE supports inter-frequency MBB handover.

49. The method of claim 43 , further comprising:

transmitting, to the source network entity, a measurement report that indicates that a handover is to be performed from the source network entity to a target network entity.

50. The method of claim 43 , further comprising:

receiving an instruction to release the connection between the UE and the source network entity.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 5, 2022
From: PALADUGU, KARTHIKA; HORN, GAVIN BERNARD; HANDE, PRASHANTH HARIDAS; KUBOTA, KEIICHI; KADIRI, PRASAD REDDY; RICO ALVARINO, ALBERTO; KITAZOE, MASATO; PHUYAL, UMESH; BHATTACHARJEE, SUPRATIK
To: QUALCOMM INCORPORATED
Reel/Frame 060399/0156 →
Continuity (5)
Continuation 16900142 · Jun 12, 2020
Continuation 16275214 · Feb 13, 2019
Provisional Application 62631479 · Feb 15, 2018
Provisional Application 62631350 · Feb 15, 2018
Related Publication 20220400422A1 · Dec 15, 2022
References Cited (46)
US 8520636B2 · Xu · 2013 [cited by applicant]
US 9775077B2 · Yang et al. · 2017 [cited by applicant]
US 10244444B2 · Ozturk et al. · 2019 [cited by applicant]
US 10687263B2 · Paladugu et al. · 2020 [cited by applicant]
US 11388642B2 · Paladugu et al. · 2022 [cited by applicant]
US 20050250509A1 · Choksi · 2005 [cited by applicant]
US 20080219215A1 · Olvera-Hernandez · 2008 [cited by examiner]
US 20090274098A1 · Chun et al. · 2009 [cited by applicant]
US 20100330999A1 · Larsson et al. · 2010 [cited by applicant]
US 20130010641A1 · Dinan · 2013 [cited by applicant]
US 20130308481A1 · Kazmi et al. · 2013 [cited by applicant]
US 20140092866A1 · Teyeb et al. · 2014 [cited by applicant]
US 20140113632A1 · Li · 2014 [cited by applicant]
US 20140349653A1 · Kanamarlapudi et al. · 2014 [cited by applicant]
US 20150215827A1 · Zhang et al. · 2015 [cited by applicant]
US 20150245269A1 · Shao et al. · 2015 [cited by applicant]
US 20160029213A1 · Rajadurai et al. · 2016 [cited by applicant]
US 20160057585A1 · Horn et al. · 2016 [cited by applicant]
US 20160057687A1 · Horn et al. · 2016 [cited by applicant]
US 20160192261A1 · Wang · 2016 [cited by examiner]
US 20170374578A1 · Selvaganapathy et al. · 2017 [cited by applicant]
US 20180098250A1 · Vrzic et al. · 2018 [cited by applicant]
US 20180176839A1 · Ohara et al. · 2018 [cited by applicant]
US 20180213456A1 · Jheng et al. · 2018 [cited by applicant]
US 20180295544A1 · Feng · 2018 [cited by applicant]
US 20180352491A1 · Shih et al. · 2018 [cited by applicant]
US 20190098606A1 · Sharma et al. · 2019 [cited by applicant]
US 20190159086A1 · Xu · 2019 [cited by examiner]
US 20190166526A1 · Xu · 2019 [cited by examiner]
US 20200092069A1 · Glennon · 2020 [cited by examiner]
US 20200344657A1 · Paladugu et al. · 2020 [cited by applicant]
US 20210105688A1 · Paladugu · 2021 [cited by examiner]
CN 107258104A · 2017 [cited by applicant]
CN 107371205A · 2017 [cited by applicant]
WO 2016040328A1 · 2016 [cited by applicant]
WO 2016090124A1 · 2016 [cited by applicant]
WO 2016140757A1 · 2016 [cited by applicant]
WO 2016195735A1 · 2016 [cited by applicant]
WO 2017138978A1 · 2017 [cited by applicant]
WO 2017193940A1 · 2017 [cited by applicant]
WO 2018085049A1 · 2018 [cited by applicant]
“3GPP TS 36.323 V14.4.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification… [cited by applicant]
International Search Report and Written Opinion—PCT/US2019/018068—ISA/EPO—Apr. 3, 2019. [cited by applicant]
Panigrahi P., “LTE X2 Handover Call Flow Procedure,” Dec. 4, 2013, pp. 1-10. [cited by applicant]
U.S. Appl. No. 62/514,200 (Priority application of Shih et al. (US 2018/0352491), Jun. 2, 2017, 46 Pages. [cited by applicant]
ZTE Corporation., et al., “Discussion on the Support of MBB and RACH-Less in NR”, R2-1710430, 3GPP TSG-RAN WG2 Meeting#99bis, Prague, Czech Republic, Oct. 9-13, 2017, 7 Pages. [cited by applicant]