IP Library Granted Patent US 12,376,184
Granted Patent B2
US 12,376,184 · App. 18/132,771 · Granted Jul 29, 2025

Configuration of bandwidth part

Inventors: Taehun Kim (Fairfax, VA); Esmael Hejazi Dinan (McLean, VA); Hyoungsuk Jeon (Centreville, VA); Kyungmin Park (Vienna, VA); Jinsook Ryu (Oakton, VA); Peyman Talebi Fard (Vienna, VA)
Assignee: Koninklijke Philips N.V.
H04W76/27H04W72/23H04W76/28
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,376,184
App. No.
18/132,771
Granted
Jul 29, 2025
Kind
B2
Abstract

A wireless device comprises one or more processors and memory storing instructions that, when executed by the one or more processors, cause the wireless device to receive, from a base station, a first radio resource control (RRC) release message comprising a suspend configuration associated with one or more first bandwidth parts (BWPs). While the wireless device is in an RRC idle state or an RRC inactive state, the one or more processors, cause the wireless device to transmit, based on the suspend configuration. first data associated with a small data transmission (SDT) procedure. The one or more processors cause the wireless device to receive, from the base station, a second RRC release message comprising a subsequent configuration associated with one or more second BWPs, and receive, from the base station via the one or more second BWPs, based on the subsequent configuration, second data associated with the SDT procedure.

Claims (65)

1. A device comprising:

at least one processor circuits; and

a memory circuit, wherein the memory circuit is arranged to store instructions for the at least one processor circuits,

wherein the at least one processor circuits are arranged to receive a first radio resource control release message,

wherein the first radio resource control release message comprises a suspend configuration

wherein the suspend configuration is associated with at least one first bandwidth parts,

wherein the at least one processor circuits are arranged to transmit first data based on the suspend configuration while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the first data is associated with a small data transmission procedure,

wherein the at least one processor circuits are arranged to transmit a radio resource control message requesting to resume a radio resource control connection based on the suspend configuration while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the at least one processor circuits are arranged to receive a second radio resource control release message while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the second radio resource control release message comprises a subsequent configuration,

wherein the subsequent configuration is associated with at least one second bandwidth parts,

wherein the at least one processor circuits are arranged to receive via the at least one second bandwidth parts second data based on the subsequent configuration while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the second data is associated with the small data transmission procedure,

wherein the at least one first bandwidth parts comprise a first uplink bandwidth part and a first downlink bandwidth part.

2. The device of claim 1 , wherein the at least one processor circuits are arranged to cause the device to transition to the radio resource control idle state or the radio resource control inactive state based on the first radio resource control release message.

3. The device of claim 1 , wherein a Msg 3 comprises the first data and/or the radio resource control message requesting resumption of the RRC connection.

4. The device of claim 1 , wherein the first radio resource control release message is received via a first downlink bandwidth part of the at least one first bandwidth parts associated with the suspend configuration.

5. The device of claim 1 , wherein the at least one second bandwidth parts comprise a second uplink bandwidth part and a second downlink bandwidth part.

6. The device of claim 1 , wherein the second data is received via a second downlink bandwidth part of the at least one second bandwidth parts.

7. The device of claim 1 wherein Msg 4 comprises the second radio resource control release message comprising the subsequent configuration.

8. The device of claim 1 wherein Msg 5 comprises the second data associated with the small data transmission procedure.

9. A base station comprising:

at least one processor circuits; and

a memory circuit, wherein the memory circuit is arranged to store instructions for the at least one processor circuits,

wherein the at least one processor circuits are arranged to transmit a first radio resource control release message to a wireless device,

wherein the first radio resource control release message comprises a suspend configuration,

wherein the suspend configuration is associated with at least one first bandwidth parts,

wherein the at least one processor circuits are arranged to receive first data based on the suspend configuration while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the first data is associated with a small data transmission procedure,

wherein the at least one processor circuits are arranged to receive a radio resource control message requesting to resume a radio resource control connection based on the suspend configuration while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

transmit a second radio resource control release message to the wireless device while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the second radio resource control release message comprises a subsequent configuration,

wherein the subsequent configuration is associated with at least one second bandwidth parts,

wherein the at least one processor circuits are arranged to transmit via the at least one second bandwidth parts second data to the wireless device based on the subsequent configuration while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the second data is associated with the small data transmission procedure,

wherein the at least one first bandwidth parts comprise a first uplink bandwidth part and a first downlink bandwidth part.

10. The base station of claim 9 , wherein the at least one processor circuits are arranged to cause the wireless device to transition to the radio resource control idle state or the radio resource control inactive state based on the first radio resource control release message.

11. The base station of claim 9 , wherein a Msg 3 comprises the first data and/or the radio resource control message requesting resumption of the radio resource control connection.

12. The base station of claim 9 , wherein the first radio resource control release message is transmitted via a first downlink bandwidth part of the at least one first bandwidth parts associated with the suspend configuration.

13. The base station of claim 9 , wherein the at least one second bandwidth parts comprise a second uplink bandwidth part and a second downlink bandwidth part.

14. The base station of claim 9 , wherein the second data is transmitted via a second downlink bandwidth part of the at least one second bandwidth parts.

15. The base station of claim 9 , wherein Msg 4 comprises the second radio resource control release message comprising the subsequent configuration.

16. The base station of claim 9 , wherein Msg 5 comprises the second data associated with the small data transmission procedure.

17. A non-transitory computer-readable medium storing a computer program, wherein the computer program when executed on a processor:

receives a first radio resource control release message,

wherein the first radio resource control release message comprises a suspend configuration

wherein the suspend configuration is associated with at least one first bandwidth parts;

transmits first data based on the suspend configuration while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the first data is associated with a small data transmission procedure

transmits a radio resource control message requesting to resume a radio resource control connection based on the suspend configuration while the wireless device is in a radio resource control idle state or a radio resource control inactive state;

receives a second radio resource control release message while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the second radio resource control release message comprises a subsequent configuration,

wherein the subsequent configuration is associated with at least one second bandwidth parts,

comprising a subsequent configuration associated with at least one second bandwidth parts; and

receives via the at least one second bandwidth parts second data based on the subsequent configuration while the wireless device is in a radio resource control idle state or a radio resource control inactive state,

wherein the second data is associated with the small data transmission procedure,

wherein the at least one first bandwidth parts comprise a first uplink bandwidth part and a first downlink bandwidth part.

18. The non-transitory computer-readable medium of claim 17 , wherein the processor causes a transition to the radio resource control idle state or the radio resource control inactive state based on the first radio resource control release message.

19. The non-transitory computer-readable medium of claim 17 , a Msg 3 comprises the first data and/or the radio resource control message requesting resumption of the RRC connection.

20. The non-transitory computer-readable medium of claim 17 , wherein the first radio resource control release message is received via a first downlink bandwidth part of the at least one first bandwidth parts associated with the suspend configuration.

21. The non-transitory computer-readable medium of claim 17 , wherein the second data is received via a second downlink bandwidth part of the at least one second bandwidth parts.

22. The non-transitory computer-readable medium of claim 17 , wherein Msg 4 comprises the second radio resource control release message comprising the subsequent configuration.

23. The non-transitory computer-readable medium of claim 17 , wherein Msg 5 comprises the second data associated with the small data transmission procedure.

24. The non-transitory computer-readable medium of claim 17 , wherein the second data is received via a second downlink bandwidth part of the at least one second bandwidth parts.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 3, 2023
From: OFINNO LLC
To: KONINKLIJKE PHILIPS N.V.
Reel/Frame 064478/0148 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 30, 2023
From: KIM, TAEHUN; DINAN, ESMAEL; JEON, HYOUNGSUK; PARK, KYUNGMIN; RYU, JINSOOK; TALEBI FARD, PEYMAN
To: OFINNO, LLC
Reel/Frame 063797/0600 →
Continuity (4)
Continuation 17712356 · Apr 4, 2022
Continuation PCTUS2021032002 · May 12, 2021
Provisional Application 63024827 · May 14, 2020
Related Publication 20230247715A1 · Aug 3, 2023
References Cited (90)
US 8234534B2 · Park et al. · 2012 [cited by applicant]
US 10999885B1 · Shih · 2021 [cited by examiner]
US 11399408B2 · Babaei · 2022 [cited by applicant]
US 11438931B2 · Rastegardoost et al. · 2022 [cited by applicant]
US 20090135769A1 · Sambhwani et al. · 2009 [cited by applicant]
US 20130170453A1 · Kim et al. · 2013 [cited by applicant]
US 20150195831A1 · Du · 2015 [cited by examiner]
US 20180139778A1 · Chou et al. · 2018 [cited by applicant]
US 20190141515A1 · Kim · 2019 [cited by examiner]
US 20190223221A1 · Johansson · 2019 [cited by examiner]
US 20200037345A1 · Ryoo · 2020 [cited by examiner]
US 20200092939A1 · Kim et al. · 2020 [cited by applicant]
US 20200107268A1 · Lee et al. · 2020 [cited by applicant]
US 20200229130A1 · Keating · 2020 [cited by examiner]
US 20200359443A1 · Lu · 2020 [cited by examiner]
US 20210058824A1 · Choe · 2021 [cited by examiner]
US 20210160949A1 · Kim et al. · 2021 [cited by applicant]
US 20210258954A1 · Wang · 2021 [cited by examiner]
US 20210259021A1 · Huang et al. · 2021 [cited by applicant]
US 20210266775A1 · Babaei et al. · 2021 [cited by applicant]
US 20210298108A1 · Wu · 2021 [cited by examiner]
US 20210315050A1 · Rönneke et al. · 2021 [cited by examiner]
US 20210337625A1 · Tsai · 2021 [cited by examiner]
US 20210352617A1 · Choe · 2021 [cited by examiner]
US 20210360730A1 · Kim · 2021 [cited by examiner]
US 20220070945A1 · Wang et al. · 2022 [cited by applicant]
US 20220124859A1 · Wang · 2022 [cited by examiner]
US 20220166594A1 · Zhang · 2022 [cited by examiner]
US 20220201794A1 · Fujishiro · 2022 [cited by examiner]
US 20220217810A1 · Bao · 2022 [cited by examiner]
CN 114642072A · 2022 [cited by applicant]
EP 3506708A1 · 2019 [cited by applicant]
EP 3716723A1 · 2020 [cited by applicant]
EP 3735049A1 · 2020 [cited by applicant]
EP 3869907A1 · 2021 [cited by applicant]
WO 2018062957A1 · 2018 [cited by applicant]
WO 2019186303A1 · 2019 [cited by applicant]
WO 2020032659A1 · 2020 [cited by applicant]
WO 2020034560A1 · 2020 [cited by applicant]
WO 2020059318A1 · 2020 [cited by applicant]
WO 2021190355A1 · 2021 [cited by applicant]
WO 2021213505A1 · 2021 [cited by applicant]
3GPP TS 33.401 V16.2.0 (Mar. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture… [cited by applicant]
3GPP TS 33.501 V16.1.0 (Dec. 2019); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system; (Release 16… [cited by applicant]
3GPP TS 36.321 V16.0.0 (Mar. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Con… [cited by applicant]
3GPP TS 36.331 V16.0.0 (Mar. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Co… [cited by applicant]
3GPP TS 36.423 V16.0.0 (Dec. 2019); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network(E-UTRAN); X2 applic… [cited by applicant]
R2-2000250; 3GPP TSG-RAN WG2 Meeting #109e; e-meeting, Feb. 24-Mar. 6, 2020; Source: Thales; Title: Remaining clarifications on PUR configuration; Agenda Item: 7.2.4; Document for: Discussion and Decision. [cited by applicant]
R2-2000435; 3GPP TSG-RAN2 Meeting #109-e; Online, Feb. 24, 2020-Mar. 6, 2020; Agenda Item: 7.2.4, 7.1.4; Source: Qualcomm Incorporated; Title: T300 applicability for PUR; Document for: Discussion/Decision. [cited by applicant]
R2-2000443; 3GPP TSG-RAN WG2 Meeting #109 electronic; Feb. 24-Mar. 6, 2020; Agenda item: 7.2.4 Transmission in preconfigured resources; Source: Sierra Wireless S.A.; Title: TA validation based on serving cell RSRP chang… [cited by applicant]
R2-2000559; Resubmission of R2-1914596; 3GPP TSG RAN WG2 Meeting #109e; Elbonia, Feb. 24-Mar. 6, 2020; Agenda item: 7.2.4; Source: Nokia, Nokia Shanghai Bell; Title: Security Aspects of D-PUR for CP Solution; WID/SID: A… [cited by applicant]
R2-2000640; Revision of R2-1915312; 3GPP TSG-RAN WG2 Meeting #109-e; Online, Feb. 24-Mar. 6, 2020; Agenda Item: 7.2.4; Source: Huawei, HiSilicon; Title: Handling of D-PUR configuration for CP solution; Document for: Dis… [cited by applicant]
R2-2000641; 3GPP TSG-RAN WG2 Meeting #109-e; Online, Feb. 24-Mar. 6, 2020; Title: [Draft] LS on handling of D-PUR configuration for the CP solution; Response to:; Release: Release 16; Work Item: NB_IOTenh3-Core, LTE_eMT… [cited by applicant]
R2-2000642; 3GPP TSG-RAN WG2 Meeting #109-e; Online, Feb. 24-Mar. 6, 2020; Agenda Item: 7.2.4; Source: Huawei, HiSilicon; Title: RRC-MAC-PHY interactions for PUR; Document for: Discussion and Decision. [cited by applicant]
R2-2000643; Signalling aspect of PUR configuration; 3GPP TSG-RAN WG2 Meeting #109-e; Online, Feb. 24-Mar. 6, 2020; Agenda Item: 7.2.4; Source: Huawei, HiSilicon; Title: Signalling aspect of PUR configuration; Document f… [cited by applicant]
R2-2000695; 3GPP TSG-RAN2 Meeting #109-e; Online, Feb. 24, 2020-Mar. 6, 2020; Agenda Item: 7.2.4, 7.1.4; Source: Qualcomm Incorporated; Title: Remaining FFSes on RRC-MAC interaction for PUR; Document for: Discussion/Dec… [cited by applicant]
R2-2000984; Revision of R2-1915405; 3GPP TSG-RAN WG2 #109-eTdoc; Electronic meeting, Feb. 24-Mar. 6, 2020; Agenda Item: 7.2.4; Source: Ericsson; Title: PUR periodicity and UE multiplexing; Document for: Discussion, Deci… [cited by applicant]
R2-2000985; 3GPP TSG-RAN WG2 Meeting #109-e; Electronic meeting, Feb. 24-Mar. 6, 2020; Agenda Item: 7.2.4; Source: Ericsson; Title: RRC-MAC interaction details and other FFSs for PUR in running MAC CR; Document for: Dis… [cited by applicant]
R2-2001198; Revision of R2-1914717; 3GPP TSG-RAN WG2 Meeting #109 electronic; Elbonia, Feb. 24-Mar. 6, 2020; Source: ZTE Corporation, Sanechips; Title: D-PUR reconfiguration and release for CP solution; Agenda item: 7.2… [cited by applicant]
R2-2001200; 3GPP TSG-RAN WG2 Meeting #109 electronic; Elbonia, Feb. 24-Mar. 6, 2020; Source: ZTE Corporation, Sanechips; Title: MAC-RRC coordination for TA validation and some FFS for D-PUR; Agenda item: 7.2.4; Document… [cited by applicant]
R2-2001201; 3GPP TSG-RAN WG2 Meeting #109 electronic; Elbonia, Feb. 24-Mar. 6, 2020; Source: ZTE Corporation, Sanechips; Title: Remaining FFSs for D-PUR in 36.331; Agenda item: 7.2.4; Document for: Discussion and Decisi… [cited by applicant]
R2-2001202; 3GPP TSG-RAN WG2 Meeting #109 electronic; Elbonia, Feb. 24-Mar. 6, 2020; Source: ZTE Corporation, Sanechips; Title: Remaining FFSs for D-PUR in 36.321; Agenda item: 7.2.4; Document for: Discussion and Decisi… [cited by applicant]
R2-2001394; 3GPP TSG RAN WG2#109-e; Electronic meeting, Feb. 24-Mar. 6, 2020; Agenda Item: 7.1.13 ; Source: LG Electronics Inc.; Title: Clarification for the condition of PUR configuration request procedure; Document fo… [cited by applicant]
R2-2001395; 3GPP TSG RAN WG2#109-e; Electronic meeting, Feb. 24-Mar. 6, 2020; Agenda Item: 7.1.13 ; Source: LG Electronics Inc.; Title : Handling application response for D-PUR transmission; Document for : Discussion an… [cited by applicant]
R2-2001397; (Resubmission of R2-1915951); 3GPP TSG RAN WG2#109-e; Electronic meeting, Feb. 24-Mar. 6, 2020; Agenda Item: 7.1.4, 7.2.4; Source: LG Electronics Inc.; Title : Discussion on delivery of D-PUR configuration r… [cited by applicant]
R2-2001398; (Resubmission of R2-1915952); 3GPP TSG-RAN WG2 Meeting #109-e; Electronic meeting, Feb. 24-Mar. 6, 2020; Agenda Item: 7.1.4, 7.2.4; Source: LG Electronics Inc.; Title : Paging response using D-PUR; Document … [cited by applicant]
R2-2001399; (Resubmission of R2-1915053); 3GPP TSG-RAN WG2 Meeting #109-e; Electronic meeting, Feb. 24-Mar. 6, 2020; Agenda Item: 7.1.4, 7.2.4; Source: LG Electronics Inc.; Title: Discussion on shared preconfigured upli… [cited by applicant]
R2-2001516; 3GPP TSG-RAN WG2 Meeting #109 electronic; Feb. 24-Mar. 6, 2020; Agenda item: 7.2.4 Transmission in preconfigured resources; Source: Sierra Wireless; Title: Further Pre-configured UL Resources Design Consider… [cited by applicant]
R2-2001601; Revision of R2-1916041; 3GPP TSG-RAN WG2 Meeting #109e; Athens, Greece, Feb. 24-28, 2020; Agenda Item: 7.2.4; Source: ASUSTeK; Title: Handling D-PUR configuration in RRC_CONNECTED state; Document for: Discus… [cited by applicant]
R2-2001602; Revision of R2-1916042; 3GPP TSG-RAN WG2 Meeting #109e; Athens, Greece, Feb. 24-28, 2020; Agenda Item: 7.2.4; Source: ASUSTeK; Title: Remaining issues of D-PUR TA timer; Document for: Discussion and Decision. [cited by applicant]
R2-2003331; 3GPP TSG RAN WG2 Meeting #109bis-e; Elbonia, Apr. 20-Mar. 6, 2020; Agenda item: 7.2.3; Source! Nokia, Nokia Shanghai Bell; Title: Security Aspects of D-PUR for CP Solution; WID/SID: Additional Enhancements f… [cited by applicant]
R2-2003355; 3GPP TSG-RAN WG2 Meeting #109bis-e; Electronic meeting, Apr. 20-30, 2020; Agenda Item: 7.2.3; Source: Ericsson, Huawei, HiSilicon; Title: Moving UL grant handling from MAC to RRC for PUR; Document for: Discu… [cited by applicant]
R2-2003415; Revision of (R2-2000443); 3GPP TSG-RAN WG2 Meeting #109bis electronic; Apr. 20, 2020- Apr. 30, 2020; Agenda item: 7.2.3 Transmission in preconfigured resources; Source: Sierra Wireless S.A.; Title: TA valida… [cited by applicant]
R2-2003429; 3GPP TSG-RAN WG2 #109bis-e; e-Meeting, Apr. 20-30, 2020; Agenda item: 7.2.3 Transmission in preconfigured UL resources; Source: Sierra Wireless; Title: Configuration and adjustment of repetition number; Docu… [cited by applicant]
R2-2003652; 3GPP TSG-RAN WG2 Meeting #109bis-e; Electronic, Apr. 20-30, 2020; Agenda Item: 7.2.3; Source: ASUSTek; Title: Remaining issues of D-PUR TA timer in MAC; Document for: Discussion and Decision. [cited by applicant]
R2-2003653; 3GPP TSG-RAN WG2 Meeting #109bis-e; Electronic, Apr. 20-30, 2020; Agenda Item: 7.2.3; Source: ASUSTek; Title: PUR configuration maintenance during RRC state transition; Document for: Discussion and Decision. [cited by applicant]
R2-2003746; 3GPP TSG-RAN WG2 Meeting#109bis-e; Online, Apr. 20-30, 2020; Agenda Item: 7.2.3; Source: Huawei; Title: Report of email discussion [Post109e#46][NBIOT/EMTC] PUR open issues; Document for: Discussion and Deci… [cited by applicant]
S2-2002259; SA WG2 Meeting #137-e; Feb. 24-27, 2020, E-meeting; CR-Form-v12.0; Change Request; 23.502 CR 2159; rev; Current version: 16.3.0. [cited by applicant]
S2-2002296; (was S2-2000295); SA WG2 Meeting #137-E; Online, Feb. 24-27, 2020; CR-Form-v11.2; Change Request; 23.502 CR 1848; rev 9; Current version: 16.3.0. [cited by applicant]
S2-2002354; (revision of S2-2002060); SA WG2 Meeting #S2-137E; Feb. 24-27, 2020, Electronic Meeting; CR-Form-v12.0; Change Request; 23.401 CR 3589; rev 1; Current version: 16.5.0. [cited by applicant]
R2-2003257; 3GPP TSG-RAN2 Meeting #109-e-Bis; Online, Apr. 20, 2020-Apr. 30, 2020; CR-Form-v12.0; Change Request; 36.321 CR; rev-; Current version: 16.0.0. [cited by applicant]
R2-2003258; 3GPP TSG-RAN2 Meeting #109-e-Bis; Online, Apr. 20, 2020-Apr. 30, 2020; CR-Form-v12.0; Change Request; 36.321 CR rev-Current version: 16.0.0. [cited by applicant]
R2-2003267; 3GPP TSG-RAN2 Meeting #109-e-Bis; Online, Apr. 20, 2020-Apr. 30, 2020; CR-Form-v12.0; Change Request; 36.321 CR rev-Current version: 16.0.0. [cited by applicant]
R2-2003278; 3GPP TSG-RAN2 Meeting #109-e-Bis; Online, Apr. 20, 2020-Apr. 30, 2020; CR-Form-v12.0; Change Request; 36.331 CR rev-Current version: 16.0.0. [cited by applicant]
S2-2002014; 3GPP TSG SA2 Meeting #137E; Elbonia, Feb. 24-27, 2020; 5G CIoT MT-EDT Discussion; Source: Qualcomm Incorporated. [cited by applicant]
S2-2002260r1; 5G-GUTI re-assignment for 5G MT-EDT; Hannu Hietalahti; Feb. 24, 2020. [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority mailed Oct. 6, 2021 in International Application No. PCT/US2021/032002. [cited by applicant]
3GPP TS 38.300 V17.0.0 (Mar. 2022); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2; (Release 17). [cited by applicant]
3GPP TS 38.321 V17.0.0 (Mar. 2022); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification; (Release 17). [cited by applicant]
3GPP TS 38.331 V17.0.0 (Mar. 2022); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification; (Release 17). [cited by applicant]