Drop timer for protocol data unit communications

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a first drop timer value associated with a radio bearer. The UE may receive multiplier values associated with characteristics of a protocol data unit or set of protocol data units to be transmitted via a radio bearer. The UE may initiate a drop timer for a protocol data unit or a set of protocol data units, the drop timer having a second drop timer value corresponding to the first drop timer value multiplied by the multiplier value. Numerous other aspects are described.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 490,732, filed March 16, 2023, entitled "Drop Timer for Protocol Data Unit Communication," and U.S. Non-Provisional Patent Application No. 18 / 593,382, filed March 1, 2024, entitled "Drop Timer for Protocol Data Unit Communication," which are incorporated herein by reference. Technical Field

[0003] In general, various aspects of this disclosure relate to wireless communication and techniques and apparatus for discarding timers for communication of protocol data units. Background Technology

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

[0005] 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 network nodes via downlink and uplink communication. "Downlink" (or "DL") refers to the communication link from the network node to the UE, while "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, for example, via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, or global level. New Radio (NR) (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 service, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM) and CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation, thereby better supporting mobile broadband internet access. Summary of the Invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a first discard timer value associated with a radio bearer. The method may include receiving a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. The method may include initiating a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0008] Some aspects described herein relate to a method for performing wireless communication by a network node. The method may include sending a first discard timer value associated with a radio bearer. The method may include sending a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. The method may include initiating a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a first discard timer value associated with a radio bearer. The one or more processors may be configured to receive a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. The one or more processors may be configured to initiate a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit a first discard timer value associated with a radio bearer. The one or more processors may be configured to transmit a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. The one or more processors may be configured to initiate a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication performed by a UE. When executed by one or more processors of the UE, the set of instructions causes the UE to: receive a first discard timer value associated with a radio bearer. When executed by one or more processors of the UE, the set of instructions causes the UE to: receive a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. When executed by one or more processors of the UE, the set of instructions causes the UE to: initiate a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions can cause the network node to: send a first discard timer value associated with a radio bearer. When executed by one or more processors of the network node, the set of instructions can cause the network node to: send a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. When executed by one or more processors of the network node, the set of instructions can cause the network node to: initiate a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include units for receiving a first discard timer value associated with a radio bearer. The apparatus may include units for receiving a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. The apparatus may include units for initiating a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include units for transmitting a first discard timer value associated with a radio bearer. The apparatus may include units for transmitting a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. The apparatus may include units for initiating a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0015] Aspects generally include, as fully described herein with reference to the accompanying drawings, description and appendices, and as shown by reference to the accompanying drawings, description and appendices, 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.

[0016] The foregoing has provided a fairly broad overview of the features and technical advantages of examples according to this disclosure in order to better understand the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features (both their organization and operation) of the concepts disclosed herein, as well as their associated advantages, will be better understood in conjunction with the accompanying drawings, based on the description below. Each drawing in the accompanying drawings is provided for illustrative and descriptive purposes and is not intended to limit the scope of the claims. Attached Figure Description

[0017] To gain a more detailed understanding of the features described above in this disclosure, a more specific description of the invention, which has been 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 drawings illustrate only certain typical aspects of this disclosure and are therefore not intended to limit its scope, as the specification may allow for other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 This is a diagram illustrating an example of a wireless network.

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

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

[0021] Figure 4 This is a schematic diagram illustrating examples of user plane protocol stacks and control plane protocol stacks for network nodes and core networks communicating with the UE, in accordance with the present disclosure.

[0022] Figures 5A-5B This is a schematic diagram illustrating an example of protocol data unit communication according to this disclosure.

[0023] Figure 6 This is a schematic diagram illustrating an example of a discard timer for protocol data unit communication in accordance with this disclosure.

[0024] Figure 7 This is a schematic diagram illustrating an example of discarding a timer multiplier value according to this disclosure.

[0025] Figure 8 This is a schematic diagram illustrating an example process performed by a UE, for example, according to this disclosure.

[0026] Figure 9 This is a schematic diagram illustrating, for example, an example process performed by a network node, based on the present disclosure.

[0027] Figure 10 This is a diagram illustrating an example device for wireless communication according to the present disclosure.

[0028] Figure 11 This is a diagram illustrating an example device for wireless communication according to the present disclosure. Detailed Implementation

[0029] A Protocol Data Unit (PDU) set can include multiple PDUs associated with the same application unit. In some cases, Quality of Service (QoS) parameters can be managed at the PDU set level. For example, Extended Reality (XR) applications can manage the PDU set Error Rate (PSER) and PDU set Delay Budget (PSDB) for all PDUs included in the PDU set. Different application units can have different importance levels, and therefore different PDU sets associated with different application units can have different QoS requirements. For example, a first PDU set including intra-coded frames (I-frames) (also called reference frames) can have a first QoS requirement associated with a higher importance level, and a second PDU set including predictive frames (P-frames) can have a second QoS requirement associated with a lower importance level. In some cases, multiple PDUs can be multiplexed on a single radio bearer. However, the radio bearer can be configured with only a single Packet Data Convergence Protocol (PDCP) drop timer. The drop timer can be associated with a drop timer value corresponding to the time period during which the device stores the PDUs in memory (such as a buffer or queue). For example, a device can initiate a drop timer for a PDU based at least in part on PDUs received by the device's PDCP layer. When the drop timer expires, the device can drop the PDU. Dropping a PDU can include deleting it from memory and / or avoiding transmission of the PDU via a radio bearer. In an example where a radio bearer is configured with a single drop timer, all PDUs on the radio bearer can be subject to the same drop timer. This may not be desirable when managing QoS parameters at the PDU set level. For example, a first PDU set and a second PDU set cannot have different drop timers because they are associated with the same radio bearer, even if PDUs included in the first PDU set have a higher importance level than those included in the second PDU set. Therefore, the PDCP drop timer duration may be too short for PDUs included in the first PDU set, potentially leading to content interruption; and the PDCP drop timer duration may be too long for PDUs included in the second PDU set, potentially leading to wasted device and system resources.

[0030] This document describes techniques and apparatus for a discard timer for PDU communication. In some aspects, a user equipment (UE) may receive a first discard timer value associated with a radio bearer. The UE may receive a multiplier value associated with characteristics of a PDU or set of PDUs to be transmitted via the radio bearer. The characteristics of the PDU or set of PDUs may be (or may be at least partially based on) the importance of the PDU or set of PDUs, the type of service associated with the PDU or set of PDUs (such as whether the PDU or set of PDUs includes XR video services or non-XR video services), the type of frames included in the PDU or set of PDUs (such as whether the PDU or set of PDUs includes I-frames or P-frames), and / or the quality of service associated with the PDU or set of PDUs. In some aspects, the UE may receive multiple multiplier values. For example, the UE may receive a first multiplier value associated with a first type of PDU or set of PDUs (such as a PDU or set of PDUs with higher priority) and a second multiplier value associated with a second type of PDU or set of PDUs (such as a PDU or set of PDUs with lower priority). The UE can initiate a discard timer for a PDU or a set of PDUs. The discard timer for a PDU or a set of PDUs can have a second discard timer value corresponding to a first discard timer value multiplied by a first multiplier value. For example, the UE can initiate a discard timer for a first type of PDU or set of PDUs based at least in part on multiplying the discard timer value by the first multiplier value (e.g., multiplying the first discard timer value by 4). Alternatively or additionally, the UE can initiate a discard timer for a second type of PDU or set of PDUs based at least in part on multiplying the same discard timer value by another multiplier value (e.g., multiplying the first discard timer value by two). Packets with higher priority can be subject to longer discard timers and therefore can be stored by the UE for a longer period, while packets with lower priority can be subject to shorter discard timers and therefore can be discarded by the UE more quickly. This allows packets with different priorities to be discarded at different time periods, even if these packets are on the same radio bearer. This can improve system reliability while reducing resource waste and other benefits.

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

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

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

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

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

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

[0037] In some aspects, the term "base station" or "network node" can refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" can refer to a CU, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" can 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" can refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) can be configured to perform at least a portion of the functions, or to replicate the performance of at least a portion of the functions, and the term "base station" or "network node" can refer to any one or more of those different devices. In some aspects, the term "base station" or "network node" can refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device can include more than one base station.

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

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

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

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

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

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

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

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

[0046] Frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR research has designated the operating bands of these IF bands as the frequency range name FR3 (7.125GHz-24.25GHz). Bands falling within FR3 can inherit characteristics of either FR1 or FR2, and thus can effectively extend the characteristics of FR1 or FR2 into the IF band. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6GHz. For example, three higher operating bands have been designated as the frequency range names 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] In light of these examples, unless otherwise specified, the term "sub-6GHz" (if used herein) can be broadly interpreted to mean a frequency that is less than 6GHz, can be within FR1, or can include intermediate frequency bands. Furthermore, unless otherwise specified, the term "millimeter wave" (if used herein) can be broadly interpreted to mean a frequency that can include intermediate frequency bands, can be within FR2, FR4, FR4a, or FR4–1 or FR5, or can be within the EHF band. It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0048] In some aspects, UE 120 may include communication manager 140. As described in more detail elsewhere herein, communication manager 140 may receive a first discard timer value associated with a radio bearer; receive a multiplier value associated with a feature of a protocol data element or protocol data set to be transmitted via the radio bearer; and initiate a discard timer for the protocol data element or protocol data set, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

[0049] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send a first discard timer value associated with a radio bearer; send a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer; and initiate a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0050] As pointed out above, Figure 1 This is provided as an example. Other examples may differ from the one provided. Figure 1 The example described.

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

[0052] At network node 110, transmitting processor 220 can receive data from data source 212 designated for UE 120 (or a set of UEs 120). Transmitting processor 220 can select one or more modulation and coding schemes (MCS) for UE 120, at least in part, based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 can use the selected MCS for UE 120 to process (e.g., encode and modulate) the data for UE 120, and can provide data symbols for UE 120. Transmitting processor 220 can process system information (e.g., for Semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, permission, or upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, overhead symbols, or reference symbols, and can 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 to 232t. For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

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

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

[0055] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element sets, non-coplanar antenna element sets, or coupled to one or more transmitting or receiving components (e.g., Figure 2 One or more antenna elements (one or more components).

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

[0057] At network node 110, uplink signals from UE 120 or other UEs can 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 transmitted by UE 120. Receive processor 238 can provide decoded data to data sink 239 and decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and can communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or any combination of TX MIMO processor 230. Processors (e.g., controller / processor 240) and memory 242 may be used with the transceiver to perform aspects of any of the processes described herein (e.g., references). Figures 6-11 ).

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

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

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

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

[0062] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or Figure 2 Any other components may perform one or more techniques associated with the discard timer for PDU communication, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component (or combination of components) can perform or direct, for example Figure 8 The process 800 Figure 9 The operation of process 900 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of network node 110 or UE 120 (e.g., directly, or after compilation, translation, or interpretation), may cause one or more processors, UE 120, or network node 110 to perform or instruct, for example... Figure 8 The process 800 Figure 9 The operation of process 900 and / or other processes as described herein. In some examples, the execution instructions may include: run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0063] In some aspects, UE 120 may include units for receiving a first discard timer value associated with a radio bearer; units for receiving a multiplier value associated with a feature of a protocol data element or protocol data set to be transmitted via the radio bearer; and / or units for initiating a discard timer for a protocol data element or protocol data set, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value. Units for UE 120 to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0064] In some aspects, network node 110 may include units for transmitting a first discard timer value associated with a radio bearer; units for transmitting a multiplier value associated with a feature of a protocol data unit or protocol data set to be transmitted via the radio bearer; and / or units for initiating a discard timer for a protocol data unit or protocol data set, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value. Units for network node 110 to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

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

[0066] As pointed out above, Figure 2 This is provided as an example. Other examples may differ from the one provided. Figure 2 The example described.

[0067] Communication systems (such as 5G NR systems) can be deployed in various ways and have a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in aggregated or decomposed architectures. For example, a base station (e.g., a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functions can be implemented as an aggregated base station (also referred to as a standalone base station or monolithic base station) or a decomposed base station. A “network entity” or “network node” can refer to a decomposed base station, or 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 combinations thereof).

[0068] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more units (e.g., 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 across one or more other network nodes. DUs can be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs can also be implemented as a virtual unit, such as a Virtual Central Unit (VCU), Virtual Distributed Unit (VDU), or Virtual Radio Unit (VRU), etc.

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

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

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

[0072] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, PDCP functions, or Service Data Adaptation Protocol (SDAP) functions, and others. Each control function may be implemented using an interface configured to transmit signaling to 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 combinations thereof. In some implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. CU-UP units may communicate bidirectionally with CU-CP units via an interface (e.g., via an E1 interface when implemented in an O-RAN configuration). Where necessary, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0073] Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RU 340s. In some aspects, at least in part depending on the functional partitioning (e.g., functional partitioning defined by 3GPP), the DU 330 may host one or more of the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and one or more high physical (PHY) layers. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, and other examples. In some aspects, the DU 330 may also host one or more low PHY layers, for example by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), or digital beamforming or Physical Random Access Channel (PRACH) extraction and filtering, and other examples. Each layer (also referred to as a module) may be implemented using an interface configured to transmit signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

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

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

[0076] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows (including model training and updates), or policy-based application / feature guidance in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on interfaces connecting one or more CUs 310s, one or more DUs 330s, or both, and the O-eNB to the near-RT RIC 325 (e.g., via an E2 interface).

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

[0078] As mentioned above, Figure 3 This is provided as an example. Other examples may differ from the one provided. Figure 3 The example described.

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

[0080] On the user plane, UE 120 and network node 110 may each include their respective Physical (PHY) layer, Medium Access Control (MAC) layer, Radio Link Control (RLC) layer, PDCP layer, and Service Data Adaptation Protocol (SDAP) layer. User plane functions handle user data transmission between UE 120 and network node 110. On the control plane, UE 120 and network node 110 may each include their respective RRC layer. Additionally, UE 120 may include a NAS layer that communicates with the Non-Access Stratum (NAS) layer of the Access and Management Mobility Functions (AMF). The AMF may be associated with the core network associated with network node 110, such as a 5G core network (5GC) or a Next Generation Radio Access Network (NG-RAN). Control plane functions handle control information transmission between the UE and the core network. Generally, if a first layer is further away from the PHY layer than a 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. The application (APP) layer can be higher than the SDAP / PDCP / RLC / MAC layer, such as... Figure 4 As shown. In some cases, an entity can handle the services and functions of a given layer (e.g., a PDCP entity can handle the services and functions of a PDCP layer), although the description here refers to the layer itself as handling services and functions.

[0081] The RRC layer handles communications associated with configuring and operating UE 120, such as broadcasting system information associated with the Access Layer (AS) and NAS, paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of RRC connections between the UE and NG-RAN, including the addition, modification, and release of carrier aggregation, as well as the addition, modification, and release of dual 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 control, inter-RAT mobility), Quality of Service (QoS) management functions; UE measurement reporting and reporting control, radio link failure detection and recovery, and NAS message transmission between the UE 120's NAS layer and lower layers. The RRC layer is often referred to as Layer 3 (L3).

[0082] The SDAP, PDCP, RLC, and MAC layers can be collectively referred to as Layer 2 (L2). Therefore, in some cases, SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. On the transmitting side (e.g., if UE 120 is transmitting uplink communication or network node 110 is transmitting downlink communication), the SDAP layer can receive data streams in the form of QoS streams. A QoS stream is associated with a QoS identifier and a QoS stream identifier (QFI). The QoS identifier identifies the QoS parameters associated with the QoS stream, and the QoS stream identifier (QFI) identifies the QoS stream. Policy and charging parameters are implemented at the QoS stream granularity. A QoS stream can include one or more Service Data Streams (SDFs), provided that each SDF of the QoS stream is associated with the same policy and charging parameters. In some respects, the RRC / NAS layer can generate control information to be transmitted and can map the control information to one or more radio bearers for provision to the PDCP layer.

[0083] The SDAP or RRC / NAS layer maps QoS flows or control information to radio bearers. Therefore, the SDAP layer can be said to process QoS flows on the transmitting side. The SDAP layer provides QoS flows to the PDCP layer via the corresponding radio bearers. The PDCP layer maps 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), user data transmission, reordering and deduplication detection (if sequential delivery to layers above the PDCP layer is required), PDCP Protocol Data Unit (PDU) routing (in the case of split bearers), retransmission of PDCP Service Data Units (SDUs), encryption and decryption, PDCP SDU dropping (e.g., according to timers, described elsewhere in this document), PDCP reconstruction and data recovery for RLC Acknowledgment Mode (AM), and PDCP PDU duplication. The PDCP layer can handle similar services and functions on the control plane, including sequence numbering, encryption, decryption, integrity protection, control plane data transmission, deduplication detection, and PDCP PDU duplication.

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

[0085] The RLC layer can provide the MAC layer with data mapped to logical channels. The services and functions of the MAC layer include mapping between logical channels and transport channels (used by the PHY layer, as described above), 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 via Hybrid ARQ (HARQ), prioritizing UEs through dynamic scheduling, prioritizing logical channels within a UE through logical channel priorities, and padding.

[0086] The MAC layer can package data from logical channels into TBs and provide these TBs to the PHY layer through one or more transport channels. The PHY layer handles various operations related to data signal transmission; see details below. Figure 2 The PHY layer is usually referred to as layer 1 (L1).

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

[0088] Data can be transferred between layers in the form of PDUs and SDUs. An SDU is a unit of data 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 this data unit into a PDU and pass it 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, or encapsulate an RLC SDU into an RLC PDU, and so on. In effect, the PDU carries the SDU as a payload.

[0089] As pointed out above, Figure 4 This is provided as an example. Other examples may differ from the one provided. Figure 4 The example described.

[0090] Figures 5A-5BThis is a schematic diagram illustrating example 500 of protocol data unit communication according to this disclosure. In some cases, a PDU may be associated with a QoS flow. Depending on the QoS profile associated with the QoS flow, the QoS flow may be a guaranteed bit rate (GBR) QoS flow or a non-GBR QoS flow. The QoS profile associated with the QoS flow may be sent to a network node (e.g., via a UE) and may include one or more QoS parameters. In some cases, for each QoS flow, the QoS profile may include a 5G QoS identifier (5QI) and an allocation and reservation priority (ARP) as QoS parameters for the QoS flow. For each non-GBR QoS flow, the QoS profile may include a reflection QoS attribute (RQA) as a QoS parameter. For each GBR QoS flow, the QoS profile may include a guaranteed flow bit rate (GFBR) (for UL and DL) and a maximum flow bit rate (MFBR) (for UL and DL) as QoS parameters. For a GBR QoS flow, the QoS profile may include notification control and / or maximum packet loss rate (for UL and DL) as QoS parameters.

[0091] In some cases, a drop timer, such as a PDCP drop timer, can be configured for the radio bearer. Upon receiving a PDCP SDU from an upper layer, the transmitting PDCP entity can start the drop timer associated with the PDCP SDU. When the drop timer associated with the PDCP SDU expires, or when a PDCP status report confirms successful delivery of the PDCP SDU, the transmitting PDCP entity can discard the PDCP SDU. The drop timer can be configured in the range of 0.5 milliseconds (ms) to 1500 ms.

[0092] In some cases, such as when an Extended Reality (XR) device connects to the UE via a radio link, there may be significant jitter when the PDU arrives at the SDAP. In some cases, network nodes can acknowledge per-PDU-set management PDCP drop timers. Although all PDU sets within the same QoS flow can share the same PDU-set Delay Budget (PSDB), decoding subsequent PDU sets may still require high-importance PDU sets, even if those sets miss their decoding deadlines. In some cases, PDU sets with different importance can be configured with different PDCP drop timers. Applications with different PDU-set Integration Processing Indications (PSIHI) can react differently to drops. In some cases, when the PDCP drop timer for a PDU set expires, all PDUs associated with that set that have not yet been submitted to lower layers (including PDUs that have not yet been received) may be dropped. If the PSIHI of a PDU set indicates that all PDUs in that set are required by the application, the network can be configured to discard PDUs already submitted to lower layers. In some cases, if a MAC PDU contains at least one MAC sub-PDU that should not be discarded, then the MAC PDU may not be discarded.

[0093] like Figure 5AAs shown, network stack 505 can provide Transmission Control Protocol (TCP) Acknowledgment (ACK) PDUs to data layer 510. Data layer 510 can provide data and TCP ACK PDUs to Internet Protocol (IP) layer 515. Data layer 510 can provide data and TCP ACK PDUs to PDCP layer. For example, data may include multiple PDUs belonging to different application units, thus forming different PDU sets. In one example, a first PDU set (PDU set 1) may include one or more intra-coded frames (I-frames), and a second PDU set (PDU set 2) may include one or more predicted frames (P-frames). In some cases, multiple data streams may be multiplexed on the same radio bearer. For example, streams F1, F2, and F3 may be multiplexed on the same radio bearer (RB). PDCP layer can configure PDCP drop timers for each radio bearer. For each stream multiplexed on a radio bearer, the PDCP drop timer may be the same (e.g., for each stream multiplexed on a radio bearer, it may have the same PDCP drop timer value). Data streams can be placed into UL PDCP queue 520. NR-PDCP 525 can use its respective RLC, MAC, and PHY layers to transmit data streams, such as LTE UL services or NR UL services. For example, NR-PDCP 530 can use its respective PHY, MAC, and RLC layers to receive LTE DL services or NR DL services that include one or more data streams. NR-PDCP 530 can place data streams into PDCP reordering queue 535. PDCP reordering queue 535 can reorder data streams and provide them to data layer 510. Data layer 510 can provide data streams to network stack 505.

[0094] like Figure 5BAs shown, the User Plane Function (UPF) 540 can receive multiple IP streams 545. The multiple IP streams 545 may include, for example, a best-effort stream, a first video service stream (video service stream 1), a second video service stream (video service stream 2), a first streaming service stream (streaming service 1), a second streaming service stream (streaming service 2), a voice stream, and a video stream, as well as other examples. The best-effort stream, the first video service stream, the second video service stream, and the first streaming service stream may be associated with an Internet PDU. The second streaming service stream may be associated with a streaming service PDU. The voice stream and video stream may be associated with an IP Multimedia Subsystem (IMS) PDU. For example, the UPF 540 using a Service Data Stream / Service Stream Template (SDF / TFT) can use a QFI insert 550 to map the IP streams 545 to one or more QoS streams. For example, UPF 540 can map a best-effort stream to a first QoS stream with a first QFI (QoS stream 1, QFI 1), map a first video service stream and a second video service stream to a second QoS stream with a second QFI (QoS stream 2, QFI 2), map a first streaming service stream to a third QoS stream with a third QFI (QoS stream 3, QFI 3), map a second streaming service stream to a fourth QoS stream with a fourth QFI (QoS stream 4, QFI 4), map a voice stream to a fifth QoS stream with a fifth QFI (QoS stream 5, QFI 5), and map a video stream to a sixth QoS stream with a sixth QFI (QoS stream 6, QFI 6). Network node 110 can map one or more QoS streams to one or more SDAP functions. For example, network node 110 can map a first QoS flow, a second QoS flow, and a third QoS flow to a first SDAP function (SDAP 1), a fourth QoS flow to a second SDAP function (SDAP 2), and a fifth and sixth QoS flow to a third SDAP function (SDAP 3). Network node 110 can use DRB mapping 555 to map one or more SDAP functions to one or more DRBs. For example, network node 110 can map a first QoS flow associated with a first SDAP function to a first DRB (DRB 1), a second and third QoS flow associated with a first SDAP function to a second DRB (DRB 2), a fourth QoS flow associated with a second SDAP function to a third DRB (DRB 3), a fifth QoS flow associated with a third SDAP function to a fourth DRB (DRB 4), and a sixth QoS flow associated with a third SDAP function to a fifth DRB (DRB 5). UE 120 can map one or more DRBs to one or more SDAP and TFT functions.For example, UE 120 can map the first and second DRBs to the first SDAP and TFT function (SDAP+TFT 1), the third DRB to the second SDAP and TFT function (SDAP+TFT 2), and the fourth and fifth DRBs to the third SDAP and TFT function (SDAP+TFT 3). The SDAP and TFT functions can output one or more IP streams.

[0095] A PDU set can include multiple PDUs associated with the same application unit. In some cases, QoS parameters can be managed at the PDU set level. For example, an XR application can manage the PDU set error rate (PSER) and PDU set delay budget (PSDB) for all PDUs included in the PDU set. Different application units can have different importance levels, and therefore different PDU sets associated with different application units can have different QoS requirements. For example, a first PDU set including I-frames can have a first QoS requirement associated with a higher importance level, and a second PDU set including P-frames can have a second QoS requirement associated with a lower importance level. In some cases, multiple PDUs can be multiplexed on a single radio bearer. However, the radio bearer may only be configured to be dropped by a single PDCP timer. Therefore, all PDUs on the radio bearer may conform to the same drop timer. This may not be desirable when managing QoS parameters at the PDU set level. For example, the first PDU set and the second PDU set cannot have different drop timers because they are associated with the same radio bearer, even if the PDUs included in the first PDU set have a higher importance level than those included in the second PDU set. Therefore, for PDUs included in the first PDU set, the PDCP drop timer duration may be too short, potentially leading to content interruption; conversely, for PDUs included in the second PDU set, the PDCP drop timer duration may be too long, potentially wasting equipment and system resources.

[0096] This document describes techniques and apparatus for a discard timer for PDU communication. In some aspects, the UE may receive a first discard timer value associated with a radio bearer. The UE may receive a multiplier value associated with characteristics of the PDU or PDU set to be transmitted via the radio bearer. The characteristics of the PDU or PDU set may be (or may be at least partially based on) the importance of the PDU or PDU set, the service type associated with the PDU or PDU set (such as whether the PDU or PDU set is associated with XR video service or non-XR video service), the frame type included in the PDU or PDU set (such as whether the PDU or PDU set includes I-frames or P-frames), and / or the quality of service associated with the PDU or PDU set. In some aspects, the UE may receive multiple multiplier values. For example, the UE may receive a first multiplier value associated with a first type of PDU or PDU set (such as a PDU or PDU set with higher priority) and a second multiplier value associated with a second type of PDU or PDU set (such as a PDU or PDU set with lower priority). The UE can initiate a discard timer for a PDU or a set of PDUs. The discard timer for a PDU or a set of PDUs can have a second discard timer value corresponding to a first discard timer value multiplied by a multiplier value. For example, the UE can initiate a discard timer for a first type of PDU or set of PDUs at least partially based on multiplying the discard timer value by a first multiplier value (e.g., multiplying the first discard timer value by 4). Alternatively or additionally, the UE can initiate a discard timer for a second type of PDU or set of PDUs at least partially based on multiplying the same discard timer value by another multiplier (e.g., multiplying the first discard timer value by two). Packets with higher priority can be subject to longer discard timers and therefore can be stored by the UE for a longer period, while packets with lower priority can be subject to shorter discard timers and therefore can be discarded by the UE more quickly. This allows packets with different priorities to be discarded at different time periods, even if these packets are on the same radio bearer. This can improve system reliability while reducing resource waste and other benefits.

[0097] As mentioned above, providing Figures 5A-5B As an example. Other examples may differ from those regarding... Figures 5A-5B The example described.

[0098] Figure 6 This is a schematic diagram illustrating an example 600 of a discard timer for protocol data unit communication according to this disclosure. UE 120 can communicate with network node 110.

[0099] As shown by reference numeral 605 in the accompanying drawings, UE 120 may receive a first discard timer value associated with a radio bearer. For example, network node 110 may send and UE 120 may receive the first discard timer value associated with a radio bearer.

[0100] As shown by reference numeral 610 in the attached figure, UE 120 can receive multiplier values. For example, network node 110 can send and UE 120 can receive multiplier values. Multiplier values ​​can be applied to a first discard timer value. Multiplier values ​​can be associated with characteristics of a PDU or set of PDUs to be transmitted via radio bearer. For example, multiplier values ​​can be associated with the importance of a PDU or set of PDUs to be transmitted via radio bearer. In some aspects, the UE can receive multiple multiplier values, wherein each multiplier value is associated with a different PDU or set of PDUs to be transmitted via radio bearer.

[0101] In some respects, the multiplier value can be a flow-level multiplier value. For example, the multiplier value can be applied to a PDU or set of PDUs that has flow-level characteristics (such as QoS characteristics). In some respects, the multiplier value can be included as a parameter in a QoS profile associated with a PDU or set of PDUs.

[0102] In some aspects, the multiplier value can be a sub-stream level multiplier value or a system level multiplier value. For example, the multiplier value can be applied to all PDUs or sets of PDUs that have sub-stream level characteristics or system level characteristics (such as the frame types included in the PDUs or PDU sets). In one example, the multiplier value can be based at least partially on a PSIHI mapping. For example, UE 120 can receive a first multiplier value for a PDU or set of PDUs with a first PSIHI configuration and a second multiplier value for a PDU or set of PDUs with a second PSIHI configuration. In another example, the multiplier value can be based at least partially on the frame type associated with the PDU or set of PDUs. For example, UE 120 can receive a first multiplier value to be applied to an I-frame associated with an application unit and a second multiplier value to be applied to a P-frame associated with an application unit.

[0103] In some aspects, a drop timer can be used for PDU sets. A drop timer (e.g., a PDU set drop timer) can be based at least in part on logical relationships between multiple streams and dependencies across packets. For example, a PDU set drop timer can be configured to use a first drop timer value for a first logical relationship between streams and / or a first dependency across packets, and can be configured to use a second drop timer value for a second logical relationship between streams and / or a second dependency across packets. A PDU set drop timer can also be based at least in part on obtaining a second drop timer value by applying a multiplier value to a first drop timer value.

[0104] In some cases, multiplier values ​​may be included in the configuration (such as static configuration). Multiplier values ​​may be at least partially based on QoS requirement normalized values. In one example, a PDU or set of PDUs with a first QoS requirement may be associated with a first multiplier value, and a PDU or set of PDUs with a second QoS requirement may be associated with a second multiplier value. In some aspects, QoS requirements and associated multiplier values ​​may be included in a QoS mapping table.

[0105] As shown by reference numeral 615 in the attached figure, UE 120 can initiate a discard timer for a PDU or a set of PDUs. For example, UE 120 can initiate a discard timer at least in part based on the PDUs or a set of PDUs received by the PDCP layer. The discard timer can have a second discard timer value corresponding to a first discard timer value multiplied by a multiplier value. In an example where the discard timer value is 1 second and the multiplier value is 2, the discard timer for a PDU or a set of PDUs can have a second discard timer value of 2 seconds (1 second multiplied by 2). Therefore, UE 120 can discard the PDU or set of PDUs two seconds after the discard timer is initiated. In some aspects, network node 110 can initiate a discard timer. The discard timer initiated by network node 110 can have the same discard timer value as the discard timer initiated by UE 120. For example, the discard timer initiated by network node 110 can have a second discard timer value corresponding to a first discard timer value multiplied by a multiplier value. In some aspects, only one of UE 120 or network node 110 can initiate a discard timer with a second discard timer value. In some respects, either UE 120 or network node 110 can initiate a drop timer with a second drop timer value.

[0106] In some aspects, UE 120 can be configured with multiple multiplier values ​​corresponding to multiple PDU or PDU set characteristics, respectively. In one example, UE 120 can be configured with a first multiplier value (e.g., 4) for PDUs or PDU sets having a first characteristic (e.g., a PDU set associated with an XR video stream), and a second multiplier value (e.g., 2) for PDUs or PDU sets having a second characteristic (such as a PDU set associated with a non-XR video stream). The discard timer value for the PDU set including the XR video stream can be 4 seconds (1 second multiplied by 4), while the discard timer value for the PDU set including the non-XR video stream can be 2 seconds (1 second multiplied by 2). UE 120 can be configured to discard PDUs associated with the XR video stream after 4 seconds, but can discard PDUs associated with the non-XR video stream only after 2 seconds, even if the PDUs associated with the XR video stream and the PDUs associated with the non-XR video stream are transmitted using the same radio bearer. This allows UE 120 to discard lower-importance packets faster than packets with higher importance. Additionally, this allows UE 120 to store higher-importance packets for longer periods instead of lower-importance packets. This increases the likelihood that higher-importance packets will be processed by UE 120 (e.g., displayed to the user of UE 120). In some aspects, the discard timer may not expire. Therefore, packets with high importance (e.g., importance greater than an importance threshold) may not be discarded by UE 120 until the packet is processed by UE 120 (e.g., displayed to the user of UE 120). For example, a second discard timer value for the discard timer could be set to an infinite value (e.g., infinite). In this case, UE 120 and / or network node 110 may not discard PDUs or PDU sets. For example, UE 120 and / or network node 110 may transmit PDUs or PDU sets via radio bearers.

[0107] As pointed out above, Figure 6 This is provided as an example. Other examples may differ from the one provided. Figure 6 The example described.

[0108] Figure 7This is a schematic diagram illustrating example 700 of a discard timer multiplier value according to this disclosure. PDU 705 and PDU 710 may be included in PDU set 715. PDU 705 and PDU 710 may be associated with XR applications. For example, PDU 705 may be associated with video for an XR application, while PDU 710 may be associated with audio for an XR application. PDU 720 may include one or more I-frames associated with a video stream. PDU 725 may include one or more P-frames associated with a video stream. Each PDU may include one or more PDUs. For example, PDU 705 may include 25 PDUs associated with video for an XR application, PDU 710 may include 15 PDUs associated with audio for an XR application, PDU 720 may include 40 I-frames for a video stream, and PDU 725 may include 40 P-frames for a video stream. PDU set 715 (e.g., both PDU 705 and PDU 710) can be associated with a multiplier value of 4. PDU 720 can be associated with a multiplier value of 2. PDU 725 can be associated with a multiplier value of 1. PDU 705 and PDU 710 can be transmitted via QoS stream 730. The first drop timer value for data radio bearer 740 (e.g., the default drop timer value) can be one second. All PDUs transmitted via QoS stream 730 can have a drop timer value of 4 seconds (1 second multiplied by 4) (displayed as "Second Drop Timer Value"). PDU 720 associated with QoS stream 735 can have a drop timer value of 2 seconds (1 second multiplied by 2) (displayed as "Third Drop Timer Value"). PDU 725 associated with QoS stream can have a drop timer value of 1 second (1 second multiplied by 1) (displayed as "Fourth Drop Timer Value"). Therefore, multiple PDUs or sets of PDUs transmitted via the same data radio bearer (DRB 740) can have different discard timer values, depending on, for example, the respective priority of the PDU or set of PDUs.

[0109] As pointed out above, Figure 7 This is provided as an example. Other examples may differ from the one provided. Figure 7 The example described.

[0110] Figure 8 This is a schematic diagram illustrating an example process 800 performed by a device of a UE, for example, in accordance with this disclosure. Example process 800 is an example in which a device for a UE (e.g., UE 120) performs operations associated with a discard timer for Protocol Data Unit communication.

[0111] like Figure 8As shown, in some aspects, process 800 may include receiving a first discard timer value associated with the radio bearer (block 810). For example, the UE (e.g., using receiving component 1002 and / or communication manager 1006, such as...) Figure 10 (As shown) can receive the first discard timer value associated with the radio bearer, as described above.

[0112] like Figure 8 As shown, in some aspects, process 800 may include receiving a multiplier value associated with a characteristic of a protocol data element or set of protocol data elements to be transmitted via a radio bearer (block 820). For example, the UE (e.g., using receiving component 1002 and / or communication manager 1006, such as...) Figure 10 As shown, it can receive multiplier values ​​associated with the characteristics of a protocol data unit or set of protocol data units to be transmitted via a radio bearer (e.g., by the UE), as described above.

[0113] like Figure 8 Further shown, in some aspects, process 800 may include initiating a discard timer for a protocol data element or set of protocol data elements, the discard timer having a second discard timer value corresponding to a first discard timer value multiplied by a multiplier value (box 830). For example, the UE (e.g., using communication manager 1006, such as...) Figure 10 As shown, a discard timer can be initiated for a protocol data unit or the set of protocol data units, the discard timer having a second discard timer value corresponding to a first discard timer value multiplied by a multiplier value, as described above.

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

[0115] In the first aspect, process 800 includes discarding protocol data units or the set of protocol data units at least in part based on the expiration of a discard timer.

[0116] In the second aspect, either alone or in combination with the first aspect, process 800 includes initiating another discard timer for another protocol data unit or protocol data unit set associated with the same radio bearer as the protocol data unit or protocol data unit set, the other discard timer having a third discard timer value that is different from the second discard timer value and corresponds to the first discard timer value multiplied by another multiplier value.

[0117] In the third aspect, initiating the drop timer, either alone or in combination with one or more of the first and second aspects, includes initiating the drop timer based at least in part on the protocol data unit or the set of protocol data units arriving at the packet data convergence protocol layer.

[0118] In the fourth aspect, receiving the multiplier value, either alone or in combination with one or more of the first to third aspects, includes receiving a Quality of Service profile that includes the multiplier value corresponding to the protocol data unit or the set of protocol data units.

[0119] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the multiplier value is applied to all protocol data units or sets of protocol data units having the aforementioned characteristics.

[0120] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, each of the plurality of protocol data unit sets is associated with a protocol data unit set integration processing instruction indicating the multiplier value to be used for the protocol data unit set.

[0121] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, a first protocol data unit set in a plurality of protocol data unit sets is associated with a first multiplier value, and a second protocol data unit set in the plurality of protocol data unit sets is associated with a second multiplier value that is different from the first multiplier value.

[0122] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first protocol data unit set includes one or more intra-coded frames associated with the application unit, and the second protocol data unit set includes one or more predicted frames associated with the application unit.

[0123] In the ninth aspect, receiving the multiplier value, either alone or in combination with one or more of the first to eighth aspects, includes receiving a plurality of multiplier values ​​and a plurality of corresponding service flow quality values, and the feature associated with the protocol data unit or the set of protocol data units includes the service flow quality associated with the protocol data unit or the set of protocol data units.

[0124] In the tenth aspect, either alone or in combination with one or more aspects from the first to the ninth aspect, the plurality of multiplier values ​​and the plurality of corresponding service flow quality values ​​are included in a service quality mapping table, which maps each service flow quality value to one or more of the plurality of multiplier values.

[0125] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the protocol data unit set includes multiple protocol data units associated with a single application unit.

[0126] Although Figure 8 An example box of process 800 is shown, but in some aspects, process 800 may include... Figure 8 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes of process 800 may be executed in parallel.

[0127] Figure 9 This is a schematic diagram illustrating an example process 900 performed by a device, such as a network node, according to the present disclosure. Example process 900 is an example in which a device for a network node (e.g., network node 110) performs operations associated with a discard timer for protocol data unit communication.

[0128] like Figure 9 As shown, in some aspects, process 900 may include transmitting a first discard timer value associated with the radio bearer (box 910). For example, network nodes (e.g., using transmitting component 1104 and / or communication manager 1106, such as...) Figure 11 (As shown) can send the first discard timer value associated with the radio bearer, as described above.

[0129] like Figure 9 As shown, in some aspects, process 900 may include transmitting a multiplier value associated with the characteristics of a protocol data element or set of protocol data elements to be transmitted via a radio bearer (box 920). For example, network nodes (e.g., using transmitting component 1104 and / or communication manager 1106, such as...) Figure 11 As shown, a multiplier value can be sent that is associated with the characteristics of a protocol data unit or set of protocol data units to be transmitted via a radio bearer (e.g., by a network node), as described above.

[0130] like Figure 9 Further shown, in some aspects, process 900 may include initiating a discard timer for a protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to a first discard timer value multiplied by a multiplier value (box 930). For example, a network node (e.g., using a communication manager 1106, such as...) Figure 11 As shown, a discard timer can be initiated for a protocol data unit or a set of protocol data units, the discard timer having a second discard timer value corresponding to a first discard timer value multiplied by a multiplier value, as described above.

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

[0132] In the first aspect, process 900 includes discarding protocol data units or the set of protocol data units at least in part based on the expiration of a discard timer.

[0133] In the second aspect, either alone or in combination with the first aspect, process 900 includes initiating another discard timer for another protocol data unit or protocol data unit set associated with the same radio bearer as the protocol data unit or protocol data unit set, the other discard timer having a third discard timer value that is different from the second discard timer value and corresponds to the first discard timer value multiplied by another multiplier value.

[0134] In the third aspect, initiating the drop timer, either alone or in combination with one or more of the first and second aspects, includes initiating the drop timer based at least in part on the protocol data unit or the set of protocol data units arriving at the packet data convergence protocol layer.

[0135] In the fourth aspect, sending the multiplier value, either alone or in combination with one or more of the first to third aspects, includes sending a Quality of Service profile that includes the multiplier value corresponding to the protocol data unit or the set of protocol data units.

[0136] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the multiplier value is applied to all protocol data units or sets of protocol data units having the aforementioned characteristics.

[0137] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, each of the plurality of protocol data unit sets is associated with a protocol data unit set integration processing instruction indicating the multiplier value to be used for the protocol data unit set.

[0138] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, a first protocol data unit set in a plurality of protocol data unit sets is associated with a first multiplier value, and a second protocol data unit set in the plurality of protocol data unit sets is associated with a second multiplier value that is different from the first multiplier value.

[0139] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first protocol data unit set includes one or more intra-coded frames associated with the application unit, and the second protocol data unit set includes one or more predicted frames associated with the application unit.

[0140] In the ninth aspect, sending the multiplier value, either alone or in combination with one or more of the first to eighth aspects, includes sending a plurality of multiplier values ​​and a plurality of corresponding service flow quality values, and the feature associated with the protocol data unit or the set of protocol data units includes the service flow quality associated with the protocol data unit or the set of protocol data units.

[0141] In the tenth aspect, either alone or in combination with one or more aspects from the first to the ninth aspect, the plurality of multiplier values ​​and the plurality of corresponding service flow quality values ​​are included in a service quality mapping table, which maps each service flow quality value to one or more of the plurality of multiplier values.

[0142] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the protocol data unit set includes multiple protocol data units associated with a single application unit.

[0143] Although Figure 9 An example box of process 900 is shown, but in some aspects, process 900 may include... Figure 9 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 900 may be executed in parallel.

[0144] Figure 10 This is a diagram of an example device 1000 for wireless communication according to the present disclosure. Device 1000 may be a UE, or a UE may include device 1000. In some aspects, device 1000 includes a receiving component 1002, a transmitting component 1004, and / or a communication manager 1006, which can 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 combined with... Figure 1 The communication manager 140 is described above. As shown, the device 1000 can use the receiving component 1002 and the transmitting component 1004 to communicate with another device 1008, such as a UE or a network node (such as a CU, DU, RU or base station).

[0145] In some respects, device 1000 can be configured to perform the functions described herein. Figure 6-7One or more operations described herein. Alternatively or concurrently, the apparatus 1000 may be configured to perform one or more processes described herein, such as... Figure 8 The process 800. In some aspects, the device 1000 and / or Figure 10 One or more components shown may include combinations Figure 2 One or more components of the UE as described. Alternatively or alternatively, Figure 10 One or more components shown can be combined Figure 2 Implemented within one or more of the described components. Alternatively, one or more components in the set of components may be implemented at least partially as software stored in 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 that component.

[0146] Receiver 1002 may receive communications from device 1008, such as reference signals, control information, data communications, or combinations thereof. Receiver 1002 may provide the received communications to one or more other components of device 1000. In some aspects, receiver 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signal to one or more other components of device 1000. In some aspects, receiver 1002 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

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

[0148] The communication manager 1006 can support the operation of the receiving component 1002 and / or the transmitting component 1004. For example, the communication manager 1006 can receive information associated with configuring the receiving component 1002 to receive communication and / or the transmitting component 1004 to transmit communication. Alternatively, the communication manager 1006 can generate and / or provide control information to the receiving component 1002 and / or the transmitting component 1004 to control the reception and / or transmission of communication.

[0149] The receiving component 1002 can receive a first discard timer value associated with the radio bearer. The receiving component 1002 can also receive a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. The communication manager 1006 can initiate a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0150] The communication manager 1006 can discard a protocol data unit or set of protocol data units, at least in part, based on the expiration of a discard timer. The communication manager 1006 can initiate another discard timer for another protocol data unit or set of protocol data units associated with the same radio bearer as the protocol data unit or set of protocol data units, the other discard timer having a third discard timer value that is different from the second discard timer value and corresponds to the first discard timer value multiplied by another multiplier value.

[0151] Figure 10 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 10 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, in Figure 10 The two or more components shown can be implemented within a single component, or in Figure 10 The single component shown can be implemented as multiple distributed components. Alternatively, in Figure 10 The set (one or more) components shown can perform actions described by [the following]: Figure 10 The other set of components shown performs one or more functions.

[0152] Figure 11This is a diagram of an example device 1100 for wireless communication according to the present disclosure. Device 1100 may be a network node, or a network node may include device 1100. In some aspects, device 1100 includes a receiving component 1102, a transmitting component 1104, and / or a communication manager 1106, which can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1106 is combined with... Figure 1 The communication manager 150 is described above. As shown, the device 1100 can communicate with another device 1108, such as a UE or a network node (such as a CU, DU, RU or base station), using the receiving component 1102 and the transmitting component 1104.

[0153] In some respects, device 1100 can be configured to perform the functions described herein. Figure 6-7 One or more operations described herein. Alternatively or concurrently, device 1100 may be configured to perform one or more processes described herein, such as Figure 9 The process is 900. In some aspects, Figure 11 The device 1100 and / or one or more components shown may include a combination Figure 2 One or more components of the described network node. Alternatively, Figure 11 One or more components shown can be combined Figure 2 The description is implemented within one or more components. Alternatively, one or more components in the set of components may be implemented at least partially as software stored in 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 that component.

[0154] Receiver 1102 may receive communications from device 1108, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signal to one or more other components of device 1100. In some aspects, receiver 1102 may include combinations of... Figure 2The described network node includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof. In some aspects, receiver component 1102 and / or transmitter component 1104 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals to device 1100 via one or more communication links (such as backhaul links, midhaul links, and / or forward links).

[0155] Transmitting component 1104 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1108. In some aspects, one or more other components of device 1100 can generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1108. In some aspects, transmitting component 1104 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signal to device 1108. In some aspects, transmitting component 1104 can include combinations of... Figure 2 The described network node includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1104 may be co-located with the receive component 1102 in a transceiver.

[0156] The communication manager 1106 can support the operation of the receiving component 1102 and / or the transmitting component 1104. For example, the communication manager 1106 can receive information associated with configuring the receiving component 1102 to receive communication and / or the transmitting component 1104 to transmit communication. Alternatively, the communication manager 1106 can generate and / or provide control information to the receiving component 1102 and / or the transmitting component 1104 to control the reception and / or transmission of communication.

[0157] Transmitting component 1104 can transmit a first discard timer value associated with the radio bearer. Transmitting component 1104 can also transmit a multiplier value associated with a feature of a protocol data unit or set of protocol data units to be transmitted via the radio bearer. Communication manager 1106 can initiate a discard timer for the protocol data unit or set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0158] The communication manager 1106 can discard a protocol data unit or set of protocol data units, at least in part, based on the expiration of a discard timer. The communication manager 1106 can initiate another discard timer for another protocol data unit or set of protocol data units associated with the same radio bearer as the protocol data unit or set of protocol data units, the other discard timer having a third discard timer value that is different from the second discard timer value and corresponds to the first discard timer value multiplied by another multiplier value.

[0159] exist Figure 11 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 11 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, in Figure 11 The two or more components shown can be implemented within a single component, or in Figure 11 The single component shown can be implemented as multiple distributed components. Alternatively, in Figure 11 The set (one or more) components shown can perform actions described by [the following]: Figure 11 The other set of components shown performs one or more functions.

[0160] The following provides an overview of some aspects of this disclosure:

[0161] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a first discard timer value associated with a radio bearer; receiving a multiplier value associated with a feature of a protocol data unit or protocol data set to be transmitted via the radio bearer; and initiating a discard timer for the protocol data unit or the protocol data set, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0162] Aspect 2: The method according to aspect 1 further includes: discarding the protocol data unit or the set of protocol data units at least in part based on the expiration of the discard timer.

[0163] Aspect 3: The method according to any one of Aspects 1-2 further includes: initiating another discard timer for another protocol data unit or protocol data unit set associated with the same radio bearer as the protocol data unit or the protocol data unit set, the other discard timer having a third discard timer value that is different from the second discard timer value and corresponds to the first discard timer value multiplied by another multiplier value.

[0164] Aspect 4: The method according to any of Aspects 1-3, wherein initiating the drop timer includes initiating the drop timer at least in part based on the protocol data unit or the set of protocol data units arriving at the packet data convergence protocol layer.

[0165] Aspect 5: The method according to any of Aspects 1-4, wherein receiving the multiplier value includes receiving a Quality of Service profile including the multiplier value corresponding to the Protocol Data Unit or the set of Protocol Data Units.

[0166] Aspect 6: The method according to any of aspects 1-5, wherein the multiplier value is applied to all protocol data units or sets of protocol data units having the described feature.

[0167] Aspect 7: According to the method of aspect 6, wherein the feature is associated with the importance of the protocol data unit or the importance of the protocol data unit set.

[0168] Aspect 8: According to the method of aspect 6, each of the plurality of protocol data unit sets is associated with a protocol data unit set integration processing instruction indicating the multiplier value to be used for the protocol data unit set.

[0169] Aspect 9: According to the method of aspect 6, a first protocol data unit set in a plurality of protocol data unit sets is associated with a first multiplier value, and a second protocol data unit set in the plurality of protocol data unit sets is associated with a second multiplier value different from the first multiplier value.

[0170] Aspect 10: According to the method of aspect 9, wherein the first protocol data unit set includes one or more intra-coded frames associated with the application unit, and the second protocol data unit set includes one or more predicted frames associated with the application unit.

[0171] Aspect 11: The method according to any of aspects 1-10, wherein receiving the multiplier value includes receiving a plurality of multiplier values ​​and a plurality of corresponding service flow quality values, and wherein the feature associated with the protocol data unit or the set of protocol data units includes the service flow quality associated with the protocol data unit or the set of protocol data units.

[0172] Aspect 12: According to the method of aspect 11, wherein the plurality of multiplier values ​​and the plurality of corresponding service flow quality values ​​are included in a service quality mapping table, the service quality mapping table mapping each service flow quality value to one or more multiplier values ​​among the plurality of multiplier values.

[0173] Aspect 13: An aspect according to any of aspects 1-12, wherein the protocol data unit set comprises a plurality of protocol data units associated with a single application unit.

[0174] Aspect 14: The method according to any of aspects 1-13, wherein the feature of the protocol data unit or the set of protocol data units is the feature of the set of protocol data units, and wherein initiating the discard timer for the protocol data unit or the set of protocol data units includes initiating the discard timer for the set of protocol data units.

[0175] Aspect 15: A method of wireless communication performed by a network node, comprising: transmitting a first discard timer value associated with a radio bearer; transmitting a multiplier value associated with a feature of a protocol data unit or protocol data set to be transmitted via the radio bearer; and initiating a discard timer for the protocol data unit or the protocol data set, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

[0176] Aspect 16: The method according to aspect 15 further includes: discarding the protocol data unit or the set of protocol data units at least in part based on the expiration of the discard timer.

[0177] Aspect 17: The method according to any of aspects 15-16 further includes: initiating another discard timer for another protocol data unit or set of protocol data units associated with the same radio bearer as the protocol data unit or the set of protocol data units, the other discard timer having a third discard timer value that is different from the second discard timer value and corresponds to the first discard timer value multiplied by another multiplier value.

[0178] Aspect 18: The method according to any of aspects 15-17, wherein initiating the drop timer includes initiating the drop timer at least in part based on the protocol data unit or the set of protocol data units arriving at the packet data convergence protocol layer.

[0179] Aspect 19: The method according to any of aspects 15-18, wherein sending the multiplier value includes sending a quality of service profile including the multiplier value corresponding to the protocol data unit or the set of protocol data units.

[0180] Aspect 20: The method according to any of aspects 15-19, wherein the multiplier value is applied to all protocol data units or sets of protocol data units having the said feature.

[0181] Aspect 21: According to the method of aspect 20, wherein the feature is associated with the importance of the protocol data unit or the importance of the protocol data unit set.

[0182] Aspect 22: According to the method of aspect 20, each of the plurality of protocol data unit sets is associated with a protocol data unit set integration processing instruction indicating the multiplier value to be used for the protocol data unit set.

[0183] Aspect 23: According to the method of aspect 20, a first protocol data unit set in a plurality of protocol data unit sets is associated with a first multiplier value, and a second protocol data unit set in the plurality of protocol data unit sets is associated with a second multiplier value different from the first multiplier value.

[0184] Aspect 24: According to the method of aspect 23, wherein the first protocol data unit set includes one or more intra-coded frames associated with the application unit, and the second protocol data unit set includes one or more predicted frames associated with the application unit.

[0185] Aspect 25: The method according to any of aspects 15-24, wherein sending the multiplier value includes sending a plurality of multiplier values ​​and a plurality of corresponding service flow quality values, and wherein the feature associated with the protocol data unit or the set of protocol data units includes the service flow quality associated with the protocol data unit or the set of protocol data units.

[0186] Aspect 26: The method according to aspect 25, wherein the plurality of multiplier values ​​and the plurality of corresponding service flow quality values ​​are included in a service quality mapping table, the service quality mapping table mapping each service flow quality value to one or more multiplier values ​​among the plurality of multiplier values.

[0187] Aspect 27: An aspect according to any of aspects 15-26, wherein the protocol data unit set comprises a plurality of protocol data units associated with a single application unit.

[0188] Aspect 28: The method according to any of aspects 15-27, wherein the feature of the protocol data unit or the set of protocol data units is the feature of the set of protocol data units, and wherein initiating the discard timer for the protocol data unit or the set of protocol data units includes initiating the discard timer for the set of protocol data units.

[0189] Aspect 29: 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 a method according to one or more of aspects 1-28.

[0190] Aspect 30: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform one or more of the methods of aspects 1-28.

[0191] Aspect 31: An apparatus for wireless communication, comprising at least one unit for performing one or more of the methods of aspects 1-28.

[0192] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform one or more of the methods of aspects 1-28.

[0193] Aspect 33: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 1-28.

[0194] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or modifications and variations may be derived from practice in the aspects.

[0195] Further disclosure is included in the appendix. The appendix is ​​provided by way of example only and will be considered part of the specification. Definitions, illustrations, or other descriptions in the appendix do not supersede or cover similar information included in the detailed description or drawings. Furthermore, the appendix is ​​not intended to limit the disclosure of possible aspects.

[0196] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented as hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be interpreted broadly as "at least partially based on". As used herein, depending on the context, "meeting a threshold" can mean a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, or not equal to a threshold, etc. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c.

[0197] Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and can be used interchangeably with “one or more”. Furthermore, as used herein, the article “the” is intended to include one or more items mentioned in combination with the article “the” and can be used interchangeably with “the one or more”. Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and can be used interchangeably with “one or more”. If only one item is desired, the phrase “only one” or similar terms will be used. Furthermore, as used herein, the terms “has,” “have,” “having,” and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., “having” element A can also have B). Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and can be used interchangeably with “and / or” unless otherwise expressly stated (e.g., if used in combination with “any” or “only one of”).

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

[0199] Hardware and data processing apparatuses for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, a particular process or method may be executed by circuitry specific to a given function.

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

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

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

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

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

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

Claims

1. An apparatus for wireless communication, comprising: One or more memory units; as well as One or more processors coupled to the one or more memories, the one or more processors being configured individually or collectively to: Receive the first discard timer value associated with the radio bearer; Receive multiplier values ​​associated with the characteristics of a protocol data unit or set of protocol data units to be transmitted via the radio bearer; as well as Initiate a discard timer for the protocol data unit or the set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

2. The apparatus according to claim 1, wherein, The one or more processors are also configured to discard the protocol data unit or the set of protocol data units at least in part based on the expiration of the discard timer.

3. The apparatus according to claim 1, wherein, The one or more processors are also configured to initiate another drop timer for another protocol data unit or protocol data unit set associated with the same radio bearer as the protocol data unit or the protocol data unit set, the other drop timer having a third drop timer value that is different from the second drop timer value and corresponds to the first drop timer value multiplied by another multiplier value.

4. The apparatus according to claim 1, wherein, In order to initiate the drop timer, the one or more processors are configured to initiate the drop timer at least in part based on the protocol data unit or the set of protocol data units arriving at the packet data convergence protocol layer of the device.

5. The apparatus according to claim 1, wherein, In order to receive the multiplier value, the one or more processors are configured to receive a Quality of Service profile including the multiplier value corresponding to the Protocol Data Unit or the set of Protocol Data Units.

6. The apparatus according to claim 1, wherein, The multiplier value is applied to all protocol data units or sets of protocol data units that have the aforementioned characteristics.

7. The apparatus according to claim 6, wherein, The feature is associated with the importance of the protocol data unit or the importance of the protocol data unit set.

8. The apparatus according to claim 6, wherein, Each of the multiple protocol data unit sets is associated with a protocol data unit set integration processing instruction that indicates the multiplier value to be used for the protocol data unit set.

9. The apparatus according to claim 6, wherein, A first protocol data unit set in a plurality of protocol data unit sets is associated with a first multiplier value, and a second protocol data unit set in the plurality of protocol data unit sets is associated with a second multiplier value that is different from the first multiplier value.

10. The apparatus according to claim 9, wherein, The first protocol data unit set includes one or more intra-coded frames associated with the application unit, and the second protocol data unit set includes one or more predicted frames associated with the application unit.

11. The apparatus according to claim 1, wherein, Receiving the multiplier value includes receiving multiple multiplier values ​​and multiple corresponding service flow quality values, wherein the feature associated with the protocol data unit or the set of protocol data units includes the service flow quality associated with the protocol data unit or the set of protocol data units.

12. The apparatus according to claim 11, wherein, The plurality of multiplier values ​​and the plurality of corresponding service flow quality values ​​are included in a service quality mapping table, which maps each service flow quality value to one or more multiplier values ​​among the plurality of multiplier values.

13. The apparatus according to claim 1, wherein, The protocol data unit set includes multiple protocol data units associated with a single application unit.

14. The apparatus according to claim 1, wherein, The feature of the protocol data unit or the set of protocol data units is the feature of the set of protocol data units, and wherein, in order to initiate the discard timer for the protocol data unit or the set of protocol data units, the one or more processors are configured to initiate the discard timer for the set of protocol data units.

15. An apparatus for wireless communication, comprising: One or more memory units; as well as One or more processors coupled to the one or more memories, the one or more processors being configured individually or collectively to: Send the first discard timer value associated with the radio bearer; Transmit multiplier values ​​associated with the characteristics of the protocol data unit or set of protocol data units to be transmitted via the radio bearer; as well as Initiate a discard timer for the protocol data unit or the set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

16. The apparatus according to claim 15, wherein, The one or more processors are also configured to discard the protocol data unit or the set of protocol data units at least in part based on the expiration of the discard timer.

17. The apparatus according to claim 15, wherein, The one or more processors are also configured to initiate another drop timer for another protocol data unit or protocol data unit set associated with the same radio bearer as the protocol data unit or the protocol data unit set, the other drop timer having a third drop timer value that is different from the second drop timer value and corresponds to the first drop timer value multiplied by another multiplier value.

18. The apparatus according to claim 15, wherein, In order to initiate the drop timer, the one or more processors are configured to initiate the drop timer at least in part based on the protocol data unit or the set of protocol data units arriving at the packet data convergence protocol layer of the device.

19. The apparatus according to claim 15, wherein, In order to send the multiplier value, the one or more processors are configured to send a Quality of Service (QoS) profile including the multiplier value corresponding to the Protocol Data Unit (PDU) or the PDU set.

20. The apparatus according to claim 15, wherein, The multiplier value is applied to all protocol data units or sets of protocol data units that have the aforementioned characteristics.

21. The apparatus according to claim 20, wherein, The feature is associated with the importance of the protocol data unit or the importance of the protocol data unit set.

22. The apparatus according to claim 20, wherein, Each of the multiple protocol data unit sets is associated with a protocol data unit set integration processing instruction that indicates the multiplier value to be used for the protocol data unit set.

23. The apparatus according to claim 20, wherein, A first protocol data unit set in a plurality of protocol data unit sets is associated with a first multiplier value, and a second protocol data unit set in the plurality of protocol data unit sets is associated with a second multiplier value that is different from the first multiplier value.

24. The apparatus according to claim 23, wherein, The first protocol data unit set includes one or more intra-coded frames associated with the application unit, and the second protocol data unit set includes one or more predicted frames associated with the application unit.

25. The apparatus according to claim 15, wherein, Sending the multiplier value includes sending multiple multiplier values ​​and multiple corresponding service flow quality values, wherein the feature associated with the protocol data unit or the set of protocol data units includes the service flow quality associated with the protocol data unit or the set of protocol data units.

26. The apparatus according to claim 25, wherein, The plurality of multiplier values ​​and the plurality of corresponding service flow quality values ​​are included in a service quality mapping table, which maps each service flow quality value to one or more multiplier values ​​among the plurality of multiplier values.

27. The apparatus according to claim 15, wherein, The protocol data unit set includes multiple protocol data units associated with a single application unit.

28. The apparatus according to claim 15, wherein, The feature of the protocol data unit or the set of protocol data units is the feature of the set of protocol data units, and wherein, in order to initiate the discard timer for the protocol data unit or the set of protocol data units, the one or more processors are configured to initiate the discard timer for the set of protocol data units.

29. A method for wireless communication performed by a user equipment (UE), comprising: Receive the first discard timer value associated with the radio bearer; Receive multiplier values ​​associated with the characteristics of a protocol data unit or set of protocol data units to be transmitted via the radio bearer; as well as Initiate a discard timer for the protocol data unit or the set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

30. A method for wireless communication performed by a network node, comprising: Send the first discard timer value associated with the radio bearer; Transmit multiplier values ​​associated with the characteristics of the protocol data unit or set of protocol data units to be transmitted via the radio bearer; as well as Initiate a discard timer for the protocol data unit or the set of protocol data units, the discard timer having a second discard timer value corresponding to the first discard timer value multiplied by the multiplier value.

Images