Methods and apparatuses for discarding protocol data unit sets

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for discarding protocol data unit sets. A UE 102 receives (310), from a network entity (104), a first indicator of a PSI to enable discarding a PDU Set during a discard cycle having a first discard cycle time period and a second discard cycle time period. The UE (102) discards (314a), after expiration of a first discard time period, a first PDU Set from a transmit buffer during the first discard cycle time period. The UE (102) discards (314b), after expiration of a legacy / second discard time period that is longer than the first discard time period, a second PDU Set from the transmit buffer during the second discard cycle time period.

Description

METHODS AND APPARATUSES FOR DISCARDING PROTOCOL DATA UNIT SETSCROSS REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 527,923, filed on July 20, 2023, and U.S. Provisional Application Serial No. 63 / 591,708, filed on October 19, 2023, both entitled “Methods and Apparatuses for Discarding Protocol Data Unit Sets’", and which are both expressly incorporated by reference herein in their entireties.TECHNICAL FIELD

[0002] The present disclosure relates generally to wireless communication, and more particularly, to methods and apparatuses for discarding protocol data unit (PDU) Sets.BACKGROUND

[0003] The Third Generation Partnership Project (3 GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5GNR). An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), a user equipment (5G UE), etc. The 5G NR architecture seeks to provide increased data rates, decreased latency, and / or increased capacity compared to prior generation cellular communication systems.

[0004] Wireless communication systems, in general, provide various telecommunication services (e.g., telephony, video, data, messaging, etc.) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in mobile broadband continue the progression of such wireless communication technologies.BRIEF SUMMARY

[0005] A user equipment (UE) software application queues data in a transmit buffer for transmission to a network entity. The data is organized into protocol data unit (PDU) Sets. A PDU Set includes one or more PDUs carrying a payload of one unit of information generated at the application level (e.g., a video frame or video slice). In some implementations, all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, where somePDUs are missing, the application layer can still recover parts or all of the information unit.

[0006] A PDU Set containing Multi-modal Data may be called a multi-modal PDU Set. A multi-modal PDU Set refers to a PDU Set including different data types (e.g., video data, audio data, pose data, etc.) that are closely related and require application coordination for a multi-modal application (e.g., extended reality (XR) application). Multi-modal Data includes the input data from different kinds of devices / sensors and / or the output data to different kinds of destinations (e.g., one or more UEs) required for the same task or application. Multi-modal Data includes more than one Single-modal Data, and there is a strong dependency among each Single-modal Data.

[0007] Single-modal Data can be seen as one type of data (e.g., video data, audio data, pose data, etc.). A single modal PDU Set refers to a PDU Set including Single-modal Data of the same data type (e.g., only video data, only audio data, only haptic data, only pose data, etc.) associated with the same application (e.g., XR application).

[0008] Whether multi-modal or single-modal, the PDUs of a PDU Set are transmitted within the same quality of service (QoS) flow. The PDU Sets may be classified according to a PDU Set importance (PSI) level, which identifies the relative importance / priority of a PDU Set compared to other PDU Sets within a QoS flow. A radio access network (RAN) may use PSI threshold for PDU Set packet discarding in the presence of network congestion. A PDU Set Information and Identification (e.g., dynamic information for downlink (DL) provided via the user plane in a general packet radio system tunnelling protocol user plane (GTP-U) header) includes a PDU Set Sequence Number (SN). a PDU Set Size in bytes, a PDU SN within a PDU Set. and / or an indication of an End PDU of the PDU Set.

[0009] When the network entity PDU Set packet discarding procedure indicates a PSI threshold that is higher than needed to alleviate network congestion to a target congestion level, the number of discarded PDU Sets causes the network channel to be underutilized. On the other hand, when the network entity indicates a PSI threshold that is lower than needed to alleviate the network congestion to the target congestion level, the number of discarded PDU Sets is insufficient to alleviate the network congestion to the target congestion level.

[0010] To address this problem (and others), the network entity implements network congestion control techniques that leverage UE information and additional controls (e.g., PDU Set discard timer, PDU Set discard disable message, etc.). For example,when the total data volume of PDU Sets associated with UEs served by the network entity exceeds a threshold, the network entity configures the UE(s) to discard certain PDU Sets to reduce the network congestion. The network entity configures the UE(s) to discard PDU Sets according to an importance level (e.g., PSI) of the PDU Set.

[0011] In some aspects, the network entity indicates a PSI threshold to the UE and an indicator to discard PDU Sets according to the PSI threshold. The UE discards the PDU Sets in the transmit buffer that satisfies a PSI threshold criterion. In some aspects, the UE discards the PDU Sets based on a PDU Set type. The PDU Set type indicates parameters of the PDU Set including data rate and latency. The PDU Set type may be determined by the software application. Additionally or alternatively, the network entity may indicate a discard time period to the UE. During the discard time period, the UE may discard PDU Sets that satisfy the PSI threshold criterion. Additionally or alternatively, the UE may discard PDU Sets that satisfy the PSI threshold criterion until the UE receives a second indicator to refrain from discarding PDU Sets.

[0012] In order to assist the network entity in determining the PSI threshold criterion, the UE transmits a PDU Set parameter to the network entity. A PDU Set parameter indicates an amount of data in the transmit buffer that stores the PDU Set or a data rate for the PDU Set. The data rate may be determined by the application (e.g., XR application). The UE transmits, to the network entity, the data rate via RRC signaling (e.g., UEAssistancelnformation). Additionally or alternatively, the UE may dynamically determine the data rate at a protocol layer by dividing the total data volume from the PDU Sets by a time penod over which the data arrives from the application (or upper layers). The time period depends on the PDU Set type. Other types of PDU Set parameters include: (a) data volume information for a PSI for a logical channel or logical channel group, or (b) data volume information of urgent data in a transmit buffer for a logical channel or a logical channel group whose remaining time for delivery satisfies a threshold criterion.

[0013] In some aspects, the network entity configures the UE with an On / Off discard cycle period for discarding a PDU Set according to a first discard time period and / or a legacy discard time period. The UE receives On / Off discard cycle parameters (e.g.. periodicity) from the network entity indicating a first discard cycle time period (e.g.. On period) and a second discard cycle time period (e.g., Off period). When the UE receives the first PDU Set into a transmit buffer during the first discard cycle timeperiod (e.g., On period), the UE discards the first PDU Set when the first discard time period expires. When the UE receives a second PDU Set into the transmit buffer during the second discard cycle time period (e.g., Off period), the UE refrains from discarding the second PDU Set based on expiration of the first discard time period. Instead, the UE discards the second PDU Set after expiration of a legacy discard time period (e.g., 3GPP TS 38.323 discardTimer) that is longer than the first discard time period. In this manner, PDU Sets arriving in the transmit buffer during the Off period have an increased probability of being transmitted by the UE as compared to PDU Sets arriving in the transmit buffer during the On period.

[0014] According to some aspects, a UE receives, from a network entity, a first indicator of a PSI to enable discarding a PDU Set during a discard cycle having a first discard cycle time period and a second discard cycle time period. The UE discards, a first PDU Set received in a transmit buffer during the first discard cycle time period, after expiration of a first discard time period (if the first PDU Set is still in the transmit buffer). The UE discards, after expiration of a legacy discard time period that is longer than the first discard time period, a second PDU Set received in the transmit buffer during the second discard cycle time period.

[0015] According to some aspects, a network entity receives, from a UE. a first report indicating a PDU Set parameter for a PSI, the PSI identifying a relative importance of a PDU Set. The network entity transmits, to the UE based on the report and a network congestion level, a first indicator of a PSI to enable PDU Set discarding according to the PSI. during a discard cycle having a first discard cycle time period and a second discard cycle time penod.

[0016] Technical benefits of the present disclosure include assisting the network entity in alleviating network congestion by the UE providing the network entity with PDU Set type(s) for discarding PDU Sets. Further benefits include the network entity and / or the UE controlling the enabling / disabling of PDU Set discarding using the examples described with reference to FIGs. 3-16.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG. 1 illustrates a diagram of a wireless communications system that includes a plurality of user equipments (UEs) and network entities in communication over one or more cells according to an embodiment.

[0018] FIG. 2A illustrates a diagram of a wireless communications system that includes a plurality of UEs and a network entity in communication over access links according to an embodiment.

[0019] FIG. 2B is a diagram illustrating a timeline for UE PDU Set discarding based on a discard cycle having a first discard cycle time period and a second discard cycle time period according to an embodiment.

[0020] FIG. 3A is a signaling diagram illustrating communications between a UE and a network entity for discarding PDU Set(s) according to an embodiment that supports PDU Set Discard disabling.

[0021] FIG. 3B is a signaling diagram illustrating communications between a UE and a network entity for discarding PDU Set(s) based on a discard cycle having a first discard cycle time period and a second discard cycle time period.

[0022] FIG. 4 is a signaling diagram illustrating communications between a UE and a network entity for discarding PDU Set(s) according to another embodiment with a PDU Discard Time Period.

[0023] FIG. 5 is a signaling diagram illustrating communications between a UE and a network entity for discarding PDU Set(s) according to another embodiment that supports the embodiments of both FIG. 3 A and FIG. 4.

[0024] FIG. 6 is a signaling diagram illustrating communications between a UE and a network entity for discarding PDU Set(s) according to another embodiment with multiple thresholds and multiple PDU Discard Time Periods.

[0025] FIG. 7 is a signaling diagram illustrating communications between a UE and a network entity for discarding PDU Set(s) according to another embodiment with multiple PDU Discard Time Periods.

[0026] FIG. 8A is a flowchart of a method of wireless communication at a UE according to an embodiment.

[0027] FIG. 8B is a flowchart of a method of UE PDU Set discarding based on a discard cycle having a first discard cycle time period and a second discard cycle time period according to an embodiment.

[0028] FIG. 9 is a flowchart of a method of wireless communication at a UE according to another embodiment with a PDU Set Discard Timer.

[0029] FIG. 10 is a flowchart of a method of wireless communication at a UE according to another embodiment with multiple PDU Set Discard Timers.

[0030] FIG. 11 is a flowchart of a method of wireless communication at a network entity according to an embodiment.

[0031] FIG. 12 is a flowchart of a method of wireless communication at a UE according to another embodiment.

[0032] FIG. 13 is a flowchart of a method of wireless communication at a network entity according to another embodiment.

[0033] FIG. 14 is a diagram illustrating a hardware implementation for an example UE apparatus according to some embodiments.

[0034] FIG. 15 is a diagram illustrating a hardware implementation for one or more example network entities according to some embodiments.

[0035] In FIGs. 1-15 like reference numbers refer to like actions.DETAILED DESCRIPTION

[0036] FIG. 1 illustrates a diagram 100 of a wireless communications system associated with a plurality of cells 190. The wireless communications system includes user equipments (UEs) 102 and base stations / network entities 104. Some base stations may include an aggregated base station architecture and other base stations may include a disaggregated base station architecture. The aggregated base station architecture utilizes a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. A disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, a CU 1 10 is implemented within a RAN node, and one or more DUs 108 may be co-located with the CU 110, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs 108 may be implemented to communicate with one or more RUs 106. Any of the RU 106, the DU 108 and the CU 110 can be implemented as virtual units, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). The base station / network entity 104 (e.g., an aggregated base station or disaggregated units of the base station, such as the RU 106 or the DU 108), may be referred to as a transmission reception point (TRP).

[0037] Operations of the base station 104 and / or network designs may be based on aggregation characteristics of base station functionality. For example, disaggregated base station architectures are utilized in an integrated access backhaul (IAB) network,an open-radio access network (O-RAN) network, or a virtualized radio access network (vRAN), which may also be referred to a cloud radio access network (C- RAN). Disaggregation may include distributing functionality across the two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility' in network designs. The various units of the disaggregated base station architecture, or the disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. For example, the base stations 104d, 104e and / or the RUs 106a, 106b, 106c, 106d may communicate with the UEs 102a, 102b, 102c. 102d, and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In examples, multiple RUs 106 and / or base stations 104 may simultaneously serve the UEs 102, such as by intracell and / or inter-cell access links between the UEs 102 and the RUs 106 / base stations 104.

[0038] The RU 106. the DU 108. and the CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via a wired or wireless transmission medium. For example, a wired interface can be configured to transmit or receive the information / signals over a wired transmission medium, such as via the fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 of the base station 104d associated with the cell 190d. The BBU 112 includes a DU 108 and a CU 110, which may also have a wired interface (e.g., midhaul link) configured between the DU 108 and the CU 110 to transmit or receive the information / signals between the DU 108 and the CU 110. In further examples, a wireless interface, which may include a receiver, a transmitter, or a transceiver, such as an RF transceiver, configured to transmit and / or receive the information / signals via the wireless transmission medium, such as for information communicated between the RU 106a of the cell 190a and the base station 104e of the cell 190e via cross-cell communication beams 136-138 of the RU 106a and the base station 104e.

[0039] The RUs 106 may be configured to implement lower layer functionality. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions, or lower layer PHY functionality, such as execution of fast Fourier transform (FFT). inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RU 106 may be based on the functional split, such as a functional split of lower layers.

[0040] The RUs 106 may transmit or receive over-the-air (OTA) communication with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via a first set of communication beams 132 of the RU 106b and a second set of communication beams 134b of the UE 102b, which may correspond to inter-cell communication beams or, in some examples, cross-cell communication beams. For instance, the UE 102b of the cell 190b may communicate with the RU 106a of the cell 190a via a third set of communication beams 134a of the UE 102b and a fourth set of communication beams 136 of the RU 106a. DUs 108 can control both real-time and non-real-time features of control plane and user plane communications of the RUs 106.

[0041] Any combination of the RU 106, the DU 108, and the CU 110, or reference thereto individually, may correspond to a base station 104. Thus, the base station 104 may include at least one of the RU 106, the DU 108, or the CU 110. The base stations 104 provide the UEs 102 with access to a core network. The base stations 104 may relay communications between the UEs 102 and the core network (not shown). The base stations 104 may be associated with macrocells for higher-power cellular base stations and / or small cells for lower-power cellular base stations. For example, the cell 190e may correspond to a macrocell, whereas the cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network.”

[0042] Transmissions from a UE 102 to a base station 104 / RU 106 are referred to as uplink (UL) transmissions, whereas transmissions from the base station 104 / RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106d utilizes antennas of the base station 104d of cell 190d to transmit a downlink / forward link communication to the UE 102d or receive an uplink / reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104d / RU 106d.

[0043] Communication links between the UEs 102 and the base stations 104 / RUs 106 may be based on multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be associated with one or more carriers. The UEs 102 andthe base stations 104 / RUs 106 may utilize a spectrum bandwidth of T MHz (e.g., 5. 10, 15, 20, 100, 400, 800, 1600, 2000, etc. MHz) per carrier allocated in a carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along a frequency spectrum. In examples, uplink and downlink carriers may be allocated in an asymmetric manner, with more or fewer carriers allocated to either the uplink or the downlink. A primary' component carrier and one or more secondary' component carriers may be included in the component carriers. The primary component earner may be associated with a primary cell (P Cell) and a secondary component carrier may be associated with a secondary cell (SCell).

[0044] Some UEs 102, such as the UEs 102a and 102s, may perform device-to-device (D2D) communications over sidelink. For example, a sidelink communication / D2D link utilizes a spectrum for a wireless wide area netw ork (WWAN) associated with uplink and downlink communications. Such sidelink / D2D communication may be performed through various wireless communications systems, such as wireless fidelity' (Wi-Fi) systems, Bluetooth systems, Long Term Evolution (LTE) systems, New Radio (NR) systems, etc.

[0045] The UEs 102 and the base stations 104 / RUs 106 may each include a plurality of antennas. The plurality of antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that may7facilitate beamforming operations. For example, the RU 106b transmits a downlink beamformed signal based on a first set of communication beams 132 to the UE 102b in one or more transmit directions of the RU 106b. The UE 102b may receive the downlink beamformed signal based on a second set of communication beams 134b from the RU 106b in one or more receive directions of the UE 102b. In a further example, the UE 102b may also transmit an uplink beamformed signal (e.g., sounding reference signal (SRS)) to the RU 106b based on the second set of communication beams 134b in one or more transmit directions of the UE 102b. The RU 106b may receive the uplink beamformed signal from the UE 102b in one or more receive directions of the RU 106b. The UE 102b may perform beam training to determine the best receive and transmit directions for the beamformed signals. The transmit and receive directions for the UEs 102 and the base stations 104 / RUs 106 may or may not be the same.

[0046] In further examples, beamformed signals may be communicated between a first base station / RU 106a and a second base station 104e. For instance, the base stationcommunication beams 138 in one or more transmit directions of the base station 104e. The RU 106a may receive the beamformed signal from the base station 104e of the cell 190e based on the RU communication beams 136 in one or more receive directions of the RU 106a. In further examples, the base station 104e transmits a downlink beamformed signal to the UE 102e based on the communication beams 138 in one or more transmit directions of the base station 104e. The UE 102e receives the downlink beamformed signal from the base station 104e based on UE communication beams 130 in one or more receive directions of the UE 102e. The UE 102e may also transmit an uplink beamformed signal to the base station 104e based on the UE communication beams 130 in one or more transmit directions of the UE 102e, such that the base station 104e may receive the uplink beamformed signal from the UE 102e in one or more receive directions of the base station 104e.

[0047] The base station 104 may include and / or be referred to as a network entity. That is, ‘’network entity” may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and / or the CU 110. The base station 104 may also include and / or be referred to as a next generation evolved Node B (ng-eNB), a next generation NB (gNB), an evolved NB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station, or a disaggregated base station including one or more RUs 106, DUs 108, and / or CUs 110. A set of aggregated or disaggregated base stations may be referred to as a next generation-radio access network (NG-RAN). In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station / RU 106a. In such cases, the base station 104e can be a master node and the base station / RU 160a can be a secondary' node.

[0048] Still referring to FIG. 1 , in certain aspects, any of the UEs 102 may include a PDU Set discard component 140 configured to receive, from a network entity, a first indicator of a protocol data unit (PDU) Set importance (PSI) to enable discarding a PDU Set during a discard cycle having a first discard cycle time period and a second discard cycle time period; discard, after expiration of a first discard time period, a first PDU Set from a transmit buffer during the first discard cycle time period; and discard,after expiration of a second discard time period that is longer than the first discard time period, a second PDU Set from the transmit buffer during the second discard cycle time period.

[0049] In certain aspects, any of the base stations 104 or a network entity of the base stations 104 may include a congestion control component 150 configured to receive, from a UE, a report indicating a PDU Set parameter for a PSI, the PSI indicating a relative importance of a PDU Set; and transmit, to the UE based on the report and a network congestion level, a first indicator of the PSI to enable PDU discarding during a discard cycle having a first discard cycle time period and a second discard cycle time penod.

[0050] Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein. Further, although the following description may be focused on 5G NR. the concepts described herein may be applicable to other similar areas, such as 5G- Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies, such as 6G.

[0051] FIG. 2A illustrates a diagram 200 of a wireless communications system that includes a plurality of UEs 102 and a network entity 104 in communication over access links 250 (e.g., Uu access links) according to an embodiment. In some aspects, a UE 102 software application (e.g., extended reality (XR) application) queues data in a transmit buffer for uplink transmission to network entity 104. The data is organized into PDU Sets.

[0052] In some aspects, the network entity detects that the network congestion level on access links 250 has reached a threshold. This network congestion may be caused by uplink data bursts or core network congestion affecting downlink radio access. To alleviate the netw ork congestion, netw ork entity 104 and UEs 102 begin congestion control techniques as described below with reference to FIGs. 3-11. To address the problem of a network entity setting a PSI threshold for a PDU Set packet discarding procedure either too high or too low relative to a dynamic network congestion situation as discussed in the Background (and other problems), the network entity implements network congestion control techniques that leverage UE information and additional controls.

[0053] The network entity' 104 implements network congestion control techniques that leverage UE 102 information and additional controls (e.g., PDU Set discard timer,PDU Set discard disable message. PSI threshold ramp down. etc.). The relative importance of the PDU Set is dictated by the PSI. UEs 102 may set a PSI based on a PDU Set Type. For example, when UEs 102 are transmitting video data (e.g., XR video data) to the network entity 104, UEs 102 configure a first PDU Set Type containing I-frame video data to have a higher importance than a second PDU Set Type containing P-frame video data. In some aspects, the PSI may have a range of values (e.g., 2 values, 4 values, 8 values, 16 values, etc.) in which a higher PSI value indicates a higher PDU Set Type importance. Alternatively, a lower PSI value indicates a higher PDU Set Type importance.

[0054] FIG. 2B is a diagram 251 illustrating a timeline for UE PDU Set discarding based on an On / Off discard cycle period T3 212 having a first discard cycle period Tl 216 and a second discard cycle period T2 215 according to an embodiment. In some aspects, a network entity 104 determines a network congestion level nears or exceeds a threshold. In order to alleviate the network congestion, the network entity 104 configures the UE 102 to discard PDU Sets based on an On / Off discard cycle period T3 212. The UE 102 receives On / Off discard cycle parameters from the network entity 104 indicating a periodicity of the On / Off discard cycle period T3 212, a first discard cycle period Tl 216 (e.g., On period), and / or a second discard cycle period T2 215 (e.g., Off period). For example, the network entity 104 transmits the On / Off discard cycle parameters in one or more RRC messages (e.g. RRCReconfiguration, RRCRelease, RRCSetup, or RR( ' Reestablishment), When the UE 102 receives the first indicator 210 at time tl, the UE 102 periodically starts the On / Off discard cycle timer T3 212. For example, when the UE 102 receives the first indicator 210 in subframe n. the UE 102 periodically starts the On / Off discard cycle timer T3 212 in the subframe (n+m+k*periodicity) or (k*periodicity), where m is predefined or configured by the network entity 104 and k is a whole number. In another example, the UE 102 periodically starts the On / Off discard cycle timer T3 212 in the subframe (k*periodicity), where k is a whole number.

[0055] The UE begins PDU Set discarding periodically based on receiving the first indicator 210. The UE discards PDU Sets during first discard cycle period Tl 216a using first discard time period T4 204a (e.g., a first discard timer period) and optionally a PSI. For example, at time t3, the UE 102 receives a first PDU Set in a transmit buffer from an upper layer and starts a first discard period timer T4 204a. If the first discard period timer T4 204a expires before the UE 102 transmits the firstPDU Set. the UE 102 discards the first PDU Set at time t4. The UE 102 may have multiple overlapping discard timers running where each discard timer starts when each additional PDU Set arrives in the transmit buffer.

[0056] At the end of the first discard cycle period T1 216a the second discard cycle period T2 215a begins. During the second discard cycle period T2 215a. the UE discards PDU Sets using legacy discard time period T5 205a. For example, at time t5, the UE 102 receives a second PDU Set in a transmit buffer from an upper layer and starts a legacy discard period timer T5 205a. If the legacy discard period timer T5 205a expires before the UE 102 transmits the second PDU Set, the UE 102 discards the second PDU Set at time t6. In this manner, PDU Sets arriving in the transmit buffer during the second discard cycle period T2 215 have an increased probability of being transmitted by the UE 102 as compared to PDU Sets arriving in the transmit buffer during the first discard cycle period T1 216.

[0057] At the end of the On / Off discard cycle period T3 212a the next On / Off discard cycle period T3 212b begins (Thus, in this example k = 0 ). The On / Off discard cycle period T3 212 repeats for a configured or preset time period. In some aspects, On / Off discard cycle period T3 212 repeats until the UE 102 receives, from the network entity, the second indicator 206 at time t2. The second indicator 206 directs the UE 102 to refrain from PDU Set discarding according to the On / Off discard cycle period T3 212.

[0058] The UE 102 continues PDU Set discarding during first discard cycle period T1 216b using first discard time period T4 204b and optionally a PSI. For example, at time t7. the UE 102 receives a third PDU Set in a transmit buffer from an upper layer and starts first discard period timer T4 204b. If the first discard period timer T4 204b expires before the UE 102 transmits the third PDU Set, the UE 102 discards the third PDU Set at time t8.

[0059] At the end of the first discard cycle period T1 216b, the second discard cycle period T2 215b begins. During the second discard cycle period T2 215b, the UE 102 discards PDU Sets using legacy discard time period T5 205b. For example, at time t9, the UE 102 receives a fourth PDU Set in a transmit buffer from an upper layer and starts a legacy discard period timer T5 205b. If the legacy discard period timer T5 205b expires before the UE 102 transmits the fourth PDU Set, the UE 102 discards the fourth PDU Set at time tlO.

[0060] The network entity 104 optionally transmits a second indicator 206 at time t2 to disable PDU Set discarding according to the On / Off discard cycle period T3 212. For example, after receiving the second indicator 206, all discard timers for transmit buffers revert to their legacy discard time period values.

[0061] FIG. 3A is a signaling diagram of a method 300 illustrating communications between a UE 102 and a network entity 104 for discarding PDU Set(s) according to an embodiment in a wireless communications system as shown in FIGs. 1-2A.

[0062] The UE 102 transmits 302 a PDU Set parameter report for a PDU Set Type or for a PSI to network entity 104. In this regard, the UE 102 transmits 302 the PDU Set parameter report to network entity 104 using a radio resource control (RRC) message, a medium access control-control element (MAC-CE), a service data adaptation protocol (SDAP) control PDU, a PDCP control PDU, an RLC control PDU, or other suitable communication. The PDU Set parameter report includes several parameters for each PDU Set Type. For example, for each PDU Set Type the parameters include data rate, data rate range, PSI, data modality (e.g., single modal data or multi-modal data), data volume, and / or data volume range in the UE transmit buffer. The PSI indicates the relative importance of a PDU Set. In some aspects, if UE 102 generates data with certain PSI values (e.g., PSI 1. PSI 5, and PSI 7), the UE 102 transmits the PDU Set parameter report indicating the certain PSI values (e.g., PSI 1, PSI 5, and PSI 7) to network entity 104. In this way the network entity 104 knows how many PSI values the UE 102 will generate and uses this information to determine a PSI threshold for the UE to discard PDU Sets. The PDU Set Type or PSI of a PDU Set is determined by the software application. In some aspects, the UE 102 periodically transmits 302 a PDU Set parameter report for a PDU Set Type or for a PSI to network entity 104. The periodicity of transmitting the PDU Set parameter report is configured (e.g., via RRC message) by the network entity 104.

[0063] The PDU Set parameter report includes a bitmap with each bit (or group of bits) position indicating a PDU Set Type and the bit (or group of bits) contents indicating parameters of the respective PDU Set Type. Additionally or alternatively, the UE 102 periodically transmits 302 a PDU Set parameter report for a PDU Set Type or for a PSI to network entity 104. For example, the network entity 104 may transmit a request (e.g., when a network congestion level nears or exceeds a threshold) to the UE 102 for the PDU Set parameter report. In response to the request, the UE 102 transmits 302 the PDU Set parameter report. Additionally or alternatively, the UE 102 transmits302 the PDU Set parameter report to a second network entity 104 during a handover or when re-establishing a RRC connection to the second network entity 104.

[0064] In some aspects, an application (e.g., XR application) running on the UE 102 determines the data rates to report. In some aspects, the data rate is an average (e.g., statistical average) of data rates. For example, the UE 102 determines a data rate to report by dividing the total data volume from the PDU Sets per PDU Set Type (or per PSI) over the time period when the data arrives in the transmit buffer from the application (or upper layers). Additionally or alternatively, the UE 102 determines the data rate by aggregating the data rates from more than one PDU Set Type (or more than one per PSI). Additionally or alternatively, the UE 102 indicates the data rate as a range of data rates. For example, the UE 102 may store a lookup table having a set of indexes corresponding to a range of data rates. The UE 102 transmits the PDU Set parameter report including an index to the range of data rates that the measured data rate for the PDU Set Type (or for the PSI) falls into. Other types of PDU Set parameters include data volume information per PDU Set Type (or per PSI) for a logical channel group or data volume information of urgent data in a transmit buffer for a logical channel or a logical channel group whose remaining time for delivery is less than or equal to a threshold. Additionally or alternatively, the UE 102 may include the data volume per PDU Set Type or per PSI in a buffer status report (BSR). In some aspects, the PDU Set parameter report may include a bitmap with each bit indicating a PDU Set Type and transmit buffer status.

[0065] The network entity 104 determines 306 a network congestion level in order to determine whether to enable PDU Set discarding to alleviate the network congestion. For example, if the total data volume reported by the UE 102 and / or other UEs 102 (see FIG. 2A) is larger than or equal to a threshold, the network entity 104 enables PDU Set discarding. Each UE 102 reports total data volume using the PDU Set parameter report and / or a BSR. Additionally or alternatively, if the total data volume of urgent data (e.g., data with a low latency budget) reported by the UE 102 and / or other UEs 102 is larger than or equal to a threshold, the network entity 104 enables PDU Set discarding.

[0066] The network entity 104 selects one or more UEs 102 to enable PDU Set discarding. For example, the network entity 104 selects the UE 102 to enable PDU Set discarding when the importance (e.g., PSI) of the reported PDU Set Types is lower than other UEs. In this way, the network entity 104 selects lower priority data fordiscarding. In some aspects, the network entity 104 determines an amount of uplink data from the UE(s) 102 that needs to be reduced (e g., discarded) in order to alleviate the network congestion. If multiple UEs report data of the same PDU Set Type (e.g., same PSI), the network entity 104 may select the UE reporting the higher data rate for that PDU Set Type in order to reduce signaling overhead. Additionally or alternatively, if multiple UEs report data of the same PDU Set Type (e g., same PSI), the network entity 104 may select the UE reporting the lower data rate for that PDU Set Type to begin PDU Set discarding.

[0067] Similarly, if multiple UEs report data volumes of the same PDU Set Type (e.g.. same PSI), the network entity 104 may select the UE reporting the larger volume of data for that PDU Set Type in order to reduce signaling overhead. Additionally or alternatively, if multiple UEs report data volumes of the same PDU Set Type (e.g., same PSI), the network entity 104 may select the UE reporting the lower amount of data for that PDU Set Type to begin PDU Set discarding.

[0068] The netw ork entity' transmits 310, based on the PDU Set parameter report and its congestion level, a first indicator to the UE 102 to enable PDU Set discarding. In this regard, the network entity transmits 310 the first indicator via DCI, a MAC-CE, an RRC message, or other suitable communication. The first indicator includes a PDU Set Type threshold or a PSI threshold and either explicitly or implicitly directs PDU Set discards of PDUs having that PDU Set Type or a lower-priority PDU Set Type. When the UE 102 receives 310 the first indicator, UE 102 discards 314 PDU Sets with a PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI lower than or equal to the PSI threshold indicated by the first indicator. In some aspects, the UE 102 discards 314 only the PDU Sets in the transmit buffer (e.g., PDCP layer buffer, RLC layer buffer, or MAC layer buffer) when the first indicator was received 310 from the netw ork entity 104. When the UE 102 transmit buffer contains PDU Sets of different PDU Set Types, the UE discards only the PDU Sets in the buffer that satisfy the PDU Set Type threshold or the PSI threshold. Additionally or alternatively, the UE 102 continues to discard 314 PDU Sets with PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI low er than or equal to the PSI threshold.

[0069] The network entity 104 optionally transmits 322 a second indicator to disable PDU Set discarding. The UE 102 continues to discard 314 PDU Sets with PDU Set Type low er than or equal to the PDU Set Type threshold or a PSI low er than or equal to the PSI threshold until the UE 102 receives 322 the second indicator from thenetwork entity 104 directing the UE 102 to refrain 326 from PDU Set discarding. For example, when the network entity 104 determines that the network congestion has dropped below the network congestion threshold, the network entity 104 transmits 322 (e.g., via RRC or MAC-CE) the second indicator to the UE 102 to disable PDU Set discarding.

[0070] The network entity 104 may transmit the second indicator via a groupcast message to UEs having the same group radio network temporary' identifier (RNTI). Additionally or alternatively, the network entity 104 may transmit the second indicator to the UE 102 via a unicast message. The network entity 104 may initially transmit 322 the second indicator to UE(s) having higher priority PDU Sets for uplink transmission. The higher priority PDU Sets are determined based on the PSI of the PDU Sets. Additionally or alternatively, the network entity 104 transmits 322 the second indicator to UE(s) having a higher priority (e g., UEs of a higher priority type) than other UEs. Later, the network entity 104 may' transmit 322 the second indicator to other UE(s) having lower priority uplink transmissions.

[0071] FIG. 3B is a signaling diagram 301 illustrating communications between a UE 102 and a network entity 104 for discarding PDU Set(s) based on a ON / Off discard cycle period 312 (e.g., On / Off discard cycle period T3 212 of FIG. 2B) having a first discard cycle time period 316 (e.g., first discard cycle period T1 216 of FIG. 2B) and a second discard cycle time period 315 (e.g., second discard cycle period T2 215 of FIG. 2B). Reference numbers 302, 306, and 310 were previously described with reference to FIG. 3 A. As shown in FIG. 3B. the network entity 104 optionally transmits 309 a third indicator to the UE 102 indicating a periodicity of the On / Off discard cycle period 312. In this regard, the network entity 104 transmits 309 the third indicator to the UE 102 using RRC signaling, a MAC-CE, DCI, or other suitable communication. In some aspects, the network entity 104 transmits 309 the third indicator to the UE 102 before transmitting 310 a first indicator to enable PDU Set discarding based on the On / Off discard cycle period 312. The first indicator optionally indicates the periodicity of the On / Off discard cycle period 312. The periodicity of the On / Off discard cycle period 312 may be indicated as atime period (e.g., a number of slots, a number of radio frames, and / or a number of subframes) and a first discard cycle time period value 316 or a second discard cycle time period value 315. Alternatively, the periodicity of the On / Off discard cycle period 312 may be indicatedas a first discard cycle time period value 316 and a second discard cycle time penod value 315.

[0072] In some aspects, the On / Off discard cycle period 312 begins when the UE 102 receives 310 the first indicator to begin discarding PDU Set(s). In some aspects, the On / Off discard cycle period 312 begins after the UE 102 receives 310 the first indicator and at a leading subframe of a radio frame. Alternatively, the On / Off discard cycle period 312 begins at a whole number of subframes after the UE 102 receives 310 the first indicator. In some aspects, the first indicator indicates the whole number of subframes.

[0073] During the first discard cycle time period 316a, the UE 102 discards 314a a first PDU Set from the transmit buffer after expiration of the first discard time period (e.g., first discard time period T4 204a of FIG. 2B). In some aspects, the UE 102 discards 314a the first PDU Set based on the first PDU Set satisfying a PSI threshold criterion.

[0074] At the end of the first discard cycle time period 316a the second discard cycle period 315a begins. During the second discard cycle period 315a, the UE discards 314b a second PDU Set using a legacy discard time period (e.g., legacy discard timer period T5 205a of FIG. 2B) and optionally a PSI threshold criterion. The legacy discard timer is longer than the first discard timer. In this manner, the second PDU Set arriving in the transmit buffer during the second discard cycle period 315a has an increased probability of being transmitted by the UE 102 as compared to the first PDU Set arriving in the transmit buffer during the first discard cycle time period 316a.

[0075] At the end of the On / Off discard cycle period 312a, the next On / Off discard cycle period 312b begins. The On / Off discard cycle period 312 repeats for a configured / preset time period or until the UE 102 receives 322 a second indicator disabling PDU Set discarding based on the On / Off discard cycle.

[0076] During the first discard cycle time period 316b, the UE 102 discards 314c a third PDU Set from the transmit buffer after expiration of the first discard time period (e.g.. first discard time period T4204a). In some aspects, the UE 102 discards 314a the third PDU Set based on the third PDU Set satisfying a PSI threshold criterion. At the end of the first discard cycle period time 316b the second discard cycle period 315b begins. During the second discard cycle time period 315b, the UE 102 discards 314b a fourth PDU Set using a legacy discard time period (e.g., legacy discard timer period T5 205a) and optionally a PSI threshold criterion.

[0077] In some aspects, On / Off discard cycle period 312 repeats until the UE 102 receives 322, from the network entity 104, a second indicator. The second indicator directs the UE 102 to refrain from PDU Set discarding. For example, upon UE receipt of the second indicator, all discard timers for transmit buffers revert to their legacy discard time period values.

[0078] FIG. 4 is a signaling diagram of a method 400 illustrating communications between a UE 102 and a network entity 104 for discarding PDU Set(s) based on a PDU Set discard time period according to another embodiment.

[0079] In the example of FIG. 4, the network entity 104 transmits 410 a first indicator including a PSI threshold and optionally a PDU Set discard time period 418. Element 410 is similar to element 310 and optionally includes a PDU Set discard time period 418 indicator. When the first indication does not indicate a PDU Set discard time period, the UE sets a timer equivalent to a default discard time period. In some aspects, the first indicator optionally includes a PDU Set discard time period 418 indicator for each PSI. In some aspects, the UE 102 stores a preconfigured default PDU Set discard time period 418. For example, the network entity 104 transmits the preconfigured PDU Set discard time period to UE 102 in one or more RRC messages (e.g., RRCReconfiguration, RRCRelease, RRCSetup, or RRCReestablishment message). The PDU Set discard time period 418 in the first indicator overrides a preconfigured PDU Set discard time period. When the UE 102 receives 410 the first indicator, the UE 102 starts a PDU Set discard timer based on the PDU Set discard time period 418 and discards 314 PDU Sets in the buffer with a PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI lower than or equal to the PSI threshold indicated by the first indicator. The UE 102 continues to discard PDUs of PDU Sets entering the buffer with PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI lower than or equal to the PSI threshold during the PDU Set discard time period 418. When the PDU Set discard timer expires, the UE 102 refrains 326 from PDU Set discarding.

[0080] FIG. 5 is a signaling diagram of a method 500 illustrating communications between a UE 102 and a network entity 104 for discarding PDU Set(s) according to an embodiment. FIG. 5 describes discarding PDU Set(s) based on a PDU Set discard timer similar to FIG. 4 and adds a second indicator 322 to interrupt the PDU Set discard timer and disable PDU Set discarding. In FIG. 5, the UE 102 continues to discard PDU Sets with PDU Set Type lower than or equal to the PDU Set Typethreshold or a PSI lower than or equal to the PSI threshold during the PDU Set discard time period 418 until the UE 102 receives 322 a second indicator from the network entity 104 to disable PDU Set discarding or the PDU Set discard timer expires, whichever comes first. The UE 102 interrupts the PDU Set discard timer based on the second indicator and refrains 326 from PDU Set discarding.

[0081] FIG. 6 is a signaling diagram of a method 600 illustrating communications between a UE 102 and a network entity 104 for discarding PDU Set(s) according to an embodiment with multiple thresholds and multiple PDU Discard Time Periods. FIG. 6 starts in a manner similar to FIG. 5 in that the UE 102 discards PDU Sets with PDU Set Type lower than or equal to the first PDU Set Type threshold or a PSI lower than or equal to the PSI threshold during the PDU Set discard time period 418a. In FIG. 6, the UE 102 receives 410b a second value for a second PDU Set discard time period 418b and a second discard threshold. At that time, the UE 102 stops using the first discard threshold discards PDU Sets with PDU Set Type lower than or equal to the second PDU Set Type threshold or a PSI lower than or equal to the PSI threshold during the second PDU Set discard time period 418b.

[0082] When the UE 102 receives 410a the first indicator, the UE 102 starts a PDU Set discard timer based on the PDU Set discard time period 418a (or the preconfigured time period if the first indication does not include a value for 418a) and discards 314 PDU Sets with PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI lower than or equal to the PSI threshold indicated by the first indicator. The UE 102 continues to discard PDU Sets with PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI lower than or equal to the PSI threshold dunng the PDU Set discard time period 418a.

[0083] The UE 102 receives 410b another first indicator from the network entity' 104 to enable PDU Set discarding based on second PSI threshold. The additional first indicator includes a second PSI threshold that is the same or different from the first PSI threshold indicated by the first indicator. The UE 102 interrupts the first PDU Set discard timer 418a, starts the second PDU Set discard timer 418b based on the UE receiving 410b another first indicator indicating the second PDU Set discard timer 418b (or the preconfigured timer value if there is no value for 418b). and discards PDU Sets with PDU Set Type lower than or equal to the second PDU Set Type threshold or a PSI lower than or equal to the second PSI threshold. When the second PDU Set discard timer 418b expires, the UE 102 refrains 326 from PDU Setdiscarding. After the second PDU Set discard timer 418b expires, the UE 102 transmits a PDU Set parameter report and / or BSR indicating data volume per PDU Set Type or PSI to the network entity 104 to inform the network entity 104 about the amount of data in the UE 102's transmit buffer. The BSR may indicate data volume of urgent data for a logical channel or a logical channel group.

[0084] FIG. 6 uses two first indicators to indicate multiple thresholds and multiple PDU Discard Time Periods. FIG. 7 uses a single indicator to instruct behavior similar to FIG. 6 and describes the UE 102 discarding PDU Sets for a first PDU Set discard time period 418a using a first PDU Set Type threshold or PSI threshold and then discarding PDU Sets for a second PDU Set discard time period 418b using a second PDU Set Type threshold or PSI threshold.

[0085] In the example 700 of FIG. 7, the UE 102 receives 710 a first indicator includes a first PDU Set Type (e.g., PSI) threshold and optionally a first PDU Set discard time period 418a. In some aspects, the first indicator includes a PDU Set discard time period 418 for each PDU Set Type (e.g., per PSI). In some aspects, the UE 102 stores a preconfigured PDU Set discard time period 418. The PDU Set discard time period 418a in the first indicator overrides the preconfigured PDU Set discard time period 418. When the UE 102 receives 710 the first indicator, the UE 102 starts a PDU Set discard timer and discards PDU Sets as described with reference to FIG. 4.

[0086] When the first PDU Set discard timer expires, the UE 102 starts a second PDU Set discard timer using a second PDU Set discard time period 418b. In some aspects, the UE 102 stores a preconfigured default second PDU Set discard time period 418b. For example, the network entity' 104 transmits the preconfigured second PDU Set discard time period to UE 102 in one or more RRC messages. The second PDU Set discard time period 418b in the first indicator overrides a second preconfigured PDU Set discard time period. The UE 102 discards PDU Sets with PDU Set Type lower than or equal to a second PDU Set Type threshold or a PSI lower than or equal to the PSI threshold during the second PDU Set discard time period 418b. The first PDU Set discard time period 418a may be the same or different from the second PDU Set discard time period 418b. The second PDU Set Type threshold or PSI threshold is different from the first PDU Set Type threshold or PSI threshold. Generally speaking, the first PDU Set Type threshold should be higher (more important) than the second PDU Set Type threshold. In this way, the UE 102 ramps down the PDU Set discarding. The UE 102 may continue the ramp down process using a third PDU Set discard timeperiod and corresponding third PDU Set Type threshold, a fourth PDU Set discard time period and corresponding fourth PDU Set Type threshold, etc. The UE 102 uses sequential PDU Set discard time period values to achieve customized ramp-downs or a step-wise ramp-down. When the ramp down process is complete, the UE 102 refrains 326 from PDU Set discarding.

[0087] FIG. 8A illustrates a flowchart of a method 800 of a UE performing PDU Set discarding that relates to FIGs. 3-7, which illustrated several flow diagrams showing options for PDU Set discarding.

[0088] The UE transmits 802 a PDU Set parameter report for a PDU Set Type to a network entity as described with reference to 302 in FIGs. 3-7. The UE receives 810, from the network entity based on the PDU Set parameter report, a first indicator to enable PDU Set discarding according to the PDU Set Type as described with reference to FIGs. 3 A, 3B, 4-7 elements 310, 410, and 710. When the UE receives 810 the first indicator, the UE discards 814 PDU Sets with PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI lower than or equal to the PSI threshold indicated by the first indicator. In some aspects, the UE discards 814 only the PDU Sets in the transmit buffer (e.g., PDCP layer buffer or MAC layer buffer) when the first indicator was received 810 from the network entity. Additionally or alternatively, the UE continues to discard 814 PDU Sets with PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI lower than or equal to the PSI threshold. The UE optionally receives 822 a second indicator from the network entity to disable PDU Set discarding. The UE continues to discard 814 PDU Sets with PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI lower than or equal to the PSI threshold until the UE receives 822 the second indicator from the network entity indicating the UE to refrain 826 from PDU Set discarding. For example, when the network entity determines that the netw ork congestion has dropped below the netw ork congestion threshold, the UE receives 822 (e.g.. via RRC, DCI, or MAC-CE) the second indicator to disable PDU Set discarding.

[0089] FIG. 8B is a flow-chart of a method 801 of UE PDU Set discarding based on a discard cycle having a first discard cycle time period and a second discard cycle time period according to an embodiment. The UE transmits 802, to a network entity, a PDU Set parameter report for a PDU Set Type. In this regard, the UE transmits 802 the PDU Set parameter report as described with reference to FIGS. 3 A, 3B, and 4-7 and element 302. The UE optionally receives 809, from a network entity, a third indicator.In this regard, the UE optionally receives 809 a third indicator from a network entity as described with reference to FIG. 3B element 309.

[0090] The UE receives 810, from the network entity, a first indicator to enable PDU Set discarding according to an On / Off discard cycle (e.g., On / Off discard cycle period T3 212 of FIG. 2B) as described with reference to FIGs. 2B and 3B. In some aspects, the On / Off discard cycle begins when the UE receives 810 the first indicator to begin discarding PDU Set(s). In some aspects, the On / Off discard cycle begins after the UE receives 810 the first indicator and at a leading subframe of a radio frame. Alternatively, the On / Off discard cycle begins at a whole number of subframes after the UE receives 810 the first indicator. In some aspects, the first indicator indicates the whole number of subframes.

[0091] The UE receives 849 a PDU Set in a transmit buffer from an upper layer and starts a first discard cycle period timer (e.g., first discard cycle period T1 216 of FIG. 2B). This received PDU Set is represented by the first and third PDU Sets in FIGS. 2B and 3B. The UE determines 851 if the first discard cycle period timer has expired. If the first discard cycle period timer has not expired 851 -No, the UE discards 814a the first and / or third PDU Set after expiration of a first discard timer period (e.g., first discard timer period T4 204a of FIG. 2B) assuming that the PDU Set is still in the transmit buffer at the end of the first discard timer period.

[0092] When the first discard cycle period timer is over 851-Yes, the UE starts a second discard cycle period timer (e.g.. second discard cycle period T2 215 of FIG. 2B). During this second discard cycle period T2, the UE receives 853 a PDU Set (represented by the second and fourth PDU Sets in FIGS. 2B and 3B) in the transmit buffer. As long as the second discard cycle period timer has not expired 852-No, the UE discards 814b the second and / or the fourth PDU Set after expiration of a legacy discard timer period (e.g., legacy discard timer period T5 205a of FIG. 2B).

[0093] When the second discard cycle period timer is over 852-Yes. the UE determines 822 whether it has received a second indicator to disable the discarding of PDU Sets according to the On / Off cycle timer. If the UE determines 822-Yes it has received the second indicator, the UE refrains 826 from discarding PDU Sets according to the On / Off cycle timer and all discard timers for transmit buffers revert to their legacy discard time period values. If the UE has not received 822-No the second indicator, the next On / Off discard cycle period begins. The On / Off discard cycle period repeatsfor a configured / preset time period or until the UE 102 receives 822 the second indicator disabling PDU Set discarding based on the On / Off discard cycle.

[0094] FIG. 9 illustrates a flowchart of a method 900 of wireless communication at a UE. The UE transmits 902 a PDU Set parameter report for a PDU Set Type to a network entity. In this regard, the UE transmits 902 the PDU Set parameter report as described with reference to FIGS. 3A and 8.

[0095] The UE receives 910, from the network entity based on the PDU Set parameter report, a first indicator to enable PDU Set discarding according to the PSI. In this regard, the UE receives 910 the first indicator as described with reference to FIGS. 4- 7 elements 410, 710.

[0096] In the example of FIG. 9, the first indicator includes a PSI threshold and an optional PDU Set discard time period. When the first indication does not indicate a PDU Set discard time period, the UE sets a timer equivalent to a default discard time period. In some aspects, the first indicator includes a PDU Set discard time period for each PSI. When the UE receives 910 the first indicator, the UE 102 starts 912 a PDU Set discard timer based on the PDU Set discard time period.

[0097] The UE determines 918 if the PDU Set discard timer has expired. If the PDU Set discard timer has not expired, the UE discards 914 PDU Sets with PDU Set Type lower than or equal to the PDU Set Type threshold or a PSI lower than or equal to the PSI threshold indicated by the first indicator. If the PDU Set discard timer has expired, the UE refrains 926 from discarding PDU Sets.

[0098] FIG. 10 builds upon FIG. 9 and illustrates a flowchart 1000 of a UE discarding PDU Sets based on a ramp down of PDU Set Type threshold.

[0099] The UE transmits 1002 a PDU Set parameter report for a PDU Set Type to a network entity. In this regard, the UE transmits 1002 the PDU Set parameter report as described with reference to FIG. 8A element 802.

[0100] The UE receives 1010. from the network entity based on the PDU Set parameter report, a first indicator to enable PDU Set discarding according to the PSI. In this regard, the UE receives 1010 the first indicator as described with reference to FIG. 8A element 810 but with some differences as described below and with reference to FIG. 7.

[0101] In the example of FIG. 10, the first indicator includes a first PSI threshold and an optional first PDU Set discard time period. When the UE receives 1010 the firstindicator, the UE 102 starts 1018a a first PDU Set discard timer based on the first PDU Set discard time period.

[0102] The UE determines 1015 if the first PDU Set discard timer has expired. If the first PDU Set discard timer has not expired, the UE discards 1014a PDU Sets with PDU Set Type lower than or equal to the first PDU Set Type threshold or a PSI tower than or equal to the PSI threshold indicated by the first indicator. If the first PDU Set discard timer has expired, the UE decrements 1016 the PDU Set Type threshold or PSI threshold to a second PDU Set Type threshold or PSI threshold.

[0103] The UE 102 starts 1018b a second PDU Set discard timer based on the second PDU Set discard time period. The second PDU Set discard time period for the second PDU Set Type threshold or PSI threshold may differ from or be the same value as either the first PDU Set discard time period or the default PDU Set discard time period.

[0104] The UE determines 1020 if the second PDU Set discard timer has expired. If the second PDU Set discard timer has not expired, the UE discards 1014b PDU Sets with PDU Set Type lower than or equal to the second PDU Set Type threshold or a PSI lower than or equal to the PSI threshold. If the second PDU Set discard timer has expired, the UE refrains 1026 from discarding PDU Sets. The second PDU Set Type threshold or PSI threshold is different from the first PDU Set Type threshold or PSI threshold. The first PSI threshold is higher (more important) than the second PSI threshold. In this way, the UE ramps down the PDU Set discarding. The UE may continue the ramp down process using a third PDU Set discard time period / third PSI threshold, a fourth PDU Set discard time period / fourth PSI threshold, etc.

[0105] FIGs. 8-10 provided flow charts for a UE performing PDU Set discarding, and now FIG. 11 illustrates a flow chart of a method 1100 of wireless communication at a network entity.

[0106] The network entity receives 1102 a PDU Set parameter report for a PDU Set Type from a UE. In this regard, the network entity receives 1102 the PDU Set parameter report as described with reference to FIGs. 3A, 3B, 4-7 element 302.

[0107] The network entity determines 1106 whether a network congestion level exceeds a threshold. The network entity determines 1106 whether a network congestion level exceeds a threshold as described with reference to FIGs. 3A, 4-7. To alleviate the network congestion, the network entity and UEs begin congestion control techniques. The network entity 104 implements network congestion control techniques thatleverage UE information and additional controls (e.g., PDU Set discard timer. PDU Set discard disable message, PSI threshold ramp down, etc.). For example, when the total data volume of PDU Sets associated with UEs served by the network entity exceeds a threshold, the network entity' configures the UE(s) to discard certain PDU Sets to reduce the network congestion.

[0108] The network entity selects 1107 a UE for PDU Set discarding. The network entity selects 1107 one or more UEs to enable PDU Set discarding as described with reference to FIGs. 2-3 A.

[0109] The network entity transmits 1110, to the UE based on the PDU Set parameter report, a first indicator to enable PDU Set discarding according to the PDU Set Type. In this regard, the network entity' transmits 11 10 the first indicator as described with reference to FIGs. 3A, 3B, 4-7 elements 310, 410, and 710.

[0110] The network entity determines 1111 whether the network congestion level continues to exceed the threshold. If the network congestion continues to exceed the threshold, the network entity may select 1107 an additional UE to begin PDU Set discarding as described with reference to FIG. 3A. Additionally or alternatively, the network entity' may transmit a different PDU Set Type threshold or discard timer value to the UE. When the network entity determines 1111 that the network congestion has dropped below the threshold, the network entity transmits 1 122 a second indicator to the UE to discontinue PDU Set discarding.

[0111] FIGs. 2-11 illustrate discarding PDU Sets to alleviate network congestion. FIGs. 12 and 13 show methods for implementing one or more aspects of FIGs. 2-11. In particular, FIG. 12 shows an implementation by the UE 102 of the one or more aspects of FIGs. 2- 11. FIG. 13 shows an implementati on by the network entity 104 of the one or more aspects of FIGs. 2-11.

[0112] FIG. 12 illustrates a flowchart 1200 of a method of wireless communication at a UE. With reference to FIGs. 3 A. 3B, 4-7, 8A, 8B, and 9-10. the method may be performed by the UE 102.

[0113] The UE 102 transmits 1202 to a first network entity' 104, a report indicating a PDU Set parameter for a PDU Set Type, the PDU Set Type identifying a relative importance of a PDU Set. For example, referring to FIGs. 3B and 8B. UE 102 transmits 302, 802, to a first network entity 104, a report indicating a PDU Set parameter for a PDU Set Type or a PSI.

[0114] The UE 102 receives 1210, from the first network entity 104, a first indicator to enable discarding a PDU Set during a discard cycle having a first discard cycle time period and a second discard cycle time period. For example, referring to FIGs. 3B and 8B, the UE 102 receives 310, 810 from the first network entity 104, a first indicator to enable discarding a PDU Set during a discard cycle having a first discard cycle time period and a second discard cycle time period.

[0115] The UE 102 discards 1214a, after expiration of a first discard time period, a first PDU Set received in a transmit buffer during the first discard cycle time period. For example, referring to FIGs. 3B and 8B. the UE 102 discards 314a, 814a, after expiration of a first discard time period, a first PDU Set received in a transmit buffer during the first discard cycle time period.

[0116] The UE 102 discards 1214b, after expiration of a legacy discard time period that is longer than the first discard time period, a second PDU Set received in the transmit buffer during the second discard cycle time period. For example, referring to FIGs. 3B and 8B, the UE 102 discards 314b, 814b, after expiration of a legacy discard time period that is longer than the first discard time period, a second PDU Set received in the transmit buffer during the second discard cycle time period.

[0117] The UE 102 optionally receives 1222, from the first network entity 104, a second indicator to disable PDU discarding. For example, referring to FIGs. 3B and 8B, the UE 102 optionally receives 322, 822, from the first network entity 104, a second indicator to disable PDU discarding.

[0118] FIG. 12 describes a method from a UE-side of a wireless communication link, whereas FIG. 13 describes a flowchart 1300 of a method from a network-side of the wireless communication link.

[0119] The network entity 104 receives 1302, from a UE 102, a report indicating a PDU Set parameter for a PDU Set Type, the PDU Set Type identifying a relative importance of a PDU Set. For example, referring to FIGs. 3B and 8B, network entity 104 receives 302, 802, from a UE 102, a report indicating a PDU Set parameter for a PDU Set Type or PSI.

[0120] The network entity 104 transmits 1310. to the UE 102 based on the first report and a network congestion level, a first indicator to enable PDU discarding during a discard cycle having a first discard cycle time period and a second discard cycle time period. For example, referring to FIGs. 3B and 8B, network entity 104 transmits 310, 810, to the UE 102 based on the first report and a network congestion level, a first indicatorto enable PDU discarding during a discard cycle having a first discard cycle time period and a second discard cycle time period.

[0121] The network entity 104 optionally transmits 1322, to the UE 102 a second indicator to disable PDU Set discarding. For example, referring to FIGs. 3B and 8B, network entity 104 optionally transmits 322. 822, to the UE 102 a second indicator to disable PDU Set discarding.

[0122] A UE apparatus 1402, as described in FIG. 14, may perform the method of flowchart 1200. The one or more network entities 104, as described in FIG. 15, may perform the method of flowchart 1300.

[0123] FIG. 14 is a diagram 1400 illustrating an example of a hardware implementation for a UE apparatus 1402. The UE apparatus 1402 may be the UE 102, a component of the UE 102, or may implement UE functionality as described in FIGs. 3-10 and 12. The UE apparatus 1402 may include an application processor 1406, which may have on-chip memory 1406’. In examples, the application processor 1406 may be coupled to a secure digital (SD) card 1408 and / or a display 1410. The application processor 1406 may also be coupled to a sensor(s) module 1412, a power supply 1414, an additional module of memory' 1416, a camera 1418 for recording single modal video data, a video codec for encoding and decoding I-frame video and P-frame video, and / or other related components. For example, the sensor(s) module 1412 may control a barometric pressure sensor / altimeter, a motion sensor such as an inertial management unit (IMU), a gyroscope, accelerometer(s), a light detection and ranging (LIDAR) device, a radio-assisted detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, a microphone for single modal audio data, and / or other technologies used for positioning. The sensor module 1412 may be used for generating multi-modal data (e.g., video data and audio data and pose data, etc.)

[0124] The UE apparatus 1402 may further include a wireless baseband processor 1426. which may be referred to as a modem. The wireless baseband processor 1426 may have on-chip memory 1426'. Along with, and similar to, the application processor 1406, the wireless baseband processor 1426 may also be coupled to the sensor(s) module 1412, the power supply 1414, the additional module of memory 1416, the camera 1418, and / or other related components. The wireless baseband processor 1426 may be additionally coupled to one or more subscriber identity module (SIM) card(s) 1420 and / or one or more transceivers 1430 (e.g., wireless RF transceivers).

[0125] Within the one or more transceivers 1430. the UE apparatus 1402 may include a Bluetooth module 1432, a WLAN module 1434, an SPS module 1436 (e.g., GNSS module), and / or a cellular module 1438. The Bluetooth module 1432, the WLAN module 1434, the SPS module 1436. and the cellular module 1438 may each include an on-chip transceiver (TRX), or in some cases, just a transmitter (TX) or just a receiver (RX). The Bluetooth module 1432, the WLAN module 1434, the SPS module 1436, and the cellular module 1438 may each include dedicated antennas and / or utilize antennas 1440 for communication with one or more other nodes. For example, the UE apparatus 1402 can communicate through the transceiver(s) 1430 via the antennas 1440 with another UE (e.g., sidelink communication) and / or with a network entity 104 (e.g., uplink / downlink communication), where the network entity7104 may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, or the CU 110.

[0126] The wireless baseband processor 1426 and the application processor 1406 may each include a computer-readable medium / memory 1426', 1406', respectively. The additional module of memory' 1416 may also be considered a computer-readable medium I memory. Each computer-readable medium / memory 1426', 1406', 1416 may be non-transitory. The wireless baseband processor 1426 and the application processor 1406 may each be responsible for general processing, including execution of software stored on the computer-readable medium / memory 1426', 1406', 1416. The software, when executed by the wireless baseband processor 1426 / application processor 1406, causes the wireless baseband processor 1426 / application processor 1406 to perform the various functions described herein. The computer-readable medium / memory’ may also be used for storing data that is manipulated by the wireless baseband processor 1426 / application processor 1406 when executing the software. The wireless baseband processor 1426 / application processor 1406 may be a component of the UE 102. The UE apparatus 1402 may be a processor chip (e.g.. modem and / or application) and include just the wireless baseband processor 1426 and / or the application processor 1406. In other examples, the UE apparatus 1402 may be the entire UE 102 and include the additional modules of the apparatus 1402.

[0127] As discussed in FIG. 1 and implemented with respect to FIG. 13, the PDU Set discard component 140 is configured to receive, from a network entity, a first indicator of a PSI to enable discarding a PDU Set during a discard cycle having a first discard cycle time period and a second discard cycle time period; discard, afterexpiration of a first discard time period, a first PDU Set from a transmit buffer during the first discard cycle time period; and discard, after expiration of a second discard time period that is longer than the first discard time period, a second PDU Set from the transmit buffer during the second discard cycle time period. The PDU Set discard component 140 may be within the application processor 1406 (e.g., at 140a). the wireless baseband processor 1426 (e g., at 140b), or both the application processor 1406 and the wireless baseband processor 1426. The PDU Set discard component 140a- 140b may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer- readable medium for implementation by the one or more processors, or a combination thereof.

[0128] FIG. 15 is a diagram 1500 illustrating an example of a hardware implementation for one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality as described in FIGs. 3-7, 11, and 13. The one or more network entities 104 may include, or may correspond to, at least one of the RU 106, the DU, 108, or the CU 110. The CU 110 may include a CU processor 1546. which may have on-chip memory 1546'. In some aspects, the CU 110 may further include an additional module of memory' 1556 and / or a communications interface 1548, both of which may be coupled to the CU processor 1546. The CU 110 can communicate with the DU 108 through a midhaul link 162. such as an Fl interface between the communications interface 1548 of the CU 110 and a communications interface 1528 of the DU 108.

[0129] The DU 108 may include a DU processor 1526, which may have on-chip memory 1526'. In some aspects, the DU 108 may further include an additional module of memory' 1536 and / or the communications interface 1528, both of which may be coupled to the DU processor 1526. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1528 of the DU 108 and a communications interface 1508 of the RU 106.

[0130] The RU 106 may include an RU processor 1506, which may have on-chip memory1506'. In some aspects, the RU 106 may further include an additional module of memory 1516, the communications interface 1508, and one or more transceivers 1530, all of which may be coupled to the RU processor 1506. The RU 106 may further include antennas 1540, which may be coupled to the one or more transceivers 1530,such that the RU 106 can communicate through the one or more transceivers 1530 via the antennas 1 40 with the UE 102.

[0131] The on-chip memory' 1506', 1526', 1546' and the additional modules of memory71516, 1536, 1556 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 1506, 1526, 1546 is responsible for general processing, including execution of software stored on the computer-readable medium / memory7. The software, when executed by the corresponding processor(s) 1506, 1526, 1546 causes the processor(s) 1506, 1526, 1546 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor(s) 1506, 1526, 1546 when executing the software. In examples, the congestion control component 150 may sit at any of the one or more network entities 104. such as at the CU 110; both the CU 110 and the DU 108; each of the CU 110. the DU 108, and the RU 106; the DU 108; both the DU 108 and the RU 106; or the RU 106.

[0132] As discussed in FIG. 1 and implemented with respect to FIG. 15, the congestion control component 150 is configured to receive, from a UE, a report indicating a PDU Set parameter for a PSI, the PSI indicating a relative importance of a PDU Set; and transmit, to the UE based on the report and a network congestion level, a first indicator of the PSI to enable PDU discarding during a discard cycle having a first discard cycle time period and a second discard cycle time period. The congestion control component 150 may be within one or more processors of the one or more network entities 104, such as the RU processor 1506 (e.g., at 150a), the DU processor 1526 (e.g., at 150b), and / or the CU processor 1546 (e.g., at 150c). The congestion control component 150a- 150c may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors 1506. 1526, 1546 configured to perform the stated processes / algorithm. stored within a computer-readable medium for implementation by the one or more processors 1506, 1526, 1546, or a combination thereof.

[0133] The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is an illustration of example approaches. Hence, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the diagrams. The accompanying method claims present elements of the various blocks in anexample order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0134] The detailed description set forth herein describes various configurations in connection with the drawings and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough explanation of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0135] Aspects of wireless communication systems, such as telecommunication systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as ‘"elements”). These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0136] An element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems-on-chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software, which may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0137] If the functionality described herein is implemented in software, the functions may be stored on, or encoded as, one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer- readable media includes computer storage media and can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer.

[0138] Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, machine learning (ML)-enabled devices, etc. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein.

[0139] Devices incorporating the aspects and features described herein may also include additional components and features for the implementation and practice of the claimed and described aspects and features. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes, such as hardware components, antennas, RF-chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders / summers, etc. Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of vary ing configurations.

[0140] The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspectsdescribed herein, but are to be interpreted in view of the full scope of the present disclosure consistent with the language of the claims.

[0141] Reference to an element in the singular does not mean “one and only one" unless specifically stated, but rather “one or more.’' Terms such as “if,’' “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The terms “may”, “might”, and “can”, as used in this disclosure, often carry certain connotations. For example, “may” refers to a permissible feature that may or may not occur, “might” refers to a feature that probably occurs, and “can” refers to a capability (e.g., capable of). The phrase “For example” often carries a similar connotation to “may” and, therefore, “may” is sometimes excluded from sentences that include “for example” or other similar phrases.

[0142] Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C” or “one or more of A, B, or C” include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiples of A. multiples of B. and / or multiples of C, or may include A only, B only, or C only. Sets should be interpreted as a set of elements where the elements number one or more. Terms or articles such as “a”, “an”, and / or “the” may refer to one of an item, feature, element, etc., that the term or article precedes, or may refer to more than one of said item, feature, element, etc. that the term or article precedes. For example, the recitation “a widget” does not preclude reference to multiples of said widget, as “multiple widgets” necessarily includes “a widget”. Hence, the recitation “a widget” may be interpreted as “at least one widget” or, similarly, interpreted as “one or more widgets”.

[0143] Unless otherwise specifically indicated, ordinal terms such as “first” and “second” do not necessarily imply an order in time, sequence, numerical value, etc., but are used to distinguish between different instances of a term or phrase that follows each ordinal term. Reference numbers, as used in the specification and figures, are sometimes cross-referenced among drawings to denote same or similar features. A feature that is exactly the same in multiple drawings may be labeled with the same reference number in the multiple drawings. A feature that is similar among the multiple drawings, but not exactly the same, may be labeled with reference numbersthat have different leading numbers, but have one or more of the same trailing numbers (e.g., 206, 306, 406, etc., may refer to similar features in the drawings). Sometimes an “X” is used to universally denote multiple variations of a feature. For instance, “X06” can universally refer to all reference numbers that end in “06” (e.g., 206, 306. 406, etc.).

[0144] Structural and functional equivalents to elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. The words “module,” “mechanism.” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.” As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A”, where “A” may be information, a condition, a factor, or the like, shall be construed as “based at least on A” unless specifically recited differently.

[0145] The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.

[0146] Example 1 is a method of wireless communication performed by a UE, the method including: receiving, from a network entity, a first indicator of a PSI to enable discarding a PDU Set during a discard cycle having a first discard cycle time period and a second discard cycle time period; discarding, after expiration of a first discard time penod, a first PDU Set from a transmit buffer dunng the first discard cycle time period; and discarding, after expiration of a second discard time period that is longer than the first discard time period, a second PDU Set from the transmit buffer during the second discard cycle time period.

[0147] Example 2 may be combined with Example 1 and includes that the first discard cycle time period comprises a value greater than zero.

[0148] Example 3 may be combined w ith any of Examples 1-2 and includes that the first indicator indicates a periodicity' of the discard cycle and at least one of: a first discard cycle time period value; or a second discard cycle time period value.

[0149] Example 4 may be combined with Example 3 and includes that the periodicity of the discard cycle is an integer number of subframes.

[0150] Example 5 may be combined with any of Examples 1-4 and includes that the first indicator indicates: a first discard cycle time period value; and a second discard cycle time period value.

[0151] Example 6 may be combined with any of Examples 1-5 and further includes receiving, from the network entity before the receiving the first indicator, a third indicator indicating the periodicity of the discard cycle.

[0152] Example 7 may be combined with any of Examples 1-6 and includes that the discard cycle at least one of: begins when the UE receives the first indicator, begins during a leading subframe of a radio frame, or begins during an integer number of subframes after receiving the first indicator.

[0153] Example 8 may be combined with any of Examples 1-7 and includes that the discarding the first PDU Set comprises discarding the first PDU Set based on a PSI of the first PDU Set satisfying a PSI threshold criterion.

[0154] Example 9 may be combined with any of Examples 7-8 and includes that the first indicator indicates at least one of: the integer number of subframes, or the PSI threshold criterion.

[0155] Example 10 may be combined with any of Examples 1-9 and further includes receiving, from the network entity, a second indicator to disable the PDU Set discarding during the discard cycle.

[0156] Example 11 may be combined with any of Examples 1-10 and includes that the receiving the first indicator includes receiving the first indicator via at least one of: an RRCReconflguratlon message, an RRCRelease message, an RRCSetup message, or an RRCReestablishment message.

[0157] Example 12 may be combined with any of Examples 1-11 and further includes transmitting, to the network entity, a report indicating a PDU Set parameter for a PDU Set Type via an RRC message or a MAC-CE message.

[0158] Example 13 is a method of wireless communication performed by a network entity, the method including: receiving, from a UE, a report indicating a PDU Set parameter for a PSI, the PSI indicating a relative importance of a PDU Set; and transmitting, to the UE based on the report and a network congestion level, a first indicator of the PSI to enable PDU discarding during a discard cycle having a first discard cycle time period and a second discard cycle time period.

[0159] Example 14 may be combined with Example 13 and further includes determining, by the network entity , the PSI based on the network congestion level.

[0160] Example 15 may be combined with any of Examples 13-14 and includes that the first indicator indicates a periodicity of the discard cycle and at least one of: a first discard cycle time period value; or a second discard cycle time period value.

[0161] Example 16 may be combined with any of Examples 13-15 and further includes transmitting, to the UE before the transmitting the first indicator, a third indicator indicating a periodicity of the discard cycle.

[0162] Example 17 may be combined with any of Examples 13-16 and further includes transmitting, to the UE, a second indicator to disable the PDU Set discarding during the discard cycle.

[0163] Example 18 may be combined with any of Examples 13-17 and includes that the transmitting the first indicator includes transmitting the first indicator via at least one of RRC signaling, DCI, or a MAC-CE message.

[0164] Example 19 is an apparatus for wireless communication for implementing a method as in any of Examples 1-18.

[0165] Example 20 is an apparatus for wireless communication including means for implementing a method as in any of Examples 1-18.

[0166] Example 21 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of Examples 1-18.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. A method of wireless communication performed by a user equipment, UE. (102) the method comprising: receiving (310), from a network entity (104), a first indicator of a protocol data unit, PDU. Set importance, PSI. to enable discarding a PDU Set during a discard cycle having a first discard cycle time period and a second discard cycle time period; discarding (314a), after expiration of a first discard time period, a first PDU Set from a transmit buffer during the first discard cycle time period; and discarding (314b), after expiration of a second discard time period that is longer than the first discard time period, a second PDU Set from the transmit buffer during the second discard cycle time period.

2. The method of claim 1, wherein the first discard cycle time period comprises a value greater than zero.

3. The method any of claims 1 to 2, wherein the first indicator indicates a periodicity of the discard cycle and at least one of: a first discard cycle time period value; or a second discard cycle time period value.

4. The method of claim 3, wherein the periodicity of the discard cycle is an integer number of subframes.

5. The method any of claims 1 to 4, wherein the first indicator indicates: a first discard cycle time period value; and a second discard cycle time period value.

6. The method any of claims 1 to 5, further comprising: receiving (309), from the network entity7(104) before the receiving (310) the first indicator, a third indicator indicating the periodicity of the discard cycle.

7. The method any of claims 1 to 6, wherein the discard cycle at least one of: begins when the UE receives the first indicator, begins during a leading subframe of a radio frame, or begins during an integer number of subframes after receiving the first indicator.

8. The method any of claims 1 to 7, wherein the discarding (314a) the first PDU Set comprises discarding (314a) the first PDU Set based on a PSI of the first PDU Set satisfying a PSI threshold criterion.

9. The method of any of claims 7-8, wherein the first indicator indicates at least one of: the integer number of subframes, or the PSI threshold criterion.

10. The method of any of claims 1 to 9, further comprising: receiving (322), from the network entity (104), a second indicator to disable the PDU Set discarding during the discard cycle.

11. The method of any of claims 1 to 10, wherein the receiving (310) the first indicator comprises receiving (310) the first indicator via at least one of: an RRCReconfiguration message, an RRCRelease message, an RRCSetup message, or an RRCReestablishment message.

12. The method of any of claims 1 to 11, further comprising: transmitting (302), to the network entity (104), a report indicating a PDU Set parameter for a PDU Set Type via a radio resources control, RRC, message or a medium access control-control element, MAC-CE. message.

13. A method of wireless communication performed by a network entity (104), the method comprising: receiving (302), from a user equipment, UE (102), a report indicating a protocol data unit, PDU, Set parameter for a PDU Set importance, PSI, the PSI indicating a relative importance of a PDU Set; andtransmitting (310). to the UE (102) based on the report and a network congestion level, a first indicator of the PSI to enable PDU discarding during a discard cycle having a first discard cycle time period and a second discard cycle time period.

14. The method of claim 13, further comprising: determining (306), by the network entity (104), the PSI based on the network congestion level.

15. An apparatus for wireless communication comprising a transceiver, a memory, and a processor coupled to the transceiver and the memory and configured to implement a method as in any of claims 1-14.

Images