Enhancement of application data unit metadata

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive control information identifying criteria for determining a delivery state of a set of protocol data units (PDUs) including a plurality of PDUs. The set of PDUs may be associated with an application layer of the UE. Thus, the UE may receive at least a portion of the set of PDUs, and may determine a delivery status of the set of PDUs based on the received portion of the set of PDUs and the criteria identified by the control information. The delivery status of the set of PDUs may indicate whether the set of PDUs is successfully delivered to the UE. The delivery status of the set of PDUs may be based on a number of bits or PDUs in the received portion of the set of PDUs, a threshold number of bits or PDUs, or a combination thereof.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 884,550, entitled “ENHANCEMENTS TO APPLICATION DATA UNIT METADATA,” filed by Mondet et al. on August 9, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including enhancements to Application Data Unit (ADU) metadata. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE).

[0005] In some wireless communication systems, a UE may receive a data burst from a network entity. The UE may use various metrics to determine whether the burst was successfully delivered. However, in some cases, the relatively inflexible nature of these metrics may not be suitable for deployment scenarios with dynamic delivery conditions. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses that support enhancements of application data unit (ADU) metadata. More specifically, the technology described herein can improve the flexibility and applicability of ADU delivery standards. According to various aspects of the present disclosure, a user equipment (UE) may receive control information identifying a standard for determining the delivery status of a set of protocol data units (PDUs) associated with an application layer of the UE. The UE may receive at least a portion of a set of PDUs (equivalently referred to as ADUs). Therefore, the UE may determine the delivery status of the PDU set based on the received portion of the PDU set and the standard identified by the control information. The delivery status of the PDU set may indicate whether the PDU set is successfully delivered.

[0007] A method for wireless communication at a UE is described. The method may include receiving control information from a core network entity via an access network entity, the control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The method may also include receiving at least a portion of the PDU set with the control information. The method may also include determining a delivery status of the PDU set based on a value associated with the received portion of the PDU set and a threshold indicated by the criterion, the delivery status indicating whether the PDU set was successfully delivered to the UE.

[0008] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to receive control information from a core network entity via an access network entity, the control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The instructions may also be executable by the processor to cause the device to receive at least a portion of the PDU set with the control information. The instructions may also be executable by the processor to cause the device to determine a delivery status of the PDU set based on a value associated with a received portion of the PDU set and a threshold indicated by the criterion, the delivery status indicating whether the PDU set is successfully delivered to the UE.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include a component for receiving control information from a core network entity via an access network entity, the control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The apparatus may also include a component for receiving at least a portion of the PDU set with the control information. The apparatus may also include a component for determining a delivery status of the PDU set based on a value associated with the received portion of the PDU set and a threshold indicated by the criterion, the delivery status indicating whether the PDU set was successfully delivered to the UE.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to receive control information from a core network entity via an access network entity, the control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The instructions may also be executable by the processor to receive at least a portion of the PDU set with the control information. The instructions may also be executable by the processor to determine a delivery status of the PDU set based on a value associated with the received portion of the PDU set and a threshold indicated by the criterion, the delivery status indicating whether the PDU set was successfully delivered to the UE.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the delivery status of a PDU set may include operations, features, components, or instructions for determining whether the PDU set is successfully delivered to the UE based on a value of a number of PDUs preceding a first unsuccessfully delivered PDU included in the PDU set.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the delivery status of a PDU set may include operations, features, components, or instructions for determining whether the PDU set is successfully delivered to the UE based on the value of the number of bits preceding a first unsuccessfully delivered bit included in the PDU set.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the delivery status of a PDU set may include operations, features, components, or instructions for determining whether the PDU set is successfully delivered to the UE based on a value including a threshold number of PDUs and a number of PDUs in a received portion of the PDU set.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the delivery status of a PDU set may include operations, features, components, or instructions for determining whether the PDU set is successfully delivered to the UE based on a value including a number of bits in a received portion of the PDU set and a threshold including a threshold number of bits.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control information may include an operation, feature, component, or instruction for receiving an indication of a threshold value including a threshold number of PDUs for determining a delivery status of a set of PDUs, wherein the threshold number of PDUs is less than or equal to a total number of PDUs in the set of PDUs.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control information may include operations, features, components, or instructions for receiving an indication of a threshold including a threshold number of bits for determining a delivery status of a set of PDUs, wherein the threshold number of bits is less than or equal to a total number of bits in the set of PDUs.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control information may include an operation, feature, component, or instruction for receiving metadata indicating a stream type field associated with a PDU in a PDU set, a first sequence number associated with the PDU in the PDU set, a second sequence number associated with the PDU set, a number of PDUs in the PDU set, a content standard field associated with a delivery status of the PDU set, a user plane indicator field associated with the content standard field, or a combination thereof.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining, based on a value of a stream type field, whether the metadata includes a first sequence number, a second sequence number, a number of PDUs in a PDU set, and a user plane indicator field.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining whether the metadata includes a content criteria field based on a value of the user plane indicator field and a value of the stream type field.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first sequence number identifies a set of PDUs and the second sequence number identifies a PDU within the set of PDUs.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first value of a user plane indicator field indicates that a delivery status of a PDU set depends on whether all PDUs in the PDU set are successfully delivered, and a second value of the user plane indicator field indicates that a delivery status of the PDU set depends on a content standard field.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the content criteria field includes a forward error correction (FEC) information field, a delivery threshold field, or both.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control information may include an operation, feature, component, or instruction for receiving metadata indicating an applicability field associated with a standard, a size indicator field, a number of PDUs in a PDU set, a number of bits in the PDUs of the PDU set, an FEC indicator field, an FEC information field associated with a delivery status of the PDU set, a delivery threshold field associated with a delivery status of the PDU set, or a combination thereof.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining whether to be relative to a PDU or to a bit-defined standard based on a value of an applicability field.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining, based on a value of a size indicator field, whether the metadata indicates a number of PDUs in a PDU set.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining whether the metadata includes a FEC information field based on a value of the FEC indicator field.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a criterion based on a value of a suitability field, a value of a FEC indicator field, a value of a FEC information field, a value of a delivery threshold field, or a combination thereof.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining whether the metadata includes a delivery threshold field based on a value of the FEC indicator field and a value of the FEC information field.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, if the applicability field can be set to a first value, the delivery threshold field indicates a threshold number of PDUs, and if the applicability field can be set to a second value, the delivery threshold field indicates a threshold number of bits.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining, based on a value of the applicability field, whether the metadata indicates a number of bits in a PDU of a PDU set.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control information indicating whether a criterion may be associated with a dynamic FEC scheme or a static FEC scheme.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control information may be included in a Packet Data Convergence Protocol (PDCP) header of a PDU in the set of PDUs.

[0033] A method for wireless communication at an access network entity is described. The method may include outputting control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The method may also include outputting a plurality of PDUs in the PDU set with the control information, wherein the delivery status of the PDU set is based on a threshold indicated by the criterion.

[0034] An apparatus for wireless communication at an access network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to output control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The instructions may also be executable by the processor to cause the apparatus to output a plurality of PDUs in the PDU set with the control information, wherein the delivery status of the PDU set is based on a threshold indicated by the criterion.

[0035] Another apparatus for wireless communication at an access network entity is described. The apparatus may include means for outputting control information identifying criteria for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The apparatus may also include means for outputting a plurality of PDUs in the PDU set with the control information, wherein the delivery status of the PDU set is based on a threshold indicated by the criteria.

[0036] A non-transitory computer-readable medium storing code for wireless communication at an access network entity is described. The code may include instructions executable by a processor to output control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The instructions may also be executable by the processor to output a plurality of PDUs in the PDU set with the control information, wherein the delivery status of the PDU set is based on a threshold indicated by the criterion.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining at least a portion of the set of PDUs from a core network entity.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a delivery status of a set of PDUs based on the obtained portion of the set of PDUs and criteria identified by the control information.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the delivery status of a PDU set may include operations, features, components, or instructions for determining whether the PDU set is successfully delivered to an access network entity based on a number of PDUs preceding a first unsuccessfully delivered PDU in the PDU set.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the delivery status of a PDU set may include operations, features, components, or instructions for determining whether the PDU set is successfully delivered to an access network entity based on the number of bits before a first unsuccessfully delivered bit in the PDU set.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining a delivery status of a PDU set may include operations, features, components, or instructions for determining whether the PDU set is successfully delivered to an access network entity based on a threshold value including a threshold number of PDUs and a number of PDUs in an obtained portion of the PDU set.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining a delivery status of a PDU set may include operations, features, components, or instructions for determining whether the PDU set is successfully delivered to an access network entity based on a threshold including a threshold number of bits and a number of bits in an obtained portion of the PDU set.

[0043] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining an indication of a threshold value including a threshold number of PDUs for determining a delivery status of a set of PDUs, wherein the threshold number of PDUs is less than or equal to a total number of PDUs in the set of PDUs.

[0044] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining an indication of a threshold value including a threshold number of bits for determining a delivery status of a set of PDUs, wherein the threshold number of bits is less than or equal to a total number of bits in the set of PDUs.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, output control information may include operations, features, components, or instructions for outputting an indication of a threshold value including a threshold number of PDUs for determining a delivery status of a PDU set, wherein the threshold number of PDUs is less than or equal to a total number of PDUs in the PDU set.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, output control information may include operations, features, components, or instructions for outputting an indication of a threshold value including a threshold number of bits for determining a delivery status of a PDU set, wherein the threshold number of bits is less than or equal to a total number of bits in the PDU set.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the output control information may include operations, features, components, or instructions for outputting metadata indicating a stream type field associated with a PDU in a PDU set, a first sequence number associated with the PDU in the PDU set, a second sequence number associated with the PDU set, the number of PDUs in the PDU set, a content standard field associated with a delivery status of the PDU set, a user plane indicator field associated with the content standard field, or a combination thereof.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the output control information may include operations, features, components, or instructions for outputting metadata indicating an applicability field associated with a standard, a size indicator field, the number of PDUs in a PDU set, the number of bits in the PDUs of the PDU set, an FEC indicator field, an FEC information field associated with a delivery status of the PDU set, a delivery threshold field associated with the delivery status of the PDU set, or a combination thereof.

[0049] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of limitations to the claims.

[0050] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, each embodiment and / or use can be generated via an integrated chip embodiment and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and devices that enable artificial intelligence (AI)). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementation can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregation, distribution, or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more aspects of the described innovation. In some actual settings, the equipment in conjunction with the aspects and features must also include other components and features for the specific implementation and practice of the embodiments protected and described by the claims. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the innovations described herein can be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 An example of an enhanced wireless communication system supporting Application Data Unit (ADU) metadata in accordance with one or more aspects of the present disclosure is illustrated.

[0052] Figure 2 An example of an enhanced network architecture supporting ADU metadata according to one or more aspects of the present disclosure is illustrated.

[0053] Figure 3 An example of an enhanced wireless communication system supporting ADU metadata according to one or more aspects of the present disclosure is illustrated.

[0054] Figure 4 An example of an enhanced network diagram supporting ADU metadata in accordance with one or more aspects of the present disclosure is illustrated.

[0055] Figure 5 An example of an enhanced process flow supporting ADU metadata in accordance with one or more aspects of the present disclosure is illustrated.

[0056] Figure 6 and Figure 7 A block diagram of an enhanced device supporting ADU metadata according to one or more aspects of the present disclosure is shown.

[0057] Figure 8 A block diagram of an enhanced communication manager supporting ADU metadata in accordance with one or more aspects of the present disclosure is shown.

[0058] Fig. 9 A diagram of a system including an enhanced device supporting ADU metadata in accordance with one or more aspects of the present disclosure is shown.

[0059] Fig.10 and Fig.11 A block diagram of an enhanced device supporting ADU metadata according to one or more aspects of the present disclosure is shown.

[0060] Fig.12 A block diagram of an enhanced communication manager supporting ADU metadata in accordance with one or more aspects of the present disclosure is shown.

[0061] Fig.13 A diagram of a system including an enhanced device supporting ADU metadata in accordance with one or more aspects of the present disclosure is shown.

[0062] Figures 14 to 17 A flow chart illustrating an enhanced method of supporting ADU metadata according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0063] Some wireless communication systems may include various devices, such as user equipment (UE) and network entities (equivalently referred to as gNB or base station). In some cases, the network entity may send an application data unit (ADU) to the UE. The ADU (also referred to as a protocol data unit (PDU) set) may include one or more PDUs. The network entity may send the ADU in bursts at approximately the same time. The ADU may be routed from the application server to the UE via a user plane function (UPF) and one or more elements of the network entity. Each PDU in the ADU may include metadata that includes information related to the ADU. The metadata can be used to determine whether the ADU was successfully delivered. The ADU metadata may be provided by the application server or implicitly determined by the UPF service layer.

[0064] The ADU metadata may indicate the number of PDUs in the ADU, the ADU sequence number identifying the ADU, the PDU sequence number identifying the PDU within the ADU, the ADU burst number, the ADU discard time, and other fields defining rules for determining the delivery status of the ADU. These rules may be configured on a per-PDU basis. For example, the ADU metadata may define the number, ratio, or percentage of PDUs in the ADU that must be received for successful ADU delivery. However, existing ADU metadata frameworks may not support bit-level ADU delivery conditions and may not be suitable for some dynamic forward error correction (FEC) schemes.

[0065] Aspects of the present disclosure support an enhanced ADU metadata field structure that can be used for a wide range of ADU delivery scenarios. The enhanced ADU metadata framework described herein may include one or more ADU content criteria (ACC) fields, which can be used to dynamically configure or update ADU delivery conditions. These ACC fields may include an ACC application field, an ADU size indicator (ASI) field, an ADU size field, a PDU size field (the number of ADU bits in a PDU), an FEC information indicator (FII) field, an FEC information field, a delivery threshold field (a threshold number of bits or PDUs), or a combination thereof. These ACC fields may be included in the Packet Data Convergence Protocol (PDCP) header of the PDU. The UE (or any ADU recipient) can determine the delivery status of the ADU based on the criteria specified by these ACC fields.

[0066] In some examples, the delivery status of the ADU may depend on the number of PDUs or bits before the first unsuccessfully delivered PDU or bit of the ADU. In other examples, the delivery status of the ADU may depend on the number of successfully received PDUs or bits in the ADU and a threshold number of PDUs or bits. The UE may determine whether to determine the delivery status of the ADU relative to the bit or relative to the PDU based on the value of the ACC application field. Some of the ACC fields described herein (such as the ASI field and the FII field) may indicate whether other ACC fields (such as the ASI size field or the FEC information field) are present in the ADU metadata. The flexible ACC framework described herein may be applicable to a wide range of FEC schemes and ADU delivery conditions.

[0067] Various aspects of the present disclosure may be implemented to achieve one or more of the following advantages. The described techniques may improve the flexibility and applicability of existing ADU delivery conditions. For example, a network entity (or other communication device) may dynamically configure or update ADU delivery conditions based on the UE's FEC scheme (none, static, or dynamic). Similarly, a network entity may configure ADU delivery conditions relative to bits or PDUs, which may improve the flexibility of ADU delivery conditions. The enhanced ACC framework described herein may be used for various ADU metadata configuration and deployment scenarios.

[0068] Aspects of the present disclosure are first described in the context of wireless communication systems, network diagrams, and process flows. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to enhancement of ADU metadata.

[0069] Figure 1 An example of an enhanced wireless communication system 100 supporting ADU metadata according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0070] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other names. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0071] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices such as Figure 1 Other UEs 115 or network entities 105 are shown communicating.

[0072] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. For another example, the node may be a network entity 105. For another example, a first node may be configured to communicate with a second node or a third node.

[0073] In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, devices, equipment, computing systems, etc. may include disclosures of UE 115, network entity 105, devices, equipment, computing systems, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0074] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130).

[0075] In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to a midhaul interface protocol) or fronthaul communication link 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155.

[0076] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0077] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof.

[0078] The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0079] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionality depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of the protocol stack.

[0080] In some examples, CU 160 may host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), PDCP). CU 160 may be connected to one or more DUs 165 or RUs 170, and one or more DUs 165 or RUs 170 may host lower protocol layer, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160.

[0081] Additionally or alternatively, a functional split of the protocol stack may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack and RU 170 may support one or more different layers of the protocol stack. DU 165 may support one or more different cells (e.g., via one or more RU 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of a protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170).

[0082] CU 160 may be further functionally split into CU control plane (CU-CP) functionality and CU user plane (CU-UP) functionality. CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (e.g., a channel) between layers of a protocol stack, each layer of which is supported by a corresponding network entity 105 communicating via such a communication link.

[0083] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120).

[0084] The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0085] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0086] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward a child node associated with the IAB node 104, and an IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay transmissions to a UE through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

[0087] For example, the IAB node 104 may be referred to as a parent node supporting child IAB node communications or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 through the IAB node 104, or may directly signal the transmissions to the UE 115, or both. The CU 160 of the IAB donor may signal the IAB node 104 of the communication link establishment via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB nodes 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0088] Where the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support enhancements to the ADU metadata as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0089] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0090] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1shown.

[0091] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier used for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling to coordinate carrier operation, user data, or other signaling.

[0092] The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive" or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0093] The signal waveform transmitted via the carrier wave may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order of the modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0094] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0095] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems, a time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

[0096] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmit time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0097] Physical channels may be multiplexed according to various techniques for communicating using a carrier. Physical control channels and physical data channels may be multiplexed, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique for signaling via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115.

[0098] For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of the control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for the control information format with a given payload size. The search space set may include a common search space set configured for transmitting control information to multiple UEs 115, and a UE-specific search space set for transmitting control information to a specific UE 115.

[0099] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for respective coverage areas 110 using the same or different radio access technologies.

[0100] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0101] In some examples, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured by the network entity 105 (e.g., scheduled by the network entity). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0102] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)).

[0103] The control plane entities may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be passed through user plane entities, which may provide IP address allocation and other functions. The user plane entities may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0104] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0105] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0106] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0107] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0108] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports radio bearers of user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map transport channels to physical channels.

[0109] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), FEC, and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0110] According to the techniques described herein, a UE 115 may receive control information identifying criteria for determining a delivery status of an ADU (also referred to as a PDU set) including a plurality of PDUs. The ADU may be associated with an application layer of the UE 115. Thus, the UE 115 may receive at least a portion of the ADU from the network entity 105, and may determine a delivery status of the ADU based on the received portion of the ADU and the criteria identified by the control information. The delivery status of the ADU may refer to whether the ADU is successfully delivered to the UE 115. The delivery status of the ADU may be based on a number of bits or PDUs in the received portion of the ADU, a threshold number of bits or PDUs (defined by a standard), or a combination thereof.

[0111] Various aspects of the wireless communication system 100 may be implemented to achieve one or more of the following advantages. Figure 1 The described techniques may improve the flexibility and applicability of existing ADU delivery conditions. For example, the network entity 105 may dynamically configure or update the ADU delivery conditions based on the FEC scheme (none, static, or dynamic) of the UE 115. Additionally or alternatively, the network entity 105 may configure the ADU delivery conditions with respect to bits or PDUs, which may improve the flexibility of the ADU delivery conditions. The enhanced ACC framework described herein may be used for a wide range of ADU metadata configuration and deployment scenarios.

[0112] Figure 2 An example of an enhanced network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting application data unit metadata according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with the core network 130-a via a backhaul communication link 120-a, or indirectly communicate with the core network 130-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, a UE 115-b may be served by multiple RUs 170-a simultaneously.

[0113] Each network entity 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, the network entity 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0114] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0115] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0116] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0117] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0118] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0119] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0120] According to the techniques described herein, a UE 115-b may receive control information identifying criteria for determining a delivery status of an ADU (also referred to as a PDU set) comprising a plurality of PDUs. The ADU may be associated with an application layer of the UE 115-b. Thus, the UE 115-b may receive at least a portion of the ADU from a network entity (e.g., the O-eNB 210) and may determine the delivery status of the ADU based on the received portion of the ADU and the criteria identified by the control information. The delivery status of the ADU may refer to whether the ADU is successfully delivered to the UE 115-b. The delivery status of the ADU may be based on the number of bits or PDUs in the received portion of the ADU, a threshold number of bits or PDUs (defined by a standard), or a combination thereof.

[0121] Various aspects of the network architecture 200 can be implemented to achieve one or more of the following advantages. Figure 2 The described techniques may improve the flexibility and applicability of existing ADU delivery conditions. For example, a network entity (e.g., O-eNB 210) may dynamically configure or update ADU delivery conditions based on the FEC scheme (none, static, or dynamic) of UE 115-b. Additionally or alternatively, a network entity may configure ADU delivery conditions with respect to bits or PDUs, which may improve the flexibility of ADU delivery conditions. The enhanced ACC framework described herein may be used for a wide range of ADU metadata configuration and deployment scenarios.

[0122] Figure 3 An example of an enhanced wireless communication system 300 supporting ADU metadata according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may implement or be implemented by aspects of the wireless communication system 100 or the network architecture 200. For example, the wireless communication system 300 may include a UE 115-b and a network entity 105-a (also referred to as a gNB or base station), which may be a reference Figure 1 Examples of corresponding devices described. The network entity 105-a may include an ADU scheduling control unit 335 and a scheduler 340. In the wireless communication system 300, one or more ADUs may be sent from the application server 315 to the UE 115-b with the help of the UPF 325 and the network entity 105-a.

[0123] An application can process (consume) data in an ADU instead of an IP packet. An ADU is a collection of packets processed jointly by an application. A burst is a collection of ADUs generated by an application at approximately the same time. Figure 3 In the example of , burst 365-a may include ADU 310-a and ADU 310-b, burst 365-b may include ADU 310-c, ADU 310-d, and ADU 310-e, and burst 365-c may include ADU 310-f. As an example, there may be one video frame (or slice of a video frame) per burst. Various aspects of the present disclosure support ADU awareness at the network entity 105-a (gNB) and UE 115-b. The wireless communication system 300 illustrates an exemplary service flow for downlink ADU metadata. However, the ADU metadata principles described herein also apply to the uplink.

[0124] For each ADU 310 delivered by an application 320 on an application server 315, information related to the ADU 310 may be delivered to the RAN and UE 115-b. This information may be equivalently referred to herein as ADU metadata or control information. The service layer 330 of the UPF 325 may identify the ADU 310 and signal the ADU metadata to the RAN (network entity 105-a) using an associated IP packet 345. The ADU metadata may include Uu metadata 360, N3 metadata 355, and optional metadata 350. The ADU metadata may be explicitly provided by the application server 315 or implicitly determined (learned) by the service layer 330 of the UPF 325 (from the business). The service layer 330 may decouple the ADU signaling from the application server 315 to the UPF 325 and the ADU signaling within the 5G system (from the UPF 325 to the RAN). Some exemplary ADU metadata fields are listed in Table 1.

[0125] Table 1 ： ADU Metadata Elements

[0126]

[0127] However, in some cases, the ADU metadata elements shown in Table 1 may not support different ADU metadata configurations or prioritization of ADUs 310 within a data radio bearer (DRB). The enhanced ADU metadata structure described herein supports a large number of ADU deployment scenarios and ADU prioritization mechanisms. The elements of the enhanced ADU metadata framework are shown in Tables 2 and 3.

[0128] Table 2 : Enhanced ADU Metadata Framework

[0129]

[0130]

[0131] The parameter N2 listed in Table 2 may refer to the number of PDUs in the ADU 310, while the parameter N1 may refer to a fixed (constant) integer. The elements of the ACC-User Plane structure are listed in Table 3.

[0132] Table 3 ： ACC- User plane fields

[0133]

[0134] Various ADU deployment scenarios (and corresponding metadata requirements) are listed in Table 4. In some of the exemplary scenarios listed in Table 4, the size of the ADU 310 (the number of PDUs in the ADU 310) is known at the source (e.g., the device sending the ADU 310). In other scenarios, the ADU size is unknown at the source.

[0135] Table 4 ： ADU Deployment Scenario

[0136]

[0137]

[0138] For scenarios where static FEC is applied, ACC may be signaled by the control plane and may be applicable to all ADUs 310. For scenarios where dynamic FEC is applied, ACC may be signaled as part of the ADU metadata and may be applied to each ADU 310. For scenarios where ACC is applicable to PDUs, for consistency with the control plane, ACC may be equivalently referred to as an ADU content policy (listed in Table 1).

[0139] Figure 4An example of a network diagram 400 that supports enhancements to ADU metadata according to one or more aspects of the present disclosure is illustrated. The network diagram 400 may implement or be implemented by aspects of the wireless communication system 100 or the wireless communication system 300. For example, the network diagram 400 may include an application server 445, which may be a reference Figure 3 For example, the network diagram 400 may include a UPF 450, which may be a reference to an example application server 315. Figure 3 The network diagram 400 may also include a gNB-CU-UP 455 and a gNB-DU 460, which may be referenced Figure 1 and Figure 3 Examples of various aspects of the network entity 105 are described.

[0140] exist Figure 4 In the example of , the application server 445 may apply FEC and IP packetization to the IP packet 405. This may result in an ADU having an ADU size 410. The application server may append one or more IP, user datagram protocol (UDP), and real-time transport (RTP) headers 415 to the ADU. The UPF 450 may append or otherwise include ADU metadata 420 for the ADU. The gNB-CU-UP 455 may add the SDAP header 425 to the ADU before implementing robust header compression (RoHC), integrity protection, and encryption on the ADU by adding a compressed header 430 and MAC-I 435 to the ADU. Once encrypted, the gNB-CU-UP 455 may add the PDCP header and ADU metadata 440 to the ADU. Thus, the gNB-CU-UP 455 may send the ADU to the gNB-DU 460.

[0141] In some of the scenarios listed in Table 4, the user of the ACC may need to count the bits of the ADU within each PDU of the ADU to check whether the ACC is satisfied. For example, the ACC user may need to count bits when there is an N-to-1 mapping between PDCP PDUs, when FEC is implemented before IP packetization, or when there is an uneven IP packet size within one ADU. Figure 4 An example procedure for counting ADU bits is illustrated. For example, a user of the ACC (gNB-DU 460) may need to determine the number of bits within each RLC Service Data Unit (SDU). However, due to various IP, UDP, and RTP headers, RoHC, and encryption, the gNB-DU 460 may not be able to determine this number without additional information. Therefore, the ADU metadata may be enhanced to carry this information.

[0142] Although Figure 4The examples of apply to downlink ADU transmissions, but it should be understood that the techniques described herein are equally applicable to uplink ADU transmissions. According to aspects of the present disclosure, the existing ADU metadata framework may be enhanced to include the additional elements shown in Table 5.

[0143] Table 5 : Enhanced ADU Metadata structure

[0144]

[0145]

[0146] In order to enable the user of the ACC (gNB-DU 460) to count the ADU bits within the PDU of the ADU, a new element (Number of ADU bits in PDU) may be added to the ACC-User Plane field structure. In order to inform the user of the ACC whether to count the PDUs or bits of the ADU, a new element (ACC Application) may be added to the ACC-User Plane field structure. In order to make the presence of some elements conditional for target scenarios (and to reduce signaling overhead), multiple presence flags may be added to the ACC-User Plane field structure. These flags may include the ACCUPI field, the ASI field, and the FII field. Aspects related to these new ACC-User Plane fields are listed in Table 6.

[0147] Table 6 : Enhanced ACC- User plane field structure

[0148]

[0149]

[0150] Parameter N3 listed in Table 6 may refer to the total number of bits in an ADU, while parameter N4 may refer to the number of bits in a PDU of an ADU. In order to improve applications using dynamic FEC, a new element (FEC information) may be introduced to distinguish the conditions for successful ADU delivery. This element may indicate whether the delivery status of the ADU is based on the number of PDUs or bits before the first PDU or error bit or on the number of PDUs or bits to be delivered. Additional information related to these ADU metadata elements is listed in Table 6. For most FEC encoding schemes, the basic unit is a symbol. In order to reduce overhead, the units of these parameters may be changed from bits to symbols.

[0151] Table 7 : Deployment scenarios and ADU Metadata settings

[0152]

[0153] Table 7 illustrates various scenarios and the associated ADU metadata fields for each scenario. In scenario 1, FEC is not used and the ADU size element is not provided. In scenario 2, FEC is not used and the ADU size element is provided. In scenario 3, static FEC is used and ACC is defined relative to PDU (ACC applies = 0). In scenario 4, dynamic FEC is used and ACC is defined relative to PDU (ACC applies = 0). In scenario 5, static FEC is used and ACC is defined relative to bits (ACC applies = 0). In scenario 6, dynamic FEC is used and ACC is defined relative to bits (ACC applies = 0). In scenario 1, the number element of PDU may indicate a value of N2 for the last PDU and a value of 0 for all other PDUs. For scenarios 4 and 6, if the FEC information element has a value of 1, the number element of PDUs or bits to be delivered may be included, and if the FEC information element has a value of 0, the number element of PDUs or bits to be delivered may be excluded.

[0154] Figure 5 An example of a process flow 500 for supporting enhancements to ADU metadata in accordance with one or more aspects of the present disclosure is illustrated. The process flow 500 may implement or be implemented by aspects of the wireless communication system 100 or the wireless communication system 300. For example, the process flow 500 may include a UE 115-c and a network entity 105-b (which in some examples may be or may be referred to as an access network entity herein), which may be referenced Figure 1 and Figure 3 Examples of corresponding devices described. In the following description of process flow 500, operations between UE 115-c and network entity 105-b may be added, omitted, or performed in a different order (relative to the exemplary order shown).

[0155] At 505, the network entity 105-b may, with the assistance of the UPF (e.g., see Figure 3 UPF 325 described herein) or another core network entity from an application server (e.g., reference Figure 3 105 - c) obtains the ADU. The ADU may be associated with the application layer of the network entity 105 - b. The ADU may include data (IP packets) and control information (metadata). In some examples, the ADU (equivalently referred to as a PDU set) may be sent in a burst (at approximately the same time) with other ADUs. Although described in the context of downlink ADU transmission from the network entity 105 - b to the UE 115 - c, it should be understood that the techniques and operations described herein are equally applicable to uplink ADU transmission from the UE 115 - c to the network entity 105 - b.

[0156] At 510, the network entity 105-b may send control information to the UE 115-c. The network entity 105-b may include the control information in a PDCP header of the PDU in the ADU. The control information may include an AI field, an ADU sequence number, a PDU sequence number, an ADU size field, an ACCUPI field, one or more ACC user plane fields, or a combination thereof. The one or more ACC user plane fields may indicate criteria for determining the delivery status of the ADU. For example, the ACC user plane field may include an ACC application field, an ASI field, an ADU size field, a PDU size field, a FII field, a FEC information field, a delivery threshold field, or any combination thereof.

[0157] The AI ​​field may indicate whether the PDU belongs to an ADU service flow or a PDU service flow. If the PDU belongs to an ADU service flow, the ADU sequence number may identify which ADU includes the PDU, and the PDU sequence number may identify the corresponding position of the PDU within the ADU. The ADU size field may indicate the number of PDUs in the ADU. The UE 115-c may determine whether the control information includes the ACC user plane field based on the value of the ACCUPI field. If the ACC user plane field is excluded from the control information, the delivery status of the ADU may depend on whether the UE 115-c successfully receives all PDUs in the ADU.

[0158] The ACC application field may indicate whether the standard is defined with respect to bits or with respect to PDUs (packets). The ADU size field may indicate the number of bits in the ADU. The UE 115-c may determine whether the control information includes the ADU size field based on the value of the ASI field. The PDU size field may indicate the number of ADU bits in the PDU of the ADU (excluding all headers). The FEC information field may indicate the conditions for successful ADU delivery. The UE 115-c may determine whether the control information includes the FEC information field based on the value of the FII field. The delivery threshold field may indicate the threshold number of PDUs or bits for successful ADU delivery. The UE 115-c may determine whether the control information includes the delivery threshold field based on the value of the FEC information field.

[0159] At 515, the UE 115-c may determine a criterion based on the value of the ACC user plane field, if present. For example, if the ACC application field is set to a first value, the criterion may be defined relative to a bit. Otherwise, the criterion may be defined relative to a PDU. If the FEC information field is set to a first value, the delivery status of the ADU may depend on the number of successfully received bits or PDUs prior to the first unsuccessfully delivered bit or PDU in the ADU. Otherwise, the delivery status of the ADU may depend on a threshold number of bits or PDUs indicated by the delivery threshold field. In some examples, the criterion may correspond to the FEC scheme (none, static, or dynamic) of the UE 115-c.

[0160] At 520, the UE 115-c may receive at least a portion (one or PDU or bits) of the ADU from the network entity 105-b (e.g., with control information). At 525, the UE 115-c may determine a delivery status of the ADU based on the received portion of the ADU and the criteria indicated by the control information. For example, if the delivery status of the ADU depends on a threshold number of bits indicated by the delivery threshold field, the UE 115-c may determine that the ADU was successfully delivered if the number of bits in the received portion of the ADU exceeds the threshold number of bits. Figure 5 The described techniques and operations may support more flexible ADU delivery conditions, among other benefits.

[0161] Figure 6 A block diagram 600 of a device 605 supporting enhancements of ADU metadata according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0162] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to enhancements for ADU metadata). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or multiple antennas.

[0163] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information associated with various information channels (e.g., control channels related to enhancements for ADU metadata, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or multiple antennas.

[0164] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of enhancements for ADU metadata as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0165] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0166] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0167] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0168] According to the examples disclosed herein, the communication manager 620 can support wireless communication at the UE (device 505). For example, the communication manager 620 can be configured as or otherwise support a component for receiving control information from a core network entity (e.g., UPF) via an access network entity (e.g., a base station or DU), the control information identifying a standard for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The communication manager 620 can be configured as or otherwise support a component for receiving at least a portion of the PDU set with the control information. The communication manager 620 can be configured as or otherwise support a component for determining a delivery status of the PDU set based on a value associated with the received portion of the PDU set and a threshold indicated by the standard, the delivery status indicating whether the PDU set is successfully delivered to the UE.

[0169] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling or otherwise coupled to the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support a more flexible standard for determining the ADU delivery status. Using the enhanced ADU standard described herein can reduce the number of ADU retransmissions requested by the device 605, which can result in reduced power consumption at the device 605 and other benefits.

[0170] Figure 7 A block diagram 700 of a device 705 supporting enhancements of ADU metadata according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0171] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to enhancements for ADU metadata). The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or multiple antennas.

[0172] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information associated with various information channels (e.g., control channels related to enhancements for ADU metadata, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or multiple antennas.

[0173] The device 705 or its various components may be examples of components for performing various aspects of the enhancement of ADU metadata as described herein. For example, the communication manager 720 may include a control information receiving component 725, a PDU receiving component 730, a delivery status determination component 735, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0174] According to an example as disclosed herein, the communication manager 720 can support wireless communication at the UE (device 605). The control information receiving component 725 can be configured to or otherwise support a component for receiving control information from a core network entity (e.g., UPF) via an access network entity (e.g., a base station or DU), the control information identifying a standard for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The PDU receiving component 730 can be configured to or otherwise support a component for receiving at least a portion of the PDU set with control information. The delivery status determining component 735 can be configured to or otherwise support a component for determining a delivery status of the PDU set based on a value associated with the received portion of the PDU set and a threshold indicated by the standard, the delivery status indicating whether the PDU set is successfully delivered to the UE.

[0175] Figure 8 A block diagram 800 of an enhanced communication manager 820 supporting ADU metadata according to one or more aspects of the present disclosure is shown. The communication manager 820 may be as described in reference Figure 5 and Figure 6 The communication manager 820 or various components thereof may be examples of components for performing various aspects of the enhancement of ADU metadata as described herein. For example, the communication manager 820 may include a control information receiving component 825, a PDU receiving component 830, a delivery status determining component 835, a metadata determining component 840, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0176] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. The control information receiving component 825 may be configured to or otherwise support a component for receiving control information from a core network entity (e.g., UPF) via an access network entity (e.g., a base station or DU), the control information identifying a standard for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The PDU receiving component 830 may be configured to or otherwise support a component for receiving at least a portion of a PDU set with control information. The delivery status determining component 835 may be configured to or otherwise support a component for determining a delivery status of a PDU set based on a value associated with a received portion of the PDU set and a threshold indicated by the standard, the delivery status indicating whether the PDU set is successfully delivered to the UE.

[0177] In some examples, to support determining the delivery status of a PDU set, the delivery status determination component 835 may be configured as or otherwise support a component for determining whether the PDU set is successfully delivered to the UE based on a value of the number of PDUs preceding the first unsuccessfully delivered PDU included in the PDU set.

[0178] In some examples, to support determining the delivery status of a PDU set, the delivery status determination component 835 may be configured as or otherwise support a component for determining whether the PDU set is successfully delivered to the UE based on the value of the number of bits preceding the first unsuccessfully delivered bit included in the PDU set.

[0179] In some examples, to support determining the delivery status of a PDU set, the delivery status determination component 835 may be configured as or otherwise support a component for determining whether the PDU set is successfully delivered to the UE based on a threshold value including a threshold number of PDUs and a value including the number of PDUs in a received portion of the PDU set.

[0180] In some examples, to support determining the delivery status of a PDU set, the delivery status determination component 835 may be configured as or otherwise support components for determining whether the PDU set is successfully delivered to the UE based on a value including the number of bits in a received portion of the PDU set and a threshold including a threshold number of bits.

[0181] In some examples, to support receiving control information, the control information receiving component 825 may be configured as or otherwise support components for receiving an indication of a threshold including a threshold number of PDUs for determining a delivery status of a PDU set, wherein the threshold number of PDUs is less than or equal to a total number of PDUs in the PDU set.

[0182] In some examples, to support receiving control information, the control information receiving component 825 may be configured as or otherwise support components for receiving an indication of a threshold including a threshold number of bits for determining a delivery status of a PDU set, wherein the threshold number of bits is less than or equal to a total number of bits in the PDU set.

[0183] In some examples, to support receiving control information, the control information receiving component 825 may be configured to or otherwise support a component for receiving metadata indicating a stream type field associated with a PDU in a PDU set, a first sequence number associated with the PDU in the PDU set, a second sequence number associated with the PDU set, the number of PDUs in the PDU set, a content standard field associated with a delivery status of the PDU set, a user plane indicator field associated with the content standard field, or a combination thereof, wherein the delivery status of the PDU set depends on the metadata.

[0184] In some examples, metadata determination component 840 may be configured or otherwise support components for determining whether metadata includes a first sequence number, a second sequence number, a number of PDUs in a PDU set, and a user plane indicator field based on the value of the stream type field.

[0185] In some examples, metadata determining component 840 may be configured or otherwise support means for determining whether metadata includes a content criteria field based on a value of a user plane indicator field and a value of a stream type field.

[0186] In some examples, the first sequence number identifies a PDU set. In some examples, the second sequence number identifies a PDU within the PDU set. In some examples, the first value of the user plane indicator field indicates that the delivery status of the PDU set depends on whether all PDUs in the PDU set are successfully delivered.

[0187] In some examples, the second value of the user plane indicator field indicates that the delivery status of the PDU set depends on the content criteria field. In some examples, the content criteria field includes the FEC information field, the delivery threshold field, or both.

[0188] In some examples, to support receiving control information, the control information receiving component 825 may be configured to or otherwise support components for receiving metadata indicating an applicability field associated with a standard, a size indicator field, a number of PDUs in a PDU set, a number of bits in the PDUs of the PDU set, an FEC indicator field, an FEC information field associated with a delivery status of the PDU set, a delivery threshold field associated with the delivery status of the PDU set, or a combination thereof, wherein the delivery status of the PDU set depends on the metadata.

[0189] In some examples, metadata determination component 840 can be configured or otherwise support means for determining whether the standard is with respect to a PDU or with respect to a bit definition based on a value of an applicability field.

[0190] In some examples, metadata determining component 840 may be configured or otherwise support means for determining whether the metadata indicates a number of PDUs in a PDU set based on a value of a size indicator field.

[0191] In some examples, metadata determination component 840 may be configured or otherwise support components for determining whether metadata includes a FEC information field based on a value of the FEC indicator field.

[0192] In some examples, metadata determination component 840 may be configured or otherwise support components for determining criteria based on a value of a suitability field, a value of an FEC indicator field, a value of an FEC information field, a value of a delivery threshold field, or a combination thereof.

[0193] In some examples, metadata determination component 840 may be configured or otherwise support means for determining whether metadata includes a delivery threshold field based on a value of the FEC indicator field and a value of the FEC information field.

[0194] In some examples, if the applicability field is set to a first value, the delivery threshold field indicates a threshold number of PDUs. In some examples, if the applicability field is set to a second value, the delivery threshold field indicates a threshold number of bits.

[0195] In some examples, metadata determining component 840 may be configured or otherwise support means for determining whether metadata indicates a number of bits in a PDU of a PDU set based on a value of the applicability field.

[0196] In some examples, control information receiving component 825 can be configured or otherwise support means for receiving control information indicating whether the standard is associated with a dynamic FEC scheme or a static FEC scheme. In some examples, the control information is included in a PDCP header of a PDU in the PDU set.

[0197] Fig. 9 A diagram of a system 900 including an enhanced device 905 supporting ADU metadata according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein or include components thereof. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).

[0198] I / O controller 910 can manage input and output signals for device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor (such as processor 940). In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0199] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

[0200] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 930 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0201] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to enable the device 905 to perform various functions (e.g., enhanced functions or tasks that support ADU metadata). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0202] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured as or otherwise support a component for receiving control information from a core network entity (e.g., UPF) via an access network entity (e.g., a base station or DU), the control information identifying a standard for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The communication manager 920 may be configured as or otherwise support a component for receiving at least a portion of a PDU set with control information. The communication manager 920 may be configured as or otherwise support a component for determining a delivery status of a PDU set based on a value associated with a received portion of the PDU set and a threshold indicated by the standard, the delivery status indicating whether the PDU set is successfully delivered to the UE.

[0203] By including or configuring a communication manager 920 according to examples as described herein, the device 905 may support techniques for improving the flexibility and adaptability of ADU delivery criteria (parameters for determining whether an ADU is successfully delivered). For example, an ADU may be successfully delivered even if some PDUs or bits are not successfully received. In such examples, the device 905 may determine the delivery status of an ADU relative to a threshold number of PDUs or bits, the number of successfully delivered PDUs or bits, or some combination thereof.

[0204] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions executable by the processor 940 to cause the device 905 to perform various aspects of the enhancement for ADU metadata as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0205] Fig.10 A block diagram 1000 of a device 1005 supporting enhancements of ADU metadata according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0206] Receiver 1010 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, PDUs, service data units). The information may be communicated to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0207] The transmitter 1015 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, PDUs, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0208] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of enhancement for ADU metadata as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0209] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0210] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0211] In some examples, communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 can receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0212] According to examples disclosed herein, the communication manager 1020 may support wireless communications at an access network entity (device 905). For example, the communication manager 1020 may be configured to or otherwise support a component for outputting control information that identifies a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The communication manager 1020 may be configured to or otherwise support a component for outputting a plurality of PDUs in the PDU set with control information, wherein the delivery status of the PDU set is based on a threshold indicated by the criterion.

[0213] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) can support a more flexible standard for determining the ADU delivery status. Using the enhanced ADU standard described herein can reduce the number of ADU retransmissions performed by the device 1005, which can result in reduced power consumption at the device 1005 and other benefits.

[0214] Fig.11A block diagram 1100 of a device 1105 supporting enhancement of ADU metadata according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0215] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, PDUs, service data units). The information may be communicated to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0216] The transmitter 1115 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, PDUs, service data units). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0217] The device 1105 or its various components may be examples of components for performing various aspects of the enhancement of the ADU metadata as described herein. For example, the communication manager 1120 may include a control information output component 1125, a PDU output component 1130, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0218] According to examples disclosed herein, the communication manager 1120 may support wireless communications at an access network entity (device 1005). The control information output component 1125 may be configured to or otherwise support components for outputting control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The PDU output component 1130 may be configured to or otherwise support components for outputting a plurality of PDUs in the PDU set with control information, wherein the delivery status of the PDU set is based on a threshold indicated by the criterion.

[0219] Fig.12 A block diagram 1200 of an enhanced communication manager 1220 supporting ADU metadata according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be as described in reference Fig. 9 and Fig.10 The communication manager 1020 or the communication manager 1120 described herein are examples of various aspects of the communication manager 1020 or the communication manager 1120. The communication manager 1220 or its various components may be examples of components for performing various aspects of the enhancement of the ADU metadata as described herein. For example, the communication manager 1220 may include a control information output component 1225, a PDU output component 1230, a PDU acquisition component 1235, a PDU delivery status component 1240, a control information acquisition component 1245, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), and the communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0220] According to examples disclosed herein, the communication manager 1220 can support wireless communications at an access network entity. The control information output component 1225 can be configured to or otherwise support components for outputting control information that identifies a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The PDU output component 1230 can be configured to or otherwise support components for outputting a plurality of PDUs in the PDU set with control information, wherein the delivery status of the PDU set is based on a threshold indicated by the criterion.

[0221] In some examples, PDU obtaining component 1235 may be configured or otherwise support components for obtaining at least a portion of a set of PDUs from a core network entity. In some examples, PDU delivery status component 1240 may be configured or otherwise support components for determining a delivery status of a set of PDUs based on the obtained portion of the set of PDUs and criteria identified by the control information.

[0222] In some examples, to support determining the delivery status of a PDU set, the PDU delivery status component 1240 may be configured as or otherwise support components for determining whether the PDU set is successfully delivered to an access network entity based on the number of PDUs preceding the first unsuccessfully delivered PDU in the PDU set.

[0223] In some examples, to support determining the delivery status of a PDU set, the PDU delivery status component 1240 may be configured as or otherwise support components for determining whether the PDU set is successfully delivered to an access network entity based on the number of bits preceding the first unsuccessful delivery bit in the PDU set.

[0224] In some examples, to support determining the delivery status of a PDU set, the PDU delivery status component 1240 may be configured as or otherwise support components for determining whether the PDU set is successfully delivered to an access network entity based on a threshold including a threshold number of PDUs and a number of PDUs in an obtained portion of the PDU set.

[0225] In some examples, to support determining the delivery status of a PDU set, the PDU delivery status component 1240 may be configured as or otherwise support components for determining whether the PDU set is successfully delivered to an access network entity based on a threshold including a threshold number of bits and a number of bits in an obtained portion of the PDU set.

[0226] In some examples, the control information obtaining component 1245 may be configured as or otherwise support components for obtaining an indication of a threshold including a threshold number of PDUs for determining a delivery status of a PDU set, wherein the threshold number of PDUs is less than or equal to a total number of PDUs in the PDU set.

[0227] In some examples, control information obtaining component 1245 may be configured to or otherwise support components for obtaining an indication of a threshold including a threshold number of bits for determining a delivery status of a PDU set, where the threshold number of bits is less than or equal to a total number of bits in the PDU set.

[0228] In some examples, to support outputting control information, the control information output component 1225 may be configured as or otherwise support components for outputting an indication of a threshold value including a threshold number of PDUs for determining a delivery status of a PDU set, wherein the threshold number of PDUs is less than or equal to a total number of PDUs in the PDU set.

[0229] In some examples, to support outputting control information, control information output component 1225 may be configured as or otherwise support components for outputting an indication of a threshold including a threshold number of bits for determining a delivery status of a PDU set, where the threshold number of bits is less than or equal to a total number of bits in the PDU set.

[0230] In some examples, to support outputting control information, the control information output component 1225 may be configured as or otherwise support a component for outputting metadata indicating a stream type field associated with a PDU in a PDU set, a first sequence number associated with the PDU in the PDU set, a second sequence number associated with the PDU set, the number of PDUs in the PDU set, a content standard field associated with a delivery status of the PDU set, a user plane indicator field associated with the content standard field, or a combination thereof, wherein the delivery status of the PDU set is based on the metadata.

[0231] In some examples, to support outputting control information, the control information output component 1225 may be configured as or otherwise support components for outputting metadata indicating an applicability field associated with a standard, a size indicator field, the number of PDUs in a PDU set, the number of bits in the PDUs of the PDU set, an FEC indicator field, an FEC information field associated with a delivery status of the PDU set, a delivery threshold field associated with the delivery status of the PDU set, or a combination thereof, wherein the delivery status of the PDU set is based on the metadata.

[0232] Fig.13A diagram of a system 1300 including an enhanced device 1305 supporting ADU metadata according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0233] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and for demodulating a signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receiving or obtaining operations or one or more interfaces coupled to one or more antennas 1315 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components, which are operable to: perform or support operations based on received or obtained information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335, or memory 1325, or both) may be included in a chip or chip assembly installed in the device 1305. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0234] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0235] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) to enable the device 1305 to perform various functions (e.g., enhanced functions or tasks supporting ADU metadata). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform various functions described herein. The processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions for performing functions of the device 1305 (e.g., by executing code 1330). The processor 1335 can be any suitable processor or processors capable of executing scripts or instructions of one or more software programs stored in the device 1305, such as within the memory 1325. In some implementations, the processor 1335 can be a component of a processing system.

[0236] A processing system may generally refer to a system or series of machines or components that receive inputs and process those inputs to produce a set of outputs (which may be delivered to other systems or components of, for example, device 1305). For example, a processing system of device 1305 may refer to a system that includes various other components or subcomponents of device 1305, such as processor 1335, or transceiver 1310, or communication manager 1320, or other components or combinations of components of device 1305. A processing system of device 1305 may interface with other components of device 1305 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information or both.

[0237] One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1305 can send information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1305 can obtain information or signal input, and the information can be passed to the processing system. Those of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0238] In some examples, bus 1340 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305, or communications performed between different components of device 1305 that may be co-located or may be located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one component of different components or divided between different components).

[0239] In some examples, communication manager 1320 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1320 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other network entities 105. In some examples, communication manager 1320 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0240] According to examples disclosed herein, the communication manager 1320 may support wireless communications at an access network entity (device 1305). For example, the communication manager 1320 may be configured to or otherwise support a component for outputting control information that identifies a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The communication manager 1320 may be configured to or otherwise support a component for outputting a plurality of PDUs in the PDU set with control information, wherein the delivery status of the PDU set is based on a threshold indicated by the criterion.

[0241] By including or configuring a communication manager 1320 according to examples as described herein, the device 1305 may support techniques for improving the flexibility and adaptability of ADU delivery criteria (parameters for determining whether an ADU is successfully delivered). For example, an ADU may be successfully delivered even if some PDUs or bits are not successfully received. In such examples, the device 1305 may determine the delivery status of the ADU relative to a threshold number of PDUs or bits, the number of successfully delivered PDUs or bits, or some combination thereof.

[0242] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 may include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of the enhancement for ADU metadata as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0243] Fig.14 A flowchart illustrating a method 1400 for supporting enhancements of ADU metadata according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0244] At 1405, the UE may receive control information from a core network entity via an access network entity, the control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The operations of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The control information receiving component 825 described above is executed.

[0245] At 1410, the UE may receive at least a portion of a set of PDUs having control information. The operations of 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The described PDU receiving component 830 is executed.

[0246] At 1415, the UE may determine a delivery status of the PDU set based on a value associated with the received portion of the PDU set and a threshold indicated by the criterion, the delivery status indicating whether the PDU set is successfully delivered to the UE. The operations of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The described delivery status determination component 835 is performed.

[0247] Fig.15 A flowchart illustrating a method 1500 for supporting enhancements of ADU metadata according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof. For example, the operations of the method 1500 may be implemented by a UE or a component thereof. Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0248] At 1505, the UE may receive control information from a core network entity via an access network entity, the control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the UE. The operations of 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The control information receiving component 825 described above is executed.

[0249] At 1510, the UE may receive metadata indicating a flow type field associated with a PDU in a PDU set, a first sequence number associated with a PDU in a PDU set, a second sequence number associated with a PDU set, a number of PDUs in a PDU set, a content standard field associated with a delivery status of a PDU set, a user plane indicator field associated with a content standard field, or a combination thereof. The operations of 1510 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The control information receiving component 825 described above is executed.

[0250] At 1515, the UE may receive at least a portion of a set of PDUs having control information. The operations of 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The described PDU receiving component 830 is executed.

[0251] At 1520, the UE may determine a delivery status of the PDU set based on a value associated with the received portion of the PDU set and a threshold indicated by the criterion, the delivery status indicating whether the PDU set is successfully delivered to the UE. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 8 The described delivery status determination component 835 is performed.

[0252] Fig.16 A flowchart illustrating a method 1600 for supporting enhancements of ADU metadata according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by an access network entity or a component thereof. For example, the operations of the method 1600 may be implemented by a reference to Figures 1 to 5 as well as Figures 10 to 13 The access network entity 105 may be used to perform the described functions. In some examples, the access network entity may execute an instruction set to control the functional elements of the access network entity to perform the described functions. Additionally or alternatively, the access network entity may use dedicated hardware to perform various aspects of the described functions.

[0253] At 1605, the access network entity may output control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The operations of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.12 The control information output component 1225 executes.

[0254] At 1610, the access network entity may output a plurality of PDUs having a PDU set of control information, wherein a delivery status of the PDU set is based on a threshold indicated by a standard. The operations of 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.12 The PDU output component 1230 is used to execute.

[0255] Fig.17 1700 is a flowchart illustrating an enhanced method 1700 for supporting ADU metadata according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by an access network entity or a component thereof. For example, the operations of the method 1700 may be implemented by a reference to Figures 1 to 5 as well as Figures 10 to 13 In some examples, the access network entity may execute an instruction set to control the functional elements of the access network entity to perform the described functions. Additionally or alternatively, the access network entity may use dedicated hardware to perform various aspects of the described functions.

[0256] At 1705, the access network entity may output control information identifying a criterion for determining a delivery status of a PDU set including a plurality of PDUs, wherein the PDU set is associated with an application layer of the access network entity. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.12 The control information output component 1225 executes.

[0257] At 1710, the access network entity may output metadata indicating an applicability field associated with a standard, a size indicator field, a number of PDUs in a PDU set, a number of bits in a PDU of a PDU set, an FEC indicator field, an FEC information field associated with a delivery status of a PDU set, a delivery threshold field associated with a delivery status of a PDU set, or a combination thereof. The operations of 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.12 The control information output component 1225 executes.

[0258] At 1715, the access network entity may output a plurality of PDUs in a PDU set with control information, wherein a delivery status of the PDU set is based on a threshold indicated by a standard. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.12 The PDU output component 1230 is used to execute.

[0259] The following provides an overview of various aspects of the disclosure:

[0260] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving control information from a core network entity via an access network entity, the control information identifying a criterion for determining a delivery status of a set of protocol data units comprising a plurality of protocol data units, wherein the set of protocol data units is associated with an application layer of the UE; receiving at least a portion of the set of protocol data units having the control information; and determining the delivery status of the set of protocol data units based at least in part on a value associated with the received portion of the set of protocol data units and a threshold indicated by the criterion, the delivery status indicating whether the set of protocol data units is successfully delivered to the UE.

[0261] Aspect 2: A method according to Aspect 1, wherein determining the delivery status of the protocol data unit set includes: determining whether the protocol data unit set is successfully delivered to the UE based at least in part on the value of the number of protocol data units preceding the first unsuccessfully delivered protocol data unit included in the protocol data unit set.

[0262] Aspect 3: A method according to Aspect 1, wherein determining the delivery status of the set of protocol data units includes: determining whether the set of protocol data units is successfully delivered to the UE based at least in part on the value of the number of bits preceding the first unsuccessfully delivered bit included in the set of protocol data units.

[0263] Aspect 4: A method according to Aspect 1, wherein determining the delivery status of the set of protocol data units includes: determining whether the set of protocol data units is successfully delivered to the UE based at least in part on the threshold value including a threshold number of protocol data units and the value including the number of protocol data units in the received part of the set of protocol data units.

[0264] Aspect 5: A method according to Aspect 1, wherein determining the delivery status of the set of protocol data units includes: determining whether the set of protocol data units is successfully delivered to the UE based at least in part on the value of the number of bits in the received part of the set of protocol data units and the threshold of the threshold number of bits.

[0265] Aspect 6: A method according to Aspect 1, wherein receiving the control information includes: receiving an indication of the threshold value including a threshold number of protocol data units for determining the delivery status of the protocol data unit set, wherein the threshold number of protocol data units is less than or equal to the total number of protocol data units in the protocol data unit set.

[0266] Aspect 7: A method according to Aspect 1, wherein receiving the control information includes: receiving an indication of the threshold including a threshold number of bits for determining the delivery status of the set of protocol data units, wherein the threshold number of bits is less than or equal to the total number of bits in the set of protocol data units.

[0267] Aspect 8: A method according to any one of Aspects 1 to 7, wherein receiving the control information includes: receiving metadata, the metadata indicating a stream type field associated with a protocol data unit in the protocol data unit set, a first sequence number associated with the protocol data unit in the protocol data unit set, a second sequence number associated with the protocol data unit set, the number of protocol data units in the protocol data unit set, a content standard field associated with the delivery status of the protocol data unit set, a user plane indicator field associated with the content standard field, or a combination thereof.

[0268] Aspect 9: According to the method described in Aspect 8, the method also includes: determining whether the metadata includes the first sequence number, the second sequence number, the number of protocol data units in the protocol data unit set and the user plane indicator field at least in part based on the value of the stream type field.

[0269] Aspect 10: The method according to any one of aspects 8 to 9, further comprising: determining whether the metadata includes the content criteria field based at least in part on the value of the user plane indicator field and the value of the stream type field.

[0270] Aspect 11: The method according to any one of aspects 8 to 10, wherein the first sequence number identifies the set of protocol data units; and the second sequence number identifies a protocol data unit within the set of protocol data units.

[0271] Aspect 12: A method according to any one of Aspects 8 to 11, wherein the first value of the user plane indicator field indicates that the delivery status of the protocol data unit set depends on whether all protocol data units in the protocol data unit set are successfully delivered; and the second value of the user plane indicator field indicates that the delivery status of the protocol data unit set depends on the content standard field.

[0272] Aspect 13: The method according to any one of aspects 8 to 12, wherein the content criteria field comprises a forward error correction information field, a delivery threshold field, or both.

[0273] Aspect 14: A method according to any one of Aspects 1 to 13, wherein receiving the control information includes: receiving metadata, the metadata indicating an applicability field associated with the standard, a size indicator field, the number of protocol data units in the protocol data unit set, the number of bits in the protocol data units of the protocol data unit set, a forward error correction indicator field, a forward error correction information field associated with the delivery status of the protocol data unit set, a delivery threshold field associated with the delivery status of the protocol data unit set, or a combination thereof.

[0274] Aspect 15: The method according to aspect 14, the method further comprising: determining whether the standard is defined with respect to a protocol data unit or with respect to a bit based at least in part on the value of the applicability field.

[0275] Aspect 16: According to the method of any one of Aspects 14 to 15, the method also includes: determining whether the metadata indicates the number of protocol data units in the set of protocol data units based at least in part on the value of the size indicator field.

[0276] Aspect 17: The method according to any one of Aspects 14 to 16, further comprising: determining whether the metadata includes the forward error correction information field based at least in part on the value of the forward error correction indicator field.

[0277] Aspect 18: According to the method described in any one of Aspects 14 to 17, the method also includes: determining the criterion at least in part based on the value of the applicability field, the value of the forward error correction indicator field, the value of the forward error correction information field, the value of the delivery threshold field, or a combination thereof.

[0278] Aspect 19: According to the method described in any one of Aspects 14 to 18, the method further includes: determining whether the metadata includes the delivery threshold field based at least in part on the value of the forward error correction indicator field and the value of the forward error correction information field.

[0279] Aspect 20: A method according to any one of Aspects 14 to 19, wherein if the applicability field is set to a first value, the delivery threshold field indicates a threshold number of protocol data units; and if the applicability field is set to a second value, the delivery threshold field indicates a threshold number of bits.

[0280] Aspect 21: According to any one of Aspects 14 to 20, the method also includes: determining whether the metadata indicates the number of bits in the protocol data unit of the protocol data unit set based at least in part on the value of the applicability field.

[0281] Aspect 22: The method according to any one of aspects 1 to 21, the method further comprising: receiving control information indicating whether the standard is associated with a dynamic forward error correction scheme or a static forward error correction scheme.

[0282] Aspect 23: The method according to any one of aspects 1 to 22, wherein the control information is included in a packet data convergence protocol header of a protocol data unit in the set of protocol data units.

[0283] Aspect 24: A method for performing wireless communications at an access network entity, the method comprising: outputting control information, the control information identifying a criterion for determining a delivery status of a protocol data unit set comprising a plurality of protocol data units, wherein the protocol data unit set is associated with an application layer of the access network entity; and outputting the plurality of protocol data units in the protocol data unit set with the control information, wherein the delivery status of the protocol data unit set is based at least in part on a threshold indicated by the criterion.

[0284] Aspect 25: According to the method described in Aspect 24, the method also includes: obtaining at least a portion of the protocol data unit set from a core network entity; and determining the delivery status of the protocol data unit set based at least in part on the obtained portion of the protocol data unit set and the standard identified by the control information.

[0285] Aspect 26: A method according to Aspect 25, wherein determining the delivery status of the protocol data unit set includes: determining whether the protocol data unit set is successfully delivered to the access network entity based at least in part on the number of protocol data units preceding the first unsuccessfully delivered protocol data unit in the protocol data unit set.

[0286] Aspect 27: A method according to Aspect 25, wherein determining the delivery status of the set of protocol data units includes: determining whether the set of protocol data units is successfully delivered to the network entity based at least in part on the number of bits preceding the first unsuccessful delivery bit in the set of protocol data units.

[0287] Aspect 28: A method according to Aspect 25, wherein determining the delivery status of the set of protocol data units includes: determining whether the set of protocol data units is successfully delivered to the network entity based at least in part on a threshold number of protocol data units and a number of protocol data units in the obtained part of the set of protocol data units.

[0288] Aspect 29: A method according to Aspect 25, wherein determining the delivery status of the set of protocol data units includes: determining whether the set of protocol data units is successfully delivered to the network entity based at least in part on a threshold number of bits and a number of bits in the obtained portion of the set of protocol data units.

[0289] Aspect 30: According to the method according to Aspect 24, the method also includes: obtaining an indication of a threshold number of protocol data units used to determine the delivery status of the protocol data unit set, wherein the threshold number of protocol data units is less than or equal to the total number of protocol data units in the protocol data unit set.

[0290] Aspect 31: According to the method according to Aspect 24, the method also includes: obtaining an indication of a threshold number of bits used to determine the delivery status of the set of protocol data units, wherein the threshold number of bits is less than or equal to the total number of bits in the set of protocol data units.

[0291] Aspect 32: A method according to Aspect 24, wherein outputting the control information includes: outputting an indication of a threshold number of protocol data units used to determine the delivery status of the protocol data unit set, wherein the threshold number of protocol data units is less than or equal to the total number of protocol data units in the protocol data unit set.

[0292] Aspect 33: A method according to Aspect 24, wherein outputting the control information includes: outputting an indication of a threshold number of bits used to determine the delivery status of the set of protocol data units, wherein the threshold number of bits is less than or equal to the total number of bits in the set of protocol data units.

[0293] Aspect 34: A method according to any one of Aspects 24 to 33, wherein outputting the control information includes: outputting metadata, the metadata indicating a stream type field associated with a protocol data unit in the protocol data unit set, a first sequence number associated with the protocol data unit in the protocol data unit set, a second sequence number associated with the protocol data unit set, the number of protocol data units in the protocol data unit set, a content standard field associated with the delivery status of the protocol data unit set, a user plane indicator field associated with the content standard field, or a combination thereof.

[0294] Aspect 35: A method according to any one of Aspects 24 to 34, wherein outputting the control information includes: outputting metadata, the metadata indicating an applicability field associated with the standard, a size indicator field, the number of protocol data units in the protocol data unit set, the number of bits in the protocol data units of the protocol data unit set, a forward error correction indicator field, a forward error correction information field associated with the delivery status of the protocol data unit set, a delivery threshold field associated with the delivery status of the protocol data unit set, or a combination thereof.

[0295] Aspect 36: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 23.

[0296] Aspect 37: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 1 to 23.

[0297] Aspect 38: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 23.

[0298] Aspect 39: A device for performing wireless communications at an access network entity, the device comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to cause the device to perform a method according to any one of Aspects 24 to 35.

[0299] Aspect 40: An apparatus for wireless communication at an access network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 24 to 35.

[0300] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication at an access network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 24 to 35.

[0301] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined in a method.

[0302] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0303] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0304] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0305] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0306] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes computer program to transfer from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0307] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Moreover, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0308] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Also, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0309] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0310] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0311] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to: receiving, via an access network entity from a core network entity, control information identifying criteria for determining a delivery status of a set of protocol data units comprising a plurality of protocol data units, wherein the set of protocol data units is associated with an application layer of the UE; receiving at least a portion of said set of protocol data units having said control information; as well as The delivery status of the set of protocol data units is determined based at least in part on a value associated with the received portion of the set of protocol data units and a threshold indicated by the criterion, the delivery status indicating whether the set of protocol data units was successfully delivered to the UE.

2. The apparatus of claim 1 , wherein the instructions for determining the delivery status of the set of protocol data units are executable by the processor to cause the apparatus to: Whether the set of protocol data units is successfully delivered to the UE is determined based at least in part on the value of the number of protocol data units preceding a first unsuccessfully delivered protocol data unit included in the set of protocol data units.

3. The apparatus of claim 1 , wherein the instructions for determining the delivery status of the set of protocol data units are executable by the processor to cause the apparatus to: Whether the set of protocol data units is successfully delivered to the UE is determined based at least in part on the value of the number of bits preceding a first unsuccessfully delivered bit included in the set of protocol data units.

4. The apparatus of claim 1 , wherein the instructions for determining the delivery status of the set of protocol data units are executable by the processor to cause the apparatus to: Whether the set of protocol data units is successfully delivered to the UE is determined based at least in part on the threshold comprising a threshold number of protocol data units and the value comprising a number of protocol data units in the received portion of the set of protocol data units.

5. The apparatus of claim 1 , wherein the instructions for determining the delivery status of the set of protocol data units are executable by the processor to cause the apparatus to: Whether the set of protocol data units was successfully delivered to the UE is determined based at least in part on the value comprising a number of bits in the received portion of the set of protocol data units and the threshold comprising a threshold number of bits.

6. The apparatus of claim 1, wherein the instructions for receiving the control information are executable by the processor to cause the apparatus to: An indication of the threshold comprising a threshold number of protocol data units for determining the delivery status of the set of protocol data units is received, wherein the threshold number of protocol data units is less than or equal to a total number of protocol data units in the set of protocol data units.

7. The apparatus of claim 1, wherein the instructions for receiving the control information are executable by the processor to cause the apparatus to: An indication of the threshold is received including a threshold number of bits for determining the delivery status of the set of protocol data units, wherein the threshold number of bits is less than or equal to a total number of bits in the set of protocol data units.

8. The apparatus of claim 1, wherein the instructions for receiving the control information are executable by the processor to cause the apparatus to: receiving metadata indicating a stream type field associated with a protocol data unit in the set of protocol data units, a first sequence number associated with the protocol data unit in the set of protocol data units, a second sequence number associated with the set of protocol data units, a number of protocol data units in the set of protocol data units, a content standard field associated with the delivery status of the set of protocol data units, a user plane indicator field associated with the content standard field, or a combination thereof.

9. The apparatus of claim 8, wherein the instructions are further executable by the processor to cause the apparatus to: A determination is made based at least in part on a value of the flow type field whether the metadata includes the first sequence number, the second sequence number, the number of protocol data units in the set of protocol data units, and the user plane indicator field.

10. The apparatus of claim 8, wherein the instructions are further executable by the processor to cause the apparatus to: A determination is made whether the metadata includes the content criteria field based at least in part on a value of the user plane indicator field and a value of the stream type field.

11. The device according to claim 8, wherein: The first sequence number identifies the set of protocol data units; and The second sequence number identifies a protocol data unit within the set of protocol data units.

12. The device according to claim 8, wherein: The first value of the user plane indicator field indicates that the delivery status of the set of protocol data units depends on whether all protocol data units in the set of protocol data units are successfully delivered; and A second value of the user plane indicator field indicates that the delivery status of the set of protocol data units depends on the content criteria field.

13. The apparatus of claim 8, wherein the content criteria field comprises a forward error correction information field, a delivery threshold field, or both.

14. The apparatus of claim 1, wherein the instructions for receiving the control information are executable by the processor to cause the apparatus to: receiving metadata indicating an applicability field associated with the standard, a size indicator field, a number of protocol data units in the set of protocol data units, a number of bits in a protocol data unit of the set of protocol data units, a forward error correction indicator field, a forward error correction information field associated with the delivery status of the set of protocol data units, a delivery threshold field associated with the delivery status of the set of protocol data units, or a combination thereof.

15. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Whether the criterion is defined with respect to protocol data units or with respect to bits is determined based at least in part on a value of the applicability field.

16. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Whether the metadata indicates the number of protocol data units in the set of protocol data units is determined based at least in part on a value of the size indicator field.

17. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: A determination is made whether the metadata includes the forward error correction information field based at least in part on a value of the forward error correction indicator field.

18. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: The criterion is determined based at least in part on a value of the applicability field, a value of the forward error correction indicator field, a value of the forward error correction information field, a value of the delivery threshold field, or a combination thereof.

19. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Whether the metadata includes the delivery threshold field is determined based at least in part on a value of the forward error correction indicator field and a value of the forward error correction information field.

20. The apparatus of claim 14, wherein: If the applicability field is set to a first value, the delivery threshold field indicates a threshold number of protocol data units; and If the applicability field is set to a second value, the delivery threshold field indicates a threshold number of bits.

21. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Whether the metadata indicates the number of bits in the protocol data unit of the set of protocol data units is determined based at least in part on a value of the applicability field.

22. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Control information is received indicating whether the standard is associated with a dynamic forward error correction scheme or a static forward error correction scheme.

23. The apparatus of claim 1, wherein the control information is included in a packet data convergence protocol header of a protocol data unit in the set of protocol data units.

24. An apparatus for wireless communication at an access network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to: outputting control information identifying criteria for determining a delivery status of a set of protocol data units comprising a plurality of protocol data units, wherein the set of protocol data units is associated with an application layer of the access network entity; as well as The plurality of protocol data units in the set of protocol data units with the control information are outputted, wherein the delivery status of the set of protocol data units is based at least in part on a threshold indicated by the criterion.

25. The apparatus of claim 24, wherein the instructions are further executable by the processor to cause the apparatus to: obtaining at least a portion of the set of protocol data units from a core network entity; and The delivery status of the set of protocol data units is determined based at least in part on the obtained portion of the set of protocol data units and the criterion identified by the control information.

26. The apparatus of claim 25, wherein the instructions for determining the delivery status of the set of protocol data units are executable by the processor to cause the apparatus to: Whether the set of protocol data units was successfully delivered to the access network entity is determined based at least in part on a number of protocol data units preceding a first unsuccessfully delivered protocol data unit in the set of protocol data units.

27. The apparatus of claim 24, wherein the instructions for outputting the control information are executable by the processor to cause the apparatus to: outputting metadata indicating a stream type field associated with a protocol data unit in the set of protocol data units, a first sequence number associated with the protocol data unit in the set of protocol data units, a second sequence number associated with the set of protocol data units, a number of protocol data units in the set of protocol data units, a content standard field associated with the delivery status of the set of protocol data units, a user plane indicator field associated with the content standard field, or a combination thereof.

28. The apparatus of claim 24, wherein the instructions for outputting the control information are executable by the processor to cause the apparatus to: Outputting metadata indicating an applicability field associated with the standard, a size indicator field, a number of protocol data units in the set of protocol data units, a number of bits in a protocol data unit of the set of protocol data units, a forward error correction indicator field, a forward error correction information field associated with the delivery status of the set of protocol data units, a delivery threshold field associated with the delivery status of the set of protocol data units, or a combination thereof.

29. A method for wireless communication at a user equipment (UE), the method comprising: receiving, via an access network entity from a core network entity, control information identifying criteria for determining a delivery status of a set of protocol data units comprising a plurality of protocol data units, wherein the set of protocol data units is associated with an application layer of the UE; receiving at least a portion of said set of protocol data units having said control information; as well as The delivery status of the set of protocol data units is determined based at least in part on a value associated with the received portion of the set of protocol data units and a threshold indicated by the criterion, the delivery status indicating whether the set of protocol data units was successfully delivered to the UE.

30. A method for wireless communication at an access network entity, the method comprising: outputting control information identifying criteria for determining a delivery status of a set of protocol data units comprising a plurality of protocol data units, wherein the set of protocol data units is associated with an application layer of the access network entity; as well as The plurality of protocol data units in the set of protocol data units with the control information are outputted, wherein the delivery status of the set of protocol data units is based at least in part on a threshold indicated by the criterion.

Images