Protocol data unit set-based discard or handling

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a transmitter may receive a configuration of one or more packet data convergence protocol (PDCP) drop timers for a protocol data unit (PDU) set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP drop timers. The transmitter may communicate according to the configuration. Numerous other aspects are described.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to non-provisional patent application No. 18 / 169,004, filed on February 14, 2023, entitled “PROTOCOL-DATA-UNIT-SET-BASEDDISCARDING OR PROCESSING,” and Taiwan non-provisional patent application No. 113100800, filed on January 8, 2024, entitled “PROTOCOL-DATA-UNIT-SET BASEDDISCARDING OR PROCESSING,” which are expressly incorporated herein by reference. Technical Field

[0002] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for discarding or processing based on sets of protocol data units (PDUs). Background Art

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

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

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR) (which may also be referred to as 5G) is a set of enhancements to the LTE mobile standard released by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, and using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation, thereby better supporting mobile broadband Internet access. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0006] Some aspects described herein relate to a method of wireless communication performed by a transmitter. The method may include receiving a configuration of one or more Packet Data Convergence Protocol (PDCP) discard timers for a protocol data unit (PDU) set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers. The method may include communicating according to the configuration.

[0007] Some aspects described herein relate to a method of wireless communication performed by a receiver. The method may include receiving a configuration indicating one or more PDU set parameters, the configuration indicating a radio link control (RLC) entity corresponding to a PDU set importance parameter in the one or more PDU set parameters. The method may include receiving one or more PDUs in a PDU set, the PDU set being associated with the PDU set importance parameter. The method may include processing the one or more PDUs according to the RLC entity.

[0008] Some aspects described herein relate to a transmitter for wireless communication. The transmitter may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a configuration of one or more PDCP discard timers for a PDU set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers. The one or more processors may be configured to communicate based on the configuration.

[0009] Some aspects described herein relate to a receiver for wireless communication. The receiver may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a configuration indicating one or more PDU set parameters, the configuration indicating an RLC entity corresponding to a PDU set importance parameter in the one or more PDU set parameters. The one or more processors may be configured to receive one or more PDUs in a PDU set, the PDU set being associated with the PDU set importance parameter. The one or more processors may be configured to process the one or more PDUs according to the RLC entity.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a transmitter. The instruction set, when executed by one or more processors of the transmitter, may cause the transmitter to receive a configuration of one or more PDCP discard timers for a PDU set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers. The instruction set, when executed by the one or more processors of the transmitter, may cause the transmitter to communicate according to the configuration.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a receiver. The instruction set, when executed by one or more processors of the receiver, may cause the receiver to receive a configuration indicating one or more PDU set parameters, the configuration indicating an RLC entity corresponding to a PDU set importance parameter in the one or more PDU set parameters. The instruction set, when executed by the one or more processors of the receiver, may cause the receiver to receive one or more PDUs in a PDU set, the PDU set being associated with the PDU set importance parameter. The instruction set, when executed by the one or more processors of the receiver, may cause the receiver to process the one or more PDUs according to the RLC entity.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a configuration of one or more PDCP discard timers for a PDU set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers. The apparatus may also include means for communicating in accordance with the configuration.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a configuration indicating one or more PDU set parameters, the configuration indicating an RLC entity corresponding to a PDU set importance parameter in the one or more PDU set parameters. The apparatus may include means for receiving one or more PDUs in a PDU set, the PDU set associated with the PDU set importance parameter. The apparatus may include means for processing the one or more PDUs according to the RLC entity.

[0014] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings.

[0015] The foregoing has outlined quite broadly the features and technical advantages of the examples according to the present disclosure so that the detailed description below may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood based on the description below. Each figure is provided for the purpose of illustration and description and not as a definition of a limitation of the claims.

[0016] Although various aspects are described in this disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip embodiments or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The device incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). It is intended that the aspects described herein can be practiced in a variety of devices, components, systems, distributed arrangements, and / or end-user devices of different sizes, shapes, and structures. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to understand the above-mentioned features of the present disclosure in detail, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are shown in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope of the present disclosure, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

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

[0020] Figure 3 is a schematic diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0021] Figure 4 is a diagram illustrating an example 400 of a user plane protocol stack and a control plane protocol stack of a network node and a core network for communicating with a UE according to the present disclosure.

[0022] Figure 5is a schematic diagram illustrating an example of a system including a UE, an extended reality (XR) device, and a network node according to the present disclosure.

[0023] Figure 6 is a diagram illustrating an example of signaling associated with a Packet Data Convergence Protocol (PDCP) discard time for a set of Protocol Data Units (PDUs) according to the present disclosure.

[0024] Figure 7 is a diagram illustrating an example of signaling associated with a retransmission timer of a PDU set according to the present disclosure.

[0025] Figure 8 is a diagram illustrating an example process performed, for example, by a transmitter, according to the present disclosure.

[0026] Figure 9 is a diagram illustrating an example process, such as performed by a receiver, according to the present disclosure.

[0027] Figure 10 is a schematic diagram illustrating an example apparatus for wireless communication according to the present disclosure. DETAILED DESCRIPTION

[0028] An application at a transmitter may generate information for consumption by an application at a receiver. For example, the information may include information units that would benefit from being delivered to the receiver as an integrated unit after migration through the network layers and radio access network (RAN) layers of the transmitter and receiver. To facilitate the delivery of information units as integrated units (e.g., as opposed to processing different parts of the information independently without considering the information unit as a whole), wireless communication technologies (e.g., 5G / NR) may provide protocol data units (PDUs) carrying information units for delivery as PDU sets. PDU sets may have common quality of service (QoS) attributes, such as a PDU set delay budget and a PDU set error rate. PDU sets may also be associated with various PDU set parameters, such as a PDU set importance parameter (indicating the importance level of the PDU set) or a PDU set integrated processing indication (PSIHI) (indicating whether the PDU set is an all-or-nothing PDU set or a non-all-or-nothing PDU set).

[0029] Various functions of the RAN protocol stack, such as the Packet Data Convergence Protocol (PDCP) function (e.g., buffered packet discard at a transmitter) and the Radio Link Control (RLC) function (e.g., reassembly at a receiver), may be configured per protocol entity (e.g., per PDCP entity or per RLC entity). For example, a transmitter may perform a PDCP discard operation on a single PDU based on a PDCP discard timer of the transmitter's PDCP entity. As another example, a receiver may perform an RLC reassembly operation on a single PDU based on a reassembly timer of the receiver's RLC entity. However, processing such operations on a per-entity basis (e.g., for individual PDUs) may not ensure proper processing of a PDU set such that the information units carried by the PDU set are successfully transmitted or received. For example, applying a PDCP discard timer at a per-entity granularity for individual PDUs may result in a difference between the length of the PDCP discard timer for a given PDU and the PDU set delay budget for the PDU set, thereby resulting in discarded PDUs in jitter scenarios. As another example, applying a reassembly timer at a per-entity granularity for individual PDUs may cause PDUs with a high importance level (as indicated by the PDU set importance parameter) to be discarded equally quickly as PDUs with a low importance level, which may result in failure to receive a PDU set.

[0030] Some techniques described herein provide for configuration and / or execution of protocol functions (such as PDCP discard or RLC reassembly) at the granularity of a PDU set rather than a single PDU. For example, the configuration of a PDCP discard timer at a transmitter may correspond to a specific PDU set parameter (e.g., a specific PSIHI or a specific PDU set importance parameter). As another example, the configuration of an RLC entity at a receiver may correspond to a PDU set parameter (e.g., a PDU set importance parameter). The transmitter may perform a PDCP discard operation on the PDUs belonging to the PDU set based on the PDCP discard timer corresponding to the PDU set. Thus, the occurrence of discarded PDUs is reduced. The receiver may perform an RLC operation (e.g., reassembly) on the PDUs belonging to the PDU set based on the RLC entity corresponding to the PDU set parameter of the PDU set. Thus, the possibility of failing to receive the PDU set is reduced.

[0031] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether the aspect is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect. For example, a device can be implemented or a method can be practiced using any number of aspects set forth herein. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0032] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the detailed description below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] Although aspects may be described using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0034] Figure 11 is a schematic diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, among others. The wireless network 100 may include one or more network nodes 110 (illustrated as BS 110a, BS 110b, BS 110c, and BS 110d), a user equipment (UE) 120 or multiple UEs 120 (illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0035] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link (such as a RU). In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or via a midhaul link, such as a DU. In some examples, the network node 110 can be or include a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregation network node 110 or a decomposition network node 110) can include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 can include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobile element of a network, a core network node, a network element, a network device, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network over various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0036] In some examples, network node 110 can provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​network node 110 and / or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 can provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs 120 with service subscriptions. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UEs 120 with service subscriptions. A femto cell can cover a relatively small geographic area (e.g., a residence) and can allow restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell can be referred to as a macro network node. A network node 110 for a pico cell can be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

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

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

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

[0040] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a mid-range communication link. The network nodes 110 may communicate with each other directly or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0041] UE 120 can be dispersed throughout wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric authentication device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio device), an in-vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE functional unit of a network node, and / or any other suitable device configured to communicate via a wireless medium or a wired medium.

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

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

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

[0045] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. by frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified with the frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "Sub-6 GHz" band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to above 52.6GHz. For example, three higher operating bands have been identified as the frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0047] With the foregoing in mind, unless otherwise specifically stated, it will be understood that the terms "sub-6 GHz," etc., if used herein, may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specifically stated, it will be understood that the terms "millimeter wave," etc., if used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0048] In some aspects, the transmitter may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may receive a configuration of one or more PDCP discard timers for a PDU set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers; and communicate in accordance with the configuration. In some aspects, the communications manager 140 may perform the following operations: receive a configuration indicating one or more PDU set parameters, the configuration indicating an RLC entity corresponding to a PDU set importance parameter in the one or more PDU set parameters; receive one or more PDUs in a PDU set, the PDU set associated with the PDU set importance parameter; and process the one or more PDUs in accordance with the RLC entity. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0049] As indicated above, Figure 1 is provided as an example. Other examples may differ from those described in relation to Figure 1 Examples described.

[0050] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0051] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. Modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0052] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols (if applicable), and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other parameters. In some examples, one or more components of the UE 120 may be included in a housing 284.

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

[0054] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. The antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as antennas). Figure 2 One or more antenna elements of one or more components in.

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

[0056] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 may include a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., with reference to FIG. Figure 4-10 ).

[0057] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the UE 120 may perform one or more techniques associated with PDCP or RLC processing, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in may perform or direct e.g. Figure 8 The process of 800 Figure 9 900, and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or instruct, for example, Figure 8 The process of 800 Figure 9 The process 900 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0058] In some aspects, the UE 120 includes: means for receiving a configuration of one or more PDCP discard timers for a PDU set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers; and / or means for communicating in accordance with the configuration. Means for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0059] In some aspects, the UE 120 includes: means for receiving a configuration indicating one or more PDU set parameters, the configuration indicating an RLC entity corresponding to a PDU set importance parameter in the one or more PDU set parameters; means for receiving one or more PDUs in a PDU set, the PDU set associated with the PDU set importance parameter; and / or means for processing the one or more PDUs in accordance with the RLC entity. Means for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0060] Although Figure 2 The blocks in FIG. 2 are shown as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0061] As indicated above, Figure 2 is provided as an example. Other examples may differ from those described in relation to Figure 2 Examples described.

[0062] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways and have various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or a network device can be implemented in an aggregated or decomposed architecture. For example, a base station (e.g., a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.), or one or more units (or one or more components) that perform base station functions can be implemented as an aggregated base station (also known as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station, or to one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0063] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit (such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples).

[0064] Base station type operation or network design can take into account the aggregated nature of base station functionality. For example, a decomposed base station can be used in an IAB network, an open radio access network (O-RAN (such as a network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. The decomposed base station can include functionality implemented on two or more units at different physical locations, as well as functionality implemented virtually for at least one unit, which can enable flexibility in network design. The various units of the decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0065] Figure 3 3 is a schematic diagram of an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (e.g., a near-RT RIC 325 via an E2 link, a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding mid-haul links (e.g., via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via a respective front-end link. Each RU 340 may communicate with one or more UEs 120 via a respective radio frequency (RF) access link. In some embodiments, a UE 120 may be served simultaneously by multiple RUs 340.

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

[0067] In some aspects, the CU 310 may host one or more high-level control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among others. Each control function may be implemented using an interface configured to transmit signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functions (e.g., central unit-user plane (CU-UP) functions), control plane functions (e.g., central unit-control plane (CU-CP) functions), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. The CU 310 may be implemented to communicate with the DU 330 as needed for network control and signaling.

[0068] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, depending at least in part on a functional partition (such as that defined by 3GPP), a DU 330 may house one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers. In some aspects, the one or more higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and the like. In some aspects, a DU 330 may also house one or more lower PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering. Each layer (also referred to as a module) may be implemented with an interface configured to communicate signals with other layers (and modules) housed by the DU 330, or with control functions housed by the CU 310.

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

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

[0071] The non-RT RIC 315 may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over interfaces connecting one or more CUs 310, one or more DUs 330, or both, and O-eNBs with the near-RT RIC 325 (e.g., via an E2 interface).

[0072] In some implementations, the non-RT RIC 315 may receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in the near-RT RIC 325. Such information may be utilized by the near-RT RIC 325 and may be received at the SMO framework 305 or the non-RT RIC 315 from a non-network data source or from a network function. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and use the AI / ML model to perform corrective actions through the SMO framework 305 (e.g., via reconfiguration of the O1 interface) or via the creation of RAN management policies (e.g., A1 interface policies).

[0073] As indicated above, Figure 3 is provided as an example. Other examples may differ from those described in relation to Figure 3 Examples described.

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

[0075] On the user plane, UE 120 and network node 110 may each include a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer. User plane functions may handle the transmission of user data between UE 120 and network node 110. On the control plane, UE 120 and network node 110 may each include a radio resource control (RRC) layer. UE 120 may also include a non-access stratum (NAS) layer that communicates with an access and management mobility function (AMF). The AMF may be associated with a core network associated with network node 110, such as a 5G core network (5GC) or a next-generation radio access network (NG-RAN). Control plane functions may handle the transmission of control information between the UE and the core network. Generally speaking, if a first layer is further away from the PHY layer than the second layer, the first layer is referred to as being above the second layer. For example, the PHY layer may be referred to as the lowest layer, and the SDAP / PDCP / RLC / MAC layers may be referred to as being above the PHY layer and below the RRC layer. Figure 4 The application (APP) layer, not shown in FIG, may be higher than the SDAP / PDCP / RLC / MAC layer. In some cases, an entity may handle the services and functions of a given layer (e.g., a PDCP entity may handle the services and functions of the PDCP layer), although the description herein refers to the layer itself as handling the services and functions.

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

[0077] The SDAP layer, PDCP layer, RLC layer, and MAC layer may be collectively referred to as Layer 2 (L2). Therefore, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. On the transmitting side (for example, if the UE 120 is sending uplink communications or the network node 110 is sending downlink communications), the SDAP layer may receive data streams in the form of QoS flows. A QoS flow is associated with a QoS identifier and a QoS flow identifier (QFI), the QoS identifier identifies the QoS parameters associated with the QoS flow, and the QoS flow identifier (QFI) identifies the QoS flow. Policy and charging parameters are implemented at a QoS flow granularity. A QoS flow may include one or more service data flows (SDFs), as long as each SDF of the QoS flow is associated with the same policy and charging parameters. In certain aspects, the RRC / NAS layer may generate control information to be sent and may map the control information to one or more radio bearers for provision to the PDCP layer.

[0078] The SDAP layer or the RRC / NAS layer can map QoS flows or control information to radio bearers. Therefore, the SDAP layer can be said to handle QoS flows on the transmit side. The SDAP layer can provide QoS flows to the PDCP layer via the corresponding radio bearers. The PDCP layer can map radio bearers to RLC channels. The PDCP layer can handle various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), delivery, reordering, and duplicate detection of user data (if in-sequence delivery to layers above the PDCP layer is required), PDCP protocol data unit (PDU) routing (in the case of split bearers), PDCP service data unit (SDU) retransmission, ciphering, and deciphering, PDCP SDU discard (e.g., based on the PDCP discard timer, as described elsewhere herein), PDCP re-establishment and data recovery for RLC Acknowledged Mode (AM), and PDCP PDU repetition. The PDCP layer can handle similar services and functions on the control plane, including sequence numbering, ciphering, deciphering, integrity protection, delivery of control plane data, duplicate detection, and PDCP PDU repetition.

[0079] As described above, the PDCP layer (e.g., a PDCP entity) may be configured with a PDCP discard timer. The PDCP discard timer (sometimes indicated by a parameter such as a discardTimer of a PDCP-Config configuration) may indicate a length of time, such as in milliseconds (ms). At a transmitter (e.g., a UE 120 on the uplink or a network node 110 on the downlink), the PDCP entity may receive packets, such as PDCP SDUs or data packets, from higher layers (e.g., RRC or SDAP). The PDCP entity may cache the packets in a transmission buffer for the length of the PDCP discard timer. For example, the PDCP entity may cache the packets in the transmission buffer until the transmitter receives a status report indicating successful reception, or the PDCP discard timer expires. After the PDCP discard timer expires, the packet may be discarded (e.g., cleared from the buffer, discarded, deleted). In some examples, a PDCP discard timer may be configured for each PDCP PDU such that all data (e.g., packets, PDCP SDUs) for a given PDCP PDU is buffered until a status report indicating successful reception is received or the PDCP discard timer expires for the given PDCP PDU. Some techniques described herein provide for PDCP discard timers to be configured and used per PDU set (e.g., PDCP PDU set), as described in greater detail elsewhere herein.

[0080] The PDCP layer may provide data in the form of PDCP PDUs to the RLC layer via an RLC channel. The RLC layer may handle the delivery of upper layer (e.g., PDCP) PDUs to the MAC and / or PHY layers, sequence numbering independent of the PDCP sequence numbering, error correction through automatic repeat request (ARQ), segmentation and resegmentation, reassembly of SDUs, discarding RLC SDUs, and reestablishing RLC.

[0081] The RLC layer provides the MAC layer with data mapped to logical channels. The services and functions of the MAC layer include mapping between logical channels and transport channels (used by the PHY layer as described below), multiplexing / demultiplexing MAC SDUs belonging to one or different logical channels into transport blocks (TBs) (transmitted from the physical layer to the physical layer on the transport channel), scheduling information reporting, error correction through hybrid ARQ (HARQ), handling priority between UEs through dynamic scheduling, handling priority between logical channels of a UE through logical channel priority, and padding.

[0082] As described above, the RLC layer can handle the reassembly of SDUs. Reassembly can be supported in unacknowledged mode and / or acknowledged mode. At the transmitter (e.g., the network node 110 on the downlink or the UE 120 on the uplink), the RLC layer can segment higher layer data (e.g., RLC SDUs) into RLC PDU sets and can provide the RLC PDU sets for transmission on the air interface. The receiver (e.g., the UE 120 on the downlink or the network node 110 on the uplink) can receive at least a portion of the RLC PDU set and can store the RLC PDU set in a reassembly buffer. The receiver can attempt to reassemble the RLC SDU from the received RLC PDU, which is referred to as "performing reassembly" here. The receiver can perform reassembly based on a reassembly timer, which can be configured as part of the RLC-Config configuration. The receiver can start the reassembly timer when receiving the first RLC PDU of a new RLC SDU and can reset the timer when all RLC PDUs of the RLC SDU have been received. If the reassembly timer expires before all RLC PDUs of an RLC SDU have been received, the receiver may send a status report, which may trigger retransmission of the missing RLC PDUs of the RLC SDU. The reassembly timer may be configured in conjunction with the RLC entity. Some techniques described herein may provide for the RLC entity to be configured to correspond to a PDU set parameter, such as a PDU set importance parameter, as described elsewhere herein.

[0083] The MAC layer can package the data of the logical channel into TBs and provide the TBs to the PHY layer through one or more transmission channels. The PHY layer can handle various operations related to data signal transmission. Figure 2 The PHY layer is often referred to as Layer 1 (L1).

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

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

[0086] Some of the techniques described herein relate to PDU sets. A PDU set includes one or more PDUs. The one or more PDUs may carry a payload of an information unit generated at the application layer. As just one example, an information unit may include a video frame or a slice within a video frame, such as may be generated or consumed by an extended reality (XR) application. An application associated with a transmitter may provide such an information unit to a network layer associated with the transmitter. The network layer may segment the information unit into a collection of PDUs in a PDU set (e.g., a network PDU) and may provide an indication (e.g., in each PDU in the PDU set) that the collection of PDUs belongs to a single PDU set. A PDU set may correspond to an information unit. At the transmitter, the network layer may provide the PDU set to a RAN protocol stack (such as a Figure 4 , a user plane protocol stack of the RAN) for processing and transmission via the RAN, as described above. At a receiver, a RAN protocol stack (e.g., the user plane protocol stack described above) may receive a wireless communication carrying PDUs (e.g., RLC PDUs) derived from a PDU set generated by the network layer. The RAN protocol stack may attempt to obtain the PDU set from the received wireless communication, and if successful, may provide the PDU set to the network layer of the receiver for provision to the application layer of the receiver as an information unit. Thus, although the RAN stack of the transmitter or receiver may process the PDUs in a PDU set as a single PDU, the RAN stack may have some indication that a collection of PDUs belongs to a PDU set. The PDUs that belong to a PDU set may be associated with an indication that the PDUs belong to a PDU set, such as a PDU set sequence number.

[0087] All PDUs of a PDU set may share common QoS parameters, such as a PDU set delay budget (PSDB) and / or a PDU set error rate (PSER). The PSDB may indicate the time between receipt of the first PDU of a PDU set and successful delivery of the last arriving PDU of the PDU set. The PSER may indicate an upper limit on the rate at which a PDU set has been processed by the sender of a link layer protocol but not successfully delivered to upper layers by the corresponding receiver.

[0088] Some PDU sets may require successful reception of all PDUs of the PDU set to be considered successfully recovered for the underlying information unit. For such PDU sets, if any PDU in the PDU set is lost, the information unit of the PDU set may be considered unrecoverable. Such PDU sets are referred to herein as "all or nothing" PDU sets.

[0089] On the other hand, in some examples, if fewer than all PDUs in a PDU set are received or recovered, the information unit can be recovered from the PDU set. For example, the PDUs in a PDU set can be encoded using a coding scheme that provides recovery from one or more discarded PDUs, such as application-layer forward error correction (FEC) coding. FEC coding provides redundant information to the PDUs being transmitted to detect and correct errors that may occur during transmission. FEC works by adding redundant information in the form of check symbols to the original data, which can be used at the receiver to detect and correct errors. Depending on the redundancy rate of the FEC coding, the application layer only needs an appropriate subset of the PDUs in the PDU set to decode the PDU set. Such PDU sets are referred to herein as "non-all-or-nothing" PDU sets. Whether a PDU set is an all-or-nothing or non-all-or-nothing PDU set can be indicated by a PDU set parameter corresponding to the PDU set, which is referred to herein as a PDU Set Integration Handling Indicator (PSIHI). For example, the PSIHI may indicate whether the application layer requires all PDUs in a PDU set to use the PDU set (eg, the bottom layer unit of information of the PDU set).

[0090] Different PDU sets may have different importance levels. For example, the decoding of a first PDU set (or multiple PDU sets) may depend on the data included in a second PDU set (e.g., due to a video encoding or compression scheme associated with the underlying data units of the first and second PDU sets). Due to this dependency, the second PDU set may be considered more important to the application layer than the first PDU set. An application (e.g., an application function) may indicate the importance level of a PDU set via a PDU set parameter referred to herein as a PDU set importance parameter. In the event of congestion, PDU sets associated with higher importance levels may be less likely to be discarded than PDU sets associated with lower importance levels. PDU sets associated with higher importance levels may also be prioritized for scheduling, resulting in a higher likelihood of meeting delivery deadlines than PDU sets associated with lower importance levels. PDU set importance parameters may be mapped to importance levels in any suitable manner. PDU sets associated with the same service flow and with different importance levels can be mapped to the same QoS flow and therefore can have the same PSDB, PSER and / or other QoS parameters (e.g., priority, guaranteed bit rate (GBR), maximum data burst size (MDBV), etc.).

[0091] As indicated above, Figure 4 is provided as an example. Other examples may differ from those described in relation to Figure 4 Examples described.

[0092] Figure 5 is a diagram illustrating an example 500 of a system including a UE 505 (e.g., UE 120), an XR device 510, and a network node 110 according to the present disclosure. As shown, in example 500, the UE 505 is associated with (e.g., hosted, running) an application 515. In some aspects, the application 515 can generate information based on, for example, information received from the XR device 510 (e.g., sensor data, video data, user input, feedback), content to be consumed (e.g., displayed, provided, outputted) by the XR device 510, and the like. In some aspects, the application 515 can be associated with (e.g., run, hosted at) the XR device 510.

[0093] The XR device 510 can provide an XR environment and / or facilitate interactions related to the XR environment. "XR" can refer to all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices (such as the XR device 510). XR is an umbrella term that can include virtual reality (VR), augmented reality (AR), mixed reality (MR), and / or other terms. VR is a rendered version of a delivered visual and audio scene. The rendering can be designed to simulate the visual and audio sensory stimulation of the real world to the observer or user as the observer or user moves within the limitations defined by the application. VR can be provided via an XR device 510 including a head-mounted display (HMD), which can replace the user's field of view with simulated visual components and headphones to provide accompanying audio to the user. Some form of head and motion tracking of the user in VR can allow the visual and audio components of the simulation to be updated to ensure that items and sound sources are consistent with the user's movements from the user's perspective. In AR, additional information is provided to the user or artificially generated items or content is superimposed on the user's current environment. Such additional information or content can be visual and / or auditory, and the user's observation of the user's current environment can be direct, without intermediate sensing, processing, and rendering, or indirect, where the user's perception of the user's environment is relayed via sensors and can be augmented or processed. MR is a form of AR in which some virtual elements are inserted into a physical scene with the intention of providing the illusion that these elements are part of the actual scene. XR device 510 may include a wearable device (e.g., an HMD), a processor associated with the HMD, sensors, etc.

[0094] In some aspects, the UE 505 and the XR device 510 may be co-located. For example, the UE 505 and the XR device 510 may have hardware interfaces to each other, which may provide ideal or near-ideal communication (e.g., low latency or no latency, low jitter or no jitter) between the UE 505 and the XR device 510. In some other aspects, the UE 505 and the XR device 510 may not be co-located, meaning that there may be a wireless connection (referred to as a "tether") between the UE 505 and the XR device 510. The tether may be implemented using WiFi, Bluetooth, BL, PC5 interface, or another suitable radio technology. In some aspects, the tether may be non-ideal, meaning that the tether may be associated with non-negligible delay, non-negligible jitter (e.g., uncertainty in the arrival time and / or arrival order of packets), etc. In some aspects, the network node 110 may not be aware of whether the UE 505 and the XR device 510 are co-located. For example, the presence or absence of a tether may be transparent to the network node 110, and the presence or absence of a tether may affect expectations regarding jitter, latency, etc., as described elsewhere herein.

[0095] On the uplink, the UE 505 may receive information 520 from the application 515 (e.g., directly if the application 515 is implemented at the UE 505, or via a tether if the application 515 is implemented at the XR device 510). The UE 505 may provide the information 520 to the network layer 525 of the UE 505, which may provide the information 520 to the RAN protocol stack of the UE 505 in the form of a PDU set 530 (e.g., in conjunction with a tether). Figure 4 The RAN protocol stack of the UE 505 may process the PDUs in the PDU set 530 and may send a communication carrying the PDU set 530 to the network node 110. The RAN protocol stack of the network node 110 (e.g., in conjunction with Figure 4 530 for a network layer 535 of the network node 110. If successful, the network layer 535 may reconstruct information 520 from the PDU set 530 and may provide information 520 to an application 540 of the network node 110. On the other hand, the network node 110 may fail to obtain the PDU set 530 for various reasons, in which case the network node 110 may attempt to obtain a retransmission of the communication carrying the PDU set 530 or may provide an indication that the PDU set 530 was not obtained. For uplink transmissions, the UE may be referred to as a transmitter and the network node 110 may be referred to as a receiver.

[0096] On the downlink, the network node 110 may receive information 545 from the application 540. The network node 110 may provide the information 545 to the network layer 535, which may provide the information 545 to the RAN protocol stack of the network node 110 in the form of a PDU set 550. The RAN protocol stack of the network node 110 may process the PDUs in the PDU set 550 and may send a communication carrying the PDU set 550 to the UE 505. The RAN protocol stack of the UE 505 may process the communication carrying the PDU set 550 in an attempt to obtain the PDU set 550 for the network layer 525 of the UE 505. If successful, the network layer 525 may reconstruct the information 545 from the PDU set 550 and may provide the information 545 to the UE 505 or the application 515 of the XR device 510. The UE 505 may fail to obtain the PDU set 550 for various reasons, in which case the UE 505 may attempt to obtain a retransmission of the communication carrying the PDU set 550, or may provide an indication of the failure to obtain the PDU set 550. For uplink transmissions, the UE may be referred to as a transmitter, and the network node 110 may be referred to as a receiver.

[0097] As indicated above, Figure 5 is provided as an example. Other examples may differ from those described in relation to Figure 5 Examples described.

[0098] Figure 6 6 is a schematic diagram illustrating example 600 of signaling associated with the PDCP discard time of a PDU set according to the present disclosure. Example 600 includes a transmitter and a receiver. Example 600 can be an example of an uplink transmission (wherein the transmitter is UE 120 or UE 505 and the receiver is network node 110) or a downlink transmission (wherein the transmitter is network node 110 and the receiver is UE 120 or UE 505). In the example 600 shown in the figure, the transmitter is a UE (e.g., UE 120 or UE 505) and the receiver is a network node (NN) (e.g., network node 110), which means that example 600 is shown as an example of an uplink transmission of a PDU set.

[0099] As shown in reference numeral 610, the receiver may output and the transmitter may receive a configuration. In the case of downlink communication, the transmitter may output the configuration and the receiver may receive the configuration. The configuration may include radio resource control (RRC) information, medium access control (MAC) information, downlink control information (DCI), or a combination thereof.

[0100] The configuration may include configuration of one or more PDCP discard timers. For example, the configuration may include a PDCP-Config configuration. In some aspects, a PDU discard timer may be applied to a PDU set. For example, a PDU discard timer may be started when the first PDU in the PDU set is received (e.g., generated, received from the application 515, etc.) at the transmitter and may run for the length of the PDU discard timer. If all PDUs in the PDU set have not been received by the PDCP entity of the transmitter before the timer expires, the transmitter may discard the PDU set, or may provide one or more received PDUs in the PDU set, as described elsewhere herein. If the PDCP entity receives all PDUs in the PDU set before the timer expires, the PDCP entity may provide the PDU set to lower layers of the transmitter for transmission. By applying the PDCP discard timer at the granularity of a PDU set (as compared to the granularity of a single PDU), the effects of jitter on the tether between the transmitter and an XR device associated with the transmitter (e.g., the XR device 510) are mitigated. For example, if a PDCP discard timer is applied to a single PDU in a PDU set, the single PDU may be discarded before the other PDUs in the PDU set arrive (e.g., due to jitter on the tether affecting the arrival times of the PDUs in the PDU set), even if the single PDU is subject to the PSDB for the PDU set rather than the packet delay budget (PDB) specific to the single PDU. Discarding the single PDU may result in the loss of the entire PDU set (for an all-or-nothing PDU set) and / or the loss of one or more PDUs of the PDU set (for a non-all-or-nothing PDU set), thereby reducing reliability and increasing latency. By applying the PDCP discard timer at the granularity of the PDU set (as compared to the granularity of the single PDU), the impact of jitter on the tether between a transmitter and an XR device associated with the transmitter (e.g., XR device 510) is mitigated because the single PDU will not be discarded until the PDCP discard timer for the entire PDU set (which in some aspects may be equal to or based on the PSDB for the PDU set) has expired.

[0101] In some aspects, the configuration may indicate a PDU set parameter corresponding to a PDCP discard timer. For example, the configuration may indicate that the PDCP discard timer is to be used for the PDU set associated with the PDU set parameter. In some aspects, the PDU set parameter may include a PSDB. For example, the configuration may indicate a PDCP discard timer corresponding to the PSDB. In some examples, the length of the PDCP discard timer may be equal to the PSDB, which may reduce the likelihood of discarding a single PDU in the PDU set before the PSDB expires.

[0102] In some aspects, the configuration may indicate a PDU set importance parameter and a PDCP discard timer corresponding to the PDU set importance parameter. For example, the PDU set parameter corresponding to the PDCP discard timer may be the PDU set importance parameter. As another example, the configuration may indicate multiple PDCP discard timers, and each PDCP discard timer may correspond to a different PDU set importance parameter (which may be indicated by the configuration). As yet another example, the configuration may indicate a threshold, and the PDCP discard timer may be applied to PDU sets associated with the PDU set importance parameter that meets the threshold. For example, a first PDCP discard timer may be applied to PDU sets associated with the PDU set importance parameter that meets the threshold, and a second PDCP discard timer may be applied to PDU sets associated with the PDU set importance parameter that fails to meet the threshold. In some aspects, the configuration may indicate a longer PDCP discard timer for a PDCP set importance parameter indicating a higher importance value, and / or a shorter PDCP discard timer (e.g., shorter than the longer PDCP discard timer) for a PDCP set importance parameter indicating a lower importance value (e.g., lower than the higher importance value). Therefore, a PDU set with a higher importance value (such as may be used to decode other PDU sets with lower importance values) may be more likely to be successfully received and not discarded, relative to if a shorter PDCP discard timer is used for the PDU set with the higher importance value, which may reduce the impact on the operation of the application 515. On the other hand, when a PDU set with a lower importance value arrives late (e.g., is not provided from the PDCP buffer until after the PDCP discard timer expires), the PDU set may be discarded according to the shorter PDCP discard timer with minimal impact on the application 515, thereby saving buffer space.

[0103] As shown at 620, the transmitter may receive (e.g., generate) one or more PDUs in a PDU set. For example, the PDCP layer of the transmitter may receive one or more PDCP SDUs carrying information about the one or more PDUs, such as from the transmitter's network layer, the transmitter's SDAP layer, etc. As shown at 630, the transmitter may start a PDCP discard timer corresponding to the PDU set (e.g., based at least in part on information indicating that the one or more PDCP SDUs carry information about the one or more PDUs in the PDU set). For example, the transmitter may start a PDCP discard timer configured by the configuration shown at 610. In some aspects, the PDCP discard timer may correspond to a PDU set parameter in the PDU set, such as a PSIHI or PDU set importance parameter. Additionally or alternatively, the PDCP discard timer may correspond to a QoS parameter of the PDU set, such as a PSDB. As shown at 640, in example 600, the transmitter receives all PDUs in the PDU set. Thus, as shown at 650, the transmitter transmits a communication set carrying the PDUs in the PDU set (referred to herein as "communication according to the configuration").

[0104] In some aspects, a transmitter may not receive one or more PDUs in a PDU set. For example, a PDCP entity of the transmitter may fail to receive one or more PDCP SDUs carrying one or more PDUs before a PDCP discard timer corresponding to the PDU set expires. In this example, the transmitter may discard the one or more PDUs upon expiration of the PDCP discard timer (referred to herein as communicating according to a configuration). In some aspects, the transmitter may discard one or more PDUs based at least in part on the PSIHI of the PDU set. For example, the transmitter may discard all PDUs in the PDU set based at least in part on the PSIHI indicating that the PDU set is an all-or-nothing PDU set. In this context, "all PDUs" may include PDUs in the PDU set that have not yet been received by the transmitter, PDUs in the PDU set in a transmitter buffer that have not yet been submitted to lower layers for transmission, and PDUs in the PDU set that have been submitted to lower layers, which reduces transmit resource utilization relative to transmitting PDUs in the PDU set that have been submitted to lower layers because these PDUs cannot be used in any way at the receiver. As another example, the transmitter may discard only one or more PDUs (e.g., PDUs that have not yet been received) and any PDUs that have been received and not yet submitted to lower layers based at least in part on the PSIHI indicating that the PDU set is not an all-or-nothing PDU set (e.g., the PSIHI indicating that the PDU set is a non-all-or-nothing PDU set, such as a PDU set encoded using application layer FEC). Thus, the communication efficiency of the all-or-nothing PDU set is improved by canceling the entire PDU set when any PDU in the PDU set is lost, while the functionality of the FEC-encoded PDU set is improved by reducing the likelihood of unnecessarily reducing the data rate of the FEC encoding.

[0105] As shown, a receiver may receive and process communications, such as in conjunction with Figure 4 and 5 In some aspects, the receiver may perform the following steps regarding Figure 7 Describes one or more operations.

[0106] As indicated above, Figure 6 is provided as an example. Other examples may differ from those described in relation to Figure 6 Examples described.

[0107] Figure 7is a schematic diagram illustrating example 700 of signaling associated with a retransmission timer for a PDU set according to the present disclosure. Example 700 includes a transmitter and a receiver. Example 700 may be an example of an uplink transmission (where the transmitter is UE 120 or UE 505 and the receiver is network node 110) or a downlink transmission (where the transmitter is network node 110 and the receiver is UE 120 or UE 505). In the illustrated example 700, the transmitter is network node 110 and the receiver is UE 120, which means that example 700 is illustrated as an example of a downlink transmission of a PDU set.

[0108] As shown in reference numeral 710, a receiver may output, and a transmitter may receive, information about a link (e.g., a tether) between the receiver and a device associated with the receiver, such as an XR device (e.g., XR device 510). For example, the information may include auxiliary information. The information about the link may indicate whether the receiver and the device are co-located (e.g., whether the link is ideal or non-ideal), or may indicate one or more parameters of the link. The one or more parameters may include, for example, delay parameters (e.g., average delay, maximum delay, minimum delay, standard deviation of delay), jitter parameters (e.g., average jitter, maximum jitter, minimum jitter, standard deviation of jitter, etc.), information indicating whether an application (e.g., application 515) is running on the receiver or the device, or a combination thereof. In some aspects, the transmitter may configure an RLC entity based at least in part on the information about the link. For example, if the transmitter does not know whether the application is co-located with the receiver or on a tethered device, the transmitter may misconfigure RLC timers and / or relax the network's scheduling, resulting in an unexpected increase in latency at the application. By configuring the RLC entity based at least in part on information about the link, the transmitter can account for delay and / or jitter at the link (eg, by extending RLC timers), thereby reducing occurrences of RLC timer expiration and reception failures for applications.

[0109] As shown in reference numeral 720, the transmitter may output and the receiver may receive the configuration. In the case of uplink communication, the receiver may output the configuration and the transmitter may receive the configuration. The configuration may include RRC information, MAC information, DCI, or a combination thereof.

[0110] The configuration may indicate an RLC entity. For example, the configuration may include configuration information defining a set of parameters for the RLC entity to perform RLC functions for receiving or transmitting services for a receiver. In some aspects, the configuration may indicate one or more PDU set parameters, such as PSIHI, a PDU set importance parameter, etc. In some aspects, the RLC entity may correspond to a PDU set parameter in one or more PDU set parameters. For example, a parameter of the RLC entity (e.g., a reassembly timer indicated by a t-Reassembly parameter configured by RLC-Config) may be mapped to a specific PDU set parameter so that the parameter of the RLC entity is used for RLC layer processing of a PDU set having a specific PDU set parameter. As a specific example, different timers (e.g., different reassembly timers) may be configured for different PDU set importance parameters. For example, a longer reassembly timer may be configured for a PDU set having a higher PDU set importance parameter, and a shorter reassembly timer (shorter than the longer reassembly timer) may be configured for a PDU set having a lower PDU set importance parameter (lower than the higher PDU set importance parameter). In some aspects, a longer reassembly timer can be longer than the length of the delay budget allocated to a radio access link (e.g., a Uu link) between a transmitter and a receiver, which increases the likelihood of successfully receiving a PDU set with a higher PDU set importance parameter. For example, a longer reassembly timer can be longer than the length of the delay budget allocated to the radio access link based at least in part on a higher PDU set importance parameter indicating a threshold importance level. In some aspects, this configuration is based at least in part on information about the link between the receiver and the device, as described above.

[0111] As indicated by reference numeral 730, a transmitter may transmit, and a receiver may receive, one or more PDUs in a PDU set. The PDU set may be associated with a PDU set importance parameter. For example, one or more PDUs may include an indication of the PDU set importance parameter (e.g., the transmitter may include the PDU set importance parameter in a PDU set header of the one or more PDUs or PDU set).

[0112] As shown in reference numeral 740, the receiver may process one or more PDUs based on the reassembly timer. For example, upon receiving the first RLC PDU of a new RLC SDU (e.g., a PDU set), the receiver may start a reassembly timer corresponding to the PDU set (e.g., based at least in part on a PDU set importance parameter of the PDU set corresponding to the reassembly timer). If the reassembly timer expires before all RLC PDUs of the RLC SDU have been received, the receiver may send a status report that may trigger a retransmission of the missing RLC PDUs of the RLC SDU. In some aspects, the receiver may successfully receive the PDU set. The receiver may provide the PDU set to an application (e.g., application 515) and / or a device (e.g., XR device 510).

[0113] In some aspects, a receiver may discard one or more PDUs in a PDU set based at least in part on a reassembly timer and a PSIHI for the PDU set. For example, the receiver may discard all PDUs in the PDU set (e.g., PDUs in the PDU set in a UE's RLC buffer and / or a UE's PDCP buffer (if PDCP in-order delivery is configured)) upon expiration of the reassembly timer based at least in part on a PSIHI for the PDU set indicating that the PDU set is an all-or-nothing PDU set. As another example, the receiver may discard only one or more unreceived PDUs in the PDU set upon expiration of the reassembly timer based at least in part on a PSIHI for the PDU set indicating that the PDU set is not an all-or-nothing PDU set. Thus, when one or more PDUs in the all-or-nothing PDU set are discarded, the receiver may conserve buffer resources and improve the reliability of PDU set transmission when the PDU set is not an all-or-nothing PDU set (e.g., when the PDU set uses FEC encoding).

[0114] As indicated above, Figure 7 is provided as an example. Other examples may differ from those described in relation to Figure 7 Examples described.

[0115] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a transmitter, according to the present disclosure. The example process 800 is a diagram in which a transmitter (e.g., UE 120, UE 505, Figure 6 An example of a transmitter) performing operations associated with discarding or processing based on a protocol data unit set.

[0116] like Figure 8As shown, in some aspects, process 800 may include receiving a configuration of one or more PDCP discard timers for a PDU set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers (block 810). For example, a transmitter (e.g., using Figure 10 The receiving component 1002 and / or the communication manager 1006 depicted in FIG may receive a configuration of one or more PDCP discard timers for a PDU set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers, as described above, for example, in conjunction with Figure 6 As described by the reference numeral 610 .

[0117] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include communicating according to the configuration (block 820). For example, a transmitter (e.g., using Figure 10 The receiving component 1002, the sending component 1004 and / or the communication manager 1006) depicted in FIG can communicate according to the configuration, such as in conjunction with Figure 6 As described by the figure mark 640.

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

[0119] In a first aspect, the one or more PDCP discard timers include a first PDCP discard timer for a first PDU set importance parameter of the one or more PDU set parameters, and a second PDCP discard timer for a second PDU set importance parameter of the one or more PDU set parameters.

[0120] In a second aspect, alone or in combination with the first aspect, communicating according to the configuration further comprises discarding one or more PDUs in the PDU set based at least in part on a PSIHI of the PDU set upon expiration of a PDCP discard timer in the one or more PDCP discard timers.

[0121] In a third aspect, alone or in combination with one or more of the first and second aspects, discarding the one or more PDUs includes discarding all PDUs in the PDU set based at least in part on the PSIHI indicating that the PDU set is an all or nothing PDU set.

[0122] In a fourth aspect, alone or in combination with one or more of the first to third aspects, discarding the one or more PDUs comprises discarding the one or more PDUs in the PDU set without discarding one or more other PDUs in the PDU set based at least in part on a PSIHI indicating that the PDU set is not an all-or-nothing PDU set.

[0123] Although Figure 8 Example blocks of process 800 are shown, but in some aspects process 800 may include Figure 8 The blocks may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in process 800. Additionally or alternatively, two or more blocks of the blocks of process 800 may be executed in parallel.

[0124] Figure 9 9 is a diagram illustrating an example process 900 performed, for example, by a receiver according to the present disclosure. The example process 900 is a diagram in which a receiver (e.g., UE 120, UE 505, Figure 7 An example of a receiver) performing operations associated with processing based on a protocol data unit set.

[0125] like Figure 9 As shown, in some aspects, process 900 may include receiving a configuration indicating one or more protocol data unit (PDU) set parameters, the configuration indicating a radio link control (RLC) entity corresponding to a PDU set importance parameter in the one or more PDU set parameters (block 910). For example, a receiver (e.g., using Figure 10 The receiving component 1002 and / or the communication manager 1006 depicted in FIG may receive a configuration indicating one or more PDU set parameters, the configuration indicating an RLC entity corresponding to a PDU set importance parameter in the one or more PDU set parameters, as described above.

[0126] like Figure 9 As further shown, in some aspects, process 900 may include receiving one or more PDUs in a PDU set, the PDU set being associated with a PDU set importance parameter (block 920). For example, a receiver (e.g., using Figure 10 The receiving component 1002 and / or the communication manager 1006 depicted in FIG. 1004 may receive one or more PDUs in a PDU set, the PDU set being associated with a PDU set importance parameter, as described above.

[0127] like Figure 9 As further shown in FIG. 9 , in some aspects, process 900 may include processing one or more PDUs according to an RLC entity (block 930). For example, a receiver (e.g., using Figure 10The communication manager 1006 depicted in FIG. 1006 may process one or more PDUs according to an RLC entity, as described above.

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

[0129] In a first aspect, an RLC entity indicates a reassembly timer for a PDU set importance parameter.

[0130] In a second aspect, alone or in combination with the first aspect, processing the one or more PDUs further includes discarding all PDUs in the PDU set upon expiration of the reassembly timer based at least in part on a PSIHI of the PDU set indicating that the PDU set is an all or nothing PDU set.

[0131] In a third aspect, alone or in combination with one or more of the first and second aspects, processing the one or more PDUs further comprises discarding only one or more unreceived PDUs in the PDU set upon expiration of the reassembly timer based at least in part on a PSIHI for the PDU set indicating that the PDU set is not an all-or-nothing PDU set.

[0132] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the reassembly timer is longer than a delay budget of a radio access link between a receiver and a transmitter of the PDU set, based at least in part on a PDU set importance parameter indicating a threshold importance level.

[0133] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 900 includes sending information indicative of one or more delay parameters or one or more jitter parameters of a link between a receiver and a device associated with the receiver.

[0134] Although Figure 9 Example blocks of process 900 are shown, but in some aspects process 900 may include Figure 9 The blocks may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in process 900. Additionally or alternatively, two or more blocks of the blocks of process 900 may be executed in parallel.

[0135] Figure 101 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a UE, or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002, a sending component 1004, and / or a communication manager 1006, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1006 is a communication manager that is configured to communicate with each other. Figure 1 As shown, the apparatus 1000 may communicate with another apparatus 1008, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 1002 and a sending component 1004. In some aspects, the apparatus 1000 may include a transmitter, such as Figure 6 In some aspects, the apparatus 1000 may include a receiver such as Figure 7 receiver.

[0136] In some aspects, the apparatus 1000 may be configured to perform the Figure 4-Figure 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more of the processes described herein, such as Figure 8 The process of 800 Figure 9 In some aspects, Figure 10 The apparatus 1000 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Figure 10 One or more of the components shown in the Figure 2 In addition or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0137] Receive component 1002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from apparatus 1008. Receive component 1002 may provide the received communications to one or more other components of apparatus 1000. In some aspects, receive component 1002 may perform signal processing (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and may provide the processed signals to one or more other components of apparatus 1000. In some aspects, receive component 1002 may include in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0138] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1008. In some aspects, one or more other components of the apparatus 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the apparatus 1008. In some aspects, the transmitting component 1004 may perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and may transmit the processed signals to the apparatus 1008. In some aspects, the transmitting component 1004 may include a processor in conjunction with a processor. Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0139] The communications manager 1006 can support the operation of the receiving component 1002 and / or the sending component 1004. For example, the communications manager 1006 can receive information associated with configuring the reception of communications by the receiving component 1002 and / or the transmission of communications by the sending component 1004. Additionally or alternatively, the communications manager 1006 can generate and / or provide control information to the receiving component 1002 and / or the sending component 1004 to control the reception and / or transmission of communications.

[0140] Receiving component 1002 can receive a configuration of one or more PDCP discard timers for a PDU set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers. Receiving component 1002 and / or transmitting component 1004 can communicate based on the configuration.

[0141] The receiving component 1002 can receive a configuration indicating one or more PDU set parameters, the configuration indicating an RLC entity corresponding to a PDU set importance parameter in the one or more PDU set parameters. The receiving component 1002 can receive one or more PDUs in a PDU set, the PDU set being associated with the PDU set importance parameter. The communication manager 1006 can process the one or more PDUs according to the RLC entity.

[0142] Transmitting component 1004 can transmit information indicative of one or more delay parameters or one or more jitter parameters of a link between a receiver and a device associated with the receiver.

[0143] Figure 10 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 10 Components may include additional components, fewer components, different components, or components arranged differently than those shown in FIG. Figure 10 Two or more components shown in may be implemented within a single component, or Figure 10 A single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 10 A set of (one or more) components shown in FIG can perform the operations described as being performed by Figure 10 One or more functions performed by another group of components shown in FIG.

[0144] The following provides an overview of some aspects of the disclosure:

[0145] Aspect 1: A wireless communication method performed by a transmitter, comprising: receiving a configuration of one or more packet data convergence protocol (PDCP) discard timers for a protocol data unit (PDU) set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers; and communicating according to the configuration.

[0146] Aspect 2: The method according to Aspect 1, wherein the one or more PDCP discard timers include: a first PDCP discard timer for a first PDU set importance parameter among the one or more PDU set parameters, and a second PDCP discard timer for a second PDU set importance parameter among the one or more PDU set parameters.

[0147] Aspect 3: A method according to any one of Aspects 1-2, wherein communicating according to the configuration further comprises discarding one or more PDUs in the PDU set based at least in part on a PDU set integrated processing indication (PSIHI) of the PDU set when a PDCP discard timer in the one or more PDCP discard timers expires.

[0148] Aspect 4: The method of aspect 3, wherein discarding the one or more PDUs comprises discarding all PDUs in the PDU set based at least in part on the PSIHI indicating that the PDU set is an all-or-nothing PDU set.

[0149] Aspect 5: The method of aspect 3, wherein discarding the one or more PDUs comprises: discarding the one or more PDUs in the PDU set without discarding one or more other PDUs in the PDU set based at least in part on the PSIHI indicating that the PDU set is not an all-or-nothing PDU set.

[0150] Aspect 6: A wireless communication method performed by a receiver, comprising: receiving a configuration indicating one or more protocol data unit (PDU) set parameters, the configuration indicating a radio link control (RLC) entity corresponding to a PDU set importance parameter in the one or more PDU set parameters; receiving one or more PDUs in a PDU set, the PDU set being associated with the PDU set importance parameter; and processing the one or more PDUs according to the RLC entity.

[0151] Aspect 7: The method according to aspect 6, wherein the RLC entity indicates a reassembly timer for the PDU set importance parameter.

[0152] Aspect 8: The method of aspect 7, wherein processing the one or more PDUs further comprises discarding all PDUs in the PDU set upon expiration of the reassembly timer, based at least in part on a PDU set integration handling indication (PSIHI) of the PDU set indicating that the PDU set is an all or nothing PDU set.

[0153] Aspect 9: The method according to Aspect 7, wherein processing the one or more PDUs further comprises: upon expiration of the reassembly timer, at least in part based on a PDU set integration processing indication (PSIHI) of the PDU set indicating that the PDU set is not an all-or-nothing PDU set, only discarding one or more unreceived PDUs in the PDU set.

[0154] Aspect 10: The method of aspect 7, wherein the reassembly timer is longer than a delay budget of a radio access link between a receiver and a transmitter of the PDU set based at least in part on the PDU set importance parameter indicating a threshold importance level.

[0155] Aspect 11: The method according to any of aspects 6-10, further comprising: sending information indicating one or more delay parameters or one or more jitter parameters of a link between the receiver and a device associated with the receiver.

[0156] Aspect 12: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1-11.

[0157] Aspect 13: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1-11.

[0158] Aspect 14: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 1-11.

[0159] Aspect 15: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1-11.

[0160] Aspect 16: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1-11.

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

[0162] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Regardless of being referred to as software, firmware, middleware, microcode, hardware description language or other, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented with different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code for implementing these systems and / or methods is not intended to limit various aspects. Therefore, the operation and behavior of the systems and / or methods are described herein without citing specific software codes, because those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods at least in part based on the description herein.

[0163] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0164] Even if the specific combination of feature is recorded in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many features in these features can be combined in a manner not specifically recorded in the claims and / or not specifically disclosed in the specification. The disclosure of various aspects includes the combination of each dependent claim and each other claim in the claim set. As used herein, the phrase of "at least one of" a list of items refers to any combination of these items (which includes a single member). For example, "at least one of a, b or c" is intended to encompass any combination of a, b, c, a+b, a+c, b+c and a+b+c, and with the multiple of the same elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c or any other sorting of a, b and c).

[0165] In the element used herein, action or instruction, none should be interpreted as key or necessary, unless clearly described as so.In addition, as used herein, article " one (a) " and " one (an) " are intended to include one or more projects, and can be used interchangeably with " one or more ".In addition, as used herein, article " described (the) " is intended to include one or more projects quoted in conjunction with article " described ", and can be used interchangeably with " one or more ".In addition, as used herein, term " set " and " group " are intended to include one or more projects, and can be used interchangeably with " one or more ".In the case of only expecting a project, phrase " only one " or similar language is used.In addition, as used herein, term " has ", " have ", " have " etc. are intended to be open terms, and it does not limit the element (for example, " element with " A can also have B) that they modify.In addition, unless otherwise clearly stated, phrase " based on " is intended to mean " at least partially based on ". Furthermore, as used herein, the term "or" when used in a series is intended to be inclusive and can be used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in conjunction with "any of" or "only one of").

Claims

1. A wireless communication method performed by a transmitter, comprising: receiving a configuration of one or more packet data convergence protocol (PDCP) discard timers for a protocol data unit (PDU) set, the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers; and Communication is performed according to the configuration.

2. The method according to claim 1, wherein The one or more PDCP discard timers include: a first PDCP discard timer for a first PDU set importance parameter among the one or more PDU set parameters, and a second PDCP discard timer for a second PDU set importance parameter among the one or more PDU set parameters.

3. The method according to claim 1, wherein Communicating according to the configuration further includes discarding one or more PDUs in the PDU set based at least in part on a PDU Set Integration Handling Indication (PSIHI) of the PDU set upon expiration of a PDCP discard timer in the one or more PDCP discard timers.

4. The method according to claim 3, wherein: Discarding the one or more PDUs includes discarding all PDUs in the PDU set based at least in part on the PSIHI indicating that the PDU set is an all or nothing PDU set.

5. The method according to claim 3, wherein Discarding the one or more PDUs includes discarding the one or more PDUs in the PDU set based at least in part on the PSIHI indicating that the PDU set is not an all or nothing PDU set, and not discarding one or more other PDUs in the PDU set.

6. A wireless communication method performed by a receiver, comprising: receiving a configuration indicating one or more protocol data unit (PDU) set parameters, the configuration indicating a radio link control (RLC) entity corresponding to a PDU set importance parameter in the one or more PDU set parameters; receiving one or more PDUs in a PDU set, the PDU set being associated with the PDU set importance parameter; as well as The one or more PDUs are processed according to the RLC entity.

7. The method according to claim 6, wherein: The RLC entity indicates a reassembly timer for the PDU set importance parameter.

8. The method according to claim 7, wherein: Processing the one or more PDUs further includes discarding all PDUs in the PDU set based at least in part on a PDU set integration handling indication (PSIHI) of the PDU set indicating that the PDU set is an all or nothing PDU set upon expiration of the reassembly timer.

9. The method according to claim 7, wherein: Processing the one or more PDUs further includes discarding only the one or more unreceived PDUs in the PDU set based at least in part on a PDU set integration handling indication (PSIHI) of the PDU set indicating that the PDU set is not an all-or-nothing PDU set upon expiration of the reassembly timer.

10. The method according to claim 7, wherein: Based at least in part on the PDU set importance parameter indicating a threshold importance level, the reassembly timer is longer than a delay budget of a radio access link between a receiver and a transmitter of the PDU set.

11. The method according to claim 6, further comprising: Information indicative of one or more delay parameters or one or more jitter parameters of a link between the receiver and a device associated with the receiver is transmitted.

12. A transmitter for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors being configured to: receiving a configuration of one or more packet data convergence protocol (PDCP) discard timers for a set of protocol data units (PDUs), the configuration indicating one or more PDU set parameters corresponding to the one or more PDCP discard timers; and Communication is performed according to the configuration.

13. The transmitter according to claim 12, wherein The one or more PDCP discard timers include: a first PDCP discard timer for a first PDU set importance parameter among the one or more PDU set parameters, and a second PDCP discard timer for a second PDU set importance parameter among the one or more PDU set parameters.

14. The transmitter according to claim 12, wherein The one or more processors configured to communicate according to the configuration are configured to discard one or more PDUs in the PDU set based at least in part on a PDU set integrated handling indication (PSIHI) of the PDU set upon expiration of a PDCP discard timer in the one or more PDCP discard timers.

15. The transmitter according to claim 14, wherein The one or more processors for discarding the one or more PDUs are configured to discard all PDUs in the PDU set based at least in part on the PSIHI indicating that the PDU set is an all or nothing PDU set.

16. The transmitter according to claim 14, wherein The one or more processors for discarding the one or more PDUs are configured to discard the one or more PDUs in the PDU set based at least in part on the PSIHI indicating that the PDU set is not an all or nothing PDU set and not discard one or more other PDUs in the PDU set.

17. A receiver for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors being configured to: receiving a configuration indicating one or more protocol data unit (PDU) set parameters, the configuration indicating a radio link control (RLC) entity corresponding to a PDU set importance parameter in the one or more PDU set parameters; receiving one or more PDUs in a PDU set, the PDU set being associated with the PDU set importance parameter; as well as The one or more PDUs are processed according to the RLC entity.

18. The receiver according to claim 17, wherein The RLC entity indicates a reassembly timer for the PDU set importance parameter.

19. The receiver according to claim 18, wherein The one or more processors for processing the one or more PDUs are configured to, upon expiration of the reassembly timer, discard all PDUs in the PDU set based at least in part on a PDU set integration handling indication (PSIHI) of the PDU set indicating that the PDU set is an all-or-nothing PDU set.

20. The receiver of claim 18, wherein The one or more processors for processing the one or more PDUs are configured to, upon expiration of the reassembly timer, simply discard one or more unreceived PDUs in the PDU set based at least in part on a PDU set integration handling indication (PSIHI) of the PDU set indicating that the PDU set is not an all-or-nothing PDU set.

21. The receiver of claim 18, wherein Based at least in part on the PDU set importance parameter indicating a threshold importance level, the reassembly timer is longer than a delay budget of a radio access link between a receiver and a transmitter of the PDU set.

22. The receiver of claim 17, wherein: The one or more processors are further configured to send information indicative of one or more delay parameters or one or more jitter parameters of a link between the receiver and a device associated with the receiver.

Images