Patent ID: 12238039

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

FIG.1is a diagram illustrating an example of a wireless network100, in accordance with the present disclosure. The wireless network100may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network100may include one or more base stations110(shown as a BS110a, a BS110b, a BS110c, and a BS110d), a user equipment (UE)120or multiple UEs120(shown as a UE120a, a UE120b, a UE120c, a UE120d, and a UE120e), and/or other network entities. A base station110is an entity that communicates with UEs120. A base station110(sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and/or a transmission reception point (TRP). Each base station110may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a base station110and/or a base station subsystem serving this coverage area, depending on the context in which the term is used.

A base station110may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs120with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs120with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs120having association with the femto cell (e.g., UEs120in a closed subscriber group (CSG)). A base station110for a macro cell may be referred to as a macro base station. A base station110for a pico cell may be referred to as a pico base station. A base station110for a femto cell may be referred to as a femto base station or an in-home base station. In the example shown inFIG.1, the BS110amay be a macro base station for a macro cell102a, the BS110bmay be a pico base station for a pico cell102b, and the BS110cmay be a femto base station for a femto cell102c. A base station may support one or multiple (e.g., three) cells.

In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a base station110that is mobile (e.g., a mobile base station). In some examples, the base stations110may be interconnected to one another and/or to one or more other base stations110or network nodes (not shown) in the wireless network100through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.

The wireless network100may include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station110or a UE120) and send a transmission of the data to a downstream station (e.g., a UE120or a base station110). A relay station may be a UE120that can relay transmissions for other UEs120. In the example shown inFIG.1, the BS110d(e.g., a relay base station) may communicate with the BS110a(e.g., a macro base station) and the UE120din order to facilitate communication between the BS110aand the UE120d. A base station110that relays communications may be referred to as a relay station, a relay base station, a relay, or the like.

The wireless network100may be a heterogeneous network that includes base stations110of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, or the like. These different types of base stations110may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts) whereas pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller130may couple to or communicate with a set of base stations110and may provide coordination and control for these base stations110. The network controller130may communicate with the base stations110via a backhaul communication link. The base stations110may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.

The UEs120may be dispersed throughout the wireless network100, and each UE120may be stationary or mobile. A UE120may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A UE120may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, and/or any other suitable device that is configured to communicate via a wireless medium.

Some UEs120may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs120may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs120may be considered a Customer Premises Equipment. A UE120may be included inside a housing that houses components of the UE120, such as processor components and/or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks100may be deployed in a given geographic area. Each wireless network100may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs120(e.g., shown as UE120aand UE120e) may communicate directly using one or more sidelink channels (e.g., without using a base station110as an intermediary to communicate with one another). For example, the UEs120may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network. In such examples, a UE120may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station110.

Devices of the wireless network100may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network100may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.

In some aspects, the transmitter network node may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may generate a grouping descriptor, for a transport block, that indicates grouping information for a plurality of protocol data units (PDUs) in the transport block; and transmit the grouping descriptor with the transport block. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, the receiver network node may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may receive a transport block having a grouping descriptor that indicates grouping information for a plurality of PDUs in the transport block; and process the transport block based at least in part on the grouping information. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

As indicated above,FIG.1is provided as an example. Other examples may differ from what is described with regard toFIG.1.

FIG.2is a diagram illustrating an example200of a base station110in communication with a UE120in a wireless network100, in accordance with the present disclosure. The base station110may be equipped with a set of antennas234athrough234t, such as T antennas (T≥1). The UE120may be equipped with a set of antennas252athrough252r, such as R antennas (R≥1).

At the base station110, a transmit processor220may receive data, from a data source212, intended for the UE120(or a set of UEs120). The transmit processor220may select one or more modulation and coding schemes (MCSs) for the UE120based at least in part on one or more channel quality indicators (CQIs) received from that UE120. The base station110may process (e.g., encode and modulate) the data for the UE120based at least in part on the MCS(s) selected for the UE120and may provide data symbols for the UE120. The transmit processor220may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor220may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor230may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems232(e.g., T modems), shown as modems232athrough232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem232. Each modem232may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem232may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The modems232athrough232tmay transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas234(e.g., T antennas), shown as antennas234athrough234t.

At the UE120, a set of antennas252(shown as antennas252athrough252r) may receive the downlink signals from the base station110and/or other base stations110and may provide a set of received signals (e.g., R received signals) to a set of modems254(e.g., R modems), shown as modems254athrough254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem254. Each modem254may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem254may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector256may obtain received symbols from the modems254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor258may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE120to a data sink260, and may provide decoded control information and system information to a controller/processor280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some examples, one or more components of the UE120may be included in a housing284.

The network controller130may include a communication unit294, a controller/processor290, and a memory292. The network controller130may include, for example, one or more devices in a core network. The network controller130may communicate with the base station110via the communication unit294.

One or more antennas (e.g., antennas234athrough234tand/or antennas252athrough252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components ofFIG.2.

On the uplink, at the UE120, a transmit processor264may receive and process data from a data source262and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor280. The transmit processor264may generate reference symbols for one or more reference signals. The symbols from the transmit processor264may be precoded by a TX MIMO processor266if applicable, further processed by the modems254(e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station110. In some examples, the modem254of the UE120may include a modulator and a demodulator. In some examples, the UE120includes a transceiver. The transceiver may include any combination of the antenna(s)252, the modem(s)254, the MIMO detector256, the receive processor258, the transmit processor264, and/or the TX MIMO processor266. The transceiver may be used by a processor (e.g., the controller/processor280) and the memory282to perform aspects of any of the methods described herein (e.g., with reference toFIGS.5-11).

At the base station110, the uplink signals from UE120and/or other UEs may be received by the antennas234, processed by the modem232(e.g., a demodulator component, shown as DEMOD, of the modem232), detected by a MIMO detector236if applicable, and further processed by a receive processor238to obtain decoded data and control information sent by the UE120. The receive processor238may provide the decoded data to a data sink239and provide the decoded control information to the controller/processor240. The base station110may include a communication unit244and may communicate with the network controller130via the communication unit244. The base station110may include a scheduler246to schedule one or more UEs120for downlink and/or uplink communications. In some examples, the modem232of the base station110may include a modulator and a demodulator. In some examples, the base station110includes a transceiver. The transceiver may include any combination of the antenna(s)234, the modem(s)232, the MIMO detector236, the receive processor238, the transmit processor220, and/or the TX MIMO processor230. The transceiver may be used by a processor (e.g., the controller/processor240) and the memory242to perform aspects of any of the methods described herein (e.g., with reference toFIGS.5-11).

The controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform one or more techniques associated with a transport block descriptor for packet grouping, as described in more detail elsewhere herein. In some aspects, the transmitter network node described herein is the base station110, is included in the base station110, or includes one or more components of the base station110shown inFIG.2. In some aspects, the transmitter network node described herein is the UE120, is included in the UE120, or includes one or more components of the UE120shown inFIG.2. In some aspects, the receiver network node described herein is the base station110, is included in the base station110, or includes one or more components of the base station110shown inFIG.2. In some aspects, the receiver network node described herein is the UE120, is included in the UE120, or includes one or more components of the UE120shown inFIG.2. For example, the controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform or direct operations of, for example, process800ofFIG.8, process900ofFIG.9, and/or other processes as described herein. The memory242and the memory282may store data and program codes for the base station110and the UE120, respectively. In some examples, the memory242and/or the memory282may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station110and/or the UE120, may cause the one or more processors, the UE120, and/or the base station110to perform or direct operations of, for example, process800ofFIG.8, process900ofFIG.9, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, the transmitter network node includes means for generating a grouping descriptor, for a transport block, that indicates grouping information for a plurality of PDUs in the transport block; and/or means for transmitting the grouping descriptor with the transport block. In some aspects, the means for the transmitter network node to perform operations described herein may include, for example, one or more of communication manager140, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246. In some aspects, the means for the transmitter network node to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

In some aspects, the receiver network node includes means for receiving a transport block having a grouping descriptor that indicates grouping information for a plurality of PDUs in the transport block; and/or means for processing the transport block based at least in part on the grouping information. In some aspects, the means for the receiver network node to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246. In some aspects, the means for the receiver network node to perform operations described herein may include, for example, one or more of communication manager150, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

While blocks inFIG.2are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor264, the receive processor258, and/or the TX MIMO processor266may be performed by or under the control of the controller/processor280.

As indicated above,FIG.2is provided as an example. Other examples may differ from what is described with regard toFIG.2.

FIG.3is a diagram illustrating an example300of a user plane protocol stack and a control plane protocol stack for a base station110and a core network in communication with a UE120, in accordance with the present disclosure.

On the user plane, the UE120and the BS110may include respective physical (PHY) layers, medium access control (MAC) layers, radio link control (RLC) layers, packet data convergence protocol (PDCP) layers, and service data adaptation protocol (SDAP) layers. A user plane function may handle transport of user data between the UE120and the BS110. On the control plane, the UE120and the BS110may include respective radio resource control (RRC) layers. Furthermore, the UE120may include a non-access stratum (NAS) layer in communication with an NAS layer of an access and management mobility function (AMF). The AMF may be associated with a core network associated with the BS110, such as a 5G core network (5GC) or a next-generation radio access network (NG-RAN). A control plane function may handle transport of control information between the UE and the core network. Generally, a first layer is referred to as higher than a second layer if the first layer is further from the PHY layer than the second layer. For example, the PHY layer may be referred to as a lowest layer, and the SDAP/PDCP/RLC/MAC layer may be referred to as higher than the PHY layer and lower than the RRC layer. An application (APP) layer, not shown inFIG.3, may be higher than the SDAP/PDCP/RLC/MAC layer. In some cases, an entity may handle the services and functions of a given layer (e.g., a PDCP entity may handle the services and functions of the PDCP layer), though the description herein refers to the layers themselves as handling the services and functions.

The RRC layer may handle communications related to configuring and operating the UE120, such as: broadcast of system information related to the access stratum (AS) and the NAS; paging initiated by the 5GC or the NG-RAN; establishment, maintenance, and release of an RRC connection between the UE and the NG-RAN, including addition, modification, and release of carrier aggregation, as well as addition, modification, and release of dual connectivity; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (e.g., handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); quality of service (QoS) management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; and NAS message transfer between the NAS layer and the lower layers of the UE120. The RRC layer is frequently referred to as Layer 3 (L3).

The SDAP layer, PDCP layer, RLC layer, and MAC layer may be collectively referred to as Layer 2 (L2). Thus, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. On the transmitting side (e.g., if the UE120is transmitting an uplink communication or the BS110is transmitting a downlink communication), the SDAP layer may receive a data flow in the form of a QoS flow. A QoS flow is associated with a QoS identifier, which identifies a QoS parameter associated with the QoS flow, and a QoS flow identifier (QFI), which identifies the QoS flow. Policy and charging parameters are enforced at the QoS flow granularity. A QoS flow can include one or more service data flows (SDFs), so long as each SDF of a QoS flow is associated with the same policy and charging parameters. In some aspects, the RRC/NAS layer may generate control information to be transmitted and may map the control information to one or more radio bearers for provision to the PDCP layer.

The SDAP layer, or the RRC/NAS layer, may map QoS flows or control information to radio bearers. Thus, the SDAP layer may be said to handle QoS flows on the transmitting side. The SDAP layer may provide the QoS flows to the PDCP layer via the corresponding radio bearers. The PDCP layer may map radio bearers to RLC channels. The PDCP layer may handle various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), transfer of user data, reordering and duplicate detection (if in-order delivery to layers above the PDCP layer is required), PDCP PDU routing (in case of split bearers), retransmission of PDCP service data units (SDUs), ciphering and deciphering, PDCP SDU discard (e.g., in accordance with a timer, as described elsewhere herein), PDCP re-establishment and data recovery for RLC acknowledged mode (AM), and duplication of PDCP PDUs. The PDCP layer may handle similar services and functions on the control plane, including sequence numbering, ciphering, deciphering, integrity protection, transfer of control plane data, duplicate detection, and duplication of PDCP PDUs.

The PDCP layer may provide data, in the form of PDCP PDUs, to the RLC layer via RLC channels. The RLC layer may handle transfer of upper layer PDUs to the MAC and/or PHY layers, sequence numbering independent of PDCP sequence numbering, error correction via automatic repeat requests (ARQ), segmentation and re-segmentation, reassembly of an SDU, RLC SDU discard, and RLC re-establishment.

The RLC layer may provide data, mapped to logical channels, to the MAC layer. The services and functions of the MAC layer include mapping between logical channels and transport channels (used by the PHY layer as described below), multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks delivered to/from the physical layer on transport channels, scheduling information reporting, error correction through hybrid ARQ (HARQ), priority handling between UEs by means of dynamic scheduling, priority handling between logical channels of one UE by means of logical channel prioritization, and padding. The logical channel(s) may be identified by a logical channel identifier (LCID) or an extended logical channel identifier (eLCID).

The MAC layer may package data from logical channels into transport blocks and may provide the transport blocks on one or more transport channels to the PHY layer. The PHY layer may handle various operations relating to transmission of a data signal, as described in more detail in connection withFIG.2. The PHY layer is frequently referred to as Layer 1 (L1).

On the receiving side (e.g., if the UE120is receiving a downlink communication or the BS110is receiving an uplink communication), the operations may be similar to those described for the transmitting side, but reversed. For example, the PHY layer may receive transport blocks and may provide the transport blocks on one or more transport channels to the MAC layer. The MAC layer may map the transport channels to logical channels and may provide data to the RLC layer via the logical channels. The RLC layer may map the logical channels to RLC channels and may provide data to the PDCP layer via the RLC channels. The PDCP layer may map the RLC channels to radio bearers and may provide data to the SDAP layer or the RRC/NAS layer via the radio bearers.

Data may be passed between the layers in the form of PDUs and SDUs. An SDU is a unit of data that has been passed from a layer or sublayer to a lower layer. For example, the PDCP layer may receive a PDCP SDU. A given layer may then encapsulate the unit of data into a PDU and may pass the PDU to a lower layer. For example, the PDCP layer may encapsulate the PDCP SDU into a PDCP PDU and may pass the PDCP PDU to the RLC layer. The RLC layer may receive the PDCP PDU as an RLC SDU, may encapsulate the RLC SDU into an RLC PDU, and so on. In effect, the PDU carries the SDU as a payload.

As described in more detail below, a transport block having a plurality of PDUs may include a grouping descriptor. The grouping descriptor may contain grouping information for at least a portion of the plurality of PDUs and may reduce processing resources and power requirements at the receiver network node.

As indicated above,FIG.3is provided as an example. Other examples may differ from what is described with regard toFIG.3.

FIG.4is a diagram illustrating an example400of a transport block, in accordance with the present disclosure. The transport block may be include one or more PDUs (e.g., MAC PDUs). In some cases, the MAC PDU may include one or more MAC subPDUs. Each MAC subPDU may include one of the following:

a MAC subheader only (including padding);

a MAC subheader and a MAC SDU;

a MAC subheader and a MAC control element (CE); or

a MAC subheader and padding.

The MAC SDUs may be of variable sizes. In some cases, each MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

In some cases, a MAC subheader (except for a fixed sized MAC CE, padding, and MAC SDU containing UL control channel) may include the header fields R/F/LCID/(eLCID)/L. Alternatively, a MAC subheader for fixed sized MAC CE, padding, and MAC SDU containing UL control channel may include the two header fields R/LCID/(eLCID).

In some cases, MAC CEs may be grouped together. In some cases, DL MAC subPDU(s) with MAC CE(s) may be placed before any MAC subPDU with MAC SDU or MAC subPDU with padding. In some cases, UL MAC subPDU(s) with MAC CE(s) may be placed after all of the MAC subPDU(s) with MAC SDU, and before the MAC subPDU with padding in the MAC PDU. In some cases, the size of the padding may be zero (e.g., there may be no padding). In some cases, a maximum of one MAC PDU may be transmitted per transport block, and per MAC entity.

In some cases, within a transport block, each PDCP SDU may be prefixed with a PDCP header, an RLC header, or a MAC header to include information used by each layer on both the transmitter side (e.g., a transmitter network node) and the receiver side (e.g., a receiver network node). In some cases, each transport block may include a large number of PDCP SDUs, depending on the transport block size. For example, for FR1 scheduling with a transport block size of 200 kilobytes, and a PDCP PDU length of 1500 bytes, a transport block received by the receiver network node may contain approximately one hundred thirty PDUs.

For each PDU that is received, the receiver network node may perform multiple functions, such as error detection, segmentation and reassembly of RLC SDUs, duplicate detection and discarding, and/or re-segmentation of RLC SDU segments. Additionally, or alternatively, the receiver network node may perform PDU reordering and duplicate discarding, and deciphering and integrity verification, when ciphering and integrity protection are enabled. L2 operations associated with traversing each PDU in the transport block may require a large amount of processing resources and power resources for the receiver network node. Thus, the PDU transmission may have a negative impact on receiver processing load and power consumption, which is not desired behavior, especially in NR and LIE peak throughput use cases.

Techniques and apparatuses are described herein for a transport block descriptor for packet grouping. In some aspects, a transmitter network node may generate one or more grouping descriptors for a transport block. The grouping descriptor may indicate grouping information for a plurality of PDUs in the transport block. For example, the grouping descriptor may include information for a plurality of PDUs having similar characteristics, such as MAC PDUs, or MAC SDUs, among other examples. The transmitter network node may transmit the grouping descriptor with the transport block to a receiver network node. For example, the transmitter network node may prepend the grouping descriptor to the transport block. The receiver network node may receive the transport block and the grouping descriptor, and the receiver network node may process the transport block based at least in part on the grouping information.

As described above, processing each PDU in the transport block may require a large number of processing resources and power resources by the receiver network node. Adding the grouping descriptor to the transport block, such as by prepending the grouping descriptor to the transport block, may decrease the number of processing resources and the power consumption by the receiver network node. For example, the receiver network node may receive the transport block having the grouping identifier, and may only need to process the grouping identifier, and not the individual PDUs themselves, for at least a portion of the PDUs in the transport block that are identified in the grouping identifier. Thus, less processing resources may be needed, and power consumption may be reduced.

As indicated above,FIG.4is provided as an example. Other examples may differ from what is described with regard toFIG.4.

FIG.5is a diagram illustrating an example500of a transport block descriptor for packet grouping, in accordance with the present disclosure. A transmitter network node, such as the transmitter network node505, may communicate with a receiver network node, such as the receiver network node510. The transmitter network node505may be implemented in a UE, such as the UE120, or in a base station, such as the base station110. Similarly, the receiver network node510may be implemented in a UE, such as the UE120, or in a base station, such as the base station110.

As shown in connection with reference number515, the transmitter network node505and the receiver network node510may communicate capability information. The capability information may indicate whether a particular network node supports the grouping descriptor capability. For example, the transmitter network node505may transmit, and the receiver network node510may receive, an indication that the transmitter network node505supports the grouping descriptor capability. Additionally, or alternatively, the receiver network node510may transmit, and the transmitter network node505may receive, an indication that the receiver network node510supports the grouping descriptor capability.

As shown in connection with reference number520, the transmitter network node505may generate a grouping descriptor that indicates grouping information for a plurality of PDUs in a transport block. The transmitter network node505may be configured to determine the grouping information based at least in part on one or more characteristics of the plurality of PDUs in the transport block. For example, the grouping descriptor may indicate first grouping information for a first group of PDUs having a first characteristic (e.g., MAC CE), and second grouping information for a second group of PDUs having a second characteristic (e.g., PDCP).

In some aspects, the grouping descriptor may include multiple portions. For example, the grouping descriptor may include an LCID subheader portion and a payload portion that includes grouping information that describes the transport block. The transmitter network node505may use an LCID value having a variable length. In some aspects, the grouping descriptor may include some or all of the following information:

the total transport block byte length covered by the grouping descriptor (if the entire transport block is parsed, this may be the entire length of the transport block);

the number of groups; and

information for each group of the number of groups.

In some aspects, the grouping descriptor may apply to different PDU types. For example, one or more of the MAC CEs (e.g., all of the MAC CEs) may be aggregated into a group. Additionally, or alternatively, one or more MAC SDUs having the same logical channel (e.g., all MAC SDUs having the same logical channel) may be aggregated into a group. In some aspects, different PDU types may be split into separate groups. For example, the RLC/PDCP data PDU may be included a first group, and the control PDU may be included a second group).

In some aspects, a group may be determined based at least in part on a MAC CE, padding, control PDUs, and/or segments. For example, grouping information may be generated if the PDUs are MAC CEs.

In some aspects, a group may be determined based at least in part on one or more RLC/PDCP SDUs. For example, one or more RLC PDUs that have consecutive sequence numbers may be aggregated into a group. Additionally, or alternatively, one or more PDCP PDUs that have consecutive sequence numbers may be aggregated into a group. In some aspects, an RLC or PDCP header may contain one or more fields that indicate whether the current PDU is a data PDU or a control PDU. The sequence number (SN) field may indicate the sequence number of the current PDU. In some aspects, the receiver may use the SN to determine whether the PDU has been received or not. In some aspects, the RLC control PDU may be included a separate group than the RLC data PDU. Additionally, or alternatively, the PDCP control PDU may be included in a separate group than the PDCP data PDU.

In some aspects, the grouping descriptor may be included as part of the existing grant. For example, the grouping descriptor may be included as part of an existing physical downlink shared channel (PDSCH) grant. The PDSCH grant size may be based at least in part on the MCS, the number of resource blocks, and/or the number of layers, among other examples. The transmitter network node505may be configured to dynamically adjust the size of the grouping descriptor based at least in part on the grant utilization efficiency (e.g., based at least in part on the traffic pattern).

In some cases, the transmitter network node505may be configured to generate the grouping descriptor during a building of the transport block. Additional details associated with the grouping descriptor are provided below in connection withFIGS.6-7.

As shown in connection with reference number525, the transmitter network node505may transmit, and the receiver network node510may receive, the transport block with the grouping descriptor. The transmitter network node505may be configured to add the grouping descriptor to the transport block. In some aspects, the transmitter network node505may prepend the grouping descriptor to a beginning of the transport block prior to transmitting the transport block.

In some aspects, the transmitter network node505may determine that a size of the grouping descriptor is above a particular size (e.g., a threshold size), or that a number of groups in the grouping descriptor is above a particular number (e.g., a group number threshold). For example, the transmitter network node505may determine that the grouping descriptor is larger than a certain number of bytes, or that the grouping descriptor is larger a certain percentage of bytes as compared to the configured grant size. Additionally, or alternatively, the transmitter network node505may determine that the grouping descriptor has a large number of groups, as compared to the number of PDUs in the transport block. In some aspects, the transmitter network node505may generate and/or transmit a grouping descriptor that includes only a portion of the grouping information, based at least in part on determining that the grouping descriptor is too large or has too many groups. In some aspects, the transmitter network node505may determine not to transmit any of the grouping information and may omit the grouping descriptor entirely, based at least in part on determining that the grouping descriptor is too large or has too many groups.

As shown in connection with reference number530, the receiver network node510may process the transport block based at least in part on the grouping information. In some aspects, the receiver network node510may be configured to process only the grouping information, contained in the grouping descriptor, for the PDUs identified in the grouping descriptor. For example, the receiver network node510may receive a transport block having PDUs 1, 2, 3, 4, and 5. The grouping descriptor may include grouping information for the PDUs 1, 2, and 3. For example, the grouping descriptor may indicate that the PDUs 1, 2, and 3 are MAC CEs. Thus, the receiver network node510may process the grouping information, contained in the grouping descriptor, for the PDUs 1, 2, and 3. The receiver network node510may not need to process the content of the individual PDUs 1, 2, and 3. The receiver network node510may determine to process only the grouping information for the PDUs 1, 2, and 3, and not to process the data of the individual PDUs 1, 2, and 3, since the information needed from those packets is included in the grouping descriptor. In contrast, since grouping information does not exist for PDUs 4 and 5, the receiver network node510may process the contents of PDUs 4 and 5 separately or individually. For example, PDU 4 may have ten sub-PDUs, and PDU 5 may have five sub-PDUs. The receiver network node510may need to process each of the ten sub-PDUs for PDU 4, and each of the five sub-PDUs for PDU 5.

As described above, processing each PDU in the transport block may require a large number of processing resources and power resources by the receiver network node. Adding the grouping descriptor to the transport block, such as by prepending the grouping descriptor to the transport block, may decrease the number of processing resources and the power consumption by the receiver network node. For example, the receiver network node may receive the transport block having the grouping identifier, and may only need to process the grouping identifier, and not the individual PDUs themselves, for at least a portion of the PDUs in the transport block that are identified in the grouping identifier. Thus, less processing resources may be needed, and power consumption may be reduced. This may be particularly true in high throughput scenarios and when the number of carriers per slot is high (e.g., for both FR1 and FR2).

As indicated above,FIG.5is provided as an example. Other examples may differ from what is described with regard toFIG.5.

FIG.6is a diagram illustrating an example600of a transport block having a grouping descriptor, in accordance with the present disclosure.

As described above, the transmitter network node505may be configured to generate a grouping descriptor that includes information associated with a plurality of PDUs of a transport block. The transmitter network node505may prepend the grouping descriptor to the transport block and may transmit the transport block having the grouping descriptor to the receiver network node510. The grouping descriptor may be a MAC PDU descriptor or a MAC subPDU descriptor. The grouping descriptor is shown in the example600as the shaded portion of the transport block.

In some cases, a portion (e.g., a first portion) of the grouping descriptor may include a header, such as an LCID subheader. The header may be a predefined header, such as a predefined LCID subheader, or any header that can be used to identify the grouping descriptor.

In some cases, a portion (e.g., a second portion) of the grouping descriptor may include the grouping information associated with one or more groups of PDUs in the transport block. For example, the grouping information may include any of the information described above in connection withFIG.5and/or the information described below in connection withFIG.7.

As indicated above,FIG.6is provided as an example. Other examples may differ from what is described with regard toFIG.6.

FIG.7is a diagram illustrating examples700and710of grouping information for a grouping descriptor, in accordance with the present disclosure.

In some cases, as shown in example700, the grouping descriptor may include grouping information per octet, and may include one or more of the fields below:

LCID: the LCID field may identify the logical channel instance of the corresponding MAC SDU, the type of the corresponding MAC CE, or the padding. In some cases, there may be one LCID field per MAC subheader. The size of the LCID field may be 6 bits. If the LCID field is set to 34, one additional octet may be present, in the MAC subheader containing the eLCID field, that follows the octet containing LCID field. If the LCID field is set to 33, two additional octets may be present in the MAC subheader containing the eLCID field. The two additional octets may follow the octet containing the LCID field.

eLCID: the eLCID field may identify the logical channel instance of the corresponding MAC SDU, or the type of the corresponding MAC CE. The size of the eLCID field may be either 8 bits or 16 bits.

L: the length field may indicate the length of the corresponding MAC SDU or variable-sized MAC CE (e.g., in bytes). In some cases, there may be one L field per MAC subheader, except for subheaders corresponding to fixed-sized MAC CEs, padding, and MAC SDUs containing UL control channel. The size of the L field may be indicated by the F field.

F: the format field may indicate the size of the length field. There may be one F field per MAC subheader, except for subheaders corresponding to fixed-sized MAC CEs, padding, and MAC SDUs containing UL control channel. The size of the F field may be 1 bit. The value 0 may indicate 8 bits of the length field. The value 1 may indicate 16 bits of the length field.

R: the reserved bit may be initially set to zero.

Descriptor payload: the descriptor payload may include some or all of the example information shown in the table below. In some cases, the descriptor payload may include other information that is not included in the table below. The following table is provided for the purposes of an example only and is not intended to limit the information that can be included in the descriptor payload.

Example of descriptor payloadDescriptorNumber of bytes occupied by the descriptorlengthStatusStatus fields indicating the descriptor status (e.g., in caseof error condition)Total bytesNumber of total bytes of transport block contents in thedescriptor. Includes entire transport block size sincewhole transport block is covered by the descriptor.Num groupsNumber of groups in the descriptorPer groupPer group information descriptioninformation

In some cases, as shown in example710, the grouping descriptor may include grouping information per group, or per word, and may include one or more of the fields below:

total_bytes: the total_bytes field indicates the total number of bytes in the grouping descriptor.

num_groups: the number of groups field indicates the number of groups in the grouping descriptor.

Num: the number field indicates a particular group of the number of groups in the grouping descriptor.

Length: the length field indicates the length of the particular group (e.g., in bytes).

The per group information may include some or all of the example information shown in the table below. In some cases, the per group information may include other information that is not included in the table. The following chart is provided for the purposes of an example only, and the chart is not intended to limit the information that can be included in the per group information.

Example of per group informationMAC CEIndicates current group is MAC control elementRLC ControlIndicates current group is RLC control PDURLC SegmentIndicates current group is RLC segmentPDCP ControlIndicates current group is PDCP control PDUDataIndicates current group contains IP dataNumNumber of MAC subPDUs within current groupLengthLength of each subPDU

As indicated above,FIG.7is provided as an example. Other examples may differ from what is described with regard toFIG.7.

FIG.8is a diagram illustrating an example process800performed, for example, by a transmitter network node, in accordance with the present disclosure. Example process800is an example where the transmitter network node (e.g., transmitter network node505) performs operations associated with a transport block descriptor for packet grouping.

As shown inFIG.8, in some aspects, process800may include generating a grouping descriptor, for a transport block, that indicates grouping information for a plurality of PDUs in the transport block (block810). For example, the transmitter network node (e.g., using communication manager140and/or generation component1008, depicted inFIG.10) may generate a grouping descriptor, for a transport block, that indicates grouping information for a plurality of PDUs in the transport block, as described above.

As further shown inFIG.8, in some aspects, process800may include transmitting the grouping descriptor with the transport block (block820). For example, the transmitter network node (e.g., using communication manager140and/or transmission component1004, depicted inFIG.10) may transmit the grouping descriptor with the transport block, as described above.

Process800may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, process800includes determining the grouping information based at least in part on one or more characteristics of the plurality of PDUs in the transport block.

In a second aspect, alone or in combination with the first aspect, the grouping descriptor indicates first grouping information for a first group of PDUs having a first characteristic, and second grouping information for a second group of PDUs having a second characteristic.

In a third aspect, alone or in combination with one or more of the first and second aspects, process800includes adding the grouping descriptor to the transport block prior to transmitting the transport block.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process800includes prepending the grouping descriptor to a beginning of the transport block.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, generating the grouping descriptor comprises generating the grouping descriptor based at least in part on building the transport block.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process800includes receiving capability information indicating whether a receiver network node supports a grouping descriptor capability.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the grouping descriptor indicates whether a group includes MAC CE PDUs, radio link control PDUs, packet data convergence protocol PDUs, AM messages, or UM messages.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the grouping descriptor indicates a length of a group of PDUs, a number of groups of PDUs included in the transport block, and information for each of the groups of PDUs in the transport block.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the grouping descriptor includes a LCID portion and a payload portion.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the LCID portion includes a predefined LCID, and the payload portion includes the grouping information for one or more groups of PDUs in the transport block.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the grouping descriptor is included in a grant size for the transport block.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, process800includes determining that a size of the grouping descriptor is above a size threshold, or that a number of groups in the grouping descriptor is above a group number threshold, wherein transmitting the grouping descriptor comprises transmitting a grouping descriptor having only a portion of the grouping information, or none of the grouping information.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the grouping descriptor includes grouping information for only a portion of the PDUs, of the plurality of PDUs, in the transport block.

AlthoughFIG.8shows example blocks of process800, in some aspects, process800may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.8. Additionally, or alternatively, two or more of the blocks of process800may be performed in parallel.

FIG.9is a diagram illustrating an example process900performed, for example, by a receiver network node, in accordance with the present disclosure. Example process900is an example where the receiver network node (e.g., receiver network node510) performs operations associated with a transport block descriptor for packet grouping.

As shown inFIG.9, in some aspects, process900may include receiving a transport block having a grouping descriptor that indicates grouping information for a plurality of PDUs in the transport block (block910). For example, the receiver network node (e.g., using communication manager150and/or reception component1102, depicted inFIG.11) may receive a transport block having a grouping descriptor that indicates grouping information for a plurality of PDUs in the transport block, as described above.

As further shown inFIG.9, in some aspects, process900may include processing the transport block based at least in part on the grouping information (block920). For example, the receiver network node (e.g., using communication manager150and/or processing component1108, depicted inFIG.11) may process the transport block based at least in part on the grouping information, as described above.

Process900may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, processing the transport block based at least in part on the grouping information includes processing only the grouping information, and not the PDUs, for the PDUs identified in the grouping descriptor.

In a second aspect, alone or in combination with the first aspect, the grouping descriptor indicates first grouping information for a first group of PDUs having a first characteristic, and second grouping information for a second group of PDUs having a second characteristic.

In a third aspect, alone or in combination with one or more of the first and second aspects, the grouping descriptor is prepended to a beginning of the transport block.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process900includes transmitting capability information indicating whether the receiver network node supports a grouping descriptor capability.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the grouping descriptor indicates whether a group includes MAC CE PDUs, radio link control PDUs, packet data convergence protocol PDUs, AM messages, or UM messages.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the grouping descriptor indicates a length of a group of PDUs, a number of groups of PDUs included in the transport block, and information for each of the groups of PDUs in the transport block.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the grouping descriptor includes a LCID portion and a payload portion.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the LCID portion includes a predefined LCID, and the payload portion includes the grouping information for one or more groups of PDUs in the transport block.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the grouping descriptor is included in a grant size for the transport block.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the grouping descriptor includes grouping information for only a portion of the PDUs, of the plurality of PDUs, in the transport block.

AlthoughFIG.9shows example blocks of process900, in some aspects, process900may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.9. Additionally, or alternatively, two or more of the blocks of process900may be performed in parallel.

FIG.10is a diagram of an example apparatus1000for wireless communication. The apparatus1000may be a transmitter network node, or a transmitter network node may include the apparatus1000. The transmitter network node may be implemented as a UE, such as the UE120, or as a base station, such as the base station110. In some aspects, the apparatus1000includes a reception component1002and a transmission component1004, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1000may communicate with another apparatus1006(such as a UE, a base station, or another wireless communication device) using the reception component1002and the transmission component1004. As further shown, the apparatus1000may include the communication manager140. The communication manager140may include one or more of a generation component1008, a determination component1010, or an adding component1012, among other examples.

In some aspects, the apparatus1000may be configured to perform one or more operations described herein in connection withFIGS.5-7. Additionally, or alternatively, the apparatus1000may be configured to perform one or more processes described herein, such as process800ofFIG.8. In some aspects, the apparatus1000and/or one or more components shown inFIG.10may include one or more components of the transmitter network node described in connection withFIG.2. Additionally, or alternatively, one or more components shown inFIG.10may be implemented within one or more components described in connection withFIG.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The reception component1002may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus1006. The reception component1002may provide received communications to one or more other components of the apparatus1000. In some aspects, the reception component1002may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus1000. In some aspects, the reception component1002may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the transmitter network node described in connection withFIG.2.

The transmission component1004may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1006. In some aspects, one or more other components of the apparatus1000may generate communications and may provide the generated communications to the transmission component1004for transmission to the apparatus1006. In some aspects, the transmission component1004may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1006. In some aspects, the transmission component1004may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the transmitter network node described in connection withFIG.2. In some aspects, the transmission component1004may be co-located with the reception component1002in a transceiver.

The generation component1008may generate a grouping descriptor, for a transport block, that indicates grouping information for a plurality of PDUs in the transport block. The transmission component1004may transmit the grouping descriptor with the transport block.

The determination component1010may determine the grouping information based at least in part on one or more characteristics of the plurality of PDUs in the transport block.

The adding component1012may add the grouping descriptor to the transport block prior to transmitting the transport block.

The adding component1012may prepend the grouping descriptor to a beginning of the transport block.

The reception component1002may receive capability information indicating whether a receiver network node supports a grouping descriptor capability.

The determination component1010may determine that a size of the grouping descriptor is above a size threshold, or that a number of groups in the grouping descriptor is above a group number threshold, wherein transmitting the grouping descriptor comprises transmitting a grouping descriptor having only a portion of the grouping information, or none of the grouping information.

The number and arrangement of components shown inFIG.10are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown inFIG.10. Furthermore, two or more components shown inFIG.10may be implemented within a single component, or a single component shown inFIG.10may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown inFIG.10may perform one or more functions described as being performed by another set of components shown inFIG.10.

FIG.11is a diagram of an example apparatus1100for wireless communication. The apparatus1100may be a receiver network node, or a receiver network node may include the apparatus1100. The receiver network node may be implemented as a UE, such as the UE120, or as a base station, such as the base station110. In some aspects, the apparatus1100includes a reception component1102and a transmission component1104, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1100may communicate with another apparatus1106(such as a UE, a base station, or another wireless communication device) using the reception component1102and the transmission component1104. As further shown, the apparatus1100may include the communication manager150. The communication manager150may include a processing component1108, among other examples.

In some aspects, the apparatus1100may be configured to perform one or more operations described herein in connection withFIGS.5-7. Additionally, or alternatively, the apparatus1100may be configured to perform one or more processes described herein, such as process900ofFIG.9. In some aspects, the apparatus1100and/or one or more components shown inFIG.11may include one or more components of the receiver network node described in connection withFIG.2. Additionally, or alternatively, one or more components shown inFIG.11may be implemented within one or more components described in connection withFIG.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The reception component1102may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus1106. The reception component1102may provide received communications to one or more other components of the apparatus1100. In some aspects, the reception component1102may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus1100. In some aspects, the reception component1102may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the receiver network node described in connection withFIG.2.

The transmission component1104may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1106. In some aspects, one or more other components of the apparatus1100may generate communications and may provide the generated communications to the transmission component1104for transmission to the apparatus1106. In some aspects, the transmission component1104may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1106. In some aspects, the transmission component1104may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the receiver network node described in connection withFIG.2. In some aspects, the transmission component1104may be co-located with the reception component1102in a transceiver.

The reception component1102may receive a transport block having a grouping descriptor that indicates grouping information for a plurality of PDUs in the transport block. The processing component1108may process the transport block based at least in part on the grouping information.

The transmission component1104may transmit capability information indicating whether the receiver network node supports a grouping descriptor capability.

The number and arrangement of components shown inFIG.11are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown inFIG.11. Furthermore, two or more components shown inFIG.11may be implemented within a single component, or a single component shown inFIG.11may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown inFIG.11may perform one or more functions described as being performed by another set of components shown inFIG.11.

The following provides an overview of some Aspects of the present disclosure:

Aspect 1: A method of wireless communication performed by a transmitter network node, comprising: generating a grouping descriptor, for a transport block, that indicates grouping information for a plurality of protocol data units (PDUs) in the transport block; and transmitting the grouping descriptor with the transport block.

Aspect 2: The method of Aspect 1, further comprising determining the grouping information based at least in part on one or more characteristics of the plurality of PDUs in the transport block.

Aspect 3: The method of any of Aspects 1-2, wherein the grouping descriptor indicates first grouping information for a first group of PDUs having a first characteristic, and second grouping information for a second group of PDUs having a second characteristic.

Aspect 4: The method of any of Aspects 1-3, further comprising adding the grouping descriptor to the transport block prior to transmitting the transport block.

Aspect 5: The method of any of Aspects 1-4, further comprising prepending the grouping descriptor to a beginning of the transport block.

Aspect 6: The method of any of Aspects 1-5, wherein generating the grouping descriptor comprises generating the grouping descriptor based at least in part on building the transport block.

Aspect 7: The method of any of Aspects 1-6, further comprising receiving capability information indicating whether a receiver network node supports a grouping descriptor capability.

Aspect 8: The method of any of Aspects 1-7, wherein the grouping descriptor indicates whether a group includes medium access control (MAC) control element PDUs, radio link control PDUs, packet data convergence protocol PDUs, acknowledgement mode (AM) messages, or unacknowledgement mode (UM) messages.

Aspect 9: The method of any of Aspects 1-8, wherein the grouping descriptor indicates a length of a group of PDUs, a number of groups of PDUs included in the transport block, and information for each of the groups of PDUs in the transport block.

Aspect 10: The method of any of Aspects 1-9, wherein the grouping descriptor includes a logical channel identifier (LCID) portion and a payload portion.

Aspect 11: The method of Aspect 10, wherein the LCID portion includes a predefined LCID, and the payload portion includes the grouping information for one or more groups of PDUs in the transport block.

Aspect 12: The method of any of Aspects 1-11, wherein the grouping descriptor is included in a grant size for the transport block.

Aspect 13: The method of any of Aspects 1-12, further comprising determining that a size of the grouping descriptor is above a size threshold, or that a number of groups in the grouping descriptor is above a group number threshold, wherein transmitting the grouping descriptor comprises transmitting a grouping descriptor having only a portion of the grouping information, or none of the grouping information.

Aspect 14: The method of any of Aspects 1-13, wherein the grouping descriptor includes grouping information for only a portion of the PDUs, of the plurality of PDUs, in the transport block.

Aspect 15: A method of wireless communication performed by a receiver network node, comprising: receiving a transport block having a grouping descriptor that indicates grouping information for a plurality of protocol data units (PDUs) in the transport block; and processing the transport block based at least in part on the grouping information.

Aspect 16: The method of Aspect 15, wherein processing the transport block based at least in part on the grouping information includes processing only the grouping information, and not the PDUs, for the PDUs identified in the grouping descriptor.

Aspect 17: The method of any of Aspects 15-16, wherein the grouping descriptor indicates first grouping information for a first group of PDUs having a first characteristic, and second grouping information for a second group of PDUs having a second characteristic.

Aspect 18: The method of any of Aspects 15-17, wherein the grouping descriptor is prepended to a beginning of the transport block.

Aspect 19: The method of any of Aspects 15-18, further comprising transmitting capability information indicating whether the receiver network node supports a grouping descriptor capability.

Aspect 20: The method of any of Aspects 15-19, wherein the grouping descriptor indicates whether a group includes medium access control (MAC) control element PDUs, radio link control PDUs, packet data convergence protocol PDUs, acknowledgement mode (AM) messages, or unacknowledgement mode (UM) messages.

Aspect 21: The method of any of Aspects 15-20, wherein the grouping descriptor indicates a length of a group of PDUs, a number of groups of PDUs included in the transport block, and information for each of the groups of PDUs in the transport block.

Aspect 22: The method of any of Aspects 15-21, wherein the grouping descriptor includes a logical channel identifier (LCID) portion and a payload portion.

Aspect 23: The method of Aspect 22, wherein the LCID portion includes a predefined LCID, and the payload portion includes the grouping information for one or more groups of PDUs in the transport block.

Aspect 24: The method of any of Aspects 15-23, wherein the grouping descriptor is included in a grant size for the transport block.

Aspect 25: The method of any of Aspects 15-24, wherein the grouping descriptor includes grouping information for only a portion of the PDUs, of the plurality of PDUs, in the transport block.

Aspect 26: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-14.

Aspect 27: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-14.

Aspect 28: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-14.

Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-14.

Aspect 30: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-14.

Aspect 31: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 15-25.

Aspect 32: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 15-25.

Aspect 33: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 15-25.

Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 15-25.

Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 15-25.

The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, 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” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).