A method of wireless communication in a user device, a device for wireless communication, and computer-readable memory.

Abstract

Several aspects described in this case relate to encoding or decoding a media access control (MAC) layer transport block that has an enhanced MAC header format, a split and partial MAC header, and a MAC transport block layout. A method, a computer-readable medium, and an apparatus are provided. The techniques described in this case can be applied to different communication technologies, including 5th generation (5G) wireless communication technology or new radio (NR).

Description

1 / 64 “METHOD OF WIRELESS COMMUNICATIONS IN A USER DEVICE, APPARATUS FOR WIRELESS COMMUNICATION, AND COMPUTER-READABLE MEMORY” Reference to related requests

[0001] This application claims the benefit of provisional patent application U.S. No. 62 / 407,435, entitled “SPLIT AND PARTIAL MEDIUM ACCESS CONTROL (MAC) HEADERS” filed October 12, 2016; provisional patent application U.S. No. 62 / 406,864, entitled “ENHANCED MAC HEADER FORMAT” filed October 11, 2016; provisional patent application U.S. No. 62 / 436,851, entitled “MEDIA ACCESS CONTROL TRANSPORT BLOCK DESIGN” filed December 20, 2016; and provisional patent application U.S. No. 15 / 703,582, entitled “MEDIA ACCESS CONTROL HEADER AND TRANSPORT BLOCK FORMATS” and filed on September 13, 2017, each of which is expressly included by reference herein in its entirety. BACKGROUND

[0002] Aspects of the present invention relate generally to wireless communications, and more particularly to techniques for generating and / or shaping a medium access control (MAC) layer of a packet data unit (PDU) for communication in a wireless communications system (e.g., 5G or New Radio (NR)).

[0003] Wireless communication systems are widely developed to provide various telecommunications services such as telephony, video, data, messaging, and broadcasting. Typical systems of Petition 870260066479, dated 06 / 07 / 2026, page 6 / 135 2 / 64 Wireless communications can employ multiple access technologies capable of supporting communications with multiple users by sharing available system resources (e.g., time, frequency, power, and / or spectrum). Examples of such multiple access technologies include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and time division synchronous code division multiple access (TD-SCDMA).

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables many different wireless devices to communicate at a municipal, national, regional, and even global level. An example of a telecommunications standard is Long Term Evolution (LTE) or LTE Advanced (LTE-A). However, although newer multiple access systems, such as an LTE or LTE-A system, offer faster data processing than older technologies, these speeds or rates have increased the demand for higher bandwidth content, such as high-resolution graphics and video, for use in or with mobile devices. As such, the demand for bandwidth, higher data rates, better transmission quality, as well as better spectrum utilization and lower latency in wireless communication systems continues to increase. Petition 870260066479, dated 06 / 07 / 2026, page 7 / 135 3 / 64

[0005] New communications technology Fifth-generation (5G) radio (NR), used across a wide range of spectrums, is expected to expand and support diverse use cases and applications compared to current generations of mobile networks. In one aspect, 5G NR communication technology includes, for example: Optimized Mobile Broadband (eMBB) addressing user-centric use cases for accessing multimedia content, services, and data; ultra-reliable low-latency communications (URLLC) with stringent requirements, especially in terms of latency and reliability; and mass machine-to-machine (mMTC) communications for a very large number of connected devices, typically transmitting a relatively low volume of delay-insensitive information. As defined in 3GPP TR 38.913, “Study on In scenarios and requirements for Next Generation Access Technologies, the target data rate can be up to 20Gbps for downlink (DL) and / or 10Gbps for uplink (UL), and the target for user plane latency for some service types (e.g., eMBB) can be 4ms for UL / DL. With the increased data rate requirements in UL (10 Gbps) and DL (20 Gbps) and the reduced latency requirements of 4ms or less for UL and DL, it becomes more important to move most of the processing, e.g., millions of instructions per second (MIPS) intensive activities, closer to hardware (HW) acceleration.

[0006] For this reason, due to the requirements for higher data rates and reduced latency, new approaches may be desirable to improve the system layout in order to meet consumer demand and Petition 870260066479, dated 06 / 07 / 2026, page 8 / 135 4 / 64 to enhance the user experience in wireless communications. SUMMARY

[0007] What follows presents a simplified summary of one or more aspects for the purpose of providing a basic understanding of such aspects. This summary does not constitute a comprehensive overview of all aspects considered, and does not intend to identify key or most important elements of all aspects, nor to delineate the scope of any or all aspects. Its purpose is to present some concepts of one or more aspects in a simplified way, as a prelude to the more detailed description presented later in this case.

[0008] According to an example, a method of wireless communication is provided in a user equipment (UE). The method may include splitting a medium access control (MAC) header into a first part and a second part. The method may further include sending, from the UE to a network entity on an uplink communication channel, the first portion of the MAC header at a first time and the second portion of the MAC header at a second time after the first time.

[0009] According to another example, a method of wireless communications is provided on a network entity. The method may include receiving, from a UE on an uplink communication channel, at least one of a first portion of a first MAC header at a first time or a second portion of the first MAC header at a second time after the first. Petition 870260066479, dated 06 / 07 / 2026, page 9 / 135 5 / 64 time. The method may also include transmitting an ACK that includes at least one control portion or a data portion to the UE in response to receiving at least one of the first portion of the first MAC header or the second portion of the MAC header. The method may also include determining the transmission of one or more MAC control elements on a downlink communication channel to the UE. Furthermore, the method may include splitting a second MAC header into a first portion and a second portion. The method also includes sending, from the network to the UE on a downlink communication channel, the first portion of the second MAC header at a first time and the second portion of the second MAC header at a second time after the first time.

[0010] According to another example, a method is provided for forming and transmitting the transport block. The method may include generating a transport block comprising a plurality of service data units allocated to a plurality of logical channels; the transport block further comprises a general medium access control header, the general medium access control header indicating a logical channel of the plurality of channels for each of the plurality of service data units. The method may further include transmitting the transport block to a device.

[0011] According to another example, a method is provided for forming and transmitting a transport block. The method may include generating a transport block comprising a plurality of units of Petition 870260066479, dated 06 / 07 / 2026, page 10 / 135 6 / 64 service data and a corresponding plurality of medium access control subheaders, with each medium access control subheader adjacent to a corresponding service data unit in the transport block, and the transport block further comprises a MAC control element that has a corresponding separate support access control subheader, the MAC control element and the corresponding support access control subheader located at one end of the transport block. The method may also include transmission of the transport block to a device.

[0012] According to another example, a method is provided relating to improvements in a MAC header used in a wireless communications system. The method includes the identification, by a processor, of pending information received on one or more logical channels in a MAC layer; the pending information includes data and / or control information to be included in a MAC transport block. The method also includes the determination, by the processor, of a size requirement corresponding to the amount of space that will be absorbed by the pending information and the corresponding MAC subheader information in the transport block. Furthermore, the method includes the processor determining the remaining space available in the transport block. When the remaining space in the transport block is greater than the size requirement, the method includes initiating the encoding of the pending information in the transport block. In addition Petition 870260066479, dated 06 / 07 / 2026, page 11 / 135 7 / 64 of this, when the remaining space in the transport block is less than or equal to the size requirement, the method includes determining a MAC header size based, at least in part, on a stored subheader information size corresponding to the previous information already encoded in the MAC transport block, initiating the encoding of at least the stored subheader information and a MAC header size indication representing the MAC header size in the MAC transport block so that the stored subheader information and the MAC header size indication are encoded and positioned within the subsequent MAC transport block to at least the previous information; and initiating the transmission of the MAC transport block.

[0013] According to another aspect, a wireless communication device is provided that includes a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute the instructions to perform the operations of the methods described in this case.

[0014] According to another aspect, a wireless communication device is provided which includes means for performing the operations of the methods described in the present case.

[0015] In yet another respect, a computer-readable medium is provided, which includes executable code for one or more processors to perform the operations of the methods. Petition 870260066479, dated 06 / 07 / 2026, page 12 / 135 8 / 64 described in this case.

[0016] For the purposes set forth and related above, one or more aspects comprise the features described below in full and highlighted in particular in the claims. The following description and the accompanying drawings present in detail certain illustrative features of one or more aspects. These features are indicative, however, only of some of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to facilitate a more complete understanding of the aspects described in this case, reference is now made to the attached drawings, in which similar elements are referenced with the same numbers. These drawings should not be considered as limiting the present exposition, but are intended to be merely illustrative.

[0018] Figure 1 is a block diagram illustrating an example of a communications network that includes at least one network entity communicating with a user equipment (UE) configured to encode or decode a medium access control (MAC) layer packet data unit (PDU), also referred to as a MAC transport block (TB), which is endowed with an enhanced MAC header format in accordance with one or more of the aspects presently described. Petition 870260066479, dated 06 / 07 / 2026, page 13 / 135 9 / 64

[0019] Figure 2 is a block diagram of an example of a MAC transport block that is provided with an example of an improved header format in accordance with one or more of the aspects described herein.

[0020] Figure 3 is a block diagram of an example of a MAC transport block.

[0021] Figure 4 is a block diagram of an example of additional MAC transport blocks, each of which has a different example of an enhanced header format in accordance with one or more of the aspects described herein.

[0022] Figure 5 is a block diagram of another example of MAC transport blocks, each of which has a different example of an enhanced header format in accordance with one or more of the aspects described herein.

[0023] Figure 6 is a block diagram of another example of MAC transport blocks, each of which has a different example of an enhanced header format in accordance with one or more of the aspects described herein.

[0024] Figure 7 is an example schematic diagram of the architecture and data flow associated with the operation of the encoder / decoder manager in an example construction of a MAC transport block (TB) that is endowed with an enhanced MAC header format in accordance with one or more of the aspects presently described.

[0025] Figure 8 is a block diagram of an example of a transport block according to one or more of the aspects described herein. Petition 870260066479, dated 06 / 07 / 2026, page 14 / 135 10 / 64

[0026] Figures 9A and 9B are block diagrams of examples of transport blocks according to one or more of the aspects described herein.

[0027] Figures 10A and 10B are block diagrams of examples of transport blocks according to one or more of the aspects described herein.

[0028] Figure 11 is a block diagram of an example of a transport block according to one or more of the aspects described herein.

[0029] Figure 12 is a flowchart of an exemplary method of wireless communications, including the construction, in a MAC layer, of a MAC transport block (TB) that is endowed with an enhanced MAC header format in accordance with one or more of the aspects presently described.

[0030] Figure 13 is a flowchart of an exemplary method of wireless communications in a user equipment (UE) that includes splitting and sending a MAC header according to one or more of the aspects described herein.

[0031] Figure 14 is a flowchart of an exemplary method of wireless communications in a network entity that includes splitting and sending a MAC header according to one or more of the aspects described herein.

[0032] Figure 15 is a flowchart of a first exemplary method of wireless communications that includes the generation and transmission of transport blocks according to one or more of the aspects described herein.

[0033] Figure 16 is a flowchart of a Petition 870260066479, dated 06 / 07 / 2026, page 15 / 135 11 / 64 second exemplary method of wireless communications which includes the generation and transmission of transport blocks in accordance with one or more of the aspects described herein. Detailed Description

[0034] The detailed description set forth below in connection with the accompanying drawings is understood to be a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be put into practice. The detailed description includes specific details for the purpose of providing a full understanding of the various concepts. Nevertheless, it will be evident to a person skilled in the art that these concepts may be put into practice without these specific details. In some cases, widely known components are illustrated in block diagram form in order to avoid obscuring such concepts. Similarly, as used herein, the term “component” may be one of the parts that constitute a system, may be hardware, firmware, and / or software, and may be divided into other components.

[0035] This disclosure includes various aspects for encoding and / or decoding a MAC transport block (TB) that has an enhanced MAC header format, such as in a wireless communications system (e.g., 5G or NR). A MAC TB may also be referred to as a MAC packet data unit (PDU). In particular, in the encoding aspect, this disclosure includes an apparatus and method that operates at the MAC layer to begin recording or Petition 870260066479, dated 06 / 07 / 2026, p. 16 / 135 12 / 64 provides the Service Data Unit (SDU) MAC and / or Control Elements (CEs) to the encoder as a MAC layer, analyzes them, and separately calculates and stores the associated MAC subheader information. The associated MAC subheader information can subsequently be encoded in the MAC transport block as the MAC header, for example, when the MAC transport block would be substantially filled considering the size of the stored associated MAC subheader information and the size of the corresponding MAC SDUs / CEs already encoded in the MAC transport block. Furthermore, the present apparatus and methods include encoding a MAC header size indicator at the end of the MAC transport block.The MAC header size indicator provides a receiving device with an indication of a MAC Header Size, thereby allowing the receiving device to identify where the MAC header can be found within the MAC transport block.

[0036] For example, in the encoding aspect, the present apparatus and methods enable the MAC layer to continue encoding MAC SDUs / CEs in the MAC transport block while performing the computation of the associated MAC subheaders. For example, each respective MAC SDU / CE can be encoded from the MAC transport block as long as the respective MAC SDU / CE, in addition to the corresponding computed MAC subheader information, fits into a remaining space in the MAC transport block. At a point where no more MAC SDUs / CEs (and their associated MAC subheader information) can fit in the remaining space, the apparatus and methods Petition 870260066479, dated 06 / 07 / 2026, p. 17 / 135 The exposed 13 / 64 device can then subsequently encode the associated MAC subheader information for all MAC SDUs / CEs already recorded at the end of the MAC transport block. Additionally, the exposed device and methods can determine and encode a MAC header size indicator at the end. Therefore, for example, the present device and methods can result in improved (e.g., reduced) encoding time and processing time requirements, for instance, by initiating the encoding of MAC SDUs / CEs in the MAC transport block as soon as they are all received and read (recorded).

[0037] The apparatus and methods disclosed may solve one or more problems in previous techniques with respect to meeting the demands for higher data throughput and lower expected latency for 5G or NR communications. For example, the present disclosure may improve (e.g., reduce) the amount of processing, e.g., measured in millions of instructions per second (MIPS), of the processor, as well as bring the encoder logic closer to that of a hardware accelerator (e.g., a specialized encoder / decoder). For example, previous techniques calculate all MAC subheaders in advance and write the MAC header (including all respective MAC subheaders) at the beginning of the MAC transport block, which is not ideal from an encoding perspective, since all MAC subheaders can only be known after parsing all MAC SDUs / CEs based on the size of the MAC transport block. Furthermore, even if these techniques Petition 870260066479, dated 06 / 07 / 2026, p. 18 / 135 Previous techniques (14 / 64) analyzed all MAC SDUs / CEs to calculate MAC subheaders, but they are not recorded in the MAC transport block because the size of the MAC header is not known in advance and the starting point of the MAC SDU is not known during the analysis of MAC SDUs. Thus, compared to previous techniques, the apparatus and methods presented in this case can increase the efficiency of encoding a MAC transport block.

[0038] This disclosure also includes several aspects of split and partial MAC headers. Specifically, to provide transmitter and receiver hardware acceleration in the UE, MAC headers can be split or divided into at least two portions for placement at the beginning and end of the MAC PDU. The former can be adapted to support a wide variety of devices and applications. Furthermore, a split MAC header can also provide multiple connectivity and interoperability for wireless wide area networks (WWANs) (e.g., LTE) and wide local area networks (WLANs). The split MAC header can apply to all protocols between the Internet Protocol (IP) and physical layers, including the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and / or the MAC layer.As such, the present aspects may divide the MAC header into at least a first portion and a second portion, and send, from the transmitter to a receiver, the first portion at a first time and the second portion at a second time, the second time being understood as after the first time. Petition 870260066479, dated 06 / 07 / 2026, page 19 / 135 15 / 64

[0039] The present disclosure further includes several aspects for a MAC transport block layout. For example, an UE can transmit data on an uplink such as TB. In certain aspects, the TB can be formed, for example, by a MAC layer of the UE and be referred to as a TB MAC. For example, the UE can receive an uplink lease from a BS, indicating a number of TBs that the UE can transmit to the base station or network entity and the size of each TB. The UE, for this reason, can generate TBs and transmit them to the BS over the resources (e.g., layers, such as frequency carriers and / or space layers and symbols) allocated, defined, scheduled or similar, in the uplink lease. In some aspects, the UE transmits several TBs to the BS at a time. In particular, each TB can be sent on a different layer of the UE to the BS at the same time (e.g., on the same symbols) of the uplink.

[0040] Furthermore, according to some aspects, the UE may be provided with data (e.g., corresponding to one or more PDCP service data units (SDUs), and so forth) corresponding to one or more logical channels (e.g., control channels, traffic channels, PUCCH, PUSCH, and so forth) to transmit to the BS. The UE may use the PDCP SDUs to construct the TBs.

[0041] Depending on certain aspects, the UE compiles a TB that includes PDCP SDUs. For example, depending on certain aspects, the UE (e.g., the UE PDCP layer) may generate a data unit of Petition 870260066479, dated 06 / 07 / 2026, page 20 / 135 16 / 64 PDCP protocol (PDU) for each PDCP SDU. Each PDCP PDU may include the PDCP SDU and a corresponding PDCP header. Furthermore, depending on aspects, the UE (e.g., UE RLC layer) may generate an RLC PDU for each PDCP PDU. Each RLC PDU may include the PDCP PDU (also referred to as an RLC SDU) and a corresponding RLC header. Depending on some aspects, the UE (e.g., UE MAC layer) may generate a TB (also referred to as a MAC PDU) that includes multiple RLC PDUs (also referred to as MAC SDUs). Each TB, as discussed in this case, may include one or more RLC PDUs and one or more corresponding MAC subheaders. Depending on some aspects, the TB may further include one or more MAC CEs and a corresponding MAC subheader for each of the MAC control elements.Consequently, depending on certain aspects, the UE can generate three headers: a PDCP header, an RLC header, and a MAC subheader for each PDCP SDU.

[0042] Depending on certain aspects, the PDCP header may include one or more sequence numbers (SNs) for the PDCP SDU, whether the PDCP PDU is data or control information (e.g., a D / C bit), SN length information, a PDCP PDU type, and so on. Depending on certain aspects, the RLC header may include one or more SNs for the RLC SDU, an extension bit, a length indicator field, a D / C bit, and so on. Depending on certain aspects, the MAC subheader for MAC SDUs may include one or more logical channel identifiers. Petition 870260066479, dated 06 / 07 / 2026, p. 21 / 135 17 / 64 (LCID) indicating the logical channel for the corresponding MAC SDU and a MAC SDU length. Depending on certain aspects, the MAC subheader for MAC CEs may include an LCID indicating the MAC CE types and a MAC CE length. Each MAC CE may carry control information for signaling between the UE and BS, such as an environmental energy space report, UE contention resolution identity, time advance command, temporary storage status report, discontinuous reception command (DRX), and so on.

[0043] According to certain aspects described in the present case, RLC concatenation is not used (for example, concatenation of RLC SDUs into a single RLC PDU), and for this reason the length indicator field in the RLC header may not be included. Different conceptions for TB are discussed further according to different aspects of the present disclosure.

[0044] Each of the aspects described in this case in relation to the exposed MAC transport block can be applied and / or performed for one or both downlink and uplink transmissions.

[0045] Similarly, each of the aspects described above in the present case can be carried out or realized in connection with the matter under consideration included in Figures 1-16, which are described below in more detail.

[0046] With reference to Figure 1, according to one aspect, a wireless communication system 10 includes at least one UE 12 in communication coverage of at least Petition 870260066479, dated 06 / 07 / 2026, p. 22 / 135 18 / 64 minus a network entity 14 or network entity 20 (e.g., base station or eNB, or a cell thereof, in a 5G NR network). UE 12 can communicate with a network via network entity 14 or network entity 20. In certain aspects, multiple UEs including UE 12 may be in communication coverage with one or more network entities, including network entity 41 and network entity 20. In one aspect, network entity 14 or network entity 20 may be a base station such as an eNode / eNB in ​​a Long-Term Evolution (LTE) network that includes an evolved packet core (EPC) (not shown). Although several aspects are described in relation to a UMTS, LTE, or 5G NR network, similar principles may be applied in other wireless wide area networks (WWANs). A wireless network can employ a scheme where multiple base stations can transmit on a single channel.According to one example, UE 12 can transmit and / or receive wireless communications to and / or from network entity 14 and / or network entity 20. For example, UE 12 can be actively communicating with network entity 14 and / or network entity 20.

[0047] According to certain aspects, the UE 12 may also be referred to by persons skilled in the art (as well as in the present case interchangeably) as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal. Petition 870260066479, dated 06 / 07 / 2026, p. 23 / 135 19 / 64 a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.A UE 12 can be understood to include a mobile phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a portable device, a tablet computer, a laptop, a cordless phone, a wireless local loop (WLL) station, a global positioning system (GPS) device, a multimedia device, a video device, a digital audio device (e.g., MP3 player), a camera, a game console, a wearable computing device (e.g., a smartwatch, smart glasses, a health or fitness tracker, and so on), an appliance, a sensor, a vehicle communication system, a medical device, a vending machine, an Internet of Things device, or any other similarly functioning device.Furthermore, network entity 14 or network entity 20 may be comprised of a macro cell, pico cell, femto cell, relay, B node, B mobile node, small cell box, UE (e.g., communication in non-hierarchical or ad-hoc network mode with UE 12), or substantially any type of component that can communicate with UE 12 to provide wireless network access on UE 12.

[0048] According to the present aspects, UE 12 and / or network entity 14 / 20 may include one or more processors 103 and a memory 130 that may operate in combination with a MAC encoder / decoder management component 40 in a MAC protocol layer for Petition 870260066479, dated 06 / 07 / 2026, page 24 / 135 20 / 64 controlling an encoder / decoder 50 in order to encode or decode a MAC transport block 52 having an enhanced MAC header format as described in this case. For example, the enhanced MAC header format may include a MAC header size indicator (HDR) positioned at one end of the MAC transport block 52 to indicate the size of the whole or part of a header. MAC 56, which according to certain aspects can be positioned subsequent to the MAC SDUs and / or MAC CEs (MAC SDUs / CEs 22) that are encoded in the MAC 52 transport block.

[0049] The MAC encoder / decoder management component 40 can operate to encode MAC SDUs / CEs 22 within the MAC transport block 52 in response to, or as soon as they are parsed, for example, from a queue of a logical channel, while storing the corresponding MAC subheader information in a header buffer 48 for subsequent encoding within the MAC transport block 52. For example, in identifying one or more MAC DUs / CEs 22 for transmission, the MAC encoder / decoder management component 40 can operate a size / space determinant component 42 to determine a size requirement corresponding to an amount of space needed to include the respective MAC SDU / CE 22, and the corresponding MAC subheader information, in the MAC transport block 52. Additionally, the size / space determinant component 42 can be configured to determine a space Petition 870260066479, dated 06 / 07 / 2026, p. 25 / 135 21 / 64 remaining MAC transport block corresponding to an amount of space available within MAC transport block 52 to include the respective MAC SDU / CE 22 of the corresponding MAC subheader information. When determining the remaining MAC transport block space, the size / space determining component 42 can be configured to take into account an amount of space needed to include the MAC subheader information stored for previous MAC SDUs / CEs 22 that have already been encoded in MAC transport block 52.According to one aspect, the size / space determinant component 42 can be configured to communicate with a header determinant component 46, which is configured to determine a size requirement for the respective MAC subheader information SDU / CE 22 and corresponding MAC, as well as the amount of space required for the MAC subheader information stored for the previous MAC SDUs / CEs 22 that have already been encoded in the MAC transport block 52. Furthermore, according to one aspect, the size / space determinant component 42 and / or the header determinant component 46 can be configured to communicate with the header buffer 48, if necessary, to obtain information regarding the MAC subheader information stored for the previous MAC SDUs / CEs 22 that have already been encoded.Furthermore, component 40 of the MAC encoder / decoder manager may include a build / transmit (TX) determinant component 44 that makes the decision to continue building the MAC transport block 52, for example. Petition 870260066479, dated 06 / 07 / 2026, page 26 / 135 22 / 64 encoding the respective MAC 22 SDU / CE or to stop adding new MAC 22 SDUs / CEs, encode MAC 56 header and MAC 54 header size indicator, and initiate transmission of MAC 52 transport block. For example, component 44 (DET) of the build / transmit (TX) determinant is configured to communicate with component 42 size / space determinant, obtain and compare the size requirement versus the remaining space, and thus build or initialize the transmission decision based on whether the respective MAC 22 SDU / CE and corresponding MAC subheader information can fit in the remaining space in MAC 52 transport block.

[0050] The MAC encoder / decoder management component 40 can, via the header determination component 46, be further configured to split the MAC header 56 into a first part corresponding to a pre-subheader 58 and a second part corresponding to a post-subheader 60. For example, MAC information may have conflicting or varying requirements regarding when the information can be generated, and how early the information is needed or requested at a receiver. In particular, placing information may be preferred at the beginning of a PDU (e.g., MAC transport block 54) if the information is needed or requested for early processing at the receiver. Conversely, information that needs time to be generated during rendering may be placed or provided at the end of the PDU (e.g., MAC transport block 54).Depending on the aspect, MAC information generally does not fall into the two previous categories. Petition 870260066479, dated 06 / 07 / 2026, page 27 / 135 23 / 64 (for example, information for early processing or information that may require time for generation). The split MAC header may allow preference for both options or categories, in order to improve the distribution of delays between UE 12 and a network entity 14 or 20.

[0051] For example, the MAC encoder / decoder management component 40 can, through the header determination component 46, be configured to split or divide the MAC header 56 into at least two parts that can be processed independently. A first portion can correspond to a pre-subheader 58 and can be placed at the beginning of the MAC PDU (e.g., MAC transport block 52). The pre-subheader 58 can include data that may be of utmost importance to be used immediately at the receiver. Depending on certain aspects, UE 12 can generate such data in advance. For example, MAC control elements can be understood as a type of data that can be generated in advance. A second portion can correspond to a post-subheader 60, and can be placed at the end of the MAC PDU (e.g., MAC transport block 52). The post-subheader 60 can include data that may take time to be generated at the sender.Furthermore, according to certain aspects, this data cannot be used at the receiver until an entire packet is received. For example, post-subheader 60 might include a header structure. The partitioning or division can be performed by MAC subheader. Additionally, instead of adding a combination of LCID / length per MAC SDU, an indication of a length might be used. Petition 870260066479, dated 06 / 07 / 2026, page 28 / 135 24 / 64 is included in one of the headers in a MAC SDU so that MAC SDUs can be independently decoded.

[0052] As illustrated in Table 1 further on provides a preferred placement of MAC control elements in the ascending and descending link directions. The - in the best placement column may indicate that a control element could be placed in pre-subheader 58 or post-subheader 60. For example, a MAC PDU structure (e.g., MAC transport block 52) may be sent later in the PDU, since processing can only begin when a final symbol is received (e.g., due to the encoding structure with serial-to-parallel mapping). Table 1: Positioning of MAC control elements MAC Control Elements Direction Best Positioning MAC Control Elements Intermediate Memory State Report UL Pre-Header MAC Control Elements Side Link BSR UL Pre-Header MAC C-RNTI Control Element UL - Energy Environmental Space Report MAC Control Element UL Pre-Header MAC Control Report UL Pre-Header Petition 870260066479, dated 06 / 07 / 2026, page 29 / 135 25 / 64 Extended Energy Environmental Space MAC Report Dual Connectivity Energy Environmental Space UL Pre-Header Enable / Disable MAC Control Element DL Pre-Header Long DRX Command MAC Control Element DL - DRX Command MAC Control Element DL - Identity MAC Control for UP Contention Resolution DL - MAC Control Element for Synchronization Advance Command DL Pre-Header

[0053] The MAC encoder / decoder management component 40, and the corresponding one or more sub-components, may include hardware code, firmware and / or software capable of being executed by processor 103 and / or memory 130, to perform the operations described in this case. For example, according to one aspect, the hardware may include a hardware accelerator or a specialized processor. Memory 130 may include information, such as one or more rows of MAC 22 SDUs / CEs from one or more logical channels, and / or intermediate header memory 48 including stored MAC subheader information from already encoded information from MAC 22 SDUs / CEs.

[0054] Processor 103, memory 130 and / or Petition 870260066479, dated 06 / 07 / 2026, p. 30 / 135 The 26 / 64 component 40 of the MAC encoder / decoder manager can be communicatively coupled with a transmitter / receiver 106, which may include a receiver 32 for receiving and processing RF signals and a transmitter 34 for processing and transmitting RF signals. For example, the processor 103 can be coupled to the transceiver 106 and memory 130 via at least one bus 110.

[0055] Receiver 32 may include hardware code, firmware and / or software capable of being executed by a processor to receive data, with the code comprising instructions and being stored in memory (e.g., a medium capable of being read by a computer). Receiver 32 may comprise, for example, a radio frequency (RF) receiver. In one aspect, receiver 32 may receive signals transmitted by UE 12 or network entity 14 / 20. Receiver 32 may obtain measurements of the signals. For example, receiver 32 may determine Ec / Io, SNR, and so forth.

[0056] Transmitter 34 may include hardware, firmware, and / or software code capable of being executed by a processor to transmit data, with the code comprising instructions and being stored in memory (e.g., a medium capable of being read by a computer). Transmitter 34 may be, for example, an RF transmitter.

[0057] According to one aspect, one or more 103 processors may include a 108 modem that uses one or more modem processors. The various functions related to the MAC encoder / decoder manager component 40 may be included in the 108 modem and / or 103 processors and, according to one aspect, may be Petition 870260066479, dated 06 / 07 / 2026, page 31 / 135 27 / 64 performed by means of a single processor, while in other respects, different functions may be performed by means of a combination of two or more different processors. For example, according to one aspect, the one or more processors 103 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmission processor, or a transceiver processor associated with the transceiver 106.

[0058] In addition, UE 12 and / or network entity 14 / 20 may include RF front end 104 and transceiver 106 for receiving and transmitting radio transmissions, for example, wireless communications 26. For example, transceiver 106 may transmit or receive MAC transport block 52.

[0059] The RF front end 104 may be connected to one or more antennas 102 and may include one or more low-noise amplifiers (LNAs) 141, one or more switches 142, 143, one or more power amplifiers (PAs) 145, and one or more filters 144 for transmitting and receiving RF signals. According to one aspect, components of the RF front end 104 may connect to the transceiver 106. The transceiver 106 may connect to one or more modems 108 and the processor 103.

[0060] According to one aspect, the LNA 141 can amplify a received signal under a desired output emission level. According to one aspect, each LNA 141 can be endowed with specified minimum and maximum gain values. According to one aspect, the end Petition 870260066479, dated 06 / 07 / 2026, p. 32 / 135 The RF front panel 104 (28 / 64) can use one or more switches 142, 143 to select a specific LNA 141 and its specified gain value based on a desired gain value for a specific application.

[0061] In addition, for example, one or more PA(s) 145 may be used by the RF front end 104 to amplify a signal to an RF output at a desired output power level. According to one aspect, each PA 145 may be provided with specified minimum and maximum gain values. According to one aspect, the RF front end 104 may use one or more switches 143, 146 to select a particular PA 145 and its specified gain value based on a desired gain value for a particular application.

[0062] Similarly, for example, one or more filters 144 may be used by the RF front end 104 to filter a received signal to obtain an input RF signal. In a similar way, according to one aspect, for example, a respective filter 144 may be used to filter an output from a respective PA 145 to produce an output signal for transmission. According to one aspect, each filter 144 may be connected to a specific LNA 141 and / or PA 145. According to one aspect, the RF front end 104 may use one or more switches 142, 143, 146 to select a transmission or reception path using a specified filter 144, LNA, 141, and / or PA 145, based on a configuration as specified by the transceiver 106 and / or processor 103.

[0063] Transceiver 106 can be configured Petition 870260066479, dated 06 / 07 / 2026, page 33 / 135 29 / 64 to transmit and receive wireless signals via antenna 102 through the RF front end 104. According to one aspect, the transceiver can be tuned to operate at specified frequencies such that UE 12 can communicate with, for example, a network entity 14 or network entity 20. According to one aspect, for example, modem 108 can configure transceiver 106 to operate at a specified frequency and power level based on UE configuration of UE 12 and the communication protocol used by modem 108.

[0064] According to one aspect, modem 108 can be understood as a multi-band multi-modality modem, which can process digital data and communicate with transceiver 106 in such a way that digital data is sent and received using transceiver 106. According to one aspect, modem 108 can be multi-band and be configured to support multiple frequency bands for a specific communications protocol. According to one aspect, modem 108 can be multi-modality and be configured to support multiple operating networks and communications protocols. According to one aspect, modem 108 can control one or more components of UE 12 or network entity 14 / 20 (e.g., RF front end 104, transceiver 106) to enable the transmission and / or reception of signals based on a specified modem configuration. According to one aspect, the modem configuration can be based on the modem modality and the frequency band in use.According to another aspect, the modem configuration can be based on the information from... Petition 870260066479, dated 06 / 07 / 2026, p. 34 / 135 30 / 64 UE configuration associated with UE 12 as provided by the network during cell selection and / or cell selection. UE 12, network entity 14 or network entity 20 may further include memory 130, such as for storing data used in this case and / or local versions of applications or component 40 of the MAC encoder / decoder / or more of its subcomponents to be executed by processor 103. Memory 130 may include any type of computer-readable media usable by a computer or processor 103, such as random access memory (RAM), read-only memory (ROM), tapes, magnetic disks, optical disks, volatile memory, non-volatile memory and any combination thereof.According to one aspect, for example, memory 130 may be a computer-readable storage medium that stores one or more computer-executable codes that define component 40 of the MAC encoder / decoder and / or one or more of its subcomponents, and / or data associated therewith, when UE 12 and / or network entity 14 / 20 is operating processor 103 to execute component 40 of the MAC encoder / decoder manager and / or one or more of its subcomponents. According to another aspect, for example, memory 130 may be understood as a non-transient computer-readable storage medium.

[0065] With reference to Figures 2-6, the exemplary MAC transport block structures 200, 400, 500 and 600 (Figures 2 and 4-6) according to the aspects described include MAC HDR. The indicator of Petition 870260066479, dated 06 / 07 / 2026, p. 35 / 135 31 / 64 size 54 and flexibility in the positioning of the MAC header 56 (including MAC subheaders), MAC control elements and MAC service data units (SDUs), compared to an existing MAC transport block structure 300 (Figure 3) which defines a fixed format that may be inefficient for encoding in a MAC layer compared to the enhanced format of the MAC transport block structures 200, 400, 500 and 600.

[0066] Referring specifically to Figure 2, the exemplary MAC transport block structure 200 defines a MAC Transport Block = n*RLC PDUs + m*MAC CE + (n+m) *MAC HDRs + MAC HDR Size, where neither can be any number respectively. The MAC HDR size indicates the total number of bytes corresponding to all MAC HDRs starting at the edge, excluding the MAC HDR size.

[0067] In 202, the MAC HDR size can be a fixed size (e.g., 1 or 2 Bytes indicating the total number of MAC HDR bytes).

[0068] Alternatively, the HDR MAC size can be a variable size. For example, when the HDR MAC size is indicated in Byte N (where N is the last Byte of the TB of MAC), then the first 2 bits (Bit 0, Bit 1) of Byte N can represent a length indicator (LI) size. For example, the first two bits can be endowed with one of the following formats: 1. (Bit 0, Bit 1) (0, 0) - 1 Byte - 6 bits to represent HDR size MAC, 2. (Bit 0, Bit 1) (0, 1) - 2 Bytes - 14 bits to represent HDR size on MAC. Petition 870260066479, dated 06 / 07 / 2026, page 36 / 135 32 / 64 3. (Bit 0, Bit 1) (1, x) — Reserved.

[0069] Thus, the present aspects can configure the MAC Header Size at the end of the MAC Transport block to indicate the amount of MAC HDR in this MAC Transport block. According to one aspect, MAC HDR includes combined information about each MAC SDU, MAC CE, and optionally, Padding. According to some embodiments, such as in the example in Figure 2, MAC HDR is only at the end of the MAC Transport block while the complete RLC PDUs are arranged from the beginning of the MAC Transport block.

[0070] Furthermore, in 204, MAC HDRs can be recorded in one or more different formats. For example, and are not limited to the same:

[0071] First Format 206 =

[0072] CE of MAC 1, CE of MAC 2, ... CE of MAC n, MAC Sub-HDR 1, MAC Sub-HDR 2, MAC Sub-HDR 3, MAC Sub-HDR 4, MAC Sub-HDR 5, MAC Sub-HDR 6, PAD; and Second Format 208 =

[0073] PAD, MAC Sub-HDR 5, MAC Sub-HDR 4, MAC Sub-HDR 3, MAC Sub-HDR 2, MAC Sub-HDR 1, CE of MAC n....... CE of MAC 2, CE of MAC 1.

[0074] With reference to Figures 4-6, additional examples of MAC 400, 500 and 600 transport block structures provide further alternatives for the flexible arrangement of various components of the MAC 52 transport block according to one or more embodiments of the present disclosure.

[0075] For example, the MAC 400 transport block structure includes MAC CEs positioned before Petition 870260066479, dated 06 / 07 / 2026, page 37 / 135 33 / 64 of SDUs MAC at the beginning (or end) of the MAC transport block, which can occur when one or more types of ECs are prioritized over SDUs during logical channel information multiplexing.

[0076] Similarly, for example, the 500 MAC transport block structure includes MAC CEs mixed with MAC SDUs and Padding at the beginning of the MAC transport block, which can occur when the CEs and SDUs and Padding have different priorities and / or when they are parsed as they occur in the logical channel queues when multiplexing logical channel information.

[0077] In addition, for example, the 600 MAC transport block structure includes the MAC header split into two or more, for example, up to x, where x is any number, of portions. In this case, the parts of the MAC header can be mixed with MAC CEs, MAC SDUs and Padding at the beginning of the MAC transport block, which can occur when the CEs and SDUs and padding have different priorities and / or when they are parsed as they occur within the logical channel queues when multiplexing the logical channel information. In some cases, for example, at least one last part (e.g., MAC Headers) of the two or more parts of the MAC Header can be positioned at the end (e.g., the rear end) of the MAC transport block and the corresponding MAC HDR size indicator can be configured to provide an adjacent MAC Header size.

[0078] With reference to Figure 7, an example of architecture and data flow 700, which should not be Petition 870260066479, dated 06 / 07 / 2026, p. 38 / 135 34 / 64 interpreted as limiting, includes a MAC encoder / decoder manager 40 performing the operations described in the present case to construct a MAC transport block 52 that is endowed with an enhanced MAC header 56, for example, which includes an HDR size indicator 54 of MAC in a position at the end of the MAC transport block 52. In particular, the MAC encoder / decoder manager 40 operates according to a first option to construct (compile) the MAC transport block 52 and a second option to initiate the transmission of a substantially full MAC transport block 52 in response to a compilation / transmission decision 73 of the compilation / transmission determination component 44.The compilation / transmission decision 73 is based on the fact that the remaining space 73 of the MAC transport block is less than a size requirement 71, identifying an amount of space needed for the respective MAC SDU / CE subheader information 22 and the corresponding MAC. In the first option, the MAC encoder / decoder manager 40 operates to encode a respective MAC SDU / CE 22 while storing the corresponding MAC subheader information in the header intermediate memory 48. In the second option, the MAC encoder / decoder manager 40 operates to encode the stored subheader information as the MAC header 56, encode the MAC header size indicator 54 at the end, and start transmitting the MAC transport block 52. Optionally, although not illustrated, in order to fill the MAC transport block 52, the second option... Petition 870260066479, dated 06 / 07 / 2026, page 39 / 135 35 / 64 may additionally include fill-in coding, and add MAC subheader information to fill in the stored MAC subheader information and code the result.

[0079] Figure 8 is an illustrative block diagram of a MAC 800 PDU. In certain respects, the MAC 800 PDU may be the same as or similar to the MAC 52 transport block. As illustrated, the various parts of the MAC 800 PDU are shown allocated, defined, programmed, positioned, ordered, or so on, for the resources (e.g., symbols) of the MAC 800 PDU in order from start (e.g., a first symbol) to end (e.g., a last symbol) (i.e., from left to right).For example, PDU MAC 800 may include a pre-subheader MAC 802, control elements MAC 804, SDUs MAC 806 and 808, padding 810, a first LCID and / or length combination part (e.g., which may correspond to, or be included within, a MAC SDU or a MAC SDU header), a second LCID and / or length combination part (e.g., which may correspond to, or be included within, a MAC SDU or a MAC SDU header), and a post-subheader MAC 816. Pre-subheader 802 and post-subheader 816 may be the same as or similar to pre-subheader 56 and post-subheader 60, respectively.

[0080] In certain respects, each of the 802 subheaders and / or 816 post-subheaders may be of fixed size and have a known structure. On the other hand, the size of the 802 pre-subheader may be Petition 870260066479, dated 06 / 07 / 2026, p. 40 / 135 36 / 64 at the beginning of the MAC PDU 800 (pre-HL MAC). According to some aspects, the post-subheader 816 of the MAC may be a pointer back to the beginning of the MAC header. Additionally, padding 810 may be added between the last MAC SDU and the post-subheader 816.

[0081] In addition, the 804 MAC control elements may be at the beginning of the 800 MAC PDU. A local cyclic redundancy check (CRC) may be added at the beginning that allows the initial headers to be processed separately (e.g., a sub-physical layer channel, first feature block, or each feature block). This part of the header may form a partial MAC header, or an 802 pre-subheader for MAC. Depending on the aspect, the reception of the 804 control elements may be acknowledged by a receiver. For example, the acknowledgment may be split into a control part and a data part, with the control acknowledgment designed to be more reliable than the data acknowledgment.

[0082] The CRC for the MAC header may include a CRC for the pre-subheader 802 and a CRC for the post-subheader 816. For example, the CRC may be included as part of, or for, the pre-subheader 802 or for a complete header at the beginning. Depending on certain aspects, this CRC may be comprised of a CRC in or for only the pre-subheader 802, a CRC in an initial part of the MAC 800 PDU that covers at least the pre-subheader 802, and / or the CRC per MAC subheader (e.g., CE of MAC 804 subheader). Furthermore, the CRC may be included as part of or for the post-subheader 816 or for a Petition 870260066479, dated 06 / 07 / 2026, p. 41 / 135 37 / 64 final total header. Depending on certain aspects, this CRC may be a CRC in or for only post-subheader 816, a CRC in a first part of the MAC 800 PDU that covers at least post-subheader 816, and / or a CRC by MAC subheader (e.g., CE subheader of MAC 804).

[0083] Depending on certain aspects, a receiver may acknowledge receipt of at least the 804 MAC control elements and / or the 802 pre-subheader and 816 post-subheader. For example, the acknowledgment or message may be split or divided into a control and data portion. The control acknowledgment may be designed to be more reliable than the data acknowledgment. The acknowledgment may be comprised by a physical layer (e.g., using two separate physical channels) and / or a MAC layer (e.g., using a physical channel carrying multiple bits). For example, the MAC layer may carry two bits including one for control and one for data. Depending on certain aspects, the MAC layer may carry N bits such that for N-1 each bit may be for each CRC and one bit to acknowledge the data.Depending on certain aspects, the MAC layer can carry three-level information (e.g., Ack control, Ack control and data, Ack control and data), where control data represents a MAC subheader covered by CRC, or control data represents an 802 pre-subheader.

[0084] Figure 9A illustrates an example of a TB 900 built by UE 12, and more specifically, through component 40 of the encoder manager / Petition 870260066479, dated 06 / 07 / 2026, page 42 / 135 38 / 64 MAC decoder, according to certain aspects. According to these aspects, the TB 900 can be equal to or similar to the 52 MAC transport block. As illustrated, the various parts of the TB 900 are shown allocated, defined, programmed, positioned, ordered, or so on, for the resources (e.g., symbols) of the TB 900 in order from start (e.g., a first symbol) to end (e.g., a last symbol) (i.e., from left to right). Although certain aspects in relation to the figures in the present case are described as allocating certain portions, elements, headers, data fields, data, and so on, to one or more TBs. The portions, elements, headers, data, data fields, and so on, can be defined, programmed, positioned, ordered, and so on, as discussed for one or more TBs.Specifically, the leftmost portion of TB 900 may correspond to a first bit of TB 900, and the rightmost portion of TB 900 may correspond to a last portion of TB 900.

[0085] In this example, TB 900 begins with a MAC subheader for the MAC CE (subHDR MAC CE), followed by MAC subheaders for the MAC SDUs (MAC subHDR SDU1 and MAC subHDR SDU2, in that order). Following the MAC subheaders in TB 900 is the MAC CE, followed by MAC SDUs (MAC SDU1 and MAC SDU2, in that order). In particular, MAC SDU1 includes, in that order, an RLC header (RLC HDR1), a PDCP header (PDCP HDR1), and a PDCP SDU (PDCP SDU1). Furthermore, MAC SDU2 includes, in that order, an RLC header (RLC HDR2), a PDCP header (PDCP HDR2), Petition 870260066479, dated 06 / 07 / 2026, p. 43 / 135 39 / 64 and PDCP SDU (PDCP SDU2). For this reason, according to certain aspects, all MAC subheaders are allocated at the beginning of TB 900, followed by the MAC CE and MAC SDUs. This TB 900 can be used for particular technologies, such as LTE.

[0086] Figure 9B illustrates an example of a TB 940 constructed by UE12, and more specifically, through the MAC encoder / decoder management component 40, according to certain aspects. According to certain aspects, TB 940 may be the same as or similar to the MAC transport block 52. As illustrated, the various parts of TB 940 are shown as allocated to the resources (e.g., symbols) of TB 940 in order from beginning (e.g., a first symbol) to end (e.g., a last symbol) (i.e., from left to right). In particular, the leftmost portion of TB 940 may correspond to a first bit of TB 940, and the rightmost portion of TB 940 may correspond to a last portion of TB 940.

[0087] In this example, unlike TB In TB 940, the MAC subheaders are not allocated continuously at the beginning of TB 940. Instead, each MAC subheader is allocated adjacent to and at the beginning of the corresponding MAC SDU, and the MAC SDUs are allocated in order in TB 940. As illustrated, TB 940 starts with MAC subHDR SDU1 followed by MAC SDU1, and then MAC subHDR SDU2 followed by MAC SDU2.

[0088] As illustrated, the TB 940 does not include a MAC CE or the corresponding MAC address. Petition 870260066479, dated 06 / 07 / 2026, p. 44 / 135 40 / 64 subHDR. Consequently, certain aspects described in the present case provide techniques for allocating the MAC CE and the corresponding MAC subheader for a TB, where MAC subheaders are not allocated continuously at the beginning of the TB (e.g., TB 940).

[0089] Depending on certain aspects, the MAC CE and corresponding subheader may be allocated, defined, programmed, positioned, ordered, and so on, at the beginning of the TB (e.g., occupying the first bit of the TB). Depending on certain aspects, the MAC CE and corresponding subheader may be allocated, defined, programmed, positioned, ordered, or so on, at the end of the TB (e.g., occupying the last bit of the TB corresponding to non-padding bits (e.g., there may be additional padding bits after the MAC CE)).

[0090] Figure 10A illustrates an example of a TB 1000A constructed by UE 12, and more specifically, by means of the MAC encoder / decoder manager component 40, according to certain aspects. According to certain aspects, the TB 100A may be the same as or similar to the MAC transport block 52. As illustrated, the TB 1000A is an example of a TB with the MAC subHDR CE and MAC CE at the beginning of the TB 1000A, followed by the fields in the order described with respect to the TB 940.

[0091] Figure 10B illustrates an example of a TB 1000B compiled by UE 12 and, more specifically, by means of the MAC 40 encoder / decoder manager component, according to Petition 870260066479, dated 06 / 07 / 2026, page 45 / 135 41 / 64 certain aspects. According to certain aspects, the TB 1000B may be the same as or similar to the MAC transport block 52. As illustrated, the TB 1000B is an example of a TB with the MAC CE subHDR and MAC CE at the end of the TB 1000B, following the fields in the order as described with respect to the TB 940.

[0092] In certain respects, including the MAC CE and corresponding subheader at the beginning of the TB provides certain advantages. For example, including the MAC CE at the beginning of the TB means that a network entity 14 and / or 20 receiving the TB can receive the MAC CE earlier and process the MAC CE earlier (e.g., assuming there is no cyclic redundancy check CRC associated with the TB).

[0093] In certain respects, including the MAC CE and corresponding subheader at the end of the TB provides certain advantages. For example, some MAC CEs are generated by UE 12 after the rest of the TB has been compiled, as well as because the information for the MAC CE is based on existing data in the TB. For this reason, by placing the MAC CE at the end of the TB, parts of the TB can still be compiled and transmitted via UE 12 to a network entity 14 and / or 20 before the MAC CE is generated and transmitted. Otherwise, if the MAC CE were at the beginning of the TB, UE 120 could not start transmitting the TB until after the MAC CE was generated, potentially increasing latency.

[0094] According to certain aspects, as discussed, different PDCP SCUs, and for that reason Petition 870260066479, dated 06 / 07 / 2026, page 46 / 135 42 / 64 reason different MAC SDUs may correspond to data coming from different logical channels. In particular, a single TB may include MAC SDUs corresponding to different logical channels. A receiver of a TB (e.g., BS 110) may be able to process MAC SDUs from different logical channels in parallel. In particular, the MAC SDUs associated with a given logical channel may be in order, and need to be processed in order, but the MAC SDUs from different logical channels may be processed in parallel.

[0095] Due to certain aspects, the MAC tracing of TB 52, TB 900, TB 940, TB 1000A or TB 1000B may hinder the parallel processing of MAC SDUs from different logical channels. In particular, to determine where each of the MAC SDUs for each logical channel is located on TB 900 / 940 / 1000A / 1000B, network entity 14 or 20 needs to process each MAC SDU in the order it is on the TB, since there is no other information on the TB outlining where the MAC SDUs are positioned. For this reason, parallel processing of MAC SDUs from different logical channels is not achieved, since each of the MAC SDUs is processed serially in order on the TB.

[0096] For this reason, certain aspects in the present case provide an additional general MAC header 62 (for example, in addition to the MAC subheaders described in the present case) in the TB that indicates the position and / or size of consecutive packets of each logical channel. For example, for each logical channel, the corresponding MAC SDUs can be positioned together consecutively. Furthermore, the MAC SDUs of a channel Petition 870260066479, dated 06 / 07 / 2026, page 47 / 135 Logical 43 / 64 SDUs can be positioned in the TB, followed by the MAC SDUs of another logical channel, and so on. The general MAC header 62 can indicate, for each logical channel, the size of the MAC SDUs of the logical channel, or indicate the starting position of the MAC SDUs of the logical channel, or some other information that a network entity 14 or 20 can use to determine the delineation between the MAC SDUs of different logical channels. In this way, a network entity 14 or 20 can use this information to analyze the MAC SDUs in groups of consecutive MAC SDUs, each associated with a different logical channel, and process these groups in parallel. Depending on certain aspects, the general MAC header 62 can be allocated, defined, programmed, positioned, ordered, or so on. at the beginning of a TB (for example, followed by the MAC information TB 52, TB 900, TB 940, 1000A, 1000B, or so on).Depending on the aspect, the general MAC header can be allocated, defined, scheduled, positioned, ordered, and so on at the end of a TB (for example, following the MAC information TB 52, TB 900, 940, 1000A, 1000B, and so on).

[0097] Depending on certain aspects, the general MAC header 62 may include information indicating which logical channel each of the MAC SDU groups belongs to. Depending on some of these aspects, since the general MAC header 62 may include such information, the general MAC header 62 may not be included in the MAC subheaders for each of the MAC SDUs.

[0098] Figure 11 illustrates an example of a TB 1100 compiled using UE 12, and in a more Petition 870260066479, dated 06 / 07 / 2026, page 48 / 135 44 / 64 specifies, through the MAC encoder / decoder management component 40, certain aspects. In some aspects, TB 1100 may be the same as or similar to TB MAC 52. As illustrated, TB 1100 may be an example of a TB that includes a general MAC header 62, as described in this case. As illustrated, TB 1100 may include the fields of TB 1000B, followed by the general MAC header.

[0099] According to one example, MAC SDU1 and MAC SDU2 belong to a first logical channel. Furthermore, MAC SDU3 and MAC SDU4 belong to a second logical channel. Additionally, MAC SDU5 belongs to a third logical channel. Depending on certain aspects, the general MAC header 52 may indicate the size of the MAC DSUs for each of the first, second, and third logical channels. For example, the general MAC header may include the size of the combination of MAC SDU1 and MAC SDU2 as the size corresponding to the first logical channel. On the other hand, the general MAC header 52 may include the size of the combination of MAC SDU3 and MAC SDU4 as the size corresponding to the second logical channel. Furthermore, the general MAC header 52 may include the size of MAC SDU5 as the size corresponding to the third logical channel.Network entity 14 or 20 can use this information to determine where the MAC SDUs for each logical channel are located on the TB 1100 and process the MAC SDUs for different logical channels in parallel.

[00100] With reference to Figure 12, an exemplary method 1200 of operating the component of Petition 870260066479, dated 06 / 07 / 2026, p. 49 / 135 45 / 64 MAC encoder / decoder management 40, and / or a UE 12 or network entity 14 or 20 executing MAC encoder / decoder management component 40, includes receiving a MAC SDU / CE in block 802. For example, according to one aspect, the MAC encoder / decoder manager 40 and / or one or more UE 12 components may obtain one or more MAC SDUs / CEs 22 from one or more logical channels of an RLC protocol layer, and / or from one or more transmission queues of one or more logical channels.

[00101] In block 1204, method 1200 includes determining the size of the respective MAC SDU / CE 22 and the size of the corresponding MAC subheader information. For example, depending on one aspect, the MAC encoder / decoder manager 40 and / or one or more UE 12 components may determine the respective dimensions as described in this case.

[00102] In block 1206, method 1200 includes the determination of a remaining space in the MAC transport block. For example, according to one aspect, the MAC encoder / decoder manager 40 and / or one or more UE 12 components may determine the remaining space as described in this case.

[00103] In 1208, method 1200 includes determining whether the remaining space in the MAC transport block is less than the sum of the size of the respective MAC 22 SDU / CE and the size of the corresponding MAC subheader information. For example, according to one aspect, the MAC encoder / decoder manager 40 and / or one or more UE 12 components can determine whether or not there is Petition 870260066479, dated 06 / 07 / 2026, p. 50 / 135 46 / 64 sufficient space remains in the MAC transport block to continue processing the current MAC SDU / CE.

[00104] If the remaining space is not too small, for example, if there is enough remaining space to accommodate the processing of the respective MAC SDU / CE, then method 1200 operates to continue compiling the MAC transport block. In block 1210, method 1200 includes starting the encoding of the respective MAC SDU / CE. Additionally, in block 1212, method 1200 also includes storing the corresponding MAC subheader information in an intermediate store. After block 1212, method 1200 may return to block 1202 to evaluate whether a subsequent MAC SDU / CE can be processed. For example, depending on one aspect, MAC encoder / decoder manager 40 and / or one or more UE 12 components may perform the actions of blocks 1210 and 1212.

[00105] If the remaining space is too small, for example, if there is not enough space to accommodate the processing of the respective MAC SDU / CE, then method 1200 operates to prepare the MAC transport block for transmission. In block 1214, method 1200 includes obtaining the stored MAC SDU / CE subheader information from intermediate storage. In block 1216, optionally, method 1200 includes adding padding to the MAC transport block and adding MAC subheader information for padding to the obtained, stored MAC SDU / CE subheader information. Furthermore, in block 1218, method 1200 includes determining a MAC header size. Petition 870260066479, dated 06 / 07 / 2026, p. 51 / 135 47 / 64 for the stored MAC SDU / CE subheader information (and optionally, the MAC subheader information for padding). Additionally, in block 1220, method 1200 includes encoding the MAC SDU / CE subheader information (and optionally padding) in the MAC transport block. Finally, in block 1222, method 1200 includes initiating the transmission of the MAC transport block. For example, according to one aspect, MAC encoder / decoder manager 40 and / or one of its components can perform the actions of blocks 1214, 1216, 1218, 1220, and 1222.

[00106] It should be noted that method 800 can then be repeated for one or more subsequent MAC transport blocks, for example, until all the information from the RLC layer logical channels has been transmitted.

[00107] According to a particular use case, a wireless communication method includes the identification, by a processor, of pending information received on one or more logical channels in a MAC layer, where the pending information includes data information and / or control information to be included in a MAC transport block, the processor determining a size requirement corresponding to an amount of space that will be absorbed by the pending information and corresponding MAC subheader information in the transport block, the processor determining a remaining space available in the transport block, when the remaining space in the transport block is greater than or equal to the size requirement: initiating the encoding of Petition 870260066479, dated 06 / 07 / 2026, page 52 / 135 48 / 64 pending information in the transport block and when the remaining space in the transport block is less than the size requirement: determine a MAC header size based, at least in part, on a stored subheader information size corresponding to the previously encoded information in the MAC transport block, starting the encoding of at least the stored subheader information and an indication of the MAC Header Size with the MAC Header Size representing the MAC transport block such that the stored subheader information and the MAC index dimension indication are subsequently encoded and positioned in the subsequent MAC transport block after at least the previous information; and starting the transmission of the MAC transport block.

[00108] Furthermore, according to one aspect, method 1200 may further include encoding the pending information and / or the preceding information to begin at a leading end of the MAC transport block; and encoding the MAC Header Size indication at a right end of the MAC transport block opposite the leading end.

[00109] Additionally, with regard to the encoding of the previous information and / or the pending information, the stored information of the subheader and / or the pending information of the header corresponding to the pending information, and the indication of the MAC header size is based on reading the previous information and the pending information in only a single pass.

[00110] Furthermore, according to certain Petition 870260066479, dated 06 / 07 / 2026, page 53 / 135 49 / 64 aspects, the method may also include 1200 encoding of subheader information corresponding to the previous information and / or the pending information in a first format or a second format; wherein the first format positions the subheader control information relative to the subheader data information, then the subheader fill information, and then a subheader fill, each in the order starting at a leading end of the transport block; and wherein the second format positions the subheader fill information relative to the subheader, then the subheader data information, and then the subheader control information, each in the reverse order starting at the leading end of the transport block.

[00111] In some cases, when the remaining space in the transport block is greater than the size that the information will occupy in the transport block, the method may also include storing information from the subheader corresponding to the information in an intermediate memory.

[00112] In some cases, when the remaining space in the transport block is less than the size requirement, the determination of the MAC Header Size is still based on the size of any padding, and the start of encoding still includes the initial encoding of the padding in such a way that the padding is subsequently encoded and positioned in the MAC transport block following the previous information.

[00113] According to an alternative aspect, such as in a device that receives the transport block Petition 870260066479, dated 06 / 07 / 2026, p. 54 / 135 50 / 64 MAC addressing that is equipped with the enhanced MAC header, a wireless communications method includes receiving, by means of a processor, a medium access control (MAC) transport block having at least one MAC header size indication positioned in the MAC transport block subsequent to the control information and / or data information within the MAC transport block, wherein the MAC Header Size indication represents a MAC header size of MAC subheader information corresponding to the control information and / or data information; determining a location of the MAC subheader information within the MAC transport block relative to a position of the MAC header size indication, based on the MAC Header Size indication; and decoding the MAC subheader information, the control information and / or data information in response to the location of the MAC subheader information.

[00114] With reference to Figure 13, an exemplary method 1300 of the operational MAC encoder / decoder manager component 40 and / or of UE 12 executing MAC encoder / decoder manager 40, splitting a MAC header into a first part and a second part in block 1302. For example, in one aspect, the MAC encoder / decoder manager component 40 and / or one or more UE 12 components may split a MAC header 56 into a first part (e.g., pre-subheader 58) and a second part (e.g., post-subheader 60).

[00115] Depending on certain aspects, the first part may include a pre-subheader 58 and the Petition 870260066479, dated 06 / 07 / 2026, page 55 / 135 Part 51 / 64 second includes a post-subheader 60. Depending on certain aspects, the pre-subheader 58 may be located at the beginning of a PDU MAC (e.g., transport block of MAC 52). Depending on certain aspects, the size of the pre-subheader 58 may be at least one of a known fixed size for one or two of the EU 12 or a network entity 14 or 20, or a variable size indicated at the beginning of the MAC PDU (e.g., MAC transport block 52).

[00116] According to certain aspects, the MAC PDU (e.g., MAC transport block 52) may include a CRC corresponding to at least one of the pre-subheader 58, in the first part of the MAC PDU (e.g., the MAC transport block 52) that covers at least the pre-subheader 58, or by the MAC control element. According to certain aspects, the post-subheader 60 is located at one end of a MAC PDU (e.g., the MAC transport block 52). According to certain aspects, the post-subheader 60 may include a header length corresponding to a pointer back to the beginning of the MAC PDU (e.g., the MAC transport block 52).According to certain aspects, the MAC PDU (e.g., the MAC transport block 52) includes a CRC according to at least one of the following: in the post-subheader 60, in the second part of the MAC PDU (e.g., the MAC transport block 52) that covers at least the post-subheader 60, or by the MAC control element.

[00117] In block 1304, method 1300 can send, from the UE to a network entity in a Petition 870260066479, dated 06 / 07 / 2026, p. 56 / 135 52 / 64 uplink communication channel, the first portion at the first time and the second portion at a second time after the first time. For example, according to one aspect, the MAC encoder / decoder manager component 40 and / or one or more UE 12 components may send, from UE 12 to a network entity 14 or 20 on an uplink communication channel, the first part (e.g., pre-subheader 58) at the first time and the second part (e.g., post-subheader 60) at the second time after the first time.

[00118] In block 1306, method 1300 may optionally receive, from the network entity on a downlink communication channel, a first split ACK that includes at least one of a control part or a data part. For example, according to one aspect, the MAC encoder / decoder manager component 40 and / or one or more UE 12 components may receive, from network entity 14 or 20 on a downlink communication channel, a first split ACK that includes at least one of a control part or a data part.

[00119] In block 1308, method 1300 may optionally receive, on the downlink communication channel from the network entity, a MAC PDU that includes a split MAC header containing at least two parts, the MAC PDU that includes downlink-specific control elements in at least one of the two parts. For example, according to one aspect, the MAC encoder / decoder manager component 40 and / or one or more UE 12 components may receive, in Petition 870260066479, dated 06 / 07 / 2026, p. 57 / 135 53 / 64 downlink communication channel from network entity 14 or 20, a MAC PDU (e.g., transport block MAC 52) that includes a split MAC header 56 that includes at least two parts (e.g., pre-subheader 58 and / or post-subheader 60), with the MAC PDU including downlink-specific control elements in at least one of the two parts.

[00120] In block 1310, method 1300 may optionally transmit, on the uplink communication channel or a distinct uplink communication channel to a network entity, a second split ACK that includes at least a control portion or a data portion in response to receiving the PDU MAC. For example, according to one aspect, the MAC encoder / decoder manager component 40 and / or one or more UE 12 components may transmit, on the uplink communication channel or a distinct uplink communication channel to a network entity, a second split ACK that includes at least a control portion or a data portion in response to receiving the PDU MAC (e.g., MAC transport block 52).

[00121] With reference to Figure 14, an exemplary method 1400 of operational MAC encoder / decoder management component 40, and / or the network entity 14 or 20 that executes the MAC encoder / decoder management component 40, may optionally receive, from a UE on an uplink communication channel, at least one of a first part of a first MAC header in a first Petition 870260066479, dated 06 / 07 / 2026, page 58 / 135 54 / 64 time or a second part of the first MAC header at a second time after the first time in block 1402. For example, according to one aspect, the MAC encoder / decoder manager 40 and / or one or more network entity components 14 or 20 may receive, from UE 12 on an uplink communication channel, at least one of a first part (e.g., pre-subheader 58) of a first MAC header (e.g., MAC transport block 52) at a first time or a second part (e.g., post-subheader 60) of the first MAC header (e.g., MAC transport block 52) at a second time after the first time.

[00122] In block 1404, method 1400 may optionally transmit an ACK that includes at least one of a data control portion to the UE. For example, according to one aspect, MAC encoder / decoder manager 40 and / or one or more network entity components 14 or 20 may transmit an ACK that includes at least one of a control portion or a data portion to the UE 12 in response to receiving at least one of a first portion (e.g., pre-subheader 58) of a first MAC header (e.g., the transport block of MAC 52) at a first time or a second portion (e.g., post-subheader 60) of the first MAC header (e.g., the transport block of MAC 52) at a second time after the first time.

[00123] In block 1406, method 1400 may optionally determine to transmit one or more MAC control elements on a link communication channel. Petition 870260066479, dated 06 / 07 / 2026, page 59 / 135 55 / 64 downlink to the UE. For example, according to one aspect, the MAC encoder / decoder manager 40 and / or one or more network entity components 14 or 20 may determine to transmit one or more MAC control elements on a downlink communication channel to the UE 12.

[00124] In block 1408, method 1400 can split a second MAC header into a first part and a second part. For example, MAC encoder / decoder manager 40 and / or one or more network entity components 14 or 20 can split a second MAC header (e.g., MAC header similar to transport block 52) into a first portion (e.g., pre-subheader 58) and a second portion (e.g., post-subheader 60).

[00125] In block 1410, method 1400 may transmit, from a network entity to the UE on the downlink communication channel, the first portion at a first time and the second portion at a second time after the first time, with at least one of the first portion or the second portion including one or more MAC control elements. For example, according to one aspect, MAC encoder / decoder manager 40 and / or one or more components of network entity 14 or 20 may transmit, from network entity 14 or 20 to UE 12 on the downlink communication channel, the first portion (e.g., pre-subheader 58) at a first time and the second portion (e.g., post-subheader 60) at a second time after the first time, with at least one of the first portion (e.g., pre-subheader 60) Petition 870260066479, dated 06 / 07 / 2026, page 60 / 135 56 / 64 subheader 58) or the second part (e.g., post-subheader 60) which includes one or more MAC control elements.

[00126] With reference to Figure 15, an exemplary method 1500 of the operational MAC encoder / decoder management component 40, and / or the UE 12 executing the MAC encoder / decoder component 40, can generate a transport block comprising a plurality of SDUs and a corresponding plurality of media access control subheaders, each media access control subheader being adjacent to a corresponding service data unit in the transport block, and the transport block further comprising a MAC control element that is endowed with a separate corresponding media access control subheader, the MAC control element and the corresponding media access control subheaders located at one end of the transport block in block 1502.For example, according to one aspect, the MAC encoder / decoder manager 40 and / or one or more components of UE 12 may generate a transport block (e.g., the MAC transport block 52) comprising a plurality of SDUs / CEs 22 and a corresponding plurality of MAC subheaders, each MAC subheader being disposed adjacent to a corresponding SDU in the transport block (e.g., the MAC transport block 52), and the transport block (e.g., the MAC transport block 52) further comprises a MAC control element which is provided with a separate corresponding MAC subheader, being the... Petition 870260066479, dated 06 / 07 / 2026, p. 61 / 135 57 / 64 MAC control element and corresponding MAC subheader located at the end of the transport block (e.g., transport block MAC 52). In block 1504, method 1500 can transmit the transport block to a device. For example, according to one aspect, the MAC encoder / decoder manager 40 and / or one of the components can transmit the transport block (e.g., transport block MAC 52) to a device (e.g., network entity 14 or 20).

[00127] Under certain aspects, each SDU may include a MAC SDU. Under certain aspects, each SDU may include an RLC header, a PDCP header, and / or a PDCP SDU. Under certain aspects, the beginning of a transport block may include a first bit of the transport block. Under certain aspects, the end of a transport block may include a last bit corresponding to the transport block data. Under certain aspects, at least one of the plurality of MAC subheaders may be separated from another of the plurality of MAC subheaders by means of an SDU.

[00128] With reference to Figure 16, an exemplary method 1500 of the operational MAC encoder / decoder manager component 40, and / or UE 12 executing the MAC encoder / decoder manager component 40, can generate a transport block comprising a plurality of SDUs allocated to a plurality of logical channels, the transport block still containing the general MAC header, with the general MAC header indicating a logical channel of the plurality of logical channels. Petition 870260066479, dated 06 / 07 / 2026, page 62 / 135 58 / 64 of each of the plurality of service data units in block 1602. For example, according to one aspect, MAC encoder / decoder manager 40 and / or one or more UE 12 components may generate a transport block (e.g., transport block MAC 52) comprising a plurality of SDUs allocated to a plurality of logical channels, the transport block further including the MAC 62 general header, with the MAC 51 general header indicating a logical channel of the plurality of logical channels of each of the plurality of SDUs in block 1602. In block 1604, method 1600 may transmit the transport block to a device. For example, according to one aspect, MAC encoder / decoder manager 40 and / or one or more UE 12 components may transmit the transport block to a device (e.g., network entity 14 or 20).

[00129] Under certain aspects, the MAC 62 general header may indicate at least one of a total size or position of consecutive SDUs for each of the plurality of logical channels. Under certain aspects, each SDU comprises a MAC SDU. Under certain aspects, each SDU may include an RLC header, a PDCP header, and / or a PDCP SDU. Under certain aspects, the MAC 62 general header may be at the end of the transport block. Under certain aspects, the end of the transport block may include a last bit corresponding to the transport block data. Under certain aspects, the MAC 62 general header may be at the beginning. Petition 870260066479, dated 06 / 07 / 2026, page 63 / 135 59 / 64 of the transport block. According to certain aspects, the beginning of the transport block may include a first bit of the transport block. According to certain aspects, the transport block may include a plurality of MAC subheaders corresponding to the plurality of SDUs. According to certain aspects, at least one of the plurality of MAC subheaders may be separated from the other plurality of MAC subheaders by means of an SDU.

[00130] According to another alternative embodiment, a wireless communications apparatus may include a transceiver; a memory configured to store instructions; and one or more processors coupled communicatively with the transceiver and the memory, wherein the one or more processors are configured to execute the instructions to perform the operations described in the present case, for example, with respect to methods 1200, 1300, 1400, 1500, and / or 1600.

[00131] According to another alternative embodiment, a wireless communications device may include one or more means for carrying out the operations described in this case. Furthermore, another embodiment includes a computer-readable means that includes executable code by means of one or more processors to carry out the operations described in this case, for example, with respect to methods 1200, 1300, 1400, 1500, and / or 1600.

[00132] For the sake of simplicity of exposition, the methods discussed in this case are illustrated and described as a series of actions, it must be Petition 870260066479, dated 06 / 07 / 2026, page 64 / 135 60 / 64 It is appreciated and understood that the method (and other methods related to it) is / are not limited by the order of actions, since some actions may, according to one or more aspects, occur in different orders and / or simultaneously with other actions different from those presented and described in this case. For example, it should be understood that a method may alternatively be represented as a series of interrelated states or events, such as in a state diagram. Furthermore, it may happen that not all actions are necessary to implement a method according to one or more of the aspects described in this case.

[00133] Several aspects of telecommunications systems have been presented with reference to various devices and methods. These devices and methods have been described in this detailed description and illustrated in the attached drawings by means of various blocks, modules, components, circuits, steps, processes, algorithms, and so forth (collectively referred to as elements). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and the design constraints imposed on the system as a whole.

[00134] By way of example, an element, any part of an element, or any combination of elements can be realized with a “processing system” that includes one or more processors. Examples of processors include microprocessors, micro Petition 870260066479, dated 06 / 07 / 2026, page 65 / 135 61 / 64 controllers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, pulsed logic, distinct hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this exposition. One or more processors in the processing system may execute software. Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads, procedures, functions, and so forth, whether it is software, firmware, middleware, microcode, hardware description language, or otherwise.

[00135] Thus, in some respects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored in or encoded as one or more instructions or code in a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other Petition 870260066479, dated 06 / 07 / 2026, page 66 / 135 62 / 64 media that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. As used in this case, disk includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and floppy disk, where discs generally reproduce data magnetically, while floppy disks reproduce data optically with lasers. Combinations of the above should also be included in the scope of computer-readable media.

[00136] Several aspects of a telecommunications system have been presented with reference to an LTE / LTE-A or 5G communication system. As those versed in the art will readily understand, several aspects described throughout this exposition can be extended to other telecommunications systems, network architectures, and communication standards.

[00137] By way of example, several aspects can be extended to other communication systems, such as HSDPA (High Speed ​​Downlink Packet Access), HSUPA (High Speed ​​Uplink Packet Access), HSPA+ (High Speed ​​Packet Access Plus), and TD-CDMA. Various aspects can also be extended to systems employing Long Term Evolution (LTE) (in FDD, TDD, or both modes), LTE-Advanced (LTE-A) (in FDD, TDD, or both modes), CDMA2000, Evolution-Data Optimized (EV-DO), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standard, network architecture, and / or communication standard employed. Petition 870260066479, dated 06 / 07 / 2026, page 67 / 135 63 / 64 will depend on the specific application and the general design constraints imposed on the system.

[00138] It should be understood that the specific order or hierarchy of steps in the methods presented is an illustration of exemplary processes. Based on design preferences, it is understood that the specific order of the hierarchy of steps in the methods may be rearranged. The accompanying method claims the elements present in the various steps in a sample order and is not intended to be limited to the specific order of the hierarchy presented, unless specifically stated therein.

[00139] The preceding description is provided so as to enable anyone skilled in the art to practice the various aspects described in the present case. Various modifications to these aspects will be readily apparent to persons skilled in the art, and the generic principles defined in this context may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects illustrated in the present case, but are to be understood in full scope in harmony with the language of the claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically stated, but rather “one or more.” Unless specifically indicated otherwise, the term “some” refers to one or more. A phrase referring to “at least one” of a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” refers to Petition 870260066479, dated 06 / 07 / 2026, p. 68 / 135 64 / 64 cover: a; b; c; aeb; aec; bec; and a, b, c. All structural and functional equivalents for the elements of the various aspects described throughout this exposition that are known or may hereafter become known to those skilled in the art are expressly included herein by reference and are intended to be encompassed by the claims. Furthermore, nothing set forth herein is intended for the public, whether such disclosure is explicitly listed in the claims. Petition 870260066479, dated 06 / 07 / 2026, p. 69 / 135

Claims

1 / 5 CLAIMS 1. Method (1300) of wireless communications in a user equipment, UE (12), characterized in that it comprises: dividing (1302) a medium access control header, MAC, (56) into a first part and a second part; and sending (1304), from the UE (12) to a network entity (14) in an uplink communication channel, the first part including a pre-subheader (58, 802) located at the beginning of a protocol data unit, PDU, MAC (800) and the second part including a post-subheader (60, 816) located at the end of the PDU MAC (800), wherein the pre-subheader (58, 802) includes data that are necessary for initial processing in the network entity (14) and the post-subheader (60, 816) includes data that take time to generate in the UE (12); And where the first part is sent in the first half and the second part in the second half, the second half is after the first half.

2. A method according to claim 1, characterized in that a presubheader size is at least one of a fixed size known to one or both of the UE or network entity, or a variable size indicated at the beginning of the PDU MAC.

3. Method, according to claim 1, characterized in that the MAC PDU includes a cyclic redundancy check, CRC, according to at least one of: in the pre-subheader, in the first part of the MAC PDU that covers at least the pre-subheader, or by means of a MAC control element.

4. Method according to claim 1, characterized in that the post-subheader includes a header length corresponding to a pointer back to the start of the MAC PDU.

5. Method, according to claim 1, characterized in that the MAC PDU includes a cyclic redundancy check, CRC, according to at least one of: in the post-subheader, in the second part of the MAC PDU that covers at least the post-subheader, or by means of a MAC control element.

6. Method, according to claim 1, characterized in that it further comprises receiving a split acknowledgment (ACK) that includes at least one of a control part or a data part in response to the sending of at least the first part at the beginning of the PDU MAC.

7. Method according to claim 1, characterized in that it further comprises: receiving, on a downlink communication channel from the network entity, a MAC PDU that includes a split MAC header comprising at least two parts, the MAC PDU comprising downlink-specific control elements in at least one of the two parts; and transmitting, on the uplink communication channel to the network entity, a split ACK comprising at least one of a control part or a data part in response to receiving the MAC PDU.

8. Wireless communication apparatus, characterized in that it comprises: means for splitting (40) a medium access control header, MAC, (56) into a first part (58, 802) and a second part (60, 816); and means for sending (40, 102), from the UE (12) to a network entity (14) in an uplink communication channel, the first part including a pre-subheader (58, 802) located at the beginning of a protocol data unit, PDU, MAC (800) and the second part including a post-subheader (60, 816) located at the end of the PDU MAC (800), wherein the pre-subheader (58, 802) includes data that are necessary for initial processing in the network entity (14) and the post-subheader (60, 816) includes data that take time to generate in the UE (12); And where the device is configured to send the first part in a first phase and the second part in a second phase, the second phase is after the first phase.

9. Device according to claim 8, characterized in that the size of the presubheader is at least one of a fixed size known to one or both of the UE or the network entity, or a variable size indicated at the beginning of the PDU MAC.

10. Device according to claim 8, characterized in that the MAC PDU includes a cyclic redundancy check, CRC, according to at least one of: in the pre-subheader, Petition 870240084174, dated 10 / 02 / 2024, page 72 / 78 4 / 5 in the first part of the MAC PDU that covers at least the pre-subheader, or by means of a MAC control element.

11. Device according to claim 8, characterized in that the post-subheader includes a header length corresponding to a pointer backward to the start of the MAC PDU.

12. Device according to claim 8, characterized in that the MAC PDU includes a cyclic redundancy check, CRC, according to at least one of: in the post-subheader, in the second part of the MAC PDU that covers at least the post-subheader, or by means of a MAC control element.

13. Device according to claim 8, characterized in that it is additionally configured to receive a split acknowledgment (ACK) that includes at least one of a control part or a data part in response to the sending of at least the first part at the beginning of the PDU MAC.

14. Device, according to claim 8, characterized in that it further comprises: means for receiving, on a downlink communication channel from the network entity, a MAC PDU that includes a split MAC header comprising at least two parts, the MAC PDU comprising downlink-specific control elements in at least one of the two parts; and means for transmitting, on the uplink communication channel to the network entity, a split ACK comprising at least one of a control part or a data part in response to receiving the MAC PDU.

15. Computer-readable memory characterized in that it comprises instructions stored therein, the instructions being executable by a computer to perform the method steps as defined in any one of claims 1 to 7. Petition 870240084174, dated 02 / 10 / 2024, pp. 74 / 78

Images