IP Library › Granted Patent US 12,432,709
Granted Patent B2
US 12,432,709 · App. 18/661,150 · Granted Sep 30, 2025

Efficient multiplexing of control information in transport block

Inventors: Joachim Loehr (Hessen, DE); Prateek Basu Mallick (Hessen, DE); Rikin Shah (Hessen, DE); Hidetoshi Suzuki (Kanagawa, JP); Takako Hori (Kanagawa, JP)
Assignee: Panasonic Intellectual Property Corporation of America
H04W72/0466H04L1/0078H04W8/02H04L1/1664H04L27/345H04W80/02H04W88/16
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,432,709
App. No.
18/661,150
Granted
Sep 30, 2025
Kind
B2
Abstract

Provided are systems and methods for transmitting data over a wireless channel from a data transmitting node to a data receiving node in a communication system. The data transmitting node comprises second-layer processing circuitry for receiving at least one second-layer SDU, to be mapped onto a resource allocated for data transmission, and for generating a second-layer PDU, including the at least one second-layer SDU and at least one second-layer control element, and first-layer processing circuitry for receiving the second-layer PDU generated by the second-layer processing circuitry and for mapping the second-layer PDU onto the resource allocated for data transmission. The data receiving node comprises first-layer processing circuitry for de-mapping at least one second-layer PDU, and second layer processing circuitry for receiving and parsing the second-layer PDU demapped by the first-layer processing circuitry, the second-layer PDU including at least one second-layer SDU, and at least one second-layer control element.

Claims (44)

1. A communication entity, comprising:

a receiver, which, in operation, receives a first-type second-layer protocol data unit (PDU) mapped onto a resource allocated for data reception, wherein the first-type second-layer PDU includes at least one second-layer service data unit (SDU) and at least one second-layer control element, which is placed after any of the at least one second-layer SDU; and

a transmitter, which, in operation, transmits at least one second-type second-layer PDU mapped onto a resource allocated for data transmission, wherein the second-type second-layer PDU includes at least one second-layer SDU and at least one second-layer control element, which precedes any of the at least one second-layer SDU;

wherein the first-type second-layer PDU and the second-type second-layer PDU are generated dependent on a type of second-layer control element to be included in the first-type second-layer PDU or the second-type second-layer PDU, and

wherein the type of second-layer control element to be included in the first-type second-layer PDU includes at least a power headroom report and the type of second-layer control element to be included in the second-type second-layer PDU includes at least one of activation/deactivation commands or a contention resolution message.

2. The communication entity according to claim 1 , wherein

the first-type or second-type second-layer PDU further includes:

a second-layer subheader associated with the at least one second-layer SDU, or

a second-layer subheader associated with the at least one second-layer control element.

3. The communication entity according to claim 2 , wherein

the at least one second-layer SDU is placed after the associated second-layer subheader and the at least one second-layer control element is placed before the associated second-layer subheader.

4. The communication entity according to claim 3 , wherein

the second-layer subheader includes a presence indicator indicating whether the first-type or second-type second-layer PDU includes at least one second-layer control element.

5. The communication entity according to claim 2 , wherein

the second-layer subheader associated with the at least one second-layer control element precedes the second-layer SDU and the second-layer subheader associated with the second-layer SDU.

6. The communication entity according to claim 1 , wherein

the first-type or second-type second-layer PDU includes a padding buffer status report (BSR) and a second-layer subheader associated with the padding BSR, and

the padding BSR and the second-layer subheader associated with the padding BSR are placed after any of the at least one second-layer SDU.

7. The communication entity according to claim 1 , wherein

the first-type second-layer PDU includes an uplink second-layer control element, and

the second-type second-layer PDU includes a downlink second-layer control element.

8. The communication entity according to claim 1 , wherein

the communication entity is a base station.

9. A method comprising:

receiving a first-type second-layer protocol data unit (PDU) mapped onto a resource allocated for data reception, wherein the first-type second-layer PDU includes at least one second-layer service data unit (SDU) and at least one second-layer control element, which is placed after any of the at least one second-layer SDU; and

transmitting at least one second-type second-layer PDU mapped onto a resource allocated for data transmission, wherein the second-type second-layer PDU includes at least one second-layer SDU and at least one second-layer control element, which precedes any of the at least one second-layer SDU;

wherein the first-type second-layer PDU and the second-type second-layer PDU are generated dependent on a type of second-layer control element to be included in the first-type second-layer PDU or the second-type second-layer PDU, and

wherein the type of second-layer control element to be included in the first-type second-layer PDU includes at least a power headroom report and the type of second-layer control element to be included in the second-type second-layer PDU includes at least one of activation/deactivation commands or a contention resolution message.

10. The method according to claim 9 , wherein

the first-type or second-type second-layer PDU further includes:

a second-layer subheader associated with the at least one second-layer SDU, or

a second-layer subheader associated with the at least one second-layer control element.

11. The method according to claim 10 , wherein

the at least one second-layer SDU is placed after the associated second-layer subheader and the at least one second-layer control element is placed before the associated second-layer subheader.

12. The method according to claim 11 , wherein

the second-layer subheader includes a presence indicator indicating whether the first-type or second-type second-layer PDU includes at least one second-layer control element.

13. The method according to claim 10 , wherein

the second-layer subheader associated with the at least one second-layer control element precedes the second-layer SDU and the second-layer subheader associated with the second-layer SDU.

14. The method according to claim 9 , wherein

the first-type or second-type second-layer PDU includes a padding buffer status report (BSR) and a second-layer subheader associated with the padding BSR, and

the padding BSR and the second-layer subheader associated with the padding BSR are placed after any of the at least one second-layer SDU.

15. The method according to claim 9 , wherein

the first-type second-layer PDU includes an uplink second-layer control element, and

the second-type second-layer PDU includes a downlink second-layer control element.

Priority Claims (1)
EP 16197412 · Nov 4, 2016 · regional
Continuity (5)
Continuation 17970207 · Oct 20, 2022
Continuation 17123599 · Dec 16, 2020
Continuation 16366234 · Mar 27, 2019
Continuation PCTJP2017031306 · Aug 31, 2017
Related Publication 20240298311A1 · Sep 5, 2024
References Cited (78)
US 7454554B1 · Norrie et al. · 2008 [cited by applicant]
US 7978640B2 · Lee et al. · 2011 [cited by applicant]
US 10749641B2 · Gholmieh et al. · 2020 [cited by applicant]
US 20050172199A1 · Miller et al. · 2005 [cited by applicant]
US 20060072494A1 · Matusz · 2006 [cited by applicant]
US 20060165045A1 · Kim et al. · 2006 [cited by applicant]
US 20060251027A1 · Chun et al. · 2006 [cited by applicant]
US 20090141670A1 · Duncan Ho · 2009 [cited by applicant]
US 20090163211A1 · Kitazoe et al. · 2009 [cited by applicant]
US 20090238124A1 · Pragada et al. · 2009 [cited by applicant]
US 20090310533A1 · Zheng et al. · 2009 [cited by applicant]
US 20100014468A1 · Lee et al. · 2010 [cited by applicant]
US 20100028911A1 · Tjioe · 2010 [cited by applicant]
US 20100111016A1 · Lee et al. · 2010 [cited by applicant]
US 20100128672A1 · Harada et al. · 2010 [cited by applicant]
US 20100157904A1 · Ho et al. · 2010 [cited by applicant]
US 20100172376A1 · Chun et al. · 2010 [cited by applicant]
US 20110019604A1 · Chun et al. · 2011 [cited by applicant]
US 20110096725A1 · Chun et al. · 2011 [cited by applicant]
US 20110149840A1 · Harada et al. · 2011 [cited by applicant]
US 20120083309A1 · Kwon et al. · 2012 [cited by applicant]
US 20130044698A1 · Susitaival et al. · 2013 [cited by applicant]
US 20130051334A1 · Sammour et al. · 2013 [cited by applicant]
US 20130250973A1 · Agiwal et al. · 2013 [cited by applicant]
US 20140050230A1 · Bao et al. · 2014 [cited by applicant]
US 20140140276A1 · Cave et al. · 2014 [cited by applicant]
US 20150085749A1 · Eravelli et al. · 2015 [cited by applicant]
US 20150156764A1 · Yang et al. · 2015 [cited by applicant]
US 20150341865A1 · Yang et al. · 2015 [cited by applicant]
US 20150382312A1 · Kim et al. · 2015 [cited by applicant]
US 20160302104A1 · Bharadwaj et al. · 2016 [cited by applicant]
US 20170013634A1 · Tsuboi et al. · 2017 [cited by applicant]
US 20180054814A1 · Zhang et al. · 2018 [cited by applicant]
US 20180124767A1 · Shaheen · 2018 [cited by applicant]
US 20180124843A1 · Shaheen · 2018 [cited by applicant]
US 20180176344A1 · Yang et al. · 2018 [cited by applicant]
US 20180183560A1 · He et al. · 2018 [cited by applicant]
US 20190215727A1 · Turtinen et al. · 2019 [cited by applicant]
US 20190223256A1 · Lin et al. · 2019 [cited by applicant]
US 20190230736A1 · Quan et al. · 2019 [cited by applicant]
US 20190260856A1 · Jiang · 2019 [cited by applicant]
US 20190306871A1 · Liu et al. · 2019 [cited by applicant]
US 20190364605A1 · Loehr et al. · 2019 [cited by applicant]
CN 101578895A · 2009 [cited by applicant]
CN 101953095A · 2011 [cited by applicant]
WO 2008127034A1 · 2008 [cited by applicant]
WO 2009104928A1 · 2009 [cited by applicant]
WO 2011012040A1 · 2011 [cited by applicant]
WO 2015141824A1 · 2015 [cited by applicant]
WO 2016010258A1 · 2016 [cited by applicant]
WO 2018068704A1 · 2018 [cited by applicant]
3GPP TS 36.212 V13.0.0 Release 13, “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding,” Jan. 2016. [cited by applicant]
3GPP TS 36.213 V13.0.0 Release 13, “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures,” May 2016. [cited by applicant]
3GPP TS 36.321 V13.3.0 Release 13, “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification,” Oct. 2016. [cited by applicant]
3GPP TS 36.322 V13.2.0 Release 13, “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification,” Aug. 2016. [cited by applicant]
3GPP TSG-RAN WG2 #66bis, R2-093800, “Dynamic Scheduling Information in LTE MBMS,” Jun. 2009. [cited by applicant]
3GPP TSG-RAN WG2 Meeting #96, R2-167796, “MAC PDU Structure for NR,” Nov. 2016. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 12),” 3GPP … [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 13),” 3GPP … [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 14),” 3GPP … [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 8),” 3GPP TS 36.211 V8.9.0, D… [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification (Release 13),” 3GPP TS … [cited by applicant]
Chinese Office Action dated Jun. 29, 2021 for the related Chinese Patent Application No. 201780051288.7. (with English translation). [cited by applicant]
Ericsson, “Placement of RLC/MAC headers,” Tdoc R2-166824, Agenda Item: 9.2.1.1, 3GPP TSG-RAN WG2 Meeting #95bis, Kaohsiung, Taiwan, Oct. 10-14, 2016, 7 pages. [cited by applicant]
Ericsson, “Report from [95#26] Concatenation (Ericsson),” Tdoc: R2-166904, Agenda Item: 9.2.1.1, 3GPP TSG-RAN WG2 #95bis, Kaohsiung, Taiwan, Oct. 10-14, 2016, 38 pages. [cited by applicant]
International Search Report of PCT application No. PCT/JP2017/031306, dated Nov. 28, 2017. [cited by applicant]
NTT DoCoMo, “MAC PDU structure for LTE,” R2-072015, Agenda Item: 4.13, 3GPP TSG RAN WG2 Meeting #58, May 7-11, 2007, Kobe, Japan, 5 pages. [cited by applicant]
NTT DoCoMo, Inc., NEC, “MAC PDU structure for LTE,” R2-073560, Agenda Item: 5.2.1, 3GPP TSG RAN WG2 Meeting #59, Aug. 20-24, 2007, Athens, Greece, 4 pages. [cited by applicant]
NTT DoCoMo, Inc., NEC, “MAC PDU structure for LTE,” R2-074174, Agenda Item: 5.1.1.2, 3GPP TSG RAN WG2 Meeting #59bis, Oct. 8-12, 2007, Shanghai, China, 5 pages. [cited by applicant]
Panasonic, “MAC PDU format for LTE,” R2-070096, Agenda Item: 5.9, 3GPP TSG RAN WG2 Meeting #56bis, Jan. 15-19, 2007, Sorrento, Italy, 3 pages. [cited by applicant]
Panasonic, “MAC PDU format for LTE,” R2-070541, Agenda Item: 11.8, 3GPP TSG RAN WG2 Meeting #57, Feb. 12-16, 2007, St. Louis, USA, 3 pages. [cited by applicant]
Panasonic, “MAC PDU format for LTE,” R2-071150, Agenda Item: 5.14, 3GPP TSG RAN WG2 Meeting #57bis, Mar. 26-30, 2007, St Julian's, Malta, 3 pages. [cited by applicant]
Panasonic, “MAC PDU format for LTE,” R2-071781, Agenda Item: 4.13, 3GPP TSG RAN WG2 Meeting #58, May 7-11, 2007, Kobe, Japan, 3 pages. [cited by applicant]
Panasonic, “MAC PDU format for LTE,” R2-072652, Agenda Item: 5.2.1, 3GPP TSG RAN WG2 Meeting #58bis, Jun. 25-29, 2007, Orlando, USA, 3 pages. [cited by applicant]
Panasonic, “MAC PDU format for LTE,” R2-073273, Agenda Item: 5.2.1, 3GPP TSG RAN WG2 Meeting #59, Aug. 20-24, 2007, Athens, Greece, 2 pages. [cited by applicant]
Panasonic, “Open issues on MAC PDU format,” R2-074148, Agenda Item: 5.1.1.2, 3GPP TSG RAN WG2 Meeting #59bis, Oct. 8-12, 2007, Shanghai, China, 2 pages. [cited by applicant]
R2-167190—Way forward on concatenation discussion, “Way forward for concatenation discussion,” Oct. 1, 2016. [cited by applicant]
Russian Search Report dated Sep. 11, 2020 for the corresponding Russian Patent Application No. 2019105130, 2 pages. [cited by applicant]