IP Library Granted Patent US 12,382,468
Granted Patent B2
US 12,382,468 · App. 17/870,234 · Granted Aug 5, 2025

Method and user equipment for handling a survival time state

Inventors: Heng-Li Chin (Taipei, TW); Hai-Han Wang (Taipei, TW); Hsin-Hsi Tsai (Taipei, TW); Chia-Hung Wei (Taipei, TW)
Assignee: SHARP KABUSHIKI KAISHA
H04W72/23H04L1/08H04L1/1812H04W72/1263H04W80/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,382,468
App. No.
17/870,234
Granted
Aug 5, 2025
Kind
B2
Abstract

A method and a user equipment (UE) for handling a survival time state are provided. The method includes: receiving a Packet Data Convergence Protocol (PDCP) configuration for indicating that a Data Radio Bearer (DRB) associated with a PDCP entity supports a survival time state functionality, the PDCP entity being associated with at least two Radio Link Control (RLC) entities; receiving an Uplink (UL) grant for retransmission of a Medium Access Control (MAC) Protocol Data Unit (PDU), the MAC PDU including data from the DRB; entering the survival time state for the DRB upon receiving the UL grant; and activating a PDCP duplication for the PDCP entity during the survival time state.

Claims (38)

1. A method performed by a User Equipment (UE) for handling a survival time state, the method comprising:

receiving, from a base station, a Packet Data Convergence Protocol (PDCP) configuration;

determining whether an indication is included in the PDCP configuration;

determining that a Data Radio Bearer (DRB) associated with a PDCP entity supports a survival time state functionality in a case that the indication is included in the PDCP configuration and indicates a specific value, wherein the PDCP entity is associated with at least two Radio Link Control (RLC) entities;

determining that the DRB associated with the PDCP entity does not support the survival time state functionality in a case that the indication is absent from the PDCP configuration;

receiving an Uplink (UL) grant for retransmission of a Medium Access Control (MAC) Protocol Data Unit (PDU), the MAC PDU including data from the DRB;

entering the survival time state for the DRB upon receiving the UL grant in a case that a counter value of a counter for counting a number of unsuccessful data transmissions is equal to a threshold; and

activating a PDCP duplication for the PDCP entity while the UE is in the survival time state.

2. The method of claim 1 , wherein

the indication is in an enumerate format.

3. The method of claim 1 , wherein the UL grant is associated with a Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI).

4. The method of claim 1 , further comprising:

after activating the PDCP duplication for the PDCP entity:

duplicating a PDCP PDU; and

sending the duplicated PDCP PDU from the PDCP entity to each of the at least two RLC entities.

5. The method of claim 1 , wherein:

the UL grant includes a Hybrid Automatic Repeat Request (HARQ) process identifier (ID) of a HARQ process, and

the MAC PDU is stored in a HARQ process buffer of the HARQ process.

6. A User Equipment (UE) for handling a survival time state, the UE comprising:

at least one non-transitory computer-readable medium storing one or more computer-executable instructions; and

at least one processor coupled to the at least one non-transitory computer-readable medium and configured to execute the one or more computer-executable instructions to cause the UE to:

receive, from a base station, a Packet Data Convergence Protocol (PDCP) configuration;

determine whether an indication is included in the PDCP configuration;

determine that a Data Radio Bearer (DRB) associated with a PDCP entity supports a survival time state functionality in a case that the indication is included in the PDCP configuration and indicates a specific value, wherein the PDCP entity is associated with at least two Radio Link Control (RLC) entities;

determine that the DRB associated with the PDCP entity does not support the survival time state functionality in a case that the indication is absent from the PDCP configuration;

receive an Uplink (UL) grant for retransmission of a Medium Access Control (MAC) Protocol Data Unit (PDU), the MAC PDU including data from the DRB;

enter the survival time state for the DRB upon receiving the UL grant in a case that a counter value of a counter for counting a number of unsuccessful data transmissions is equal to a threshold; and

activate a PDCP duplication for the PDCP entity while the UE is in the survival time state.

7. The UE of claim 6 , wherein

the indication is in an enumerate format.

8. The UE of claim 6 , wherein the UL grant is associated with a Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI).

9. The UE of claim 6 , wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:

after activating the PDCP duplication for the PDCP entity:

duplicate a PDCP PDU; and

send the duplicated PDCP PDU from the PDCP entity to each of the at least two RLC entities.

10. The UE of claim 6 , wherein:

the UL grant includes a Hybrid Automatic Repeat Request (HARQ) process identifier (ID) of a HARQ process, and

the MAC PDU is stored in a HARQ process buffer of the HARQ process.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2024
From: FG INNOVATION COMPANY LIMITED
To: SHARP KABUSHIKI KAISHA
Reel/Frame 069028/0594 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 21, 2022
From: CHIN, HENG-LI; WANG, HAI-HAN; TSAI, HSIN-HSI; WEI, CHIA-HUNG
To: FG INNOVATION COMPANY LIMITED
Reel/Frame 060581/0019 →
Continuity (3)
Provisional Application 63260051 · Aug 6, 2021
Provisional Application 63224307 · Jul 21, 2021
Related Publication 20230041119A1 · Feb 9, 2023
References Cited (35)
US 20170272975A1 · Uchino · 2017 [cited by examiner]
US 20190215717A1 · Lee · 2019 [cited by examiner]
US 20200107370A1 · Wei · 2020 [cited by examiner]
US 20200236579A1 · Cho · 2020 [cited by examiner]
US 20200274654A1 · Loehr · 2020 [cited by examiner]
US 20210144743A1 · Rastegardoost · 2021 [cited by examiner]
US 20210235399A1 · Wich · 2021 [cited by examiner]
US 20220086861A1 · Zhao · 2022 [cited by examiner]
US 20220132502A1 · Sun · 2022 [cited by examiner]
US 20220159100A1 · Xu · 2022 [cited by examiner]
US 20220182185A1 · Bostrom · 2022 [cited by examiner]
US 20220182304A1 · Yu · 2022 [cited by examiner]
US 20220224446A1 · Fan · 2022 [cited by examiner]
US 20220330049A1 · Tan · 2022 [cited by examiner]
US 20230209554A1 · Kuo · 2023 [cited by examiner]
US 20230231655A1 · Yue · 2023 [cited by examiner]
US 20230284274A1 · Loehr · 2023 [cited by examiner]
US 20230308229A1 · Kuo · 2023 [cited by examiner]
US 20230309180A1 · Tesanovic · 2023 [cited by examiner]
US 20230362707A1 · Fu · 2023 [cited by examiner]
US 20240298346A1 · Zou · 2024 [cited by examiner]
US 20240373283A1 · Zou · 2024 [cited by examiner]
CN 112929136A · 2021 [cited by applicant]
WO 2020024847A1 · 2020 [cited by applicant]
WO 2021064287A1 · 2021 [cited by applicant]
Nokia, Nokia Shanghai Bell, “RAN Enhancement for New QoS Parameters”, R2-2105873, 3GPP TSG-RAN WG2 Meeting #114 Electronic Elbonia, May 19-May 27, 2021. [cited by applicant]
CATT, “Handling of Survival Time”, R2-2102726, 3GPP TSG-RAN WG2 Meeting #113bis-e Online, Apr. 12-Apr. 20, 2021. [cited by applicant]
CATT, “Survival time triggered PDCP duplication”, R2-1905752, 3GPP TSG-RAN WG2 Meeting #106 Reno, USA, May 13-May 17, 2019. [cited by applicant]
3GPP TS 22.104, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for cyber-physical control applications in vertical domains; Stage 1 (Release 18)”, V1… [cited by applicant]
3GPP TS 22.261, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the 5G system; Stage 1 (Release 18)”, V18.3.0 (Jun. 2021). [cited by applicant]
3GPP TS 38.211, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (Release 16)”, V16.6.0 (Jun. 2021). [cited by applicant]
3GPP TS 38.212, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding (Release 16)”, V16.6.0 (Jun. 2021). [cited by applicant]
3GPP TS 38.214, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 16)”, V16.6.0 (Jun. 2021). [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.5.0 (Jun. 2021). [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.5.0 (Jun. 2021). [cited by applicant]