IP Library › Granted Patent US 12,445,903
Granted Patent B2
US 12,445,903 · App. 19/055,880 · Granted Oct 14, 2025

Base station device, terminal device, communication method and communication system

Inventors: Yoshiaki Ohta (Yokohama, JP); Takayoshi Ode (Yokohama, JP); Yoshihiro Kawasaki (Kawasaki, JP)
Assignee: FUJITSU LIMITED
H04W28/06H04W80/02H04W88/08
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,445,903
App. No.
19/055,880
Granted
Oct 14, 2025
Kind
B2
Abstract

A base station device including: a transmitter configured to transmit, for each logical channel, first data of a first type and second data of a second type; and processor circuitry configured to: omit information about a data length of the second data in a MAC protocol data unit (PDU), place a medium access control (MAC) header in front of a MAC service data unit (MSDU) of the second data, and multiplex the first data and the second data, wherein the data length of the second data is omitted from the MAC header and an R bit (reserved bit) is set in the first bit of the first octet in the MAC header.

Claims (38)

1. A transmitting device comprising:

a transmitter configured to transmit first data of a first type for a first logical channel, and to transmit second data of a second type for a second logical channel; and

processor circuitry configured to:

place, in a medium access control (MAC) layer, a first MAC header in front of a MAC service data unit (MSDU) including the second data, the second data being transferred to the MAC layer from a layer that is higher than the MAC layer, the first MAC header including a Reserve field (R-field) and a Logical Channel Identifier (LCID) field, the LCID field of the first MAC header which is placed in front of the MSDU being set to a first index which is selected from a plurality of indices, the first index indicating a first LCID value, the first LCID value being used for the second data in the MSDU, and

multiplex the first data and the second data, wherein information about a data length of the MSDU is omitted from the first MAC header and a Reserve bit (R bit) is set at bit one in a first octet in the first MAC header, the data length of the MSDU being fixed, and

wherein the processor circuitry is further configured to select the first MAC header from a plurality of MAC headers, the plurality of MAC headers including:

the first MAC header that includes the first octet, the R-field being located at the bit one of the first octet, and another R-field being located at bit two of the first octet, the LCID field being located from bit three to bit eight of the first octet, and

a second MAC header that includes:

a first octet which includes an R-field and an LCID field; and

a second octet which includes a Length field (L-field).

2. The transmitting device of claim 1 , wherein

the first MAC header consists of the first octet.

3. The transmitting device of claim 1 , wherein

the first LCID value that is used for the second data in the MSDU is used for identifying the second logical channel for the second data.

4. The transmitting device of claim 3 , wherein

the plurality of indices includes:

the first index; and

a second index indicating a second LCID value, wherein the second LCID value is used for the first data of the first type and is used for identifying the first logical channel for the first data.

5. The transmitting device of claim 4 , wherein

the plurality of indices includes a third index indicating a padding.

6. A receiving device comprising:

a receiver configured to receive first data of a first type for a first logical channel, and to receive second data of a second type for a second logical channel; and

processor circuitry configured to process data according to a first medium access control (MAC) header placed in front of a MAC service data unit (MSDU) including the second data, the second data being transferred to the MAC layer from a layer that is higher than the MAC layer, the first MAC header including a Reserve field (R-field) and a Logical Channel Identifier (LCID) field, the LCID field of the first MAC header which is placed in front of the MSDU being set to a first index which is selected from a plurality of indices, the first index indicating a first LCID value, the first LCID value being used for the second data in the MSDU,

wherein the first data and the second data are multiplexed, and wherein information about a data length of the MSDU is omitted from the first MAC header and a Reserve bit (R bit) is set at bit one in a first octet in the first MAC header, the data length of the MSDU being fixed,

wherein the first MAC header is selected from a plurality of MAC headers, the plurality of MAC headers including:

the first MAC header that includes the first octet, the R-field being located at the bit one of the first octet, and another R-field being located at bit two of the first octet, the LCID field being located from bit three to bit eight of the first octet, and

a second MAC header that includes:

a first octet which includes an R-field and an LCID field; and

a second octet which includes a Length field (L-field).

7. A transmitting method comprising:

placing, in a medium access control (MAC) layer, a first MAC header in front of a MAC service data unit (MSDU) including second data, the second data being transferred to the MAC layer from a layer that is higher than the MAC layer, the first MAC header including a Reserve field (R-field) and a Logical Channel Identifier (LCID) field, the LCID field of the first MAC header which is placed in front of the MSDU being set to a first index which is selected from a plurality of indices, the first index indicating a first LCID value, the first LCID value being used for the second data in the MSDU;

multiplexing first data of a first type and the second data of a second type, wherein information about a data length of the MSDU is omitted from the first MAC header and a Reserve bit (R bit) is set at bit one in a first octet in the first MAC header, the data length of the MSDU being fixed; and

transmitting the first data and the second data which are multiplexed,

wherein the method further comprises selecting the first MAC header from a plurality of MAC headers, the plurality of MAC headers including:

the first MAC header that includes the first octet, the R-field being located at the bit one of the first octet, and another R-field being located at bit two of the first octet, the LCID field being located from bit three to bit eight of the first octet, and

a second MAC header that includes:

a first octet which includes an R-field and an LCID field; and

a second octet which includes a Length field (L-field).

Assignments (3)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE APPLICATION NUMBER 19345640 TO CHANGE IT TO 19346640 AND TO CORRECT THE APPLICATION 19317078 TO CHANGE IT TO 19319078. PREVIOUSLY RECORDED ON REEL 73477 FRAME 351. ASSIGNOR(S) HEREBY CONFIRMS THE THE ASSIGNMENT. Recorded Jan 20, 2026
From: FUJITSU LIMITED
To: 1FINITY INC.
Reel/Frame 075265/0471 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 3, 2025
From: FUJITSU LIMITED
To: 1FINITY INC.
Reel/Frame 073477/0351 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 18, 2025
From: OHTA, YOSHIAKI; ODE, TAKAYOSHI; KAWASAKI, YOSHIHIRO
To: FUJITSU LIMITED
Reel/Frame 070243/0305 →
Continuity (5)
Continuation 17231149 · Apr 15, 2021
Continuation 16460379 · Jul 2, 2019
Continuation 16260672 · Jan 29, 2019
Continuation PCTJP2018014339 · Apr 3, 2018
Related Publication 20250193732A1 · Jun 12, 2025
References Cited (105)
US 20020090033A1 · Anderlind et al. · 2002 [cited by applicant]
US 20030007512A1 · Tourunen et al. · 2003 [cited by applicant]
US 20050238016A1 · Nishibayashi et al. · 2005 [cited by applicant]
US 20060050709A1 · Sung et al. · 2006 [cited by applicant]
US 20060171396A1 · Singh · 2006 [cited by examiner]
US 20090141670A1 · Duncan Ho · 2009 [cited by applicant]
US 20090156194A1 · Meylan · 2009 [cited by examiner]
US 20090253470A1 · Xu · 2009 [cited by applicant]
US 20090279488A1 · Zheng et al. · 2009 [cited by applicant]
US 20100208655A1 · Kim et al. · 2010 [cited by applicant]
US 20120014366A1 · Kim et al. · 2012 [cited by applicant]
US 20120147805A1 · Kim · 2012 [cited by examiner]
US 20160013918A1 · Zhang et al. · 2016 [cited by applicant]
US 20160205542A1 · Yavuz · 2016 [cited by examiner]
US 20170164238A1 · Paredes Cabrera · 2017 [cited by examiner]
US 20170318606A1 · Lee et al. · 2017 [cited by applicant]
US 20170373739A1 · Guo et al. · 2017 [cited by applicant]
US 20180035416A1 · Yi et al. · 2018 [cited by applicant]
US 20190132896A1 · Kusashima et al. · 2019 [cited by applicant]
EP 2966790A1 · 2016 [cited by applicant]
JP 2004533792A · 2004 [cited by applicant]
JP 200789107A · 2007 [cited by applicant]
JP 2017200185A · 2017 [cited by applicant]
JP 201826705A · 2018 [cited by applicant]
WO 2017195463A1 · 2017 [cited by applicant]
WO 2018049113A1 · 2018 [cited by applicant]
3GPP TS 36.211 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation (Release 15)”, Dec. … [cited by applicant]
3GPP TS 36.212 V15.0.1, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding (Release 15)”, Jan. 2… [cited by applicant]
3GPP TS 36.213 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 36.300 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network… [cited by applicant]
3GPP TS 36.321 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (R… [cited by applicant]
3GPP TS 36.322 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification (Rele… [cited by applicant]
3GPP TS 36.323 V14.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification… [cited by applicant]
3GPP TS 36.331 V15.0.1, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification … [cited by applicant]
3GPP TS 36.413 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 15)”… [cited by applicant]
3GPP TS 36.423 V15.0.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 15), … [cited by applicant]
3GPP TS 36.425 V14.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 interface user plane protocol (Release 14… [cited by applicant]
3GPP TS 37.340 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 15)”, Dec… [cited by applicant]
3GPP TS 38.201 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer; General description (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.202 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Services provided by the physical layer (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.211 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.212 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.213 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.214 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.215 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer measurements (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.300 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.321 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.322 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Link Control (RLC) protocol specification (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.323 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.331 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network NR Radio Resource Control (RRC) protocol specification (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.401 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TS 38.410 V0.6.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG general aspect and principles (Release 15)”, Dec. 2017, clean version, with cover sheet and list… [cited by applicant]
3GPP TS 38.410 V0.6.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG general aspect and principles (Release 15)”, Dec. 2017, marked up version. [cited by applicant]
3GPP TS 38.413 V0.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP) (Release 15)”, Dec. 2017, clean version, w… [cited by applicant]
3GPP TS 38.413 V0.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP) (Release 15)”, Dec. 2017, marked up versio… [cited by applicant]
3GPP TS 38.420 V0.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn general aspects and principles (Release 15)”, Dec. 2017, clean version, with cover sheet. [cited by applicant]
3GPP TS 38.420 V0.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn general aspects and principles (Release 15)”, Dec. 2017, marked up version. [cited by applicant]
3GPP TS 38.423 V0.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); Xn application protocol (XnAP) (Release 15)”, Dec. 2017, clean version, w… [cited by applicant]
3GPP TS 38.423 V0.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); Xn application protocol (XnAP) (Release 15)”, Dec. 2017, marked up versio… [cited by applicant]
3GPP TS 38.470 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 general aspects and principles (Release 15)”, Jan. 2018. [cited by applicant]
3GPP TS 38.473 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15)”, Dec. 2017. [cited by applicant]
3GPP TR 38.801 V14.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on new radio access technology: Radio access architecture and interfaces (Release 14)”, Mar. 2017. [cited by applicant]
3GPP TR 38.802 V14.2.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology Physical Layer Aspects (Release 14)”, Sep. 2017. [cited by applicant]
3GPP TR 38.803 V14.2.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on new radio access technology: Radio Frequency (RF) and co-existence aspects (Release 14)”, Sep. 20… [cited by applicant]
3GPP TR 38.804 V14.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology; Radio Interface Protocol Aspects (Release 14)”, Mar. 2017. [cited by applicant]
3GPP TR 38.900 V14.3.1, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on channel model for frequency spectrum above 6 GHz (Release 14)”, Jul. 2017. [cited by applicant]
3GPP TR 38.912 V14.1.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio (NR) access technology (Release 14)”, Jun. 2017. [cited by applicant]
3GPP TR 38.913 V14.3.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Scenarios and Requirements for Next Generation Access Technologies; (Release 14)”, Jun. 2017. [cited by applicant]
NTT Docomo, “New SID Proposal: Study on New Radio Access Technology”, Agenda Item: 9.1, 3GPP TSG-RAN Meeting #71, RP-160671, Göteborg, Sweden, Mar. 7-10, 2016. [cited by applicant]
NTT Docomo, Inc., “On co-existence of eMBB and URLLC”, Agenda Item: 8.1.8, 3GPP TSG-RAN WG1 Meeting #86, R1-167391, Gothenburg, Sweden, Aug. 22-26, 2016. [cited by applicant]
3GPP TS 36.214 V15.2.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements (Release 15)”, Jun. 2018. [cited by applicant]
3GPP TS 37.324 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification (Release 15)”, Jun. 2018. [cited by applicant]
Samsung, “MAC PDU structure in NR”, Agenda Item: 10.3.1.3, 3GPP TSG-RAN WG2 Meeting #97bis, R2-1703574, resubmission of R2-1701904, Spokane, USA, Apr. 3-7, 2017. [cited by applicant]
CATT, “NR MAC PDU format”, Agenda Item: 10.3.1.3, 3GPP TSG-RAN WG2 Meeting #97bis, R2-1703118, Spokane, USA, Apr. 3-7, 2017. [cited by applicant]
ITRI,“Non-Real-Time Segmentation and Concatenation for NR”, Agenda Item: 9.2.1.3, 3GPP TSG-RAN WG2 Meeting #95bis, R2-166483, Kaohsiung, Taiwan, Oct. 10-14, 2016. [cited by applicant]
International Search Report with Written Opinion of the International Searching Authority issued by the Japan Patent Office for corresponding International Patent Application No. PCT/JP2018/014339, mailed on May 15, 201… [cited by applicant]
Non-Final Office Action issued for corresponding U.S. Appl. No. 16/260,672 on May 6, 2019 by the United States Patent & Trademark Office, electronically delivered on May 6, 2019 on May 21, 2019 by the USPTO. [cited by applicant]
Notice of Allowance issued for corresponding U.S. Appl. No. 16/260,672 on Jun. 21, 2019 by the United States Patent & Trademark Office, electronically delivered on Jun. 21, 2019 by the USPTO. [cited by applicant]
First Notification of Office Action issued by China National Intellectual Property Administration for corresponding Chinese Application No. 201880080808.1, dated Sep. 2, 2020, with a full machine English translation. [cited by applicant]
Nokia et al., “MAC sub-header formats”, Agenda item: 10.3.1.3., 3GPP TSG-RAN WG2 #99, R2-1708763, Berlin, Germany, Aug. 21-25, 2017. [cited by applicant]
Interdigital Inc., “Summary of [99b#40] [NR UP/MAC] LCP”, Agenda item: 10.3.1.7., 3GPP TSG-RAN WG2 #100, R2-1712786, Reno, USA, Nov. 27-Dec. 1, 2017. [cited by applicant]
Notice of Reasons for Refusal issued by the Japan Patent Office for corresponding Japanese Patent Application No. 2020-512142, mailed on Nov. 24, 2020, with a full English translation. [cited by applicant]
OPPO, “LCP considering multiple numerologies”, Agenda Item: 10.3.1.6, 3GPP TSG-RAN WG2 Meeting #98, R2-1704053, Hangzhou, China, May 15-19, 2017. [cited by applicant]
Samsung, “NR MAC header fields”, Agenda Item: 10.3.1.3, 3GPP TSG-RAN WG2 Meeting #98, R2-1705680, Hangzhou, China, May 15-19, 2017. [cited by applicant]
Second Notification of Office Action issued by the China National Intellectual Property Administration for corresponding Chinese Patent Application No. 201880080808.1, dated Jan. 29, 2021, with an English translation. [cited by applicant]
Extended European search report with supplementary European search report and the European search opinion issued by the European Patent Office for corresponding European Patent Application No. EP 18 91 3294.7-1212, mail… [cited by applicant]
Fujitsu, “MAC header shortening”, Agenda Item: 10.3.1.11 (Impact of PDCP duplication on MAC), 3GPP TSG-RAN WG2 Meeting #101, R2-1802548, Athens, Greece, Feb. 26-Mar. 2, 2018. [cited by applicant]
Fujitsu, “RLC header shortening”, Agenda Item: 10.3.2.3 (Impact of PDCP duplication to Rlc), 3GPP TSG-RAN WG2 Meeting #101, R2-1802549, Athens, Greece, Feb. 26-Mar. 2, 2018. [cited by applicant]
Non-Final Office Action issued for corresponding U.S. Appl. No. 16/460,379 by the United States Patent & Trademark Office, electronically delivered on Oct. 2, 2020. [cited by applicant]
Notices of Allowance issued for corresponding U.S. Appl. No. 16/460,379 by the United States Patent & Trademark Office, electronically delivered on Dec. 30, 2020 and on Feb. 26, 2021. [cited by applicant]
Notice of Reasons for Refusal issued by the Japan Patent office for corresponding Japanese Patent Application No. 2020-512142, mailed on Apr. 13, 2021, with an English translation. [cited by applicant]
Examination Report issued by the Patent Office of India for corresponding Indian Patent Application No. 202037041391, dated Sep. 22, 2021, with an English translation. [cited by applicant]
Non-Final Office Action issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/231,149, electronically delivered on Feb. 1, 2022. [cited by applicant]
Final Office Action issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/231,149, electronically delivered on Sep. 22, 2022. [cited by applicant]
Extended European search report with the European search opinion issued by the European Patent Office for corresponding European Patent Application No. 22177875.6-1216, dated Oct. 17, 2022. [cited by applicant]
Notice of Preliminary Rejection issued by the Korean Intellectual Property Office for corresponding Korean Patent Application No. 10-2022-7033612, mailed on Nov. 16, 2022, with an English translation. [cited by applicant]
Non-Final Office Action issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/231,149, electronically delivered on Apr. 5, 2023. [cited by applicant]
First Notification of Office Action issued by the China National Intellectual Property Administration for corresponding Chinese Patent Application No. 202111170080.1, issued on Apr. 28, 2023, with an English translation. [cited by applicant]
Final Office Action issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/231,149, electronically delivered on Sep. 22, 2023. [cited by applicant]
Non-Final Office Action issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/231,149, electronically delivered on Mar. 29, 2024. [cited by applicant]
Notice of Reasons for Refusal issued by the Japan Patent Office for corresponding Japanese Patent Application No. 2023-017181, mailed on May 21, 2024, with an English translation. [cited by applicant]
Ericsson, “Msg3 size for CCCH payload”, Agenda Item: 10.3.1.4.3, 3GPP TSG-RAN WG2 #101, Tdoc R2-1803202, Athens, Greece, Feb. 26-Mar. 2, 2018. [cited by applicant]
Interdigital Communications, “LCP and Scheduling Aspects for Multiple Numerologies”, Agenda Item: 3.2.1.2, 3GPP TSG-RAN WG2 NR Ad Hoc, R2-1700236, Spokane, Washington, Jan. 17-19, 2017. [cited by applicant]
Final Office Action issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/231,149, electronically delivered on Sep. 5, 2024. [cited by applicant]
Advisory Action Before the Filing of an Appeal Brief issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/231,149, electronically delivered on Dec. 17, 2024. [cited by applicant]