Network coding for packet data convergence protocol communications

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a transmitting device may obtain a plurality of packet data convergence protocol (PDCP) packets. The transmitting device may generate a plurality of source symbols according to applying forward error correction coding to the plurality of PDCP packets, wherein the plurality of source symbols are non-segmented out-coded source symbols. A transmitting device may transmit a plurality of source symbols. Numerous other aspects are described.

Description

Network decoding for Packet Data Convergence Protocol (PDC) communication

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 583,472, filed September 18, 2023, entitled “NETWORK CODING FOR PACKET DATA CONVERGENCE PROTOCOL COMMUNICATIONS,” and U.S. Non-Provisional Patent Application No. 18 / 887,862, filed September 17, 2024, entitled “NETWORK CODING FOR PACKET DATA CONVERGENCE PROTOCOL COMMUNICATIONS,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication, and specifically to techniques and apparatus for network decoding of packet data convergence protocol communications. Background Technology

[0004] Related technical descriptions

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0006] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. UEs may communicate with network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links).

[0007] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, or global level. New Radio (NR) (also known as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink and CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation. Summary of the Invention

[0008] In some aspects, a method of wireless communication performed by a transmitting device includes: obtaining a plurality of Packet Data Convergence Protocol (PDCP) packets; generating a plurality of source symbols by applying forward error correction coding to the plurality of PDCP packets, wherein the plurality of source symbols are non-segmented externally decoded source symbols; and transmitting the plurality of source symbols by a radio link control layer.

[0009] In some aspects, a method of wireless communication performed by a transmitting device includes: obtaining a plurality of PDCP packets; generating a plurality of external decoding symbols based on a maximum PDCP packet size of the plurality of PDCP packets; adjusting the PDCP packet size to be equal to the external decoding symbol size of the plurality of external decoding symbols for one or more PDCP packets that do not have the maximum PDCP packet size; and transmitting the plurality of PDCP packets based on the adjusted PDCP packet size.

[0010] In some aspects, a method of wireless communication performed by a transmitting device includes: obtaining a plurality of PDCP packets; applying zero-padding to the plurality of externally decoded symbols based on the difference between the PDCP packet size associated with the plurality of PDCP packets and the externally decoded symbol size associated with the plurality of externally decoded symbols; and transmitting an externally decoded block based on applying the zero-padding to the plurality of externally decoded symbols.

[0011] In some aspects, a method of wireless communication performed by a receiving device includes: receiving a plurality of radio link control (RLC) packets; identifying that the plurality of RLC packets are segmented according to the external decoded symbol size; generating a plurality of source symbols based on the plurality of RLC packets and the external decoded symbol size; and processing the plurality of source symbols to obtain a plurality of PDCP packets.

[0012] In some aspects, a method of wireless communication performed by a receiving device includes: receiving a plurality of RLC protocol data units (PDUs); estimating a zero-padding length for a plurality of externally decoded symbols based on the difference between the size of the RLC PDUs associated with the plurality of RLC PDUs and the size of the externally decoded symbols associated with a plurality of externally decoded symbols; and processing the plurality of externally decoded symbols according to the zero-padding length to obtain a plurality of PDCP PDUs.

[0013] In some aspects, an apparatus for wireless communication at a transmitting device includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the transmitting device to: acquire a plurality of PDCP packets; generate a plurality of source symbols by applying forward error correction coding to the plurality of PDCP packets, wherein the plurality of source symbols are non-segmented externally decoded source symbols; and transmit the plurality of source symbols.

[0014] In some aspects, an apparatus for wireless communication at a transmitting device includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the transmitting device to: acquire a plurality of PDCP packets; generate a plurality of external decoding symbols according to a maximum PDCP packet size of the plurality of PDCP packets; adjust the PDCP packet size to be equal to the external decoding symbol size of the plurality of external decoding symbols for one or more PDCP packets that do not have the maximum PDCP packet size; and transmit the plurality of PDCP packets according to the adjusted PDCP packet size.

[0015] In some aspects, an apparatus for wireless communication at a transmitting device includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the transmitting device to: acquire a plurality of PDCP packets; apply zero-padding to the plurality of external decoded symbols based on the difference between the PDCP packet size associated with the plurality of PDCP packets and the external decoded symbol size associated with a plurality of external decoded symbols; and transmit an external decoded block based on applying the zero-padding to the plurality of external decoded symbols.

[0016] In some aspects, an apparatus for wireless communication at a receiving device includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the receiving device to: receive a plurality of RLC packets; identify that the plurality of RLC packets are segmented according to an external decoded symbol size; generate a plurality of source symbols based on the plurality of RLC packets and the external decoded symbol size; and process the plurality of source symbols to obtain a plurality of PDCP packets.

[0017] In some aspects, an apparatus for wireless communication at a receiving device includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the receiving device to: receive a plurality of RLC PDUs; estimate a zero-padding length for a plurality of external decoded symbols based on the difference between the RLC PDU size associated with the plurality of RLC PDUs and the size of an external decoded symbol associated with a plurality of external decoded symbols; and process the plurality of external decoded symbols according to the zero-padding length to obtain a plurality of PDCP PDUs.

[0018] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a transmitting device, cause the transmitting device to: acquire a plurality of PDCP packets; generate a plurality of source symbols by applying forward error correction coding to the plurality of PDCP packets, wherein the plurality of source symbols are non-segmented externally decoded source symbols; and transmit the plurality of source symbols.

[0019] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a transmitting device, cause the transmitting device to: acquire a plurality of PDCP packets; generate a plurality of external decoding symbols according to a maximum PDCP packet size of the plurality of PDCP packets; adjust the PDCP packet size to be equal to the external decoding symbol size of the plurality of external decoding symbols for one or more PDCP packets that do not have the maximum PDCP packet size; and transmit the plurality of PDCP packets according to the adjusted PDCP packet size.

[0020] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a transmitting device, cause the transmitting device to: acquire a plurality of PDCP packets; apply zero-padding to the plurality of externally decoded symbols based on the difference between the PDCP packet size associated with the plurality of PDCP packets and the externally decoded symbol size associated with a plurality of externally decoded symbols; and transmit an externally decoded block based on applying the zero-padding to the plurality of externally decoded symbols.

[0021] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a receiving device, cause the receiving device to: receive a plurality of RLC packets; identify that the plurality of RLC packets are segmented according to an external decoded symbol size; generate a plurality of source symbols based on the plurality of RLC packets and the external decoded symbol size; and process the plurality of source symbols to obtain a plurality of PDCP packets.

[0022] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a receiving device, cause the receiving device to: receive a plurality of RLC PDUs; estimate a zero-padding length for a plurality of externally decoded symbols based on the difference between the RLC PDU size associated with the plurality of RLC PDUs and the size of an externally decoded symbol associated with a plurality of externally decoded symbols; and process the plurality of externally decoded symbols according to the zero-padding length to obtain a plurality of PDCP PDUs.

[0023] In some aspects, an apparatus for wireless communication includes: components for acquiring a plurality of PDCP packets; components for generating a plurality of source symbols by applying forward error correction coding to the plurality of PDCP packets, wherein the plurality of source symbols are non-segmented externally decoded source symbols; and components for transmitting the plurality of source symbols.

[0024] In some aspects, an apparatus for wireless communication includes: components for acquiring a plurality of PDCP packets; components for generating a plurality of external decoding symbols based on a maximum PDCP packet size of the plurality of PDCP packets; components for adjusting the PDCP packet size to be equal to the external decoding symbol size of the plurality of external decoding symbols for one or more PDCP packets that do not have the maximum PDCP packet size; and components for transmitting the plurality of PDCP packets based on the adjusted PDCP packet size.

[0025] In some aspects, an apparatus for wireless communication includes: components for acquiring a plurality of PDCP packets; components for applying zero-padding to the plurality of external decoded symbols based on the difference between a PDCP packet size associated with the plurality of PDCP packets and an external decoded symbol size associated with a plurality of external decoded symbols; and components for transmitting an external decoded block based on applying the zero-padding to the plurality of external decoded symbols.

[0026] In some aspects, an apparatus for wireless communication includes: components for receiving a plurality of RLC packets; components for identifying that the plurality of RLC packets are segmented according to the external decoding symbol size; components for generating a plurality of source symbols based on the plurality of RLC packets and the external decoding symbol size; and components for processing the plurality of source symbols to obtain a plurality of PDCP packets.

[0027] In some aspects, an apparatus for wireless communication includes: components for receiving a plurality of RLC PDUs; components for estimating a zero-padding length for a plurality of external decoded symbols based on the difference between the RLC PDU size associated with the plurality of RLC PDUs and the external decoded symbol size associated with a plurality of external decoded symbols; and components for processing the plurality of external decoded symbols based on the zero-padding length to obtain a plurality of PDCP PDUs.

[0028] The entirety of the terms includes methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and description and illustrated as illustrated in the drawings and description.

[0029] The features and technical advantages of the examples according to this disclosure have been summarized rather broadly above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and operation) and their associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Attached Figure Description

[0030] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

[0031] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0032] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0033] Figure 3 is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0034] Figure 4 is an illustration of an example of a user plane protocol stack and a control plane protocol stack for a network node and a core network used to communicate with a UE according to the present disclosure.

[0035] Figure 5 is a diagram illustrating an example of retransmission and external decoding according to this disclosure.

[0036] Figure 6 is a diagram illustrating examples of protocol data units and protocol data unit sets according to this disclosure.

[0037] Figure 7 is a diagram illustrating an example of foreign decoding according to this disclosure.

[0038] Figure 8 is an illustration of an example of assembling an external decoding block with external decoding source symbol segments according to the present disclosure.

[0039] Figure 9 is an illustration of an example of assembling an external decoding block without external decoding source symbol segmentation according to the present disclosure.

[0040] Figure 10 is a diagram illustrating an example of assembling an external decoding block according to the present disclosure.

[0041] Figure 11 is an illustration of an example of adjusting the size of an external decoding symbol according to the present disclosure.

[0042] Figure 12 is a diagram illustrating an example of radio link control packet transmission using the maximum packet data convergence protocol packet size according to this disclosure.

[0043] Figure 13 is an illustration of an example of zero-padding for segmented external decoded symbols according to the present disclosure.

[0044] Figures 14A and 14B are illustrations illustrating examples of zero-filling performed by the transmitting and receiving devices according to the present disclosure.

[0045] Figure 15 is a diagram illustrating an example of zero-padding for foreign decoding symbols according to the present disclosure.

[0046] Figure 16 is a diagram illustrating an example process performed, for example, at a transmitting device or an apparatus of a transmitting device, according to the present disclosure.

[0047] Figure 17 is a diagram illustrating an example process performed, for example, at a transmitting device or an apparatus of a transmitting device, according to the present disclosure.

[0048] Figure 18 is a diagram illustrating an example process performed, for example, at a transmitting device or an apparatus of a transmitting device, according to the present disclosure.

[0049] Figure 19 is a diagram illustrating an example process performed, for example, at a receiving device or an apparatus of a receiving device, according to the present disclosure.

[0050] Figure 20 is a diagram illustrating an example process performed, for example, at a receiving device or an apparatus of a receiving device, according to the present disclosure.

[0051] Figure 21 is a diagram of an example device for wireless communication according to the present disclosure.

[0052] Figure 22 is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0053] External decoding can be used to improve latency and reduce power consumption in Protocol Data Unit (PDU) transmission. In some cases, performing external decoding may include using forward error correction (FEC) to add one or more parity symbols to the PDU set (such as after the last slot or symbol in the PDU set). Parity symbols may include redundant information associated with the transmission of the PDU set and may improve the recovery probability of the PDU set without introducing the latency associated with Hybrid Automatic Repeat Request (HARQ) retransmission. A PDU is a data unit that can vary depending on the protocol or layer within the protocol stack. For example, at the network layer, a PDU may be referred to as a packet. A packet may include data associated with the PDU and may include header information for routing, error checking, and control functions, etc. Some applications may consume data in a PDU set (rather than in individual IP packets). For example, extended reality (XR) applications may consume one video frame per burst or multiple slices of video frames per burst. In some cases, a PDU set may include multiple Internet Protocol (IP) packets corresponding to information units used by the application. For example, a PDU set may include slices of video frames that can be protected by FEC by adding one or more parity bits to the PDU set. In some cases, FEC can be applied to multiple Packet Data Convergence Protocol (PDCP) PDUs (e.g., multiple PDU sets). This allows for increased granularity of FEC protection and improves the probability of recovering the PDU set (e.g., in the event of an error during the transmission of the PDU set).

[0054] In some cases, the outer decoding (OC) sublayer configured to perform FEC encoding may receive input including a PDU set and at least one of the Service Data Application Protocol (SDAP) or PDCP header information. The OC sublayer may generate OC blocks based at least in part on the PDU set and header information. An OC block may include one or more source symbols and one or more parity symbols. The one or more source symbols and / or one or more parity symbols may have an OC symbol size, for example, based on the OC symbol size indicated in the PDCP header. In some cases, a transmitting device (such as a network node) may transmit OC blocks to a receiving device (such as a User Equipment (UE)). However, the transmitting device may not be configured with information that enables it to construct OC blocks from multiple PDCP packets. For example, the transmitting device may not be configured with mapping rules that enable it to map IP packets to OC symbols. Additionally, the transmitting device and / or the receiving device may not be configured to align the PDCP packet size with the OC symbol size. For example, the OC symbol size may be determined by the Radio Access Network (RAN), while the PDCP packet size may be determined by the application layer. IP packets included in a PDU set may have different sizes, while each OC symbol within an OC block may have the same OC symbol size. This can result in IP packets having sizes different from the OC symbols. Information enabling the transmitting and receiving devices to generate OC symbols with the same size as PDCP packets may not be used in their configuration. This can lead to transmission errors that may require HARQ retransmission, increasing latency and power consumption at the transmitting and receiving devices.

[0055] Various aspects relate to wireless communication as a whole. Some aspects more specifically relate to network decoding for Packet Data Convergence Protocol (PDCP) communications. In some aspects, a transmitting device may receive multiple PDCP packets. The transmitting device may be a network node, a UE, or any other communication device, and the multiple PDCP packets may be multiple PDCP PDUs. The transmitting device may generate multiple source symbols based on applying FEC to the multiple PDCP packets. Generating multiple source symbols may include generating multiple non-segmented external decoding source symbols. The transmitting device may transmit the multiple source symbols to a receiving device. The receiving device may be a network node, a UE, or any other communication device. In some aspects, the transmitting device may receive multiple PDCP packets and may generate multiple external decoding symbols based on the maximum PDCP packet size of the multiple PDCP packets. The transmitting device may adjust the PDCP packet size to be equal to the external decoding symbol size associated with the multiple external decoding symbols for one or more PDCP packets that do not have the maximum PDCP packet size. In one example, the transmitting device may apply one or more zero-padding bits to each PDCP packet that does not have the maximum PDCP packet size. In some aspects, the transmitting device may receive multiple PDCP packets and may calculate the difference between the PDCP packet size associated with the multiple PDCP packets and the external decoded symbol size associated with the multiple external decoded symbols. The transmitting device may apply zero padding to an external decoded block or at least one of the multiple external decoded symbols and may transmit the external decoded block according to the application of zero padding. In a first example, applying zero padding may include applying one or more zero padding bits to the end of the external decoded block. In a second example, applying zero padding may include applying one or more zero padding bits to the end of each of the multiple external decoded symbols. In some aspects, a receiving device may receive multiple RLC packets and may identify that the multiple RLC packets will be segmented according to the external decoded symbol size. The receiving device may generate multiple source symbols based on the multiple RLC packets and the external decoded symbol size.

[0056] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by generating multiple source symbols based on multiple PDCP packets, the described techniques can be used to generate an externally decoded block comprising multiple PDCP packets and an associated header. Additionally, by generating multiple source symbols and transmitting them without performing externally decoded symbol segmentation, network overhead, such as RLC layer overhead and external decoding processing overhead, can be reduced. In some aspects, by generating multiple externally decoded symbols based on the maximum PDCP packet size and adjusting the PDCP packet size of one or more PDCP packets that do not have the maximum PDCP packet size, concatenation and segmentation requirements for PDCP packet transmission can be reduced or eliminated. In some aspects, by applying zero-padding to multiple externally decoded symbols based on the difference between the PDCP packet size and the externally decoded symbol size, the described techniques can be used to align the PDCP packet size with the externally decoded symbol size, which can reduce the likelihood of transmission errors. Additionally, by transmitting the externally decoded block while avoiding the transmission of zero-padding symbols, network overhead and radio resource consumption can be reduced. In some respects, by identifying that multiple RLC packets are segmented according to the size of the external decoded symbol, and by generating multiple source symbols according to the size of the external decoded symbol, network overhead can be reduced, for example, by reducing or eliminating the transmission of external decoded symbols in the air. These examples and advantages will be described in more detail below.

[0057] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods implemented using structures, functions, or structures and functions other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be embodied by one or more elements of these claims.

[0058] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0059] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0060] Figure 1 is a diagram illustrating an example of a wireless network 100. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., LTE) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., LTE) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network nodes 110a, 110b, 110c, and 110d), one or more UEs 120 (shown as UEs 120a, 120b, 120c, 120d, and 120e), or other entities. Network node 110 is an example of a network node communicating with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (Dus), or one or more radio units (RUs)).

[0061] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, network node 110 may include NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0062] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 or a network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, or another type of cell. A macrocell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a residential area) and may allow restricted access by UE 120 associated with that femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. Network node 110 for a femtocell may be referred to as a femtocell network node or a home network node. In the example shown in Figure 1, network node 110a may be a macro network node for macrocell 102a, network node 110b may be a picocell network node for picocell 102b, and network node 110c may be a femtocell network node for femtocell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0063] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. Thus, a single device can include more than one base station.

[0064] Wireless network 100 may include one or more relay stations. A relay station is a network node that receives data transmissions from an upstream node (e.g., network node 110 or UE 120) and transmits data to a downstream node (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions to other UE 120s. In the example shown in Figure 1, network node 110d (e.g., a relay network node) may communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 that relays communication may be referred to as a relay station, relay base station, relay network node, relay node, or relay, etc.

[0065] The wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0066] Network controller 130 may be coupled to or communicate with a group of network nodes 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0067] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), an in-vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, or any other suitable device configured to communicate via wireless or wired media.

[0068] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, unmanned aerial vehicles, remote devices, sensors, meters, monitors, or location markers that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0069] Generally, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology or air interface. A frequency can also be referred to as a carrier or frequency channel. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0070] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communication with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or a mesh network. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0071] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to in documents and articles as the “millimeter wave” band, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0073] In light of these examples, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that may include intermediate frequency bands, frequencies within FR2, FR4, FR4-a, FR4-1, or FR5, or frequencies within the EHF band. It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0074] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may: acquire multiple PDCP packets; generate multiple source symbols, wherein the multiple source symbols are non-segmented external decoding source symbols, by applying forward error correction coding to the multiple PDCP packets; and transmit the multiple source symbols. In some other aspects, as described in more detail elsewhere herein, communication manager 150 may: acquire multiple PDCP packets; generate multiple external decoding symbols based on the maximum PDCP packet size of the multiple PDCP packets; adjust the PDCP packet size to be equal to the external decoding symbol size of the multiple external decoding symbols for one or more PDCP packets that do not have the maximum PDCP packet size; and transmit the multiple PDCP packets based on the adjusted PDCP packet size. In some other aspects, as described in more detail elsewhere herein, the communication manager 150 may: acquire multiple PDCP packets; apply zero-padding to multiple external decoded symbols based on the difference between the PDCP packet size associated with the multiple PDCP packets and the external decoded symbol size associated with the multiple external decoded symbols; and transmit an external decoded block based on the application of zero-padding to the multiple external decoded symbols. In some other aspects, as described in more detail elsewhere herein, the communication manager 150 may: receive multiple RLC packets; identify that the multiple RLC packets are segmented according to the external decoded symbol size; generate multiple source symbols based on the multiple RLC packets and the external decoded symbol size; and process the multiple source symbols to obtain multiple PDCP packets. In some other aspects, as described in more detail elsewhere herein, the communication manager 150 may: receive multiple RLC PDUs; estimate the zero-padding length for the multiple external decoded symbols based on the difference between the RLC PDU size associated with the multiple RLC PDUs and the external decoded symbol size associated with the multiple external decoded symbols; and process the multiple external decoded symbols based on the zero-padding length to obtain multiple PDCP PDUs. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0075] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: acquire multiple PDCP packets; generate multiple source symbols, wherein the multiple source symbols are non-segmented external decoding source symbols, by applying forward error correction coding to the multiple PDCP packets; and transmit the multiple source symbols. In some other aspects, as described in more detail elsewhere herein, the communication manager 140 may: acquire multiple PDCP packets; generate multiple external decoding symbols based on the maximum PDCP packet size of the multiple PDCP packets; adjust the PDCP packet size to be equal to the external decoding symbol size of the multiple external decoding symbols for one or more PDCP packets that do not have the maximum PDCP packet size; and transmit the multiple PDCP packets based on the adjusted PDCP packet size. In some other aspects, as described in more detail elsewhere herein, the communication manager 140 may: acquire multiple PDCP packets; apply zero-padding to multiple external decoded symbols based on the difference between the PDCP packet size associated with the multiple PDCP packets and the external decoded symbol size associated with the multiple external decoded symbols; and transmit an external decoded block based on the application of zero-padding to the multiple external decoded symbols. In some other aspects, as described in more detail elsewhere herein, the communication manager 140 may: receive multiple RLC packets; identify that the multiple RLC packets are segmented according to the external decoded symbol size; generate multiple source symbols based on the multiple RLC packets and the external decoded symbol size; and process the multiple source symbols to obtain multiple PDCP packets. In some other aspects, as described in more detail elsewhere herein, the communication manager 140 may: receive multiple RLC PDUs; estimate the zero-padding length for the multiple external decoded symbols based on the difference between the RLC PDU size associated with the multiple RLC PDUs and the external decoded symbol size associated with the multiple external decoded symbols; and process the multiple external decoded symbols based on the zero-padding length to obtain multiple PDCP PDUs. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0076] As indicated above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0077] Figure 2 is a diagram illustrating example 200 of communication between network node 110 and UE 120 in wireless network 100. Network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). Network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and modems 232. In some examples, network node 110 may include an interface, communication components, or another component facilitating communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components facilitating direct communication with UE 120, such as one or more CUs or one or more DUs.

[0078] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 can use one or more Channel Quality Indicators (CQIs) received from UE 120 to select one or more modulation and decoding schemes (MCSs) for that UE 120. Network node 110 can use the MCS selected for UE 120 to process (e.g., encode and modulate) the data for UE 120 and can provide data symbols to UE 120. Transmitting processor 220 can process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding, if applicable) on data symbols, control symbols, overhead symbols, or reference symbols, and can provide a set of output symbol streams (e.g., T modems) to a corresponding set of modems 232, shown as modems 232a to 232t. For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0079] At UE 120, an array of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 or other network nodes 110, and can provide an array of received signals (e.g., R received signals) to an array of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for the UE 120 to the data sink 260, and provide the decoded control and system information to the controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine Reference Signal Received Power (RSRP) parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, or CQI parameters, etc. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0080] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0081] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or be included in the following: one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, collections of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a coplanar collection of antenna elements, a non-coplanar collection of antenna elements, or one or more antenna elements coupled to one or more transmitting or receiving components (such as one or more components of FIG. 2).

[0082] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, or CQI). Transmit processor 264 can generate reference symbols for one or more reference signals. Symbols from transmit processor 264 may be pre-decoded by TX MIMO processor 266 where applicable, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, modem 254 of UE 120 may include modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and a memory 282 to perform any aspect of the process described herein (e.g., with reference to Figures 8 through 15).

[0083] At network node 110, uplink signals from UE 120 or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted via UE 120. Receiver processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform any aspect of the process described herein (e.g., with reference to Figures 8 through 15).

[0084] In some respects, the controller / processor 280 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as UE 120). For example, the processing system of UE 120 may be a system that includes various other components or sub-components of UE 120.

[0085] The processing system of UE 120 can interface with one or more other components of UE 120, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of UE 120 may include a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing UE 120 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing UE 120 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0086] In some respects, the controller / processor 240 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as network node 110). For example, the processing system of network node 110 may be a system that includes various other components or sub-components of network node 110.

[0087] The processing system of network node 110 may interface with one or more other components of network node 110, and may process information (such as input or signals) received from one or more other components, or may output information to one or more other components. For example, the chip or modem of network node 110 may include a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing network node 110 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing network node 110 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0088] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or any other component of FIG. 2 may perform one or more techniques associated with network decoding for packet data convergence protocol communication, as described in more detail elsewhere herein. In some aspects, the transmitting device described herein is network node 110, included in network node 110, or includes one or more components of network node 110 shown in FIG. 2. In some other aspects, the transmitting device described herein is UE 120, included in UE 120, or includes one or more components of UE 120 shown in FIG. 2. In some aspects, the receiving device described herein is network node 110, included in network node 110, or includes one or more components of network node 110 shown in FIG. 2. In some other aspects, the receiving device described herein is UE 120, included in UE 120, or includes one or more components of UE 120 shown in FIG. 2. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or any other component (or combination of components) of FIG. 2 may execute or direct the operation of processes such as process 1600 of FIG. 16, process 1700 of FIG. 17, process 1800 of FIG. 18, process 1900 of FIG. 19, process 2000 of FIG. 20, and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of network node 110 or UE 120 (e.g., directly, or after compilation, transformation, or interpretation), may cause one or more processors, UE 120, or network node 110 to perform or direct the operation of processes such as process 1600 of FIG. 16, process 1700 of FIG. 17, process 1800 of FIG. 18, process 1900 of FIG. 19, process 2000 of FIG. 20, and / or other processes and / or other processes as described herein. In some examples, execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

[0089] In some aspects, the transmitting device (e.g., network node 110 or UE 120) includes: components for acquiring a plurality of PDCP packets; components for generating a plurality of source symbols by applying forward error correction coding to the plurality of PDCP packets, wherein the plurality of source symbols are non-segmented externally decoded source symbols; and / or components for transmitting the plurality of source symbols by the radio link control layer. In some aspects, components for the transmitting device to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmitting processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receiving processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, components for the transmitting device to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0090] In some aspects, the transmitting device (e.g., network node 110 or UE 120) includes: components for acquiring a plurality of PDCP packets; components for generating a plurality of external decoding symbols based on the maximum PDCP packet size of the plurality of PDCP packets; components for adjusting the PDCP packet size for one or more PDCP packets that do not have a maximum PDCP packet size to be equal to the external decoding symbol size of the plurality of external decoding symbols; and / or components for transmitting the plurality of PDCP packets based on the adjusted PDCP packet size. In some aspects, components for the transmitting device to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmitting processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receiving processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, components for the transmitting device to perform the operations described herein may include one or more of, for example, a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0091] In some aspects, the transmitting device (e.g., network node 110 or UE 120) includes: components for acquiring a plurality of PDCP packets; components for applying zero-padding to a plurality of externally decoded symbols based on the difference between the PDCP packet size associated with the plurality of PDCP packets and the externally decoded symbol size associated with a plurality of externally decoded symbols; and / or components for transmitting an externally decoded block based on applying zero-padding to the plurality of externally decoded symbols. In some aspects, components for the transmitting device to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmitting processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receiving processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, components for the transmitting device to perform the operations described herein may include one or more of, for example, a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0092] In some aspects, the receiving device (e.g., network node 110 or UE 120) includes: components for receiving multiple RLC packets; components for identifying that the multiple RLC packets are segmented according to the external decoded symbol size; components for generating multiple source symbols based on the multiple RLC packets and the external decoded symbol size; and / or components for processing the multiple source symbols to obtain multiple PDCP packets. In some aspects, components for the receiving device to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, components for the receiving device to perform the operations described herein may include one or more of, for example, a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0093] In some aspects, the receiving device (e.g., network node 110 or UE 120) includes: components for receiving a plurality of RLC PDUs; components for estimating a zero-padding length for a plurality of externally decoded symbols based on the difference between the RLC PDU size associated with the plurality of RLC PDUs and the externally decoded symbol size associated with a plurality of externally decoded symbols; and / or components for processing the plurality of externally decoded symbols according to the zero-padding length to obtain a plurality of PDCP PDUs. In some aspects, components for the receiving device to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, components for the receiving device to perform the operations described herein may include one or more of, for example, a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0094] Although the boxes in Figure 2 are illustrated as different components, the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0095] In some aspects, a single processor can perform all functions described as being performed by the one or more processors. In other aspects, the one or more processors can jointly perform a set of functions. For example, a first set (one or more) of the one or more processors can perform a first function described as being performed by the one or more processors, and a second set (one or more) of the one or more processors can perform a second function described as being performed by the one or more processors. The processors in the first set and the processors in the second set can be the same set of processors or can be different sets of processors. The reference to “one or more processors” should be understood to refer to any one or more processors described in conjunction with FIG. 2. The reference to “one or more memories” should be understood to refer to any one or more memories of the corresponding device, such as the memories described in conjunction with FIG. 2. For example, a function described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

[0096] As indicated above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0097] Communication systems (such as 5G NR systems) can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or one or more components) that perform base station functions can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0098] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0099] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0100] Figure 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0101] Each unit in the cells (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cell, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other cells via transmission media. In some examples, each unit in the cell may include a wired interface and a wireless interface configured to receive signals or transmit signals to one or more units in other cells via a wired transmission media, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more units in other cells via a wireless transmission media, or both.

[0102] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0103] Each DU 330 may correspond to a logic unit including one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0104] Each RU 340 can implement lower-layer functionality. In some deployments, an RU 340 controlled by a DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In such architectures, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0105] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with 4G RAN hardware aspects such as the Open eNB (O-eNB) 311 via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0106] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0107] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0108] As indicated above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0109] Figure 4 is a diagram illustrating an example 400 of a network node 110 and a user plane protocol stack and a control plane protocol stack of a core network for communicating with a UE 120 according to the present disclosure. In some aspects, network node 110 may include multiple network nodes 110. In some aspects, the protocol stack functionality of network node 110 may be distributed across multiple network nodes 110. For example, a first network node 110 may implement a first layer of the protocol stack, and a second network node 110 may implement a second layer of the protocol stack. The distribution of the protocol stack across network nodes (in this example of the distribution of the protocol stack across network nodes) may be based at least in part on functional partitioning, as described elsewhere herein. It should be understood that, in some aspects, references to “network node 110” or “network node 110” may refer to multiple network nodes.

[0110] On the user plane, UE 120 and network node 110 may include corresponding physical (PHY) layers, media access control (MAC) layers, radio link control (RLC) layers, packet data convergence protocol (PDCP) layers, and service data adaptation protocol (SDAP) layers. User plane functions handle the transmission of user data between UE 120 and network node 110. On the control plane, UE 120 and network node 110 may include corresponding radio resource control (RRC) layers. Furthermore, UE 120 may include a NAS layer that communicates with the non-access stratum (NAS) layer of the access and management mobility functions (AMF). This AMF may be associated with the core network associated with network node 110, such as a 5G core network (5GC) or a next-generation radio access network (NG-RAN). Control plane functions handle the transmission of control information between the UE and the core network. Generally, if the first layer is further away from the PHY layer than the second layer, the first layer is referred to as being above the second layer. For example, the PHY layer may be referred to as the lowest layer, and the SDAP / PDCP / RLC / MAC layer may be referred to as being above the PHY layer and below the RRC layer. The Application (APP) layer, not shown in Figure 4, may be above 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), although the description herein mentions that the layer itself handles these services and functions.

[0111] The RRC layer handles communications related to configuring and operating UE 120, such as: broadcasting system information related to the Access Layer (AS) and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of RRC connections between the UE and NG-RAN, including the addition, modification, and release of carrier aggregation, as well as the addition, modification, and release of dual connections; 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 passing, 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 reports; detection and recovery from radio link failures; and NAS messaging between the NAS layer and the lower layers of UE 120. The RRC layer is often referred to as Layer 3 (L3).

[0112] The SDAP, PDCP, RLC, and MAC layers can be collectively referred to as Layer 2 (L2). Therefore, 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 UE 120 is transmitting uplink communication or network node 110 is transmitting downlink communication), the SDAP layer can receive data streams in the form of QoS streams. A QoS stream is associated with a QoS identifier and a QoS stream identifier (QFI), the QoS identifier identifying the QoS parameters associated with the QoS stream and the QoS stream identifier (QFI) identifying the QoS stream. Policies and charging parameters are implemented according to the QoS stream granularity. A QoS stream may include one or more Service Data Streams (SDFs), provided that each SDF of the QoS stream is associated with the same policies and charging parameters. In some aspects, the RRC / NAS layer can generate control information to be transmitted and can map this control information to one or more radio bearers for provision to the PDCP layer.

[0113] The SDAP or RRC / NAS layer can map QoS flows or control information to radio bearers. Therefore, it can be said that the SDAP layer handles QoS flows on the transmitting side. The SDAP layer can provide QoS flows to the PDCP layer via the corresponding radio bearer. The PDCP layer can map radio bearers to RLC channels. The PDCP layer handles various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), delivery of user data, reordering and replication detection (if required for in-order delivery to layers above the PDCP layer), PDCP Protocol Data Unit (PDU) routing (in the case of split bearers), retransmission, encryption and decryption of PDCP Service Data Units (SDUs), PDCP SDU discarding (e.g., according to timers, as described elsewhere in this document), PDCP reconstruction and data recovery for RLC Acknowledgment Mode (AM), and replication of PDCP PDUs. The PDCP layer handles similar services and functions on the control plane, including sequence numbering, encryption, decryption, integrity protection, delivery of control plane data, replication detection, and replication of PDCP PDUs.

[0114] The PDCP layer can provide data in the form of PDCP PDUs to the RLC layer via the RLC channel. The RLC layer can handle the transmission of upper-layer PDUs to the MAC and / or PHY layers, sequence numbering independent of PDCP sequence numbering, error correction via Automatic Repeat Request (ARQ), segmentation and resegmentation, SDU reassembly, RLC SDU discarding, and RLC reconstruction.

[0115] The RLC layer can provide the MAC layer with data mapped to logical channels. 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 MACSDUs belonging to one or different logical channels into / from a transport block (TB) delivered to / from the physical layer on the transport channel, scheduling information reporting, error correction via Hybrid ARQ (HARQ), priority handling between UEs via dynamic scheduling, priority handling between logical channels of a UE via logical channel prioritization, and padding.

[0116] The MAC layer can encapsulate data from logical channels into TBs and can provide TBs to the PHY layer on one or more transport channels. The PHY layer handles various operations related to the transmission of data signals, as described in more detail with reference to Figure 2. The PHY layer is often referred to as Layer 1 (L1).

[0117] On the receiving side (e.g., if UE 120 is receiving downlink communication or network node 110 is receiving uplink communication), the operation can be similar to that described for the transmitting side, but in the reverse direction. For example, the PHY layer can receive the transport layer (TB) and provide the TB to the MAC layer on one or more transport channels. The MAC layer can map the transport channels to logical channels and provide data to the RLC layer via the logical channels. The RLC layer can map the logical channels to RLC channels and provide data to the PDCP layer via the RLC channels. The PDCP layer can map the RLC channels to radio bearers and provide data to the SDAP layer or RRC / NAS layer via the radio bearers.

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

[0119] As indicated above, Figure 4 is provided as an example. Other examples may differ from those described with respect to Figure 4.

[0120] Figure 5 is a diagram illustrating an example of retransmission and external decoding according to this disclosure.

[0121] Network nodes can perform downlink transmissions that include PDU sets. In some cases, PDU sets may have stringent latency and power requirements, such as in examples where PDU sets are associated with extended reality (XR) applications. For example, a PDU set may have a packet delay budget (PDB) of ten milliseconds (ms) and a power consumption requirement of less than 1 watt (W). Additional details regarding PDU sets are described in conjunction with Figure 6.

[0122] In some cases, errors may occur during the transmission of a PDU set. In such cases, retransmission of one or more slots of the PDU set can be used for error correction. Retransmission can be, for example, Automatic Repeat Request (ARQ) retransmission or Hybrid ARQ (HARQ) retransmission. However, this may increase latency and may require additional power for PDU set transmission. As shown in Example 500, a PDU set may include multiple downlink slots (D), uplink slots (U), and special slots (S). In one example, the multiple slots may include 23 slots. After the transmission of a PDU set without a Block Error Rate (BLER), the UE may initiate an inactivity timer and may enter sleep mode after the inactivity timer expires. This allows the UE to conserve energy resources. However, for a PDU set with a BLER, downlink slot 505 of the PDU set may not be successfully received by the UE. In this scenario, the UE might send a negative acknowledgment (NACK) 510 seven slots after downlink slot 505 (e.g., the last slot in the PDU set), and a retransmission 515 of downlink slot 505 might occur six slots after NACK 510. This could introduce a delay of thirteen slots (approximately 35ms) and could prevent the UE from initiating an inactivity timer and entering sleep mode.

[0123] In some cases, external decoding can be used to improve the latency of PDU set transmission and reduce power consumption. External decoding may include using forward error correction (FEC) to add one or more parity symbols to the PDU set (e.g., after the last slot or symbol of the PDU set). The parity symbols may include redundancy information associated with the PDU set transmission and may improve the recovery probability of the PDU set without introducing delays associated with HARQ retransmission. As shown in Example 520, for a PDU set with BLER, parity symbol 525 may be added to the end of the PDU set. Parity symbol 525 may include redundancy information from the high-latency-cost portion 530 of the PDU set. Parity symbol 525 may introduce a three-slot delay to the PDU set transmission, which may allow the UE to initiate an inactivity timer and enter a sleep mode to conserve UE power resources.

[0124] As indicated above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0125] Figure 6 is a diagram illustrating examples of protocol data units and protocol data unit sets according to this disclosure.

[0126] Application Data Units (ADUs) can be generated by an application (e.g., an XR application) and may include content to be transmitted over a network. An ADU may include text, images, video, audio, or any application-layer data to be transmitted over a network. In contrast, a Programming Device Unit (PDU) is a data unit that can vary depending on a specific protocol or layer within the protocol stack. At the network layer (e.g., layer 3), a PDU may be referred to as a packet. A packet may include data associated with the PDU and may include header information for routing, error checking, and control functions, etc. Some applications may consume data in a set of PDUs (rather than individual IP packets). For example, an XR application may consume one video frame per burst, or multiple slices of a video frame per burst, etc. A burst may include a set of IP packets or ADUs to be delivered to a device simultaneously. For example, a burst may include all slices of a video frame. As shown in Example 600, a burst 605 may include one or more ADUs 610. For example, burst 605-1 may include ADU 610-1 and ADU 610-2, burst 605-2 may include ADU 610-3, 610-4, and 610-5, and burst 605-3 may include ADU 605-6. In some cases, a PDU set may include multiple IP packets corresponding to information units used for an application. For example, a PDU set may include slices of video frames (which may be protected by FEC). In some cases, FEC may be used to add one or more parity symbols to the PDU set. In one example, a set of symbols considered together for FEC may be referred to as a block. A symbol is a unit of data to be used for FEC. In one example, a symbol may have a size T. The first K symbols of symbol size T may be source symbols (e.g., system symbols), and the remaining symbols of symbol size T may be parity symbols (e.g., repair symbols).

[0127] In some cases, the OC sublayer can be integrated into the RLC layer. As shown in Example 615, the OC sublayer 620 can be integrated into the RLC layer 625 of the network protocol stack. PDCP packets belonging to the same PDU set can be identified as OC blocks. The OC sublayer 620 can receive feedback from the PHY layer indicating the OC symbol size and can set the RLC SDU size to be equal to the OC symbol size. In some cases, PDCP packets can be segmented into RLC SDUs (e.g., OC symbols), OC encoded with the desired delay, and provided to the RLC layer, MAC layer, and PHY layer for over-the-air (OTA) transmission. Integrating the OC sublayer into the RLC layer instead of the MAC layer allows for the segmentation of PDCP packets (e.g., since the MAC layer does not have segmentation functionality), allows for greater flexibility in performing OC on specific radio bearers with certain quality of service requirements, and / or allows for more efficient service-specific operations (e.g., since MAC SDUs can have packets multiplexed from different radio bearers). Similarly, integrating the OC sublayer into the RLC layer instead of the PHY layer enables segmentation functionality (e.g., since the PHY layer does not have segmentation functionality), allowing additional PDCP PDUs to be added as OC parity symbols, and enabling DU-level processing instead of CU-level processing (which can be dynamically adapted based on channel conditions).

[0128] As indicated above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.

[0129] Figure 7 is an illustration of example 700 of foreign decoding according to the present disclosure.

[0130] In some cases, FEC can be applied to a single PDCP PDU. In other cases, FEC can be applied to multiple PDCP PDUs, such as a PDU set or a burst. This allows for increased granularity of FEC protection and improves the probability of recovering the PDU set (e.g., in the event of a transmission error). The PDU set 705 may include multiple IP packets 710 (such as IP packet 710-1, IP packet 710-2, IP packet 710-3, and IP packet 710-4). An OC sublayer 715 configured to perform FEC encoding may receive input including the PDU set 705 and at least one of SDAP or PDCP header information. The OC sublayer 715 may generate an OC block 720 based at least in part on the PDU set 705 and the header information. The OC block 720 may include one or more source symbols 725 and one or more parity symbols 730. The one or more source symbols 725 and / or one or more parity symbols 730 may have an OC symbol size 735. In some cases, a transmitting device (e.g., a network node) may send OC block 720 to a receiving device (e.g., a UE). However, the transmitting device may not be configured with information that enables it to construct OC block 720 based on multiple PDCP packets. For example, the transmitting device may not be configured with mapping rules that enable it to map IP packets 710 to OC symbols (e.g., source symbol 725 and parity symbol 730). Additionally, the transmitting and / or receiving devices may not be configured to align PDCP packet sizes with OC symbol sizes 735. For example, the OC symbol size 735 may be determined by the RAN, while the PDCP packet size may be determined by the application layer. In one example, the PDCP packet size may be based at least in part on the size of the IP packet 710 and the size of the SDAP header or PDCP header. In some cases, IP packets 710 included in the PDU set 705 may have different sizes, while each OC symbol may have the same OC symbol size 735. This could result in IP packets 710 having different sizes than the source symbol 725 and parity symbol 730. The transmitting and receiving devices may not be configured with information that enables them to generate OC symbols aligned with the PDCP packet size. This could lead to transmission errors that may require HARQ retransmission, thereby increasing latency and power consumption at both the transmitting and receiving devices.

[0131] As indicated above, Figure 7 is provided as an example. Other examples may differ from those described with respect to Figure 7.

[0132] Figure 8 is a diagram illustrating an example 800 of an assembly of an externally decoded block with externally decoded source symbol segments according to the present disclosure. Transmitting device 805 can communicate with receiving device 810. Transmitting device 805 can be any device configured to transmit data (and may also be configured to receive data), and receiving device 810 can be any device configured to receive data (and may also be configured to transmit data). Transmitting device 805 can be a network node (such as network node 110) or a UE (such as UE 120). Additionally, receiving device 810 can be a network node or a UE. In one example, transmitting device 805 can be network node 110, and receiving device 810 can be UE 120.

[0133] As indicated by reference numeral 815 in the accompanying drawing, the transmitting device 805 may receive multiple PDCP packets. These multiple packets may be multiple PDCP PDUs. In some aspects, the multiple PDCP packets may be a single PDU set or multiple PDU sets.

[0134] As indicated by reference numeral 820, transmitting device 805 can generate an external decoding block. As indicated by reference numeral 825, transmitting device 805 can segment the external decoding block or multiple PDCP symbols. As shown in FIG8, the operation associated with reference numeral 820 can be performed before or after the operation associated with reference numeral 825.

[0135] In the first example, the transmitting device 805 may generate the external decoding block before segmenting it into multiple external decoding symbols. For example, in a first operation, the transmitting device 805 may generate the external decoding block at least in part based on assembling multiple PDCP packets into the external decoding block. In a second operation, the transmitting device 805 may segment the external decoding block into multiple external decoding symbols at least in part based on the external decoding symbol size. In some aspects, the transmitting device 805 may obtain an indication of the external decoding symbol size from a PHY layer function. In this first example, the PDCP boundary may not be aligned with the external decoding symbol boundary. This allows for a simple and straightforward design, allows for any external decoding symbol size (regardless of the PDCP packet size), and minimizes the required number of external decoding symbols. In some aspects, zero-padding may be assumed for the last external decoding symbol of the external decoding block. This aligns the external decoding symbol size with the PDCP packet size.

[0136] In the second example, the transmitting device 805 may perform external decoding segmentation before generating the external decoding block. For example, in the first operation, the transmitting device 805 may segment each of the plurality of PDCP packets into external decoding symbols based at least in part on the external decoding symbol size. In some aspects, the transmitting device 805 may obtain an indication of the external decoding symbol size from a PHY layer function. In the second operation, the transmitting device 805 may generate the external decoding block based at least in part on assembling the plurality of external decoding symbols. In this second example, segmentation across PDCP packets may not exist. However, segmentation may exist for each individual PDCP packet among the plurality of PDCP packets. This enables pipelined PDCP PDUs and / or enables parallel stacks and external decoding processing. In some aspects, zero-padding may be assumed for the last external decoding symbol of the PDCP packet. This aligns the external decoding symbol size with the PDCP packet size.

[0137] As indicated by reference numeral 830, transmitting device 805 may apply FEC to the external decoding block. In a first example, transmitting device 805 may apply FEC encoding to the external decoding block after generating the external decoding block and after segmenting the external decoding block into multiple external decoding symbols. In a second example, transmitting device 805 may apply FEC encoding to the external decoding block after segmenting each of the multiple PDCP packets into external decoding symbols and after generating the external decoding block using the multiple external decoding symbols.

[0138] As indicated by reference numeral 835, transmitting device 805 can transmit multiple external decoding symbols. For example, transmitting device 805 can transmit an external decoding block comprising multiple external decoding symbols, at least in part, based on applying FEC to the external decoding block.

[0139] As indicated above, Figure 8 is provided as an example. Other examples may differ from those described with respect to Figure 8.

[0140] Figure 9 is an illustration of example 900 of an assembly of an external decoding block without external decoding source symbol segmentation according to the present disclosure.

[0141] As indicated by reference numeral 905 in the accompanying drawing, the transmitting device 805 may receive multiple PDCP packets. These multiple packets may be multiple PDCP PDUs. In some aspects, the multiple PDCP packets may be a single PDU set or multiple PDU sets.

[0142] As shown by reference numeral 910, the transmitting device 805 can generate multiple source symbols. These multiple source symbols can be multiple non-segmented source symbols. The transmitting device 805 can generate multiple source symbols at least in part based on applying FEC to PDCP packets. Using external decoding FEC, the original PDCP PDU can become an externally decoded source symbol. For example, the original PDCP PDU may not be segmented and transmitted. Instead, the external decoding encoder and decoder may assume that the PDCP PDU is segmented into source symbols. Therefore, a source symbol can be equal to a PDCP PDU.

[0143] In one example, for source symbols, RLC PDUs can be transmitted without external decoded symbol segmentation. For parity symbols, the external decoder can assume that the PDCP PDU is segmented into multiple source symbols at least in part based on the external decoded symbol size, and can generate external decoded parity symbols at least in part based on the multiple source symbols. In some aspects, the transmitting device 805 (e.g., the external decoder) can obtain an indication of the external decoded symbol size from the PHY layer.

[0144] As shown by reference numeral 915, transmitting device 805 can transmit multiple RLC PDUs corresponding to multiple source symbols, and receiving device 810 can receive these multiple RLC PDUs. Multiple RLCPDUs can be transmitted without external decoding symbol segmentation. This saves the overhead associated with RLCs and external decoding headers caused by external decoding symbol segmentation.

[0145] As indicated by reference numeral 920 in the accompanying drawings, the receiving device 810 can identify that the RLC PDU is segmented according to the size of the external decoded symbol. In some aspects, the receiving device 810 (e.g., an external decoder encoder) can obtain an indication of the size of the external decoded symbol from the post-header of the external decoded message.

[0146] As indicated by reference numeral 925, the receiving device 810 can generate multiple source symbols at least partially based on the RLC PDU and the external decoded symbol size. In one example, for source symbols, the external decoder encoder may assume that the delivered RLC PDU is segmented according to the external decoded symbol size and can generate (e.g., recover) multiple source symbols at least partially based on the external decoded symbol size. For parity symbols, the external decoder encoder may receive additional parity symbols and can recover source symbols at least partially based on the multiple parity symbols.

[0147] In some respects, pipelined PDCP PDUs, as well as parallel stacks and external decoding processing, can be supported by generating multiple external decoding source symbols without segmenting the PDCP PDU. Additionally, there can be no additional overhead associated with RLC and external decoding headers, and the external decoding source symbols are compatible with legacy systems and legacy source symbols.

[0148] In some respects, the externally decoded source symbol may be associated with a symbol index. The transmitting device 805 may indicate a first externally decoded symbol index in the post-decoded header. The receiving device 810 may identify the externally decoded symbol index at least in part based on the symbol index indicated in the post-decoded header and the segmented order of the externally decoded symbols. For example, the receiving device 810 may obtain an indication of the first externally decoded symbol index and may calculate each segmented externally decoded symbol index in the segmented externally decoded symbol index at least in part based on the first externally decoded symbol index.

[0149] In some respects, the transmitting device 805 and the receiving device 810 may identify (e.g., hypothetically) zero-padding for the last of a plurality of externally decoded symbols. This may align the size of the externally decoded symbol with the size of the PDCP packet.

[0150] As indicated above, Figure 9 is provided as an example. Other examples may differ from those described with respect to Figure 9.

[0151] Figure 10 is a diagram illustrating an example 1000 assembled according to the external decoding block of this disclosure.

[0152] A transmitting device (such as transmitting device 805) can generate multiple externally decoded source symbols, at least partially based on multiple PDCP PDUs, without segmenting the externally decoded source symbols or PDCP PDUs. As shown by reference numeral 1005, the transmitting device can obtain multiple IP packets. The transmitting device can generate multiple PDCP PDUs, at least partially based on the multiple IP packets. The transmitting device can generate a pre-decoding header for each of the multiple PDCP PDUs. At the RLC layer, the transmitting device can segment the PDCP PDU (with the pre-decoding header) into multiple externally decoded symbols, generate multiple externally decoded source symbols, perform external decoding encoding on the multiple externally decoded source symbols, generate a post-decoding header for the multiple externally decoded source symbols, and generate multiple RLC PDUs, at least partially based on the multiple externally decoded source symbols with the post-decoding header. In some examples, the size of the externally decoded header may be at least partially based on (e.g., may be equal to) the externally decoded header size plus the PDCP PDU size. For example, in the external decoding sublayer, an externally decoded PDU source symbol may be defined using a PDCP PDU with an externally decoded header. Additionally or alternatively, the size of the externally decoded header may be at least partially based on (e.g., may be equal to) the externally decoded header size plus the externally decoded parity symbol size. For example, in the external decoding sublayer, an externally decoded PDU source symbol may be defined using a parity symbol with an externally decoded header. The transmitting device may generate multiple MAC transport blocks (TBs) at least partially based on multiple RLC PDUs. As shown in Figure 10, the transmitting device may transmit RLC packets associated with multiple externally decoded source symbols without segmentation based on the externally decoded symbol size. As indicated by reference numeral 1010, the transmitting device may transmit multiple MAC TBs via a radio interface, and a receiving device (such as receiving device 810) may receive multiple MAC TBs via a radio interface. As shown by reference numeral 1015 in the attached figure, at the RLC layer, the receiving device can generate multiple RLC PDUs at least partially based on multiple MAC TBs, perform external decoding symbol reordering, perform external decoding symbol decoding, generate multiple external decoding source symbols at least partially based on external symbol decoding, and perform aggregation for multiple PDCPPDUs. Additionally, the receiving device can perform PDCP PDU reconstruction, perform PDCP PDU packetization, generate multiple PDCP PDUs at least partially based on PDCP PDU packetization, and generate multiple IP packets at least partially based on PDCP PDUs. As shown in Figure 10, the receiving device can segment RLC packets into multiple external decoding source symbols at least partially based on the size of the external decoding symbol included in the external decoding header.

[0153] As indicated above, Figure 10 is provided as an example. Other examples may differ from those described with respect to Figure 10.

[0154] Figure 11 is an illustration of example 1100 of adjusting the size of the external decoding symbol according to the present disclosure.

[0155] As indicated by reference numeral 1105 in the accompanying drawing, the transmitting device 805 may receive multiple PDCP packets. These multiple packets may be multiple PDCP PDUs. In some aspects, the multiple PDCP packets may be a single PDU set or multiple PDU sets.

[0156] As indicated by reference numeral 1110, transmitting device 805 may generate multiple external decoding symbols based on multiple PDCP packets. For example, transmitting device 805 may identify the maximum PDCP packet size among the multiple PDCP packets and may generate multiple external decoding symbols based on the maximum PDCP packet size. As described herein, each external decoding symbol included in an external decoding block may have the same size. Therefore, generating multiple external decoding symbols may include generating multiple external decoding symbols of the same size equal to the maximum PDCP packet size. In some aspects, zero padding may be assumed for smaller PDCP packets (e.g., PDCP packets that do not have the maximum PDCP packet size) to align the external decoding symbol size with the maximum PDCP packet size.

[0157] As indicated by reference numeral 1115 in the accompanying drawings, the transmitting device 805 can adjust the PDCP packet size to be equal to the external decoding symbol size. For example, the transmitting device 805 can identify one or more PDCP packets with a PDCP packet size that is not equal to the external decoding symbol size, and can adjust the size of one or more PDCP packets to be equal to the external decoding symbol size. In some aspects, one or more PDCP packets can be adjusted to the external decoding symbol size during the external decoding or encoding process. Additionally, not all external decoding symbols may require concatenation and segmentation. This allows for pipelined PDCP PDUs and allows for improved parallel stacks and external decoding processing.

[0158] As indicated by reference numeral 1120 in the accompanying drawings, transmitting device 805 may transmit multiple RLC packets. For example, transmitting device 805 may transmit a single RLC packet for each of multiple PDCP packets.

[0159] As indicated above, Figure 11 is provided as an example. Other examples may differ from those described with respect to Figure 11.

[0160] Figure 12 is a diagram illustrating example 1200 of radio link control packet transmission using the Maximum Packet Data Convergence Protocol (MPDC) packet size according to this disclosure. As indicated by reference numeral 1205, a transmitting device (such as transmitting device 805) may obtain multiple IP packets. The multiple IP packets may be included in a PDU set. The multiple IP packets may be based at least in part on multiple Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) information. The TCP or UDP information may be based at least in part on Real-Time Transport (RTP) or Secure RTP (SRTP) information. The transmitting device may generate a pre-decoding header for the multiple PDCP packets, generate multiple externally decoded source symbols at least in part based on the multiple PDCP packets and the pre-decoding header, perform external decoding encoding on the multiple externally decoded source symbols, and generate a post-decoding header at least in part based on the external decoding encoding performed on the multiple externally decoded source symbols. The transmitting device may generate multiple RLC packets, at least in part, based on performing external decoding and generating an externally decoded header, and may generate multiple MAC TBs, at least in part, based on the multiple RLC packets. In some examples, the externally decoded header size may be at least in part based on (e.g., equal to) the externally decoded header size plus the PDCP PDU size. For example, in the external decoding sublayer, an externally decoded PDU source symbol may be defined using a PDCP PDU with an externally decoded header. Additionally or alternatively, the externally decoded header size may be at least in part based on (e.g., equal to) the externally decoded header size plus the externally decoded parity symbol size. For example, in the external decoding sublayer, an externally decoded PDU source symbol may be defined using a parity symbol with an externally decoded header. As indicated by reference numeral 1210, the transmitting device may transmit multiple MAC TBs via a radio interface. As shown by reference numeral 1215, a receiving device (such as receiving device 810) can receive multiple MAC TBs, generate multiple RLC packets at least partially based on the multiple MAC TBs, perform external decoding for the multiple RLC packets, generate multiple external decoding source symbols at least partially based on external decoding for the multiple RLC packets, and perform aggregation for multiple PDCP PDUs at least partially based on the multiple RLC packets. The receiving device can perform PDCP PDU packetization at least partially based on the aggregation of multiple PDCP PDUs, generate multiple PDCPPDUs at least partially based on the PDCP PDU packetization, and generate multiple IP packets at least partially based on the multiple PDCP PDUs.

[0161] As indicated above, Figure 12 is provided as an example. Other examples may differ from those described with respect to Figure 12.

[0162] As described herein, in Option 1 (as described in the first example of Figure 8), the transmitting device can perform external decoding block assembly before external decoding symbol segmentation. In Option 2 (as described in the second example of Figure 8), the transmitting device can perform external decoding symbol segmentation before performing external decoding block assembly. In Option 3 (as described in Figure 9), the transmitting device can perform external decoding block assembly without performing external decoding source symbol segmentation. In Option 4 (as described in Figure 11), the transmitting device can generate external decoding symbols based on the maximum PDCP PDU size. Table 1 shows a comparison of the first, second, third, and fourth options.

[0163] Table 1

[0164] Figure 13 is an illustration of example 1300 of zero-padding for segmented external decoded symbols according to this disclosure. In some cases, the PDCP packet size and the external decoded symbol size may not be aligned with each other (e.g., they may not be the same size). For example, the external decoded symbol size may be determined by the RAN, and the PDCP PDU size may be determined by the application layer (and may be equal to the IP packet size plus the SDAP / PDCP header size). In this case, the transmitting device (such as transmitting device 805) and the receiving device (such as receiving device 810) may indicate zero-padding to align the external decoded symbol size with the PDCP PDU size.

[0165] As indicated by reference numeral 1305 in the accompanying drawing, the transmitting device 805 may receive multiple PDCP packets. These multiple packets may be multiple PDCP PDUs. In some aspects, the multiple PDCP packets may be a single PDU set or multiple PDU sets.

[0166] As shown by reference numeral 1310 in the accompanying drawings, the transmitting device 805 can calculate the difference between the PDCP packet size and the external decoding symbol size. For example, the transmitting device 805 can subtract the external decoding symbol size from the PDCP packet size.

[0167] As shown by reference numeral 1315, transmitting device 805 may apply zero-padding to multiple externally decoded symbols. Transmitting device 805 may apply zero-padding based at least in part on calculating the difference between the PDCP packet size and the externally decoded symbol size. For a source symbol, transmitting device 805 may identify the zero-padding to be applied at the end of each externally decoded symbol segment. Transmitting device 805 may determine that the zero-padding length will be equal to the externally decoded symbol size minus the size of the last segmented RLC SDU. For example, zero-padding length = (OC symbol size) - (size of the last segmented RLC SDU). Zero-padding may not be transmitted over the air. Instead, the OC sublayer may add zero-padding during FEC encoding or decoding. This saves radio resources associated with zero-padding.

[0168] As indicated by reference numeral 1320 in the accompanying drawings, transmitting device 805 can transmit an externally decoded block comprising multiple externally decoded symbols, and receiving device 810 can receive the externally decoded block. As described above, transmitting device 805 can transmit multiple externally decoded symbols, but may not transmit zero-filling symbols.

[0169] As shown by reference numeral 1325 in the accompanying drawings, the receiving device 810 can calculate the difference between the packet size and the external decoding symbol size. For example, the receiving device 810 can subtract the external decoding symbol size from the PDCP packet size.

[0170] As shown by reference numeral 1330 in the accompanying drawing, the receiving device 810 can estimate the zero-padding length for multiple externally decoded symbols. In some aspects, the OC sublayer can estimate the zero-padding length based at least in part on the symbol size and the size of the received packet. For example, the receiving device 810 can determine that the zero-padding length will be equal to the OC symbol size minus the modulo operation between the RLC PDU size and the OC symbol size. For example, zero-padding length = (OC symbol size) - ((RLC PDU size) mod (OC symbol size)).

[0171] As indicated above, Figure 13 is provided as an example. Other examples may differ from those described with respect to Figure 13.

[0172] Figures 14A and 14B are illustrations illustrating examples of zero-filling performed by the transmitting and receiving devices according to the present disclosure.

[0173] As shown in Figure 14A and Example 1400, a transmitting device (such as transmitting device 805) can generate multiple source symbols. As indicated by reference numeral 1405, zero-padding (e.g., one or more zero-padding signals) can be encoded at the end of each externally decoded symbol segment. In this example, the PDCP PDU may not be segmented according to the externally decoded symbol size, and the size of the last segmented RLC PDU may differ from the externally decoded symbol size. The transmitting device may assume one or more zero-padding bits for the last RLC PDU in the PDCP PDU. In some respects, the zero-padding length may be equal to the externally decoded symbol size minus the size of the last segmented RLC PDU. As indicated by reference numeral 1410, the transmitting device can transmit multiple RLCPDUs. As indicated by reference numeral 1415, the RLC PDU may not include zero-padding. Zero-padding symbols may not be transmitted over the air, for example, to save radio resources.

[0174] As shown in Figure 14B and Example 1420, a receiving device (e.g., receiving device 810) can receive multiple RLC PDUs and can perform external decoding symbol reordering. The receiving device (e.g., a decoder associated with the receiving device) can decode the externally decoded symbols to obtain multiple externally decoded source symbols. At the RLC layer, if PDCP packets are segmented into multiple RLC SDUs, the RLC SDUs can be reassembled. At the external decoding decoder, the RLC SDUs can be segmented according to the externally decoded symbol size. In some aspects, the receiving device can assume one or more zero-padding bits for the last externally decoded symbol in the RLC PDU. As shown by reference numeral 1425, the external decoding sublayer can estimate the zero-padding length at least in part based on the externally decoded symbol size and / or the reassembled RLC PDU size. In some aspects, the zero-padding length can be equal to the externally decoded symbol size minus the modulo operation between the RLC PDU size and the externally decoded symbol size. The externally decoded symbol size can be indicated in the post-decoded header, and the RLC PDU size can be indicated in the MAC header. In some respects, the received RLC PDU can be reconstructed into a PDCPPDU with an RLC header. Additionally, the recovered symbols can be reconstructed into a PDCP PDU based on the PDCP length indicator included in the pre-decoding header.

[0175] As indicated above, Figures 14A and 14B are provided as examples. Other examples may differ from those described with respect to Figures 14A and 14B.

[0176] Figure 15 is a diagram illustrating an example 1500 of zero-padding for externally decoded symbols according to the present disclosure. A transmitting device (such as transmitting device 805) may obtain multiple RLC SDUs 1505. For example, the transmitting device may obtain RLC SDU 0, RLC SDU 1, RLC SDU 2, RLC SDU 3, and RLC SDUK-1. The transmitting device may generate multiple source symbols 1510 at least partially based on external decoding. For example, the transmitting device may generate source symbol 0 (at least partially based on RLC SDU 0), source symbol 1 (at least partially based on RLC SDU 1), source symbol 2 (at least partially based on RLC SDU 2), source symbol 3 (at least partially based on RLC SDU 3), and source symbol K (at least partially based on RLC SDUK). The transmitting device may generate one or more zero-padding bits 1515 to be added to the source symbols 1510. For example, the zero-padding bits 1515 may align the size of the source symbol with the symbol size (T) (e.g., the maximum value of the information symbol). Zero-padding bits may not be delivered over the air. Zero-padding can be assumed only for FEC encoding and decoding. The transmitting device can generate one or more parity symbols 1520, such as parity symbol K and parity symbol N. The transmitting device can generate parity symbols 1520 while the RAN is transmitting system symbols (e.g., source symbols). The transmitting device can generate one or more transport blocks 1525. The MAC header can indicate the boundary of each PDCP SDU, where the encoded symbol is equal to the PDCP SDU. For system symbols (source symbols), transport blocks can be transmitted according to legacy transmission. Parity symbols can be transmitted to improve the reliability of successful reception of source symbols by the receiving device.

[0177] In some aspects, the transmitting device may not indicate the external decoded symbol size for each external decoded block. For example, the transmitting device may indicate the external decoded symbol size only once. In this case, the receiving device can use the indicated symbol size for each external decoded block and may not update the external decoded symbol size until the receiving device receives additional signaling (e.g., semi-static signaling) from the transmitting device. For example, the receiving device may use the indicated external decoded symbol size for all external decoded symbols until the receiving device receives semi-static signaling indicating an update to the external decoded symbol size. Thereafter, the receiving device may use the updated external decoded symbol size for the external decoded symbols and / or for subsequent external decoded symbols. This reduces the signaling overhead for indicating and updating symbol sizes.

[0178] In some cases, the external decoding symbol size can be set to the maximum PDU size of the PDU set. However, this may cause the server (e.g., the transmitting device) to generate PDUs with larger PDU sizes (such as larger PDU sizes than permitted for external decoding encoding). In some aspects, the server and network nodes can negotiate the maximum permitted PDU size for a PDU. For example, the network node can send an indication of the maximum permitted PDU size for a PDCP PDU, and the transmitting device can receive this indication. The transmitting device can suppress the transmission of PDUs with PDU sizes larger than the maximum PDU size indicated by the network node. In some aspects, the transmitting device can send information to the network node to assist the network node in determining or updating the maximum PDU size.

[0179] As indicated above, Figure 15 is provided as an example. Other examples may differ from those described with respect to Figure 15.

[0180] Figure 16 is a diagram illustrating an example process 1600 performed, for example, at a transmitting device or an apparatus of a transmitting device according to the present disclosure. Example process 1600 is an example of an apparatus or transmitting device (e.g., transmitting device 805) performing operations associated with network decoding for packet data convergence protocol communication.

[0181] As shown in Figure 16, in some aspects, process 1600 may include acquiring multiple PDCP packets (block 1610). For example, a transmitting device (e.g., using the receiving component 2102 and / or communication manager 2106 depicted in Figure 2100) may acquire multiple PDCP packets as described above.

[0182] As further shown in Figure 16, in some aspects, process 1600 may include generating a plurality of source symbols by applying forward error correction coding to a plurality of PDCP packets, wherein the plurality of source symbols are non-segmented externally decoded source symbols (box 1620). For example, a transmitting device (e.g., using communication manager 2106 depicted in Figure 2100) may generate a plurality of source symbols by applying forward error correction coding to a plurality of PDCP packets, wherein the plurality of source symbols are non-segmented externally decoded source symbols, as described above.

[0183] As further shown in Figure 16, in some aspects, process 1600 may include transmitting multiple source symbols (block 1630). For example, a transmitting device (e.g., using the transmitting component 2104 and / or communication manager 2106 depicted in Figure 2100) may transmit multiple source symbols as described above.

[0184] Process 1600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0185] In the first aspect, process 1600 includes generating a plurality of external decoding parity symbols based on a plurality of source symbols.

[0186] In the second aspect, generating multiple external decoding parity symbols, either alone or in combination with the first aspect, includes generating multiple external decoding parity symbols based on multiple source symbols and the size of the external decoding symbols.

[0187] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1600 includes obtaining an indication of the size of the externally decoded symbols from the physical layer, wherein the plurality of externally decoded parity symbols are at least partially based on the size of the externally decoded symbols.

[0188] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the size of the source symbol associated with multiple source symbols is smaller than the size of the PDCP packet associated with multiple PDCP packets.

[0189] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1600 includes indicating a source symbol index for a first source symbol among a plurality of source symbols.

[0190] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1600 includes suppressing the source symbol index indicating the remainder of the plurality of source symbols after the first source symbol.

[0191] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1600 includes identifying the zero-padding length for the last external decoded symbol associated with a PDCP packet among a plurality of PDCP packets, thereby aligning the size of the last external decoded symbol with the size of the PDCP packet.

[0192] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, identifying the zero-padding length for the last external decoded symbol includes aligning the size of the last external decoded symbol with the size of the PDCP packet based at least in part on the zero-padding length.

[0193] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, multiple PDCP packets are multiple PDCP protocol data units.

[0194] In the tenth aspect, the transmitting device is a network node, either alone or in combination with one or more of the first to ninth aspects.

[0195] In the eleventh aspect, the transmitting device is a UE, either alone or in combination with one or more of the first to tenth aspects.

[0196] Although Figure 16 shows example blocks of process 1600, in some respects process 1600 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in Figure 16. Additionally or alternatively, two or more blocks in the blocks of process 1600 may be executed in parallel.

[0197] Figure 17 is a diagram illustrating an example process 1700 performed, for example, at a transmitting device or an apparatus of a transmitting device according to the present disclosure. Example process 1700 is an example of an apparatus or transmitting device (e.g., transmitting device 805) performing operations associated with network decoding for packet data convergence protocol communication.

[0198] As shown in Figure 17, in some aspects, process 1700 may include acquiring multiple PDCP packets (block 1710). For example, a transmitting device (e.g., using the receiving component 2102 and / or communication manager 2106 depicted in Figure 21) may acquire multiple PDCP packets as described above.

[0199] As further shown in Figure 17, in some aspects, process 1700 may include generating multiple external decoding symbols based on the maximum PDCP packet size of the multiple PDCP packets (box 1720). For example, a transmitting device (e.g., using the communication manager 2106 depicted in Figure 21) may generate multiple external decoding symbols based on the maximum PDCP packet size of the multiple PDCP packets, as described above.

[0200] As further shown in Figure 17, in some aspects, process 1700 may include adjusting the PDCP packet size to be equal to the external decoding symbol size of a plurality of external decoding symbols for one or more PDCP packets that do not have a maximum PDCP packet size (box 1730). For example, a transmitting device (e.g., using the communication manager 2106 depicted in Figure 21) may adjust the PDCP packet size to be equal to the external decoding symbol size of a plurality of external decoding symbols for one or more PDCP packets that do not have a maximum PDCP packet size, as described above.

[0201] As further shown in Figure 17, in some aspects, process 1700 may include sending multiple PDCP packets according to adjusting the PDCP packet size (block 1740). For example, a transmitting device (e.g., using the transmitting component 2104 depicted in Figure 21) may send multiple PDCP packets according to adjusting the PDCP packet size, as described above.

[0202] Process 1700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0203] In a first aspect, process 1700 includes transmitting a single radio link control layer packet corresponding to each of the plurality of PDCP packets.

[0204] In a second aspect, transmitting a single radio link control layer packet, either alone or in combination with the first aspect, includes transmitting a single radio link control layer packet corresponding to each of the plurality of PDCP packets without performing a cascading or segmentation operation.

[0205] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1700 includes applying forward error correction coding to an external decoding block comprising a plurality of external decoding symbols.

[0206] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1700 includes identifying one or more zero-padding bits to be applied to PDCP packets that do not have a size equal to the largest PDCP packet size among a plurality of PDCP packets.

[0207] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, identifying one or more zero-padding bits to be applied to the PDCP packet includes identifying one or more zero-padding bits to be applied to the PDCP packet to align the size of the PDCP packet with the maximum PDCP packet size.

[0208] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, multiple PDCP packets are multiple PDCP protocol data units.

[0209] In the seventh aspect, the transmitting device is a network node, either alone or in combination with one or more of the first to sixth aspects.

[0210] In the eighth aspect, the transmitting device is a UE, either alone or in combination with one or more of the first to seventh aspects.

[0211] Although Figure 17 shows example blocks of process 1700, in some respects process 1700 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in Figure 17. Additionally or alternatively, two or more blocks of process 1700 may be executed in parallel.

[0212] Figure 18 is a diagram illustrating an example process 1800 performed, for example, at a transmitting device or an apparatus of a transmitting device according to the present disclosure. Example process 1800 is an example of an apparatus or transmitting device (e.g., transmitting device 805) performing operations associated with network decoding for packet data convergence protocol communication.

[0213] As shown in Figure 18, in some aspects, process 1800 may include acquiring multiple PDCP packets (block 1810). For example, a transmitting device (e.g., using the receiving component 2102 and / or communication manager 2106 depicted in Figure 21) may acquire multiple PDCP packets as described above.

[0214] As further shown in Figure 18, in some aspects, process 1800 may include applying zero-padding to a plurality of external decoded symbols based on the difference between the PDCP packet size associated with a plurality of PDCP packets and the external decoded symbol size associated with a plurality of external decoded symbols (box 1820). For example, a transmitting device (e.g., using the communication manager 2106 depicted in Figure 21) may apply zero-padding to a plurality of external decoded symbols based on the difference between the PDCP packet size associated with a plurality of PDCP packets and the external decoded symbol size associated with a plurality of external decoded symbols, as described above.

[0215] As further shown in Figure 18, in some aspects, process 1800 may include transmitting an externally decoded block based on applying zero padding to a plurality of externally decoded symbols (box 1830). For example, as described above, a transmitting device (e.g., using the transmitting component 2104 and / or communication manager 2106 depicted in Figure 21) may transmit an externally decoded block based on applying zero padding to a plurality of externally decoded symbols.

[0216] Process 1800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0217] In a first aspect, applying zero-padding to a plurality of externally decoded symbols includes adding one or more zero-padding bits to the plurality of externally decoded symbols, and wherein transmitting the externally decoded block includes suppressing the transmission of one or more zero-padding bits associated with the plurality of externally decoded symbols.

[0218] In a second aspect, either alone or in combination with the first aspect, process 1800 includes obtaining an indication of the size of the externally decoded symbol from the physical layer.

[0219] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1800 includes obtaining an indication of the PDCP packet size from the application layer, wherein the PDCP packet size is based on at least one of the IP packet size and the Service Data Adaptation Protocol header size or the PDCP header size.

[0220] In the fourth aspect, zero-padding is applied to a plurality of externally decoded symbols, either alone or in combination with one or more of the first to third aspects, including applying zero-padding to the end of each of the plurality of externally decoded symbols.

[0221] In the fifth aspect, applying zero padding to the end of each externally decoded symbol, either alone or in combination with one or more of the first to fourth aspects, comprises applying zero padding to the end of each externally decoded symbol based on the size of the externally decoded block symbol minus the size of the last segmented radio link control service data unit.

[0222] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1800 includes adding one or more zero-padding symbols to the end of each of the plurality of externally decoded symbols by the external decoding sublayer according to forward error correction coding.

[0223] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, multiple PDCP packets are multiple PDCP protocol data units.

[0224] In the eighth aspect, the transmitting device is a network node, either alone or in combination with one or more of the first to seventh aspects.

[0225] In the ninth aspect, the transmitting device is a UE, either alone or in combination with one or more of the first to eighth aspects.

[0226] Although Figure 18 shows example blocks of process 1800, in some respects process 1800 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in Figure 18. Additionally or alternatively, two or more blocks of process 1800 may be executed in parallel.

[0227] Figure 19 is a diagram illustrating an example process 1900 performed, for example, at a receiving device or an apparatus of a receiving device according to the present disclosure. Example process 1900 is an example of an apparatus or receiving device (e.g., receiving device 810) performing operations associated with network decoding for packet data convergence protocol communication.

[0228] As shown in Figure 19, in some aspects, process 1900 may include receiving multiple RLC packets (block 1910). For example, a receiving device (e.g., using the receiving component 2202 and / or communication manager 2206 depicted in Figure 22) may receive multiple RLC packets as described above.

[0229] As further shown in Figure 19, in some aspects, process 1900 may include identifying that multiple RLC packets are segmented according to the external decoded symbol size (box 1920). For example, a receiving device (e.g., using the communication manager 2206 depicted in Figure 22) may identify that multiple RLC packets are segmented according to the external decoded symbol size, as described above.

[0230] As further shown in Figure 19, in some aspects, process 1900 may include generating multiple source symbols based on multiple RLC packets and external decoded symbol sizes (box 1930). For example, a receiving device (e.g., using the communication manager 2206 depicted in Figure 22) may generate multiple source symbols based on multiple RLC packets and external decoded symbol sizes, as described above.

[0231] As further shown in Figure 19, in some aspects, process 1900 may include processing multiple source symbols to obtain multiple PDCP packets (block 1940). For example, a receiving device (e.g., using the communication manager 2206 depicted in Figure 22) may process multiple source symbols to obtain multiple PDCP packets, as described above.

[0232] Process 1900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0233] In a first aspect, process 1900 includes receiving a plurality of parity symbols, wherein generating a plurality of source symbols based on a plurality of RLC blocks and an external decoded symbol size includes generating a plurality of source symbols based on a plurality of RLC blocks, an external decoded symbol size, and a plurality of parity symbols.

[0234] In a second aspect, either alone or in combination with the first aspect, process 1900 includes receiving an index of externally decoded symbols to be used for error correction of corresponding externally decoded symbols, wherein the index of externally decoded symbols is based at least in part on an externally decoded post-header indication and a segmented externally decoded symbol sequence indication.

[0235] In the third aspect, receiving an external decoding symbol index, either alone or in combination with one or more of the first and second aspects, includes receiving an external decoding symbol index for a first external decoding symbol among a plurality of external decoding symbols.

[0236] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1900 includes calculating the index of the remaining portion of the externally decoded symbols for a plurality of externally decoded symbols.

[0237] In the fifth aspect, the receiving device is a network node, either alone or in combination with one or more of the first to fourth aspects.

[0238] In the sixth aspect, the receiving device is a UE, either alone or in combination with one or more of the first to fifth aspects.

[0239] Although Figure 19 shows example blocks of process 1900, in some respects process 1900 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in Figure 19. Additionally or alternatively, two or more blocks of process 1900 may be executed in parallel.

[0240] Figure 20 is a diagram illustrating an example process 2000 performed, for example, at a receiving device or an apparatus of a receiving device according to the present disclosure. Example process 2000 is an example of an apparatus or receiving device (e.g., receiving device 810) performing operations associated with network decoding for packet data convergence protocol communication.

[0241] As shown in Figure 20, in some aspects, process 2000 may include receiving multiple RLC PDUs (block 2010). For example, a receiving device (e.g., using the receiving component 2202 and / or communication manager 2206 depicted in Figure 22) may receive multiple RLC PDUs as described above.

[0242] As further shown in Figure 20, in some aspects, process 2000 may include estimating the zero-padding length for the plurality of external decoded symbols based on the difference between the RLC PDU size associated with the plurality of RLC PDUs and the external decoded symbol size associated with the plurality of external decoded symbols (box 2020). For example, a receiving device (e.g., using the communication manager 2206 depicted in Figure 22) may estimate the zero-padding length for the plurality of external decoded symbols based on the difference between the RLC PDU size associated with the plurality of RLC PDUs and the external decoded symbol size associated with the plurality of external decoded symbols, as described above.

[0243] As further shown in Figure 20, in some aspects, process 2000 may include processing multiple external decoding symbols according to a zero-padding length to obtain multiple PDCP PDUs (block 2030). For example, a receiving device (e.g., using the communication manager 2206 depicted in Figure 22) may process multiple external decoding symbols according to a zero-padding length to obtain multiple PDCP PDUs, as described above.

[0244] Process 2000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0245] In the first aspect, process 2000 includes obtaining an indication of the size of the externally decoded symbol from the physical layer.

[0246] In a second aspect, either alone or in combination with the first aspect, process 2000 includes obtaining an indication of the size of the RLCPDU from the application layer, wherein the RLC PDU size is at least partially based on the IP PDU size and at least one of the Service Data Adaptation Protocol header size or the RLC header size.

[0247] In the third aspect, estimating the zero-padding length for a plurality of externally decoded symbols, either alone or in combination with one or more of the first and second aspects, includes estimating the zero-padding length at the end of each of the plurality of externally decoded symbols.

[0248] In the fourth aspect, estimating the zero-padding length at the end of each externally decoded symbol, either alone or in combination with one or more of the first to third aspects, includes estimating the zero-padding length at the end of each externally decoded symbol based on the externally decoded symbol size and the RLC PDU size.

[0249] In the fifth aspect, estimating the zero-padding length based on the external decoded symbol size and the RLC PDU size, either alone or in combination with one or more of the first to fourth aspects, includes: calculating the zero-padding length by performing a modulo operation between the RLC protocol data unit size and the external decoded symbol size and subtracting the result of the modulo operation from the external decoded symbol size.

[0250] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 2000 includes generating multiple PDCP PDUs based on multiple RLC PDUs and RLC header information.

[0251] In the seventh aspect, the receiving device is a network node, either alone or in combination with one or more of the first to sixth aspects.

[0252] In the eighth aspect, the receiving device is a UE, either alone or in combination with one or more of the first to seventh aspects.

[0253] Although Figure 20 shows example blocks of process 2000, in some respects process 2000 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those depicted in Figure 20. Additionally or alternatively, two or more blocks of process 2000 may be executed in parallel.

[0254] Figure 21 is a diagram of an example device 2100 for wireless communication according to the present disclosure. Device 2100 may be a transmitting device, or a transmitting device may include device 2100. In some aspects, device 2100 includes a receiving component 2102, a transmitting component 2104, and / or a communication manager 2106 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 2106 is communication manager 140 as described in conjunction with Figure 1, and device 2100 may be a UE 120, may include UE 120, or may be included in UE 120. In some other aspects, communication manager 2106 is communication manager 150 as described in conjunction with Figure 1, and device 2100 may be a network node 110, may include network node 110, or may be included in network node 110. As shown, device 2100 can communicate with another device 2108 (such as a UE or a network node (such as a CU, DU, RU, or base station)) using receiving component 2102 and transmitting component 2104.

[0255] In some aspects, device 2100 may be configured to perform one or more operations described herein in conjunction with Figures 8 through 15. Additionally or alternatively, device 2100 may be configured to perform one or more processes described herein, such as process 1600 of Figure 16, process 1700 of Figure 17, process 1800 of Figure 18, or combinations thereof. In some aspects, device 2100 and / or one or more components shown in Figure 21 may include one or more components of the transmitting device described in conjunction with Figure 2. Additionally or alternatively, one or more components shown in Figure 21 may be implemented within one or more components described in conjunction with Figure 2. Additionally or alternatively, one or more components in this group may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0256] Receiver 2102 may receive communications from device 2108, such as reference signals, control information, data communications, or combinations thereof. Receiver 2102 may provide the received communications to one or more other components of device 2100. In some aspects, receiver 2102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signals to one or more other components of device 2100. In some aspects, receiver 2102 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof, in conjunction with the transmitting apparatus described in FIG. 2.

[0257] Transmitting component 2104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 2108. In some aspects, one or more other components of device 2100 may generate communications and provide the generated communications to transmitting component 2104 for transmission to device 2108. In some aspects, transmitting component 2104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and may transmit the processed signals to device 2108. In some aspects, transmitting component 2104 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof, in conjunction with the transmitting apparatus described in FIG. 2. In some aspects, transmitting component 2104 may co-located with receiving component 2102 in one or more transceivers.

[0258] The communication manager 2106 may support the operation of the receiving component 2102 and / or the transmitting component 2104. For example, the communication manager 2106 may receive information associated with configuring communication reception for the receiving component 2102 and / or configuring communication transmission for the transmitting component 2104. Additionally or alternatively, the communication manager 2106 may generate and / or provide control information to the receiving component 2102 and / or the transmitting component 2104 to control the reception and / or transmission of communication.

[0259] The receiving component 2102 can acquire multiple PDCP packets. The communication manager 2106 can generate multiple source symbols by applying forward error correction coding to the multiple PDCP packets, wherein the multiple source symbols are non-segmented externally decoded source symbols. The transmitting component 2104 can transmit the multiple source symbols. The communication manager 2106 can generate multiple externally decoded parity symbols based on the multiple source symbols.

[0260] Receiver 2102 may obtain an indication of the size of the externally decoded symbols from the physical layer, wherein the plurality of externally decoded parity symbols are at least partially based on the size of the externally decoded symbols. Communication manager 2106 may indicate the source symbol index for the first source symbol among the plurality of source symbols. Communication manager 2106 may suppress the indication of the source symbol index for the remainder of the plurality of source symbols after the first source symbol. Communication manager 2106 may identify the zero-padding length for the last externally decoded symbol associated with a PDCP packet among the plurality of PDCP packets, thereby aligning the size of the last externally decoded symbol with the size of the PDCP packet.

[0261] The receiving component 2102 can acquire multiple PDCP packets. The communication manager 2106 can generate multiple external decoding symbols based on the maximum PDCP packet size of the multiple PDCP packets. The communication manager 2106 can adjust the PDCP packet size to be equal to the external decoding symbol size associated with the multiple external decoding symbols for one or more PDCP packets that do not have a maximum PDCP packet size.

[0262] Transmitting component 2104 can transmit a single radio link control layer packet corresponding to each of the plurality of PDCP packets. Communication manager 2106 can apply forward error correction coding to an external decoding block comprising multiple external decoding symbols. Communication manager 2106 can identify one or more zero-padding bits to be applied to PDCP packets that do not have a size equal to the largest PDCP packet size among the plurality of PDCP packets.

[0263] The receiving component 2102 can acquire multiple PDCP packets. The communication manager 2106 can apply zero-padding to multiple externally decoded symbols based on the difference between the PDCP packet size associated with the multiple PDCP packets and the externally decoded symbol size associated with the multiple externally decoded symbols. The transmitting component 2104 can transmit an externally decoded block based on the application of zero-padding to the multiple externally decoded symbols.

[0264] Receiver 2102 may obtain an indication of the size of the externally decoded symbol from the physical layer. Receiver 2102 may obtain an indication of the PDCP packet size from the application layer, wherein the PDCP packet size is based on at least one of the IP packet size and the Service Data Adaptation Protocol header size or the PDCP header size. Communication manager 2106 may add one or more zero-padding symbols to the end of each of the plurality of externally decoded symbols according to forward error correction coding.

[0265] The number and arrangement of components shown in Figure 21 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 21. Furthermore, two or more components shown in Figure 21 may be implemented within a single component, or a single component shown in Figure 21 may be implemented as multiple distributed components. Additionally or alternatively, one or more sets of components shown in Figure 21 may perform one or more functions described as being performed by another set of components shown in Figure 21.

[0266] Figure 22 is a diagram of an example device 2200 for wireless communication according to the present disclosure. Device 2200 may be a receiving device, or a receiving device may include device 2200. In some aspects, device 2200 includes a receiving component 2202, a transmitting component 2204, and / or a communication manager 2206 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 2206 is communication manager 140 as described in conjunction with Figure 1, and device 2200 may be a UE 120, may include UE 120, or may be included in UE 120. In some other aspects, communication manager 2206 is communication manager 150 as described in conjunction with Figure 1, and device 2200 may be a network node 110, may include network node 110, or may be included in network node 110. As shown, device 2200 can communicate with another device 2208 (such as a UE or a network node (such as a CU, DU, RU, or base station)) using receiving component 2202 and transmitting component 2204.

[0267] In some aspects, apparatus 2200 may be configured to perform one or more operations described herein in conjunction with Figures 8 through 15. Additionally or alternatively, apparatus 2200 may be configured to perform one or more processes described herein, such as process 1900 of Figure 19, process 2000 of Figure 20, or combinations thereof. In some aspects, apparatus 2200 and / or one or more components shown in Figure 22 may include one or more components of the receiving device described in conjunction with Figure 2. Additionally or alternatively, one or more components shown in Figure 22 may be implemented within one or more components described in conjunction with Figure 2. Additionally or alternatively, one or more components in this group may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0268] Receiver 2202 may receive communications from device 2208, such as reference signals, control information, data communications, or combinations thereof. Receiver 2202 may provide the received communications to one or more other components of device 2200. In some aspects, receiver 2202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signals to one or more other components of device 2200. In some aspects, receiver 2202 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof, in conjunction with the receiving apparatus described in FIG. 2.

[0269] Transmitting component 2204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 2208. In some aspects, one or more other components of device 2200 may generate communications and provide the generated communications to transmitting component 2204 for transmission to device 2208. In some aspects, transmitting component 2204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and may transmit the processed signals to device 2208. In some aspects, transmitting component 2204 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof, in conjunction with the receiving device described in FIG. 2. In some aspects, transmitting component 2204 may co-located with receiving component 2202 in one or more transceivers.

[0270] The communication manager 2206 may support the operation of the receiving component 2202 and / or the transmitting component 2204. For example, the communication manager 2206 may receive information associated with configuring communication reception by the receiving component 2202 and / or configuring communication transmission by the transmitting component 2204. Additionally or alternatively, the communication manager 2206 may generate and / or provide control information to the receiving component 2202 and / or the transmitting component 2204 to control the reception and / or transmission of communication.

[0271] The receiving component 2202 can receive multiple RLC packets. The communication manager 2206 can identify that the multiple RLC packets are segmented according to the external decoded symbol size. The communication manager 2206 can generate multiple source symbols based on the multiple RLC packets and the external decoded symbol size.

[0272] The receiving component 2202 can receive multiple parity symbols, wherein generating multiple source symbols based on multiple RLC blocks and the size of the external decoded symbols includes generating multiple source symbols based on multiple RLC blocks, the size of the external decoded symbols, and multiple parity symbols. The receiving component 2202 can receive an external decoded symbol index to be used for error correction of the corresponding external decoded symbols, wherein the external decoded symbol index is at least partially based on the post-decoded header indication and the segmented external decoded symbol order indication. The communication manager 2206 can calculate the external decoded symbol index for the remaining portion of the external decoded symbols among the multiple external decoded symbols.

[0273] The receiving component 2202 can receive multiple RLC PDUs. The communication manager 2206 can identify the difference between the RLC PDU size associated with the multiple RLC PDUs and the size of the external decoded symbol associated with the multiple external decoded symbols. The communication manager 2206 can estimate the zero-padding length for the multiple external decoded symbols based on the difference between the RLC PDU size associated with the multiple RLC PDUs and the size of the external decoded symbol associated with the multiple external decoded symbols.

[0274] The receiving component 2202 can obtain an indication of the size of the externally decoded symbol from the physical layer. The receiving component 2202 can obtain an indication of the size of the RLC PDU from the application layer, wherein the RLC PDU size is at least partially based on the IP PDU size and at least one of the Service Data Adaptation Protocol header size or the RLC header size. The communication manager 2206 can generate multiple PDCP PDUs based on multiple RLC PDUs and RLC header information.

[0275] The number and arrangement of components shown in Figure 22 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 22. Furthermore, two or more components shown in Figure 22 may be implemented within a single component, or a single component shown in Figure 22 may be implemented as multiple distributed components. Additionally or alternatively, one or more sets of components shown in Figure 22 may perform one or more functions described as being performed by another set of components shown in Figure 22.

[0276] The following provides an overview of some aspects of this disclosure: Aspect 1: A method of wireless communication performed by a transmitting device, the method comprising: obtaining a plurality of Packet Data Convergence Protocol (PDCP) packets; generating a plurality of source symbols by applying forward error correction coding to the plurality of PDCP packets, wherein the plurality of source symbols are non-segmented externally decoded source symbols; and transmitting the plurality of source symbols by a radio link control layer.

[0277] Aspect 2: According to the method of aspect 1, the method further includes generating a plurality of external decoding parity check symbols based on the plurality of source symbols.

[0278] Aspect 3: According to the method of aspect 2, generating the plurality of external decoding parity symbols includes generating the plurality of external decoding parity symbols based on the plurality of source symbols and the size of the external decoding symbols.

[0279] Aspect 4: According to the method of aspect 3, the method further includes obtaining an indication of the size of the external decoding symbol from the physical layer, wherein the plurality of external decoding parity symbols are at least partially based on the size of the external decoding symbol.

[0280] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the size of the source symbol associated with the plurality of source symbols is smaller than the size of the PDCP packet associated with the plurality of PDCP packets.

[0281] Aspect 6: The method according to any one of aspects 1 to 5, the method further comprising indicating a source symbol index for a first source symbol among the plurality of source symbols.

[0282] Aspect 7: According to the method of aspect 6, the method further includes suppressing the source symbol index indicating the remainder after the first source symbol for the plurality of source symbols.

[0283] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising identifying a zero-padding length for the last external decoded symbol associated with a PDCP packet among the plurality of PDCP packets, thereby aligning the size of the last external decoded symbol with the size of the PDCP packet.

[0284] Aspect 9: According to the method of aspect 8, wherein identifying the zero-padding length for the last external decoded symbol includes aligning the size of the last external decoded symbol with the size of the PDCP packet based at least in part on the zero-padding length.

[0285] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the plurality of PDCP packets are a plurality of PDCP protocol data units.

[0286] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the transmitting device is a network node.

[0287] Aspect 12: The method according to any one of aspects 1 to 11, wherein the transmitting device is user equipment.

[0288] Aspect 13: A method for wireless communication performed by a transmitting device, the method comprising: obtaining a plurality of Packet Data Convergence Protocol (PDCP) packets; generating a plurality of external decoding symbols based on a maximum PDCP packet size of the plurality of PDCP packets; adjusting the PDCP packet size to be equal to the external decoding symbol size of the plurality of external decoding symbols for one or more PDCP packets that do not have the maximum PDCP packet size; and transmitting the plurality of PDCP packets based on the adjusted PDCP packet size.

[0289] Aspect 14: According to the method of aspect 13, the method further includes transmitting a single radio link control layer packet corresponding to each of the plurality of PDCP packets.

[0290] Aspect 15: According to the method of aspect 14, transmitting the single radio link control layer packet includes: transmitting the single radio link control layer packet corresponding to each of the plurality of PDCP packets without performing a concatenation operation or a segmentation operation.

[0291] Aspect 16: According to the method of aspect 14, the method further includes applying forward error correction coding to an external decoding block including the plurality of external decoding symbols.

[0292] Aspect 17: The method according to any one of Aspects 13 to 16, the method further comprising identifying one or more zero-padding bits to be applied to a PDCP packet that does not have a size equal to the size of the largest PDCP packet among the plurality of PDCP packets.

[0293] Aspect 18: The method according to aspect 17, wherein identifying the one or more zero-padding bits to be applied to the PDCP packet includes identifying the one or more zero-padding bits to be applied to the PDCP packet to align the size of the PDCP packet with the maximum PDCP packet size.

[0294] Aspect 19: The method according to any one of Aspects 13 to 18, wherein the plurality of PDCP packets are a plurality of PDCP protocol data units.

[0295] Aspect 20: The method according to any one of aspects 13 to 19, wherein the transmitting device is a network node.

[0296] Aspect 21: The method according to any one of aspects 13 to 20, wherein the transmitting device is user equipment.

[0297] Aspect 22: The method according to any one of aspects 13 to 21, wherein one or more processors are further configured to cause the transmitting device to receive from a network node an indication of the maximum protocol data unit size for a plurality of PDCP protocol data units.

[0298] Aspect 23: The method according to any one of aspects 13 to 22, wherein the plurality of PDCP packets are associated with at least one of a protocol data unit set or a protocol data unit burst.

[0299] Aspect 24: A method of wireless communication performed by a transmitting device, the method comprising: obtaining a plurality of Packet Data Convergence Protocol (PDCP) packets; applying zero-padding to the plurality of external decoding symbols based on a difference between a PDCP packet size associated with the plurality of PDCP packets and an external decoding symbol size associated with a plurality of external decoding symbols; and transmitting an external decoding block based on applying the zero-padding to the plurality of external decoding symbols.

[0300] Aspect 25: The method according to aspect 24, wherein applying the zero-padding to the plurality of external decoded symbols includes adding one or more zero-padding bits to the plurality of external decoded symbols, and wherein transmitting the external decoded block includes suppressing the transmission of the one or more zero-padding bits associated with the plurality of external decoded symbols.

[0301] Aspect 26: The method according to any one of Aspects 24 to 25, the method further comprising obtaining an indication of the size of the external decoded symbol from the physical layer.

[0302] Aspect 27: The method according to any one of Aspects 24 to 26, the method further comprising obtaining an indication of the PDCP packet size from the application layer, wherein the PDCP packet size is based on at least one of Internet Protocol packet size and Service Data Adaptation Protocol header size or PDCP header size.

[0303] Aspect 28: The method according to any one of Aspects 24 to 27, wherein applying the zero padding to the plurality of external decoded symbols comprises applying the zero padding to the end of each of the plurality of external decoded symbols.

[0304] Aspect 29: According to the method of aspect 28, applying the zero-padding to the end of each externally decoded symbol comprises: applying the zero-padding to the end of each externally decoded symbol based on the externally decoded block symbol size minus the size of the last segmented radio link control service data unit.

[0305] Aspect 30: According to the method of aspect 28, the method further includes adding one or more zero-padding symbols to the end of each of the plurality of externally decoded symbols by an external decoding sublayer according to forward error correction coding.

[0306] Aspect 31: The method according to any one of Aspects 24 to 30, wherein the plurality of PDCP packets are a plurality of PDCP protocol data units.

[0307] Aspect 32: The method according to any one of aspects 24 to 31, wherein the transmitting device is a network node.

[0308] Aspect 33: The method according to any one of aspects 24 to 32, wherein the transmitting device is user equipment.

[0309] Aspect 34: A method for wireless communication performed by a receiving device, the method comprising: receiving a plurality of radio link control (RLC) packets; identifying that the plurality of RLC packets are segmented according to an external decoded symbol size; generating a plurality of source symbols based on the plurality of RLC packets and the external decoded symbol size; and processing the plurality of source symbols to obtain a plurality of packet data convergence protocol (PDCP) packets.

[0310] Aspect 35: According to the method of aspect 34, the method further includes receiving a plurality of parity symbols, wherein generating the plurality of source symbols based on the plurality of RLC groups and the external decoded symbol size includes generating the plurality of source symbols based on the plurality of RLC groups, the external decoded symbol size, and the plurality of parity symbols.

[0311] Aspect 36: The method according to any one of Aspects 34 to 35, the method further comprising receiving an external decoded symbol index for error correction of a corresponding external decoded symbol, wherein the external decoded symbol index is based at least in part on an external decoded header indication and a segmented external decoded symbol sequence indication.

[0312] Aspect 37: The method according to aspect 36, wherein receiving the external decoding symbol index includes receiving the external decoding symbol index for a first external decoding symbol among a plurality of external decoding symbols.

[0313] Aspect 38: According to the method of aspect 37, the method further includes calculating the external decoding symbol index for the remaining portion of the external decoding symbols among the plurality of external decoding symbols.

[0314] Aspect 39: The method according to any one of aspects 34 to 38, wherein the receiving device is a network node.

[0315] Aspect 40: The method according to any one of aspects 34 to 39, wherein the receiving device is user equipment.

[0316] Aspect 41, the method according to any one of Aspects 34 to 40, wherein the plurality of PDCP packets are associated with at least one of a Protocol Data Unit set or a Protocol Data Unit burst.

[0317] Aspect 42: A method of wireless communication performed by a receiving device, the method comprising: receiving a plurality of Radio Link Control (RLC) Protocol Data Units (PDUs); estimating a zero-padding length for a plurality of externally decoded symbols based on a difference between an RLC PDU size associated with the plurality of RLC PDUs and an externally decoded symbol size associated with a plurality of externally decoded symbols; and processing the plurality of externally decoded symbols according to the zero-padding length to obtain a plurality of Packet Data Convergence Protocol (PDCP) PDUs.

[0318] Aspect 43: According to the method of aspect 42, the method further includes obtaining an indication of the size of the external decoded symbol from the physical layer.

[0319] Aspect 44: The method according to any one of Aspects 42 to 43, the method further comprising obtaining an indication of the size of the RLC PDU from the application layer, wherein the size of the RLC PDU is based at least in part on at least one of the Internet Protocol PDU size and the Service Data Adaptation Protocol header size or the RLC header size.

[0320] Aspect 45: The method according to any one of Aspects 42 to 44, wherein estimating the zero-padding length for the plurality of externally decoded symbols includes estimating the zero-padding length at the end of each of the plurality of externally decoded symbols.

[0321] Aspect 46: The method according to aspect 45, wherein estimating the zero-padding length at the end for each externally decoded symbol comprises estimating the zero-padding length at the end for each externally decoded symbol based on the externally decoded symbol size and the RLC PDU size.

[0322] Aspect 47: According to the method of aspect 46, estimating the zero-padding length based on the external decoded symbol size and the RLC PDU size comprises: calculating the zero-padding length by performing a modulo operation between the RLC protocol data unit size and the external decoded symbol size and subtracting the result of the modulo operation from the external decoded symbol size.

[0323] Aspect 48: The method according to any one of aspects 42 to 47, the method further comprising generating a plurality of Packet Data Convergence Protocol (PDCP) PDUs based on the plurality of RLCPDUs and RLC header information.

[0324] Aspect 49: The method according to any one of aspects 42 to 48, wherein the receiving device is a network node.

[0325] Aspect 50: The method according to any one of aspects 42 to 49, wherein the receiving device is user equipment.

[0326] Aspect 51: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 50.

[0327] Aspect 52: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 50.

[0328] Aspect 53: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 50.

[0329] Aspect 54: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 50.

[0330] Aspect 55: 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 according to one or more of aspects 1 to 50.

[0331] Aspect 56: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 50.

[0332] Aspect 57: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 50.

[0333] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0334] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented as hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be interpreted broadly as "at least partially based on". As used herein, depending on the context, "meeting a threshold" can refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc. As used herein, the phrase referring to "at least one of" a list of items means any combination of those items, including a single member. 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.

[0335] Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more”. Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more”. Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and are interchangeable with “one or more”. If only one item is desired, the phrase “only one” or similar terms will be used. Moreover, as used herein, the terms “having” and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, as used herein, the term “or” when used in a sequence is intended to be inclusive and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., in conjunction with “either of” or “only one of”).

[0336] The various exemplary logic components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and illustrated in the various exemplary components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0337] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be performed by circuitry dedicated to a given function.

[0338] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and their structural equivalents or any combination thereof. Aspects of the subject matter described in this specification may also be implemented as one or more computer programs (such as one or more modules of computer program instructions) encoded on a computer storage medium for execution by or control of the operation of a data processing apparatus.

[0339] If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted through a computer-readable medium. The processes of the methods or algorithms disclosed herein can be implemented in a processor-executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, with communication media including any medium capable of transferring a computer program from one place to another. Storage media can be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection may be properly referred to as a computer-readable medium. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, where disks typically magnetically reproduce data, while optical discs optically reproduce data using lasers. Combinations of media described herein should also be included within the scope of computer-readable media. Additionally, the operation of a method or algorithm may reside as a set of code and instructions or any combination of code and instructions on a machine-readable medium and a computer-readable medium that may be incorporated into a computer program product.

[0340] Various modifications to the aspects described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0341] Additionally, those skilled in the art will readily recognize that the terms “upper” and “lower” are sometimes used to facilitate the description of the drawings and to indicate relative positioning on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0342] Some features described in the context of an independent aspect in this specification may also be implemented in combination in a single aspect. Conversely, various features described in the context of a single aspect may also be implemented individually or in any suitable sub-combination in multiple aspects. Furthermore, although features may be described as functioning in certain combinations and even originally claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.

[0343] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the shown specific order or sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some contexts, multitasking and parallel processing are advantageous. Moreover, the separation of various system components in the described aspects should not be construed as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other aspects also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

Claims

1. An apparatus for wireless communication at a transmitting device, the apparatus comprising: One or more memory units; and one or more processors, said one or more processors coupled to said one or more memories, said one or more processors individually or collectively configured to enable said transmitting device to: acquire multiple Packet Data Convergence Protocol (PDCP) packets; The process involves generating multiple source symbols by applying forward error correction coding to the multiple PDCP packets, wherein the multiple source symbols are non-segmented externally decoded source symbols; and transmitting the multiple source symbols.

2. The apparatus of claim 1, wherein the one or more processors are further configured to cause the transmitting device to generate a plurality of external decoding parity symbols based on the plurality of source symbols.

3. The apparatus of claim 2, wherein, in order for the transmitting device to generate the plurality of external decoding parity symbols, the one or more processors are configured to cause the transmitting device to generate the plurality of external decoding parity symbols according to the plurality of source symbols and the size of the external decoding symbols.

4. The apparatus of claim 3, wherein the one or more processors are further configured to cause the transmitting device to obtain an indication of the size of the external decoded symbol from the physical layer, wherein the plurality of external decoded parity symbols are at least partially based on the size of the external decoded symbol.

5. The apparatus of claim 1, wherein the size of the source symbol associated with the plurality of source symbols is smaller than the size of the PDCP packet associated with the plurality of PDCP packets.

6. The apparatus of claim 1, wherein the one or more processors are further configured to cause the transmitting device to indicate a source symbol index for a first source symbol among the plurality of source symbols.

7. The apparatus of claim 6, wherein the one or more processors are further configured to cause the transmitting device to suppress indication of the source symbol index for the remainder after the first source symbol for the plurality of source symbols.

8. The apparatus of claim 1, wherein the one or more processors are further configured to cause the transmitting device to identify a zero-padding length for the last external decoded symbol associated with a PDCP packet among the plurality of PDCP packets, thereby aligning the size of the last external decoded symbol with the size of the PDCP packet.

9. The apparatus of claim 1, wherein the plurality of PDCP packets are associated with at least one of a protocol data unit set or a protocol data unit burst.

10. An apparatus for wireless communication at a receiving device, the apparatus comprising: One or more memory units; and one or more processors, said one or more processors coupled to said one or more memories, said one or more processors individually or collectively configured to cause said receiving device to: receive multiple radio link control (RLC) packets; The method identifies that the multiple RLC packets are segmented according to the size of the external decoded symbol; generates multiple source symbols based on the multiple RLC packets and the size of the external decoded symbol; and processes the multiple source symbols to obtain multiple Packet Data Convergence Protocol (PDCP) packets.

11. The apparatus of claim 10, wherein the one or more processors are further configured to cause the receiving device to receive a plurality of parity symbols, wherein generating the plurality of source symbols based on the plurality of RLC groups and the external decoded symbol size comprises generating the plurality of source symbols based on the plurality of RLC groups, the external decoded symbol size, and the plurality of parity symbols.

12. The apparatus of claim 10, wherein the one or more processors are further configured to cause the receiving device to receive an external decoded symbol index for error correction of a corresponding external decoded symbol, wherein the external decoded symbol index is based at least in part on an external decoded header indication and a segmented external decoded symbol order indication.

13. The apparatus of claim 12, wherein, in order for the receiving device to receive the external decoded symbol index, the one or more processors are configured to cause the receiving device to receive the external decoded symbol index for a first external decoded symbol among a plurality of external decoded symbols.

14. The apparatus of claim 13, wherein the one or more processors are further configured to cause the receiving device to calculate the external decoding symbol index for the remaining portion of the external decoding symbols among the plurality of external decoding symbols.

15. The apparatus of claim 10, wherein the plurality of PDCP packets are associated with at least one of a protocol data unit set or a protocol data unit burst.

16. An apparatus for wireless communication at a transmitting device, the apparatus comprising: One or more memory units; The transmitting device may include one or more processors coupled to one or more memories, the processors being individually or collectively configured to: acquire a plurality of Packet Data Convergence Protocol (PDCP) packets; generate a plurality of external decoding symbols based on a maximum PDCP packet size of the plurality of PDCP packets; adjust the PDCP packet size to be equal to the external decoding symbol size of the plurality of external decoding symbols for one or more PDCP packets that do not have the maximum PDCP packet size; and transmit the plurality of PDCP packets based on the adjusted PDCP packet size.

17. The apparatus of claim 16, wherein, in order for the transmitting device to transmit the plurality of PDCP packets, the one or more processors are configured to cause the transmitting device to transmit a single radio link control layer packet corresponding to each of the plurality of PDCP packets.

18. The apparatus of claim 17, wherein, in order for the transmitting device to transmit the single radio link control layer packet, the one or more processors are configured to cause the transmitting device to transmit the single radio link control layer packet corresponding to each of the plurality of PDCP packets without performing a concatenation operation or a segmentation operation.

19. The apparatus of claim 16, wherein the one or more processors are further configured to cause the transmitting device to identify one or more zero-padding bits to be applied to PDCP packets that do not have a size equal to the largest PDCP packet size among the plurality of PDCP packets.

20. The apparatus of claim 16, wherein the one or more processors are further configured to cause the transmitting device to receive from a network node an indication of the maximum protocol data unit size for a plurality of PDCP protocol data units.

Images