IP Library Granted Patent US 12,219,633
Granted Patent B2
US 12,219,633 · App. 17/704,389 · Granted Feb 4, 2025

Method of triggering packet data convergence protocol status report and related device

Inventors: Heng-Li Chin (Taipei, TW); Hung-Chen Chen (Taipei, TW); Chia-Hung Wei (Taipei, TW); Yung-Lan Tseng (Taipei, TW)
Assignee: SHARP KABUSHIKI KAISHA
H04W76/15H04W24/10H04W28/06H04W80/02
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,219,633
App. No.
17/704,389
Granted
Feb 4, 2025
Kind
B2
Abstract

A method of triggering a packet data convergence protocol (PDCP) status report performed by a user equipment (UE) is provided. The method includes receiving, from a network, a Data Radio Bearer (DRB) configuration that is associated with a first PDCP entity of the UE; receiving, from the network, a Multicast Broadcast Service Radio Bearer (MRB) configuration that is associated with a second PDCP entity of the UE; triggering, by the first PDCP entity, a first PDCP status report based on a first configuration of the first PDCP entity; and triggering, by the second PDCP entity, a second PDCP status report based on a second configuration of the second PDCP entity.

Claims (30)

1. A method of triggering a packet data convergence protocol (PDCP) status report performed by a user equipment (UE), the method comprising:

receiving, from a network, a Data Radio Bearer (DRB) configuration for configuring a DRB that is associated with a first PDCP entity of the UE;

receiving, from the network, a Multicast Broadcast Service Radio Bearer (MRB) configuration for configuring an MRB that is associated with a second PDCP entity of the UE;

triggering, by the first PDCP entity, a first PDCP status report based on a first configuration of the first PDCP entity;

receiving, from the network, an information element (IE) indicating that the second PDCP entity is configured to trigger a second PDCP status report; and

triggering, by the second PDCP entity, the second PDCP status report upon receiving, from the network, the IE and a first Radio Resource Control (RRC) reconfiguration message for a second configuration of the second PDCP entity, wherein:

the first RRC reconfiguration message is used for reconfiguring the second PDCP entity and indicates at least one of PDCP entity re-establishment and PDCP data recovery of the second PDCP entity.

2. The method of claim 1 , wherein:

triggering, by the first PDCP entity, the first PDCP status report comprises triggering the first PDCP status report when the UE receives, from the network, a second Radio Resource Control (RRC) reconfiguration message for the first configuration of the first PDCP entity, and

the second RRC reconfiguration message is used for reconfiguring the first PDCP entity, and indicates at least one of PDCP entity re-establishment and PDCP data recovery of the first PDCP entity.

3. The method of claim 1 , wherein the second PDCP entity is associated with at least one Acknowledgement mode (AM) Radio Link Control (RLC) entity.

4. The method of claim 3 , wherein the second PDCP entity is associated with an Unacknowledged Mode (UM) RLC entity in addition to the at least one AM RLC entity.

5. The method of claim 1 , wherein the first RRC reconfiguration message further indicates at least one of adding, releasing, and modifying the second PDCP entity.

6. The method of claim 1 , wherein the first RRC reconfiguration message further indicates to the second PDCP entity to switch a transmission scheme of the MRB configuration from a Point to Point (PTP) transmission scheme to a Point to Multipoint (PTM) transmission scheme or from the PTM transmission scheme to the PTP transmission scheme.

7. A user equipment (UE) for triggering a packet data convergence protocol (PDCP) status report, the UE comprising:

at least one processor; and

at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to:

receive, from a network, a Data Radio Bearer (DRB) configuration for configuring a DRB that is associated with a first PDCP entity of the UE;

receive, from the network, a Multicast Broadcast Service Radio Bearer (MRB) configuration for configuring an MRB that is associated with a second PDCP entity of the UE;

trigger, by the first PDCP entity, a first PDCP status report based on a first configuration of the first PDCP entity;

receive, from the network, an information element (IE) indicating that the second PDCP entity is configured to trigger a second PDCP status report; and

trigger, by the second PDCP entity, the second PDCP status report upon receiving, from the network, the IE and a first Radio Resource Control (RRC) reconfiguration message for a second configuration of the second PDCP entity, wherein:

the first RRC reconfiguration message is used for reconfiguring the second PDCP entity and indicates at least one of PDCP entity re-establishment and PDCP data recovery of the second PDCP entity.

8. The UE of claim 7 , wherein:

the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to trigger the first PDCP status report when the UE receives, from the network, a second Radio Resource Control (RRC) reconfiguration message for the first configuration of the first PDCP entity, and

the second RRC reconfiguration message is used for reconfiguring the first PDCP entity, and indicates at least one of PDCP entity re-establishment and PDCP data recovery of the first PDCP entity.

9. The UE of claim 7 , wherein the second PDCP entity is associated with at least one Acknowledgement mode (AM) Radio Link Control (RLC) entity.

10. The UE of claim 9 , wherein the second PDCP entity is associated with an Unacknowledged Mode (UM) RLC entity in addition to the at least one AM RLC entity.

11. The UE of claim 7 , wherein the first RRC reconfiguration message further indicates at least one of adding, releasing, and modifying the second PDCP entity.

12. The UE of claim 7 , wherein the first RRC reconfiguration message further indicates to the second PDCP entity to switch a transmission scheme of the MRB configuration from a Point to Point (PTP) transmission scheme to a Point to Multipoint (PTM) transmission scheme or from the PTM transmission scheme to the PTP transmission scheme.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2024
From: FG INNOVATION COMPANY LIMITED
To: SHARP KABUSHIKI KAISHA
Reel/Frame 069028/0473 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 25, 2022
From: CHIN, HENG-LI; CHEN, HUNG-CHEN; WEI, CHIA-HUNG; TSENG, YUNG-LAN
To: FG INNOVATION COMPANY LIMITED
Reel/Frame 059403/0612 →
Continuity (2)
Provisional Application 63166124 · Mar 25, 2021
Related Publication 20220312525A1 · Sep 29, 2022
References Cited (31)
US 11425614B2 · You · 2022 [cited by examiner]
US 11765555B1 · Babaei · 2023 [cited by examiner]
US 20150304903A1 · Uchino · 2015 [cited by examiner]
US 20160066241A1 · Wu · 2016 [cited by examiner]
US 20170230873A1 · Baek · 2017 [cited by examiner]
US 20180139030A1 · Kim · 2018 [cited by examiner]
US 20210068003A1 · Kadiri et al. · 2021 [cited by applicant]
US 20210126745A1 · Kadiri · 2021 [cited by examiner]
US 20220217506A1 · Xu · 2022 [cited by examiner]
US 20220338291A1 · Hong · 2022 [cited by examiner]
US 20230007544A1 · Zhu · 2023 [cited by examiner]
US 20230085168A1 · Chen · 2023 [cited by examiner]
US 20230199437A1 · Zhu · 2023 [cited by examiner]
US 20230262734A1 · Qi · 2023 [cited by examiner]
US 20230362596A1 · Xu · 2023 [cited by examiner]
US 20230396367A1 · Hori · 2023 [cited by examiner]
US 20240015849A1 · Teyeb · 2024 [cited by examiner]
US 20240015850A1 · Fujishiro · 2024 [cited by examiner]
US 20240064831A1 · Babaei · 2024 [cited by examiner]
US 20240137826A1 · Shimoda · 2024 [cited by examiner]
CN 111901766 · 2020 [cited by applicant]
Spreadtrum Communications, Discussion on dynamic PTM PTP switch, 3GPP TSG-RAN WG2 Meeting #113 electronic, Online, Jan. 25-Feb. 5, 2021, R2-2100677, section 2. [cited by applicant]
CATT, Reliability Improvement for PTM Transmission, 3GPP TSG-RAN WG2 Meeting #113-e, Online, Jan. 25-Feb. 5, 2021, R2-2100083, section 2. [cited by applicant]
3GPP TS 36.300, “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-UTRA… [cited by applicant]
3GPP TS 38.321, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 16)”, V16.3.0 (Dec. 2020). [cited by applicant]
3GPP TS 36.331, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release… [cited by applicant]
3GPP TS 38.323, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 16)”, V16.2.0 (Sep. 2020). [cited by applicant]
3GPP TS 38.322, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Link Control (RLC) protocol specification (Release 16)”, V16.2.0 (Dec. 2020). [cited by applicant]
3GPP TS 38.331, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16)”, V16.3.1 (Jan. 2021). [cited by applicant]
3GPP TR 23.757, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architectural enhancements for 5G multicast-broadcast services (Release 17)”, V1.2.0 (Nov. 2020). [cited by applicant]
3GPP TS 36.321, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 1… [cited by applicant]