IP Library › Granted Patent US 12,324,050
Granted Patent B2
US 12,324,050 · App. 17/798,657 · Granted Jun 3, 2025

Dual active protocol stack operation for handover and PSCell change

Inventor: Chih-Hsiang Wu (Taoyuan, TW)
Assignee: GOOGLE LLC
H04W76/30H04W36/0033H04W36/185
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,324,050
App. No.
17/798,657
Granted
Jun 3, 2025
Kind
B2
Abstract

A central unit (CU) of a distributed base station for configuring a dual active protocol stack (DAPS) procedure at a UE communicating with the distributed base station via a source distributed unit (DU) (i) determines ( 1002 ) that the UE is to perform the DAPS procedure in order to disconnect from the source DU and connect to a target DU; and (ii) transmits ( 1008 ), to the source DU, an indication that the source DU is to continue communicating with the UE during the DAPS procedure.

Claims (33)

1. A method in a central unit (CU) of a distributed base station for configuring a dual active protocol stack (DAPS) procedure at a UE communicating with the distributed base station via a source distributed unit (DU), the method comprising:

determining, by the CU, that the UE is to perform the DAPS procedure in order to disconnect from the source DU and connect to a target DU;

transmitting, by the CU and to the source DU, a first message indicating that the source DU is to continue communicating with the UE during the DAPS procedure; and

subsequent to obtaining an indication of the UE connecting to the target DU during the DAPS procedure, transmitting, by the CU and to the source DU, a second message indicating that the source DU is to stop communicating with the UE.

2. The method of claim 1 , wherein the first message is a DL RRC Message Transfer message.

3. The method of claim 1 , wherein the first message is included in a handover command.

4. The method of claim 3 , wherein the handover command is included in a UE Context Modification Request.

5. The method of claim 4 , wherein the UE Context Modification Request excludes a Transmission Action Indicator field, the exclusion indicating that the source DU is to continue communicating with the UE during the DAPS procedure.

6. The method of claim 4 , wherein the UE Context Modification Request includes a Transmission Action Indicator indicative of a restart of communications with the UE, thereby indicating that the source DU is to continue communicating with the UE during the DAPS procedure.

7. The method of claim 1 ,

further comprising transmitting, by the CU and to the target DU, a message to request a DAPS configuration for the UE to perform the DAPS procedure; and

wherein the UE continues communicating with the source DU using the DAPS configuration.

8. The method of claim 7 , wherein the message transmitted to the target DU is a UE Context Setup Request message.

9. The method of claim 1 , further comprising:

causing the source DU to release a context of the UE subsequent to the obtaining of the indication of the UE connecting to the target DU during the DAPS procedure.

10. The method of claim 9 , wherein causing the source DU to release the UE context includes transmitting a UE Context Release Command to the source DU.

11. The method of claim 10 , further comprising:

receiving, from the source DU and in response to the UE Context Release Command, a UE Context Release Complete message.

12. The method of claim 1 , wherein the DAPS procedure is a DAPS handover procedure.

13. The method of claim 1 , wherein the DAPS procedure is a DAPS primary secondary cell (PSCell) change procedure.

14. A central unit (CU) of a distributed base station for configuring a dual active protocol stack (DAPS) procedure at a UE communicating with the distributed base station via a source distributed unit (DU), the CU comprising processing hardware and configured to:

determine that the UE is to perform the DAPS procedure in order to disconnect from the source DU and connect to a target DU;

transmit, to the source DU, a first message indicating that the source DU is to continue communicating with the UE during the DAPS procedure; and

subsequent to obtaining an indication of the UE connecting to the target DU during the DAPS procedure, transmit, by the CU and to the source DU, a second message indicating that the source DU is to stop communicating with the UE.

15. The CU of claim 14 , wherein the first message is a DL RRC Message Transfer message or the first message is included in a UE Context Modification Request of a handover command.

16. The CU of claim 15 , wherein the UE Context Modification Request excludes a Transmission Action Indicator field, the exclusion indicating that the source DU is to continue communicating with the UE during the DAPS procedure.

17. The CU of claim 15 , wherein the UE Context Modification Request includes a Transmission Action Indicator indicative of a restart of communications with the UE, thereby indicating that the source DU is to continue communicating with the UE during the DAPS procedure.

18. The CU of claim 14 , wherein the DAPS procedure is a DAPS handover procedure or a DAPS primary secondary cell (PSCell) change procedure.

19. The CU of claim 14 , wherein:

the CU is further configured to transmit, to the target DU, a message to request a DAPS configuration for the UE to perform the DAPS procedure; and

the UE continues communicating with the source DU using the DAPS configuration.

20. The CU of claim 14 , wherein the CU is further configured to:

cause the source DU to release a context of the UE subsequent to the obtaining of the indication of the UE connecting to the target DU during the DAPS procedure.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 17, 2022
From: WU, CHIH-HSIANG
To: GOOGLE LLC
Reel/Frame 061443/0946 →
Continuity (3)
Provisional Application 63004825 · Apr 3, 2020
Provisional Application 62976346 · Feb 13, 2020
Related Publication 20230083266A1 · Mar 16, 2023
References Cited (37)
US 12120504B2 · Xie · 2024 [cited by examiner]
US 20130029668A1 · Uchiyama · 2013 [cited by examiner]
US 20190069333A1 · Kim · 2019 [cited by applicant]
US 20190141742A1 · Zhou et al. · 2019 [cited by applicant]
US 20190166526A1 · Xu et al. · 2019 [cited by applicant]
US 20190387444A1 · Byun et al. · 2019 [cited by applicant]
US 20200022035A1 · Kadiri et al. · 2020 [cited by applicant]
US 20200029389A1 · Yilmaz et al. · 2020 [cited by applicant]
US 20200037248A1 · Zhou et al. · 2020 [cited by applicant]
US 20200314710A1 · Paladugu et al. · 2020 [cited by applicant]
US 20200314714A1 · Jung · 2020 [cited by examiner]
US 20200329405A1 · Awoniyi-Oteri · 2020 [cited by examiner]
US 20210014764A1 · Zhang et al. · 2021 [cited by applicant]
US 20220369174A1 · Centonza · 2022 [cited by examiner]
WO WO2019240770A1 · 2019 [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2021/017323, dated Apr. 28, 2021. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2021/017319, dated May 11, 2021. [cited by applicant]
Qualcomm Incorporated, “Source Connection Handling During DAPS HO,” 3GPP Draft (2019). [cited by applicant]
Qualcomm Inc., Email Discussion report for [107#79] [LTE/feMOB] Capability Coordination for RUDI HO, 3GPP Draft (2019). [cited by applicant]
Qualcomm Incorporated et al., “UE Capability Coordination Signalling Aspects for DAPS Based Enhanced MBB HO,” 3GPP Draft (2019). [cited by applicant]
Search Report for European Application No. 21753716.6, dated Jul. 4, 2022. [cited by applicant]
Huawei, “DAPS HO in Split gNB,” 3GPP Draft (Nov. 8, 2019). [cited by applicant]
CATT, “Discussion E1 impact during DAPS Handover,” 3GPP Draft (2019). [cited by applicant]
First Examination Report for India Application No. 2022470048768, dated Jan. 11, 2023. [cited by applicant]
First Examination Report for India Application No. 202247049484, dated Dec. 13, 2022. [cited by applicant]
Office Action for European Application No. 21753716.6, dated Aug. 1, 2024. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall desc… [cited by applicant]
“5G; NR; Overall description; Stage-2 (3GPP TS 38.300 version 15.8.0 Release 15),” ETSI TS 138 300 V15.8.0 (2020). [cited by applicant]
“5G; NR; Packet Data Convergence Protocol (PDCP) specification (3GPP TS 38.323 version 15.5.0 Release 15),” ETSI TS 138 323 V15.5.0 (2019). [cited by applicant]
“5G; NR; Radio Resource Control (RRC); Protocol specification (3GPP TS 38.331 version 15.8.0 Release 15),” ETSI TS 138 331 V15.8.0 (2020). [cited by applicant]
“LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification (3GPP TS 36.323 version 15.5.0 Release 15),” ETSI TS 136 323 V15.5.0 (2020). [cited by applicant]
“LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (3GPP TS 36.331 version 15.8.0 Release 15),” ETSI TS 136 331 V15.8.0 (2020). [cited by applicant]
“Universal Mobile Telecommunications System (UMTS); LTE; 5G; NR; Multi-connectivity; Overall description; Stage-2 (3GPP TS 37.340 version 15.7.0 Release 15),” ETSI TS 137 340 V15.7.0 (2019). [cited by applicant]
3GPP RAN2 email discussion [108#35][LTE Mob] Running RRC CR (Ericsson) (2020). [cited by applicant]
Intel Corporation, “RRC running CR for NR mobility on DAPS HO,” 3GPP TSG-RAN WG2 Meeting #109 (2020). [cited by applicant]
Qualcomm Incorporated, “LTE mobility enhancements for eMBB HO using dual active protocol stack,” 3GPP TSG-RAN WG2 Meeting #105bis (2019). [cited by applicant]
R3-196132, R2-1914640, 3GPP RAN2 email discussion [108#34][NR Mob] Running RRC CR for CHO and DAPS (Intel) (2020). [cited by applicant]