IP Library › Granted Patent US 12,369,220
Granted Patent B2
US 12,369,220 · App. 18/418,970 · Granted Jul 22, 2025

Method and apparatus for performing handover in wireless communication system

Inventors: Donggun Kim (Suwon-si, KR); Anil Agiwal (Suwon-si, KR); Soenghun Kim (Suwon-si, KR); Jaehyuk Jang (Suwon-si, KR)
Assignee: Samsung Electronics Co., Ltd.
H04W76/27H04W28/0263H04W28/0268H04W36/0011H04W36/185H04W80/02H04W36/00692
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,369,220
App. No.
18/418,970
Granted
Jul 22, 2025
Kind
B2
Abstract

A method, performed by a terminal, in a wireless communication system is provided. The method includes receiving, from a source base station, a radio resource control (RRC) reconfiguration message for a handover, the RRC reconfiguration message configuring a first data radio bearer (DRB) as a dual active protocol stack (DAPS) bearer and a second DRB as a non-DAPS bearer, for the first DRB, in case that an uplink data switching is requested from an upper layer, indicating, by a packet data convergence protocol (PDCP) entity for the DRB, a PDCP data volume excluding a PDCP Control protocol data unit (PDU) associated with the source base station, to a medium access control (MAC) entity for a target base station, and for the second DRB, in case that an indication of PDCP re-establishment is set, performing a PDCP re-establishment for the second DRB.

Claims (34)

1. A method performed by a terminal in a wireless communication system, the method comprising:

receiving, from a source base station, a radio resource control (RRC) reconfiguration message for a handover, the RRC reconfiguration message including information on indicating whether at least one radio bearer is configured as a dual active protocol stack (DAPS) bearer;

in case that the at least one radio bearer is configured as the DAPS bearer, configuring a packet data convergence protocol (PDCP) entity based on the RRC reconfiguration message;

in case that the at least one radio bearer is not configured as the DAPS bearer, re-establishing a PDCP entity based on the RRC reconfiguration message; and

in case that an uplink data switching is requested from an upper layer for the at least one radio bearer that is configured as the DAPS bearer, indicating, by the PDCP entity, a PDCP data volume excluding a PDCP control protocol data unit (PDU) for an interspersed robust header compression (ROHC) feedback associated with the source base station, to a medium access control (MAC) entity for a target base station.

2. The method of claim 1 , wherein the indication of PDCP re-establishment is not set for the at least one radio bearer that is configured as the DAPS bearer.

3. The method of claim 1 , further comprising:

in case that an uplink data switching is requested from an upper layer for the at least one radio bearer that is configured as the DAPS bearer, indicating, by the PDCP entity, a PDCP data volume of the PDCP Control PDU associated with the source base station, to a MAC entity for the source base station.

4. The method of claim 1 , further comprising:

in case that the uplink data switching is not requested from the upper layer for the at least one radio bearer that is configured as the DAPS bearer, indicating, by the PDCP entity, a PDCP data volume, to the MAC entity for the source base station.

5. The method of claim 1 , wherein a PDCP duplication is deactivated for the at least one radio bearer that is configured as the DAPS bearer.

6. The method of claim 1 , further comprising:

triggering, by the MAC entity for the target base station, a buffer status reporting (BSR) based on the PDCP data volume excluding the PDCP Control PDU associated with the source base station.

7. The method of claim 1 , further comprising:

triggering, by the MAC entity for the source base station, a buffer status reporting (BSR) based on the PDCP data volume of the PDCP Control PDU associated with the source base station.

8. The method of claim 1 , wherein the uplink data switching is requested from the upper layer for the at least one radio bearer that is configured as the DAPS bearer when a random access procedure is successfully performed on the target base station.

9. A terminal in a wireless communication system, the terminal comprising:

a transceiver; and

at least one processor configured to:

receive via the transceiver, from a source base station, a radio resource control (RRC) reconfiguration message for a handover, the RRC reconfiguration message including information on indicating whether at least one radio bearer is configured as a dual active protocol stack (DAPS) bearer,

in case that the at least one radio bearer is configured as the DAPS bearer, configuring a packet data convergence protocol (PDCP) entity based on the RRC reconfiguration message,

in case that the at least one radio bearer is not configured as the DAPS bearer, re-establishing a PDCP entity based on the RRC reconfiguration message,

in case that an uplink data switching is requested from an upper layer for the at least one radio bearer that is configured as the DAPS bearer, indicate, by the PDCP entity, a PDCP data volume excluding a PDCP control protocol data unit (PDU) for an interspersed robust header compression (ROHC) feedback associated with the source base station, to a medium access control (MAC) entity for a target base station.

10. The terminal of claim 9 , wherein the indication of PDCP re-establishment is not set for the at least one radio bearer that is configured as the DAPS bearer.

11. The terminal of claim 9 , wherein the processor is further configured to:

in case that an uplink data switching is requested from an upper layer for the at least one radio bearer that is configured as the DAPS bearer, indicate, by the PDCP entity, a PDCP data volume of the PDCP Control PDU associated with the source base station, to a MAC entity for the source base station.

12. The terminal of claim 9 , wherein the processor is further configured to:

in case that the uplink data switching is not requested from the upper layer for the at least one radio bearer that is configured as the DAPS bearer, indicate, by the PDCP entity, a PDCP data volume, to the MAC entity for the source base station.

13. The terminal of claim 9 , wherein a PDCP duplication is deactivated for the at least one radio bearer that is configured as the DAPS bearer.

14. The terminal of claim 9 , wherein the processor is further configured to:

trigger, by the MAC entity for the target base station, a buffer status reporting (BSR) based on the PDCP data volume excluding the PDCP Control PDU associated with the source base station.

15. The terminal of claim 9 , wherein the processor is further configured to:

trigger, by the MAC entity for the source base station, a buffer status reporting (BSR) based on the PDCP data volume of the PDCP Control PDU associated with the source base station.

16. The terminal of claim 9 , wherein the uplink data switching is requested from the upper layer for the at least one radio bearer that is configured as the DAPS bearer when a random access procedure is successfully performed on the target base station.

Priority Claims (4)
KR 10-2019-0141250 · Nov 6, 2019 · national
KR 10-2019-0141260 · Nov 6, 2019 · national
KR 10-2020-0060629 · May 20, 2020 · national
KR 10-2020-0088449 · Jul 16, 2020 · national
Continuity (3)
Continuation 17828787 · May 31, 2022
Continuation 17088933 · Nov 4, 2020
Related Publication 20240205755A1 · Jun 20, 2024
References Cited (23)
US 11140695B1 · Eyuboglu · 2021 [cited by applicant]
US 11202246B2 · Ryu et al. · 2021 [cited by applicant]
US 11356904B2 · Kim · 2022 [cited by examiner]
US 11882486B2 · Kim · 2024 [cited by examiner]
US 20180234839A1 · Tenny et al. · 2018 [cited by applicant]
US 20190254114A1 · Son · 2019 [cited by applicant]
US 20210105674A1 · Kim et al. · 2021 [cited by applicant]
EP 3706461A1 · 2020 [cited by applicant]
WO 2019093835A1 · 2019 [cited by applicant]
WO 2019135649A1 · 2019 [cited by applicant]
5G; NR; Radio Resource Control (RRC); Protocol specification (3GPP TS 38.331 version 15.7.0 Release 15), ETSI TS 138 331 V15.7.0, Sep. 27, 2019. [cited by applicant]
Nokia et al., Analysis of DAPS Operation, 3GPP TSG-RAN WG2 Meeting #107, R2-1909036, Aug. 15, 2019, Prague, Czech Republic. [cited by applicant]
Mediatek Inc., Bearer handling for RUDI during HO with DAPS, 3GPP TSG-RAN WG2 #107bis, R2-1912968, Oct. 4, 2019, Chongqing, China. [cited by applicant]
ZTE Corporation et al., Discussion on PDCP aspects for RUDI, 3GPP TSG RAN WG2 Meeting #107, R2-1910758, Aug. 16, 2019, Prague, Czech Republic. [cited by applicant]
Intel Corporation, SDAP and PDCP handling for DAPS HO, 3GPP TSG RAN WG2 Meeting #108, R2-1914838, Nov. 8, 2019, Reno, USA. [cited by applicant]
International Search Report dated Feb. 16, 2021, issued in International Application No. PCT/KR2020/015324. [cited by applicant]
Intel Corporation, Stage 2 TP for DAPS based RUDI, 3GPP TSG-RAN WG2 Meeting #107bis, R2-1912778, Oct. 4, 2019, Chongqing, China. [cited by applicant]
Qualcomm Wireless GmbH et al., Correction to SDAP Test Cases, 3GPP TSG-RAN5 Meeting #82, R5-192297, Mar. 13, 2019, Athens, Greece. [cited by applicant]
European Search Report dated Dec. 22, 2021, issued in European Application No. 20885381.2. [cited by applicant]
Indian Office Action dated Jun. 14, 2022, issued in Indian Application No. 202137031857. [cited by applicant]
European Office Action dated Apr. 29, 2024, issued in European Patent Application No. 20 885 381.2-1215. [cited by applicant]
Extended European Search Report dated Dec. 9, 2024, issued in European Application No. 24195825.5-1215. [cited by applicant]
Mediatek Inc., Huawei (Rapporteur); Report of email discussion: [107#44][LTE and NR /feMOB] Discussion on PDCP details for RUDI HO, 3GPP TSG-RAN WG2 #107bis, R2-1912966; Oct. 4, 2019, Chongqing, China. [cited by applicant]