Techniques for timer adjustment in response to packet loss

Abstract

Various aspects of the disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive information indicating a timer value of a timer associated with discarding a packet data convergence protocol (PDCP) service data unit (SDU). The UE can determine that a timer modification condition is satisfied. The UE can modify the timer value based at least in part on the determination that the timer modification condition is satisfied. The UE can transmit a communication using the modified timer value. Numerous other aspects are provided.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 706,341, filed August 11, 2020, entitled “TECHNIQUES FOR TIMERADJUSTMENT FOR PACKET LOSS”; U.S. Provisional Patent Application No. 63 / 067,760, filed August 19, 2020, entitled “TECHNIQUES FOR DYNAMIC PDCP TIMERADJUSTMENT”; and U.S. Non-Provisional Patent Application No. 17 / 302,675, filed May 10, 2021, entitled “TECHNIQUES FOR TIMER ADJUSTMENT FOR PACKET LOSS”, which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to wireless communication, and techniques and apparatus for timer adjustment in response to packet loss. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard, issued by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include multiple base stations (BSs), which can support communication with multiple user equipment (UEs). UEs can communicate with base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, and an uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit-receive point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a universal protocol enabling different user equipment to communicate at the city, national, regional, and even global levels. New Radio (NR), also known as 5G, is a collection of enhancements to the LTE mobile standard issued by the 3rd Generation Partnership Project (3GPP). NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM, DFT-s-OFDM) on the uplink (UL); and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. With the continued growth in demand for mobile broadband access, further improvements to LTE, NR, and other radio access technologies remain highly valuable. Summary of the Invention

[0007] In some aspects, a method of wireless communication performed by a user equipment (UE) includes: receiving information indicating a timer value associated with a timer for discarding a packet data convergence protocol (PDCP) service data unit (SDU); determining that a timer modification condition is met; modifying the timer value based at least in part on the determination that the timer modification condition is met; and transmitting communication using the modified timer value.

[0008] In some respects, timer modification conditions are associated with uplink permission-restricted scenarios.

[0009] In some respects, uplink permission-restricted scenarios are at least partly based on the UE modifying its buffer state report due to the thermal mitigation conditions being met.

[0010] In some respects, the timer modification condition is based at least in part on the thermal mitigation condition, and the timer modification condition indicates that the timer value is increased at least in part based on the thermal mitigation condition being met.

[0011] In some respects, at least in part, the timer is disabled because the buffer status report is modified to indicate that there is no data in the UE's buffer.

[0012] In some respects, uplink permission-restricted scenarios are at least partly based on the gaps associated with the dual-standby configuration of the dual-subscriber identification module.

[0013] In some respects, at least in part, the timer is disabled because the length of the gap is uncertain at the beginning of the gap.

[0014] In some respects, the timer modification condition is based at least in part on the fact that the length of the gap meets a threshold.

[0015] In some respects, the timer value is increased to the length of the gap.

[0016] In some respects, the timer is disabled, at least in part, based on the fact that the length of the gap meets a threshold.

[0017] In some respects, uplink permission-restricted scenarios are at least partly based on the UE's block error rate (BLER).

[0018] In some respects, at least in part, the timer value is increased based on BLER meeting a threshold.

[0019] In some respects, the method includes determining the modified timer value based at least in part on multiple thresholds for BLER.

[0020] In some respects, at least in part, the timer is disabled based on BLER meeting a threshold.

[0021] In some respects, the uplink segmented bearer is configured for the UE at least in part, the primary radio link control entity of the uplink segmented bearer is associated with a BLER that meets a threshold at least in part, and the data segmentation threshold of the uplink segmented bearer is set to infinity at least in part, and the timer is disabled.

[0022] In some respects, the timer is disabled based at least in part on the uplink segmented bearer being configured for the UE, at least in part on the primary radio link control entity of the uplink segmented bearer being associated with a BLER that meets a threshold, and at least in part on the UE having a buffer size that is less than the data segmentation threshold of the uplink segmented bearer.

[0023] In some respects, the timer modification conditions are associated with a bearer that is configured to compress packets transmitted on that bearer.

[0024] In some respects, at least in part, the timer value is incremented based on the fact that the bearer is configured to compress packets transmitted on that bearer.

[0025] In some respects, at least in part, the timer value is disabled because the bearer is configured to compress packets transmitted on that bearer.

[0026] In some respects, this bearer is configured for robust header compression.

[0027] In some respects, this bearer is configured for uplink data compression.

[0028] In some aspects, a UE for wireless communication includes a memory and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: receive information indicating a timer value associated with a discarded PDCP SDU; determine that a timer modification condition is met; modify the timer value based at least in part on the determination that the timer modification condition is met; and transmit communication using the modified timer value.

[0029] In some respects, timer modification conditions are associated with uplink permission-restricted scenarios.

[0030] In some respects, uplink permission-restricted scenarios are at least partly based on the UE modifying its buffer state report due to the thermal mitigation conditions being met.

[0031] In some respects, the timer modification condition is based at least in part on the thermal mitigation condition, and the timer modification condition indicates that the timer value is increased at least in part based on the thermal mitigation condition being met.

[0032] In some respects, at least in part, the timer is disabled because the buffer status report is modified to indicate that there is no data in the UE's buffer.

[0033] In some respects, uplink permission-restricted scenarios are at least partly based on the gaps associated with the dual-standby configuration of the dual-subscriber identification module.

[0034] In some respects, at least in part, the timer is disabled because the length of the gap is uncertain at the start of the gap.

[0035] In some respects, the timer modification condition is based at least in part on the fact that the length of the gap meets a threshold.

[0036] In some respects, the timer value is increased to the length of the gap.

[0037] In some respects, the timer is disabled, at least in part, based on the fact that the length of the gap meets a threshold.

[0038] In some respects, uplink permission-restricted scenarios are at least partly based on the UE's BLER.

[0039] In some respects, at least in part, the timer value is increased based on BLER meeting a threshold.

[0040] In some respects, one or more processors are also configured to determine the modified timer value based at least in part on multiple thresholds for BLER.

[0041] In some respects, at least in part, the timer is disabled based on BLER meeting a threshold.

[0042] In some respects, the uplink segmented bearer is configured for the UE at least in part, the primary radio link control entity of the uplink segmented bearer is associated with a BLER that meets a threshold at least in part, and the data segmentation threshold of the uplink segmented bearer is set to infinity at least in part, and the timer is disabled.

[0043] In some respects, the timer is disabled at least in part based on the uplink segmented bearer being configured for the UE, at least in part based on the main radio link control entity of the uplink segmented bearer being associated with a BLER that meets a threshold, and at least in part based on the UE’s buffer size being less than the data segmentation threshold of the uplink segmented bearer.

[0044] In some respects, the timer modification conditions are associated with a bearer that is configured to compress packets transmitted on that bearer.

[0045] In some respects, at least in part, the timer value is incremented based on the bearer being configured to compress packets transmitted on that bearer.

[0046] In some respects, at least in part, the timer value is disabled based on the fact that the bearer is configured to compress packets transmitted on that bearer.

[0047] In some respects, this bearer is configured for robust header compression.

[0048] In some respects, this bearer is configured for uplink data compression.

[0049] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of the UE, cause the UE to: receive information indicating a timer value associated with discarding a PDCP SDU; determine that a timer modification condition is met; modify the timer value at least in part based on the determination that the timer modification condition is met; and use the modified timer value to transmit communication.

[0050] In some respects, timer modification conditions are associated with uplink permission-restricted scenarios.

[0051] In some respects, uplink permission-restricted scenarios are at least partly based on the UE modifying its buffer state report due to the thermal mitigation conditions being met.

[0052] In some respects, the timer modification condition is based at least in part on the thermal mitigation condition, and the timer modification condition indicates that the timer value is increased at least in part based on the thermal mitigation condition being met.

[0053] In some respects, at least in part, the timer is disabled because the buffer status report is modified to indicate that there is no data in the UE's buffer.

[0054] In some respects, uplink permission-restricted scenarios are at least partly based on the gaps associated with the dual-standby configuration of the dual-subscriber identification module.

[0055] In some respects, at least in part, the timer is disabled because the length of the gap is uncertain at the start of the gap.

[0056] In some respects, the timer modification condition is based at least in part on the fact that the length of the gap meets a threshold.

[0057] In some respects, the timer value is increased to the length of the gap.

[0058] In some respects, the timer is disabled, at least in part, based on the fact that the length of the gap meets a threshold.

[0059] In some respects, uplink permission-restricted scenarios are at least partly based on the UE's BLER.

[0060] In some respects, at least in part, the timer value is increased based on BLER meeting a threshold.

[0061] In some respects, the one or more instructions also cause the UE to determine the modified timer value based at least in part on multiple thresholds for BLER.

[0062] In some respects, at least in part, the timer is disabled based on BLER meeting a threshold.

[0063] In some respects, the uplink segmented bearer is configured for the UE at least in part, the main radio link control entity of the uplink segmented bearer is associated with the BLER that meets the threshold at least in part, and the data segmentation threshold of the uplink segmented bearer is set to infinity at least in part, and the timer is disabled.

[0064] In some respects, the timer is disabled at least in part based on the uplink segmented bearer being configured for the UE, at least in part based on the main radio link control entity of the uplink segmented bearer being associated with a BLER that meets a threshold, and at least in part based on the UE’s buffer size being less than the data segmentation threshold of the uplink segmented bearer.

[0065] In some respects, the timer modification conditions are associated with a bearer that is configured to compress packets transmitted on that bearer.

[0066] In some respects, at least in part, the timer value is incremented based on the bearer being configured to compress packets transmitted on that bearer.

[0067] In some respects, at least in part, the timer value is disabled based on the fact that the bearer is configured to compress packets sent on the bearer.

[0068] In some respects, this bearer is configured for robust header compression.

[0069] In some respects, this bearer is configured for uplink data compression.

[0070] In some aspects, an apparatus for wireless communication includes: components for receiving information indicating a timer value associated with a timer for discarding a PDCP SDU; components for determining that a timer modification condition is met; components for determining a modified timer value based at least in part on the timer modification condition being met; and components for transmitting communication using the modified timer value.

[0071] In some respects, timer modification conditions are associated with uplink permission-restricted scenarios.

[0072] In some respects, uplink permission-restricted scenarios are at least partly based on the UE modifying its buffer state report due to the thermal mitigation conditions being met.

[0073] In some respects, the timer modification condition is based at least in part on the thermal mitigation condition, and the timer modification condition indicates that the timer value is increased at least in part based on the thermal mitigation condition being met.

[0074] In some respects, at least in part, the timer is disabled because the buffer status report is modified to indicate that there is no data in the UE's buffer.

[0075] In some respects, uplink permission-restricted scenarios are at least partly based on the gaps associated with the dual-standby configuration of the dual-subscriber identification module.

[0076] In some respects, at least in part, the timer is disabled because the length of the gap is uncertain at the start of the gap.

[0077] In some respects, the timer modification conditions are at least partially based on the gap length satisfying a threshold.

[0078] In some respects, the timer value is increased to the length of the gap.

[0079] In some respects, the timer is disabled, at least in part, based on the fact that the length of the gap meets a threshold.

[0080] In some respects, uplink permission-restricted scenarios are at least partly based on the UE's BLER.

[0081] In some respects, at least in part, the timer value is increased based on BLER meeting a threshold.

[0082] In some respects, the device includes components for determining a modified timer value based at least in part on a plurality of thresholds for BLER.

[0083] In some respects, at least in part, the timer is disabled based on BLER meeting a threshold.

[0084] In some respects, the uplink segmented bearer is configured for the UE at least in part, the main radio link control entity of the uplink segmented bearer is associated with the BLER that meets the threshold at least in part, and the data segmentation threshold of the uplink segmented bearer is set to infinity at least in part, and the timer is disabled.

[0085] In some respects, the timer is disabled at least in part based on the uplink segmented bearer being configured for the UE, at least in part based on the main radio link control entity of the uplink segmented bearer being associated with a BLER that meets a threshold, and at least in part based on the UE’s buffer size being less than the data segmentation threshold of the uplink segmented bearer.

[0086] In some respects, the timer modification conditions are associated with a bearer that is configured to compress packets transmitted on that bearer.

[0087] In some respects, at least in part, the timer value is incremented based on the bearer being configured to compress packets transmitted on that bearer.

[0088] In some respects, at least in part, the timer value is disabled based on the fact that the bearer is configured to compress packets transmitted on that bearer.

[0089] In some respects, this bearer is configured for robust header compression.

[0090] In some respects, this bearer is configured for uplink data compression.

[0091] A method for wireless communication at a UE is described. The method may include: identifying data traffic to be transmitted according to an uplink license, the data traffic being associated with a first PDCP discard timer; determining a set of conditions associated with the uplink license, the UE, or both, the set of conditions being associated with the data rate of the uplink license; determining a set of parameters associated with the data traffic based on the determined set of conditions; determining a second PDCP discard timer different from the first PDCP discard timer based on the determined set of parameters; and using the second PDCP discard timer to transmit the data traffic according to the uplink license.

[0092] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: identify a data service to be transmitted under an uplink license, the data service being associated with a first PDCP discard timer; determine a set of conditions associated with the uplink license, the UE, or both, the set of conditions being associated with a data rate of the uplink license; determine a set of parameters associated with the data service based on the determined set of conditions; determine a second PDCP discard timer different from the first PDCP discard timer based on the determined set of parameters; and transmit the data service under the uplink license using the second PDCP discard timer.

[0093] Another apparatus for wireless communication at a UE is described. The apparatus may include components for: identifying a data service to be transmitted under an uplink license, the data service being associated with a first PDCP discard timer; determining a set of conditions associated with the uplink license, the UE, or both, the set of conditions being associated with the data rate of the uplink license; determining a set of parameters associated with the data service based on the determined set of conditions; determining a second PDCP discard timer different from the first PDCP discard timer based on the determined set of parameters; and using the second PDCP discard timer to transmit the data service under the uplink license.

[0094] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to perform the following steps: identifying a data service to be transmitted under an uplink license, the data service being associated with a first PDCP discard timer; determining a set of conditions associated with the uplink license, the UE, or both, the set of conditions being associated with the data rate of the uplink license; determining a set of parameters associated with the data service based on the determined set of conditions; determining a second PDCP discard timer, different from the first PDCP discard timer, based on the determined set of parameters; and using the second PDCP discard timer to transmit the data service under the uplink license.

[0095] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for selectively adjusting the first PDCP discard timer to generate the second PDCP discard timer, wherein determining the second PDCP discard timer may be based on selectively adjusting the first PDCP discard timer.

[0096] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include determining the expiration of a validity period associated with the second PDCP discard timer, and, based on the expiration of that validity period, using the first PDCP discard timer to send the operation, feature, component, or instruction of the data service.

[0097] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, determining the set of parameters associated with a data service may include operations, characteristics, components or instructions for determining one or more bearers associated with the data service, wherein the data service may be transmitted in accordance with the uplink license based on applying a second PDCP discard timer to one or more bearers associated with the data service.

[0098] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving an indication of a set of parameters associated with the data service from an application or program executed by the UE, wherein determining the set of parameters associated with the data service may be based on receiving the indication.

[0099] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining the set of parameters associated with a data service may include operations, features, components, or instructions for determining a bearer type associated with the data service, a QoS metric associated with the data service, a priority associated with the data service, a latency sensitivity metric associated with the data service, a reliability metric associated with the data service, or any combination thereof, wherein determining the second PDCP drop timer may be based on the bearer type, the QoS metric, the latency sensitivity metric, the reliability metric, or any combination thereof.

[0100] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the first duration of the first PDCP discard timer may be less than the second duration of the second PDCP discard timer.

[0101] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for determining that the amount of data traffic to be transmitted under the uplink license may be greater than or equal to a data traffic threshold, wherein the set of determination conditions may be based on determining that the amount of data traffic may be greater than or equal to the data traffic threshold.

[0102] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for determining an indication of the amount of data traffic based on a buffer status report (BSR), wherein determining the amount of data traffic may be greater than or equal to a data traffic threshold may be based on the BSR.

[0103] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include an indication of the data rate of an uplink transmission performed by a UE from a base station, and an operation, feature, component, or instruction to determine that the data rate of the uplink transmission may be greater than or equal to a maximum data rate associated with the uplink license, wherein the set of determination conditions may be based on determining that the data rate of the uplink transmission may be greater than or equal to the maximum data rate associated with the uplink license.

[0104] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for determining that the power level used to transmit the uplink transmission may be less than or equal to a threshold power level, wherein the set of determination conditions may be based on determining that the power level may be less than or equal to the threshold power level.

[0105] Some examples of the methods, apparatuses and non-transitory computer-readable media described herein may further include operations, features, components or instructions for determining that the thermal level of a UE may be greater than or equal to a threshold thermal level, wherein the set of determination conditions may be based on determining that the thermal level may be greater than or equal to the threshold thermal level.

[0106] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the data service using the second PDCP discard timer may include operations, features, components, or instructions for suppressing the transmission of data units of the data service based on the second PDCP discard timer.

[0107] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, suppressing the transmission of data units of the data service based on the second PDCP drop timer may include operations, features, components, or instructions for performing the following steps: determining a reception time at which each data unit in the data service can be received at the buffer of the UE; determining a buffer duration associated with each data unit in the data service based on the reception time; and discarding data units including a buffer duration that may be greater than or equal to the duration of the second PDCP drop timer.

[0108] The terms generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems, which are basically described herein with reference to the accompanying drawings and description and are illustrated as shown in the drawings and description.

[0109] The features and technical advantages of the disclosed examples have been outlined quite extensively above to better understand the specific embodiments described below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures to achieve the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their organization and operation, and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and is not intended to define limitations of the claims. Attached Figure Description

[0110] To gain a more detailed understanding of the foregoing features of this disclosure, reference can be made to various aspects (briefly outlined above), some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as the specification may allow for other equally valid aspects. The same reference numerals in different drawings may denote the same or similar elements.

[0111] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

[0112] Figure 2 This is a diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0113] Figure 3 This is a diagram illustrating an example of the user plane protocol stack and control plane protocol stack of a base station and core network communicating with a UE according to this disclosure.

[0114] Figures 4-7 This is a diagram illustrating an example of modifying the timer value of a Packet Data Convergence Protocol (PDCP) discard timer based at least in part on timer modification conditions, according to this disclosure.

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

[0116] Figure 9 and Figure 10 This is a block diagram of an example device for wireless communication according to the present disclosure.

[0117] Figure 11 An example of a wireless communication system that supports techniques for dynamic PDCP timer adjustment according to this disclosure is shown.

[0118] Figure 12 An example of a processing flow supporting a technique for dynamic PDCP timer adjustment according to this disclosure is shown.

[0119] Figure 13 A block diagram of a device supporting a technique for dynamic PDCP timer adjustment according to this disclosure is shown.

[0120] Figure 14 A block diagram of a device supporting a technique for dynamic PDCP timer adjustment according to this disclosure is shown.

[0121] Figure 15 A block diagram of a communication manager supporting a technique for dynamic PDCP timer adjustment according to this disclosure is shown.

[0122] Figure 16 A diagram of a system including a device supporting technology for dynamic PDCP timer adjustment, according to this disclosure, is shown.

[0123] Figure 17 A flowchart is shown illustrating a method for supporting techniques for dynamic PDCP timer adjustment according to various aspects of this disclosure.

[0124] Figure 18 A flowchart is shown illustrating a method for supporting dynamic PDCP timer adjustment according to this disclosure.

[0125] Figure 19 A flowchart is shown illustrating a method for supporting dynamic PDCP timer adjustment according to this disclosure. Detailed Implementation

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

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

[0128] It should be noted that although terms commonly associated with 5G or NR radioaccess technology (RAT) may be used to describe aspects herein, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0129] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to this disclosure. Among other examples, the wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network. The wireless network 100 may include multiple base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, Transmit / Receive Point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0130] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or other cell types. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and allow restricted access for UEs associated with that femtocell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macrocell can be called a macro BS. A BS for a picocell can be called a pico BS. A BS for a femtocell can be called a femto BS or a home BS. Figure 1 In the example shown, BS 110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” are used interchangeably herein.

[0131] In some respects, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some respects, BSs may use any suitable transport network to interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0132] The wireless network 100 may also include relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS 110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, relay, etc.

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

[0134] Network controller 130 can be coupled to a group of base stations and can provide coordination and control for these base stations. Network controller 130 can communicate with the base stations via backhaul. Base stations can also communicate with each other, for example, directly or indirectly via wireless or wired backhaul.

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

[0136] Some UEs can be considered machine-type communication (MTC) UEs, or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, and / or location tags, which can communicate with base stations, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity to or to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet-of-Things (IoT) devices, and / or can be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components and / or memory components. In some respects, the processor components and memory components can be coupled together. For example, processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

[0139] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc., based on frequency or wavelength. For example, devices in Wireless Network 100 can communicate using an operating frequency band with a first frequency range (FR1) spanning from 410 MHz to 7.125 GHz, and / or can communicate using an operating frequency band with a second frequency range (FR2) spanning from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. Similarly, FR2 is often referred to as the "millimeter wave" band, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) recognized as a "millimeter wave" band by the International Telecommunication Union (ITU). Therefore, unless otherwise stated, it should be understood that the terms "sub-6 GHz," etc., if used herein, can broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise stated, it should be understood that the terms "millimeter wave," etc., if used herein, can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is anticipated that the frequencies included in FR1 and FR2 may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0140] The UE 120 and base station 110 of the wireless network 100 can support techniques for adjusting the Dynamic Packet Data Convergence Protocol (PDCP) drop timer. Specifically, the UE 120 of the wireless network 100 can be configured to dynamically adjust the PDCP drop timer and / or dynamically select a new PDCP drop timer based on conditions associated with the uplink granted data rate, a set of parameters associated with uplink data services, or both. By selectively adjusting and / or selecting a new PDCP drop timer that can be used to transmit data services, the UE 120 of the wireless network 100 can reduce and / or eliminate the amount of data units (e.g., protocol data units (PDUs) and serving data units (SDUs)) dropped by the PDCP drop timer in response to brief, intermittent interruptions in wireless communication.

[0141] For example, UE 120 of wireless network 100 may use a first PDCP discard timer (e.g., the timer value of a timer associated with a discarded PDCPSDU) to identify data services that will be transmitted according to an uplink license. The uplink license, the first PDCP discard timer, or both may be configured by the network (e.g., signaled to UE 120 via base station 110). In some aspects, the data service may be associated with an application or program performed or implemented by UE 120. For example, the identified data service may be associated with a video messaging application or service (e.g., FaceTime, WebEx, Zoom), a gaming application or service, a virtual reality / augmented reality application or service, a file transfer protocol (FTP), an internet browsing session or application, or any combination thereof.

[0142] In some aspects, UE 120 may determine a set of conditions (e.g., timer modification conditions) associated with uplink permission and / or UE 120 itself, which are related to the data rate (e.g., throughput) of the uplink permission. Specifically, UE 120 may determine a set of conditions that may negatively impact the data rate associated with the uplink permission, such as conditions associated with uplink permission-restricted scenarios or compression / recompression conditions. For example, the UE may identify conditions that may cause brief, intermittent interruptions in radio transmission (e.g., radio link conditions, UE 120 conditions), which may prevent data traffic transmission and cause a first PDCP drop timer to drop data units. This set of conditions may include the amount of data traffic in UE 120's buffer, the data rate allocated for uplink transmission configured by the network, the maximum data rate of the uplink permission allocated to UE 120, the heat / power level at UE 120 that may prevent uplink transmission, or any combination thereof.

[0143] For example, UE 120 may determine that the data rate allocated to a video messaging application (e.g., FaceTime) exceeds the maximum data rate associated with the uplink license allocated to UE 120. In this example, UE 120 may determine that the accumulated rate of data traffic associated with the video messaging application within UE 120's buffer may be faster than the rate at which UE 120 transmits data traffic using the uplink license. At this point, UE 120 may recognize that this condition is associated with the uplink license and may cause data units to be discarded according to a first PDCP discard timer. As another example, UE 120 may determine that UE 120's thermal profile and / or power profile exceed corresponding thresholds, and thus may cause temporary throttling of uplink transmissions. In this example, UE 120 may determine that UE 120's thermal profile and / or power profile may temporarily reduce the transmission rate of data traffic, and may therefore cause data units to be discarded according to a first PDCP discard timer.

[0144] When UE 120 identifies a set of conditions that may lead to the loss of data units, it can identify a set of parameters associated with the data service. These parameters may include the type of data service (e.g., video messaging data service, gaming data service, internet browsing data service), the bearer type associated with the data service (e.g., signaling radio bearer (SRB), dedicated radio bearer (DRB)), the QoS requirements of the data service, the latency sensitivity of the data service (e.g., the degree to which user experience depends on temporary latency), the priority of the data service, or any combination thereof. At this point, UE 120 can determine the set of conditions associated with the data service to determine whether UE 120 should dynamically adjust the first PDCP drop timer to be used for transmitting the data service (e.g., modify the timer value).

[0145] Therefore, UE 120 can determine a second PDCP drop timer based on the determined set of parameters associated with the data service (e.g., the timer value can be modified). For example, in some cases, UE 120 can determine that a data service (such as video messaging data service) is highly sensitive to latency (e.g., latency due to application-level retransmission) and determine that the data service has a budget for an extended PDCP drop timer based on end-to-end stream-level latency characteristics. In this case, UE 120 can extend (e.g., prolong) the first PDCP drop timer to generate a second PDCP drop timer and can utilize the second PDCP drop timer to transmit the data service. By utilizing a second PDCP drop timer that is longer than the first PDCP drop timer, UE 120 can reduce the amount of data units dropped (e.g., discarded) according to the corresponding PDCP drop timer, thereby improving user experience and overall QoS.

[0146] In some respects, UE 120 may apply the second PDCP drop timer based on each bearer, based on the type of data service, or based on both. For example, UE 120 may identify one or more bearers associated with a data service and may apply the second PDCP drop timer only to transmissions on the one or more bearers associated with that data service. As another example, UE 120 may identify a first type of data service that is more sensitive to latency (e.g., video messaging data service) and a second type of data service that is less sensitive to latency (e.g., internet browsing data service). In this example, UE 120 may apply the second PDCP drop timer only to transmissions of the first type of data service.

[0147] Additionally or alternatively, UE 120 may apply a second PDCP drop timer for a given (e.g., predetermined) duration. In this respect, the new and / or selectively adjusted PDCP drop timer may be associated with a validity period. For example, upon identifying conditions that may negatively impact UE 120's ability to transmit data services and determining parameters associated with data services, UE 120 may be configured to utilize a second (e.g., extended) PDCP drop timer for a determined validity period. In this example, UE 120 may use the second PDCP drop timer to transmit data services during its validity period and subsequently use the first PDCP drop timer to transmit data services after the validity period expires. In this respect, in some cases, the techniques described herein can be configured to address poor wireless communication quality for short, intermittent interruptions in wireless communication, rather than longer, sustained periods.

[0148] The techniques described herein enable dynamic adjustment of the PDCP drop timer. Specifically, the techniques described herein allow UE 120 to selectively adjust the PDCP drop timer (or select a new PDCP drop timer) to reduce or eliminate the amount of data units dropped in response to brief, intermittent interruptions in wireless communication. By enabling dynamic adjustment of the PDCP drop timer, the techniques described herein can improve the quality and efficiency of wireless communication within the wireless network 100 and enhance the overall user experience.

[0149] As mentioned above, Figure 1 This is provided as an example. Other examples may be related to... Figure 1 The descriptions are different.

[0150] Figure 2 This is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein typically T ≥ 1 and R ≥ 1.

[0151] At base station 110, transmitting processor 220 can: receive data from one or more UEs from data source 212; select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from the UE; process (e.g., encode and modulate) the UE's data based at least in part on the selected (multiple) MCS for each UE; and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, authorizations, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively.

[0152] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM) to obtain the received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data of UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), and / or CQI. In some aspects, one or more components of the UE 120 may be included in housing 284.

[0153] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

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

[0155] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting RSRP, RSSI, RSRQ, and / or CQI). The transmitting processor 264 can also generate reference symbols for one or more reference signals. Symbols from the transmitting processor 264 can be pre-encoded (if applicable) by TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 254) of UE 120 can be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modulator and / or demodulator 254, MIMO detector 256, receiver processor 258, transmitter processor 264, and / or TX MIMO processor 266. A processor (e.g., controller / processor 280) and memory 282 may be used with the transceiver to perform aspects of any of the methods described herein.

[0156] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide decoded data to data sink 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 for scheduling UE 120 for downlink and / or uplink communication. In some aspects, modulators and demodulators (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some aspects, base station 110 includes transceivers. The transceiver may include any combination of antenna(s) 234, modulator and / or demodulator 232, MIMO detector 236, receiver processor 238, transmitter processor 220, and / or TX MIMO processor 230. A processor (e.g., controller / processor 240) and memory 242 may be used to perform aspects of any of the methods described herein.

[0157] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2 Any other component(s) may perform one or more techniques associated with timer adjustments for packet loss, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component(s) can perform or direct, for example Figure 8 The operation of process 800 and / or other processes described herein. Memory 242 and 282 may store data and program code of base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, transformation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 8 The operation of process 800 and / or other processes described herein. In some aspects, execution instructions may include run instructions, translation instructions, compilation instructions, and / or interpretation instructions.

[0158] In some aspects, UE 120 may include: components for receiving information indicating a timer value associated with a discarded PDCP SDU; components for determining that a timer modification condition is met; components for modifying the timer value based at least in part on the determination that the timer modification condition is met; and components for transmitting communication using the modified timer value. In some aspects, these components may include combinations of... Figure 2 One or more components of the described UE 120, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258 and / or similar components.

[0159] As mentioned above, Figure 2 This is provided as an example. Other examples may be related to... Figure 2 The descriptions are different.

[0160] Figure 3 This is a diagram illustrating an example 300 of a base station 110 communicating with a UE 120 and a user plane protocol stack and a control plane protocol stack of the core network according to this disclosure.

[0161] On the user plane, UE 120 and BS 110 may include corresponding physical (PHY) layers, medium access control (MAC) layers, radio link control (RLC) layers, PDCP layers, and service data adaptation protocol (SDAP) layers. User plane functions handle user data transmission between UE 120 and BS 110. On the control plane, UE 120 and BS 110 may include corresponding radio resource control (RRC) layers. Furthermore, UE 120 may include a NAS layer that communicates with the non-access stratum (NAS) layer of the access and management mobility function (AMF). The AMF may be associated with the core network (such as a 5G core network (5GC) or a next-generation radio access network (NG-RAN)) associated with BS 110. Control plane functions handle the transmission of control information between the UE and the core network. Generally, if the first layer is farther from the PHY layer than the second layer, then the first layer is considered higher than the second layer. For example, the PHY layer can be considered the lowest layer, while the SDAP / PDCP / RLC / MAC layers can be considered higher than the PHY layer and lower than the RRC layer. Figure 3 The application (APP) layer, not shown, can be higher than the SDAP / PDCP / RLC / MAC layers. In some cases, an entity can handle the services and functions of a given layer (e.g., a PDCP entity can handle the services and functions of the PDCP layer), although the description herein refers to the layer itself as handling services and functions.

[0162] The RRC layer handles communications related to configuring and operating UE 120, such as: broadcasting system information related to the access stratum (AS) and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of RRC connections between the UE and NG-RAN, including the addition, modification, and release of carrier aggregation, as well as the addition, modification, and release of dual connections; security functions, including key management; establishment, configuration, maintenance, and release of SRB and DRB; mobility functions (e.g., handover and context transfer, UE cell selection and reselection, and control of cell selection and reselection, inter-RAT mobility); Quality of Service (QoS) management functions; control of UE measurement reports and notifications; detection and recovery of radio link failures; and NAS message delivery between the NAS layer and lower layers of UE 120. The RRC layer is often referred to as Layer 3 (L3).

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

[0164] The SDAP or RRC / NAS layer can map QoS flows or control information to radio bearers. Therefore, it can be said that the SDAP layer processes QoS flows on the transmitting side. The SDAP layer can provide QoS flows to the PDCP layer via the corresponding radio bearers. The PDCP layer can map radio bearers to RLC channels. The PDCP layer can handle various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), transmission of user data, reordering and deduplication detection (if ordered delivery to layers above the PDCP layer is required), PDCP PDU routing (in the case of segmented bearers), retransmission, encryption and decryption of PDCP SDUs, PDCP SDU dropping (e.g., according to timers, as described elsewhere herein), PDCP reconstruction and data recovery in RLC acknowledged mode (AM), and PDCP PDU duplication. The PDCP layer can handle similar services and functions on the control plane, including sequence numbering, encryption, decryption, integrity protection, transmission of control plane data, deduplication detection, and PDCP PDU duplication.

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

[0166] The RLC layer can provide the MAC layer with data mapped to logical channels. The services and functions of the MAC layer include: mapping between logical channels and transport channels (as described below by the PHY layer); multiplexing MAC SDUs belonging to one or different logical channels into / from transport blocks (TBs) delivered to the physical layer on the transport channel; scheduling information reporting; error correction via hybrid ARQ (HARQ); priority handling between UEs via dynamic scheduling; priority handling between logical channels of a UE via logical channel prioritization; and padding.

[0167] The MAC layer can package data from logical channels into TBs and provide TBs to the PHY layer on one or more transport channels. (For example, combining...) Figure 2 In more detail, the PHY layer can handle various operations related to the transmission of data signals. The PHY layer is often referred to as Layer 1 (L1).

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

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

[0170] As mentioned above, Figure 3 This is provided as an example. Other examples may be related to... Figure 3 The descriptions are different.

[0171] DRBs can be configured with drop timers. A drop timer indicates a time after which a given SDU will be dropped if it is not transmitted for any reason. For example, the PDCP layer can receive PDCPSDUs and buffer PDCP SDUs for transmission. The PDCP layer can start a timer for the PDCP SDU upon reception. When the drop timer expires for the PDCP SDU, or when the PDCP SDU is successfully delivered, the PDCP entity can drop the PDCP SDU and the corresponding PDCP data PDU (if generated). If the corresponding PDCP data PDU has already been provided to a lower layer, the lower layer is informed of the drop. Dropping PDCP SDUs can save UE resources in scenarios where UE communication has been interrupted for some reason, or in scenarios where higher-priority services have higher priority than lower-priority services (e.g., lower-priority service PDCPSDUs can be dropped). PDCP drop timers are designed to meet terminal application and QoS requirements. Specifically, by discarding (e.g., dropping) "stale" data units according to the PDCP discard timer, the UE can prevent delays in the transmission of subsequent data units, thereby improving overall QoS.

[0172] In certain situations, dynamic radio conditions can cause brief, intermittent interruptions in wireless communication, leading to frequent data unit (PDCP) drop timers being discarded based on the PDCP drop timer, thus degrading the end-user experience. While these brief, intermittent interruptions are unlikely to have a long-term negative impact on wireless communication quality, current PDCP drop timer technology can still result in frequent data unit drops, thereby reducing QoS. For example, there are various conditions under which dropping PDCP SDUs may lead to packet loss, which is more detrimental to UE performance than buffering PDCP SDUs for a period longer than specified by the drop timer. Two such conditions include uplink-permitted scenarios and compression / recompression scenarios.

[0173] Uplink license-constrained scenarios refer to situations where the UE needs to transmit more data than the uplink license available to the UE can accommodate. In some aspects, uplink license-constrained scenarios may be caused by thermal mitigation conditions. Thermal mitigation conditions can be associated with temperature thresholds. When a UE becomes hot due to processing demands during high-throughput scenarios, the UE can determine, at least in part, that a thermal mitigation condition has been met based on a temperature threshold. If the thermal mitigation condition is met, the UE can modify the BSR to indicate less buffered traffic than actually exists at the UE (or even zero buffered traffic if the UE's temperature is high enough), thereby reducing the number of uplink licenses provided to the UE and reducing the processing load at the UE. However, thermal mitigation conditions may persist for an indeterminate amount of time (e.g., longer than a drop timer), which may increase the chance of PDCP SDU drops.

[0174] Another example of uplink-licensed scenarios is associated with long tune-aways that can be performed by a multiple subscriber identity module (multi-SIM) UE. For instance, a dual-SIM dual-standby UE can allow one SIM to enter a long tune-away (referred to as a gap associated with a dual-SIM dual-standby configuration) while the other SIM performs active transmissions. The duration of the gap may be indeterminate and may exceed the length of the drop time, potentially increasing the chance of PDCP SDU drop.

[0175] The third example of an uplink permissioned scenario is related to the PHY layer block error rate (BLER), leading to frequent HARQ retransmissions. Frequent HARQ retransmissions can cause delays in transmitting new services. In some cases, the delay may exceed the length of the drop time, thereby increasing the chance of PDCP SDU drop.

[0176] Compression / recompression scenarios may involve robust header compression (ROHC) or uplink data compression (UDC). In ROHC and UDC, if packets on a given bearer are lost or dropped (e.g., due to PDCP SDU drop), all subsequent packets on that bearer may need to be recompressed due to the way ROHC and UDC are performed. This results in a significant processing burden and increases the likelihood that one or more subsequent packets will also be dropped.

[0177] Some of the techniques and apparatus described herein enable the adjustment of the timer value of a PDCP drop timer (referred to herein as the timer associated with the dropped PDCP SDU) based at least in part on timer modification conditions. The adjustment of the timer value can be considered as determining a second PDCP drop timer, where the initial timer value of the PDCP drop timer can be considered as the first PDCP drop timer. For example, as described above, the timer modification conditions can relate to uplink license-restricted scenarios or compression / recompression scenarios. In some aspects, the UE can extend the timer value (e.g., causing a given PDCP SDU to be buffered for a longer period, which reduces the chance of a given PDCP SDU being dropped). In some aspects, the UE can disable the PDCP drop timer, which further reduces the chance of a given PDCP SDU being dropped. In some aspects, the UE can apply the second PDCP drop timer for a predetermined duration, apply the second PDCP drop timer on a per-bearer basis, or both. Additionally or alternatively, the UE can apply the second PDCP drop timer based on the type of data service in question (e.g., data service priority, data service latency sensitivity). Therefore, the UE's drop rate is reduced, which increases throughput and saves the UE's processing resources. The technologies and devices described in this article may be particularly beneficial for non-real-time services.

[0178] Figures 4 to 7 These are schematic diagrams illustrating examples 400, 500, 600, and 700 of modifying the timer value of a PDCP discard timer based at least in part on timer modification conditions according to this disclosure. As shown, examples 400, 500, 600, and 700 include UE 120 and BS 110. Examples 400, 500, and 600 all illustrate examples of modifying timer values ​​based at least in part on uplink license-restricted scenarios. Therefore, references to modifying timer values ​​based at least in part on uplink license-restricted scenarios can be made to any one or more of examples 400, 500, and 600. In some aspects, uplink license-restricted scenarios can be based at least in part on the uplink licensed data rate. For example, if the uplink licensed data rate is limited at least in part based on one or more of the conditions described herein, the UE can be considered to be in an uplink license-restricted scenario. Example 700 is an example related to modifying timer values ​​at least in part based on compression / recompression conditions.

[0179] In some respects, timer modification conditions can be relevant to dual connectivity scenarios. In dual connectivity scenarios, the UE 120 can use one or more radio access technologies (RATs) to maintain two or more connections. Examples include multi-radio DC (MR-DC), E-UTRA-NR DC (EN-DC), and NR DC. In dual connectivity scenarios, timer modification conditions (such as BLER-based conditions, multiple subscriber identification module (SIM) gaps, thermal mitigation conditions, etc.) can be triggered on one or two connections.

[0180] In some respects, timer modification conditions can be related to a dual SIM dual active (DSDA) configuration. In a DSDA configuration, UE 120 is associated with two SIMs (and therefore with two subscribers). Both SIMs can maintain concurrent active connections to the network. In a DSDA configuration, radio frequency (RF) resources can be shared between the two SIMs. Therefore, uplink transmission losses may occur due to the shared RF resources. In a DSDA configuration, timer modification conditions can be met due to uplink transmission losses associated with shared RF resources (such as if the amount or rate of uplink transmissions on a given SIM is interrupted).

[0181] In some respects, timer modification conditions can be related to non-terrestrial networks (NTNs). For example, NTNs may be affected by differences in scheduling modes, where different UEs covered by a base station may use different scheduling modes, or where the UE and the base station may use different scheduling modes. Differences in NTN scheduling modes can lead to uplink communication interruptions for UE120. Timer modification conditions can indicate thresholds associated with uplink communication interruptions, such as a threshold block error rate, a threshold number of failed communications, etc.

[0182] In some respects, timer modification conditions can be related to radiation thresholds, such as maximum allowable exposure (MPE) thresholds or specific absorption rate (SAR) thresholds. For example, an MPE or SAR threshold may lead to throttling or limiting of certain transmission resources, such as transmit power, uplink resources, specific beam directions, etc. Such throttling or limiting may cause uplink transmission interruptions in the UE. Timer modification conditions may be based at least in part on thresholds associated with SAR or MPE limitations, such as threshold block error rate, threshold number of failed communications, the presence of SAR or MPE limitations, etc.

[0183] In some aspects, timer modification conditions may involve interference associated with the coexistence of radio access technologies (RATs). For example, operation associated with a first RAT may interfere with communication associated with a second RAT. In some aspects, timer modification conditions may be based at least in part on thresholds associated with interference caused by coexistence, such as a threshold block error rate, a threshold number of failed communications, coexistence conditions (e.g., based at least in part on identifying that the first RAT is interfering with the second RAT), etc.

[0184] In some respects, timer modification conditions may be related to unlicensed spectrum. For example, a UE 120 operating in unlicensed spectrum may be subject to a listen-before-transmit (LBT) requirement, whereby the UE 120 must listen to the channel for a period of time before reserving channel resources for transmission. Failure of the LBT can result in the UE 120 lacking sufficient resources to transmit uplink or sidelink communication. In some respects, timer modification conditions may be based at least in part on thresholds associated with unlicensed spectrum, such as a threshold block error rate, a threshold number of failed communications, or unlicensed spectrum conditions (e.g., at least in part based on the identification that an LBT failure has caused communication interruption for the UE 120).

[0185] Figure 4 Example 400 is an example in which the timer modification condition is at least in part based on the thermal mitigation condition of UE 120.

[0186] As shown by reference numeral 410 in the attached figure, BS 110 can send configuration information to UE 120. As illustrated, the configuration information can indicate the timer value of the timer associated with the discarded PDCP SDU. For example, the configuration information can indicate the configuration of the PDCP discard timer for UE 120, such as the initial value associated with the PDCP discard timer. In some aspects, the configuration information can be associated with the bearer. In some aspects, the configuration information can indicate timer modification conditions. For example, the configuration information can indicate a threshold associated with timer modification and can indicate how the timer value should be modified, at least in part, based on that threshold. Examples of timer modification conditions and corresponding modifications to the timer value are described in more detail below.

[0187] As shown by reference numeral 420 in the attached figure, UE 120 can determine that a timer modification condition has been met. In Example 400, the timer modification condition is based at least in part on a thermal mitigation condition at UE 120. For example, UE 120 may be configured with a threshold temperature. If the temperature associated with UE 120 meets the threshold (meaning the thermal mitigation condition is met), UE 120 can modify the buffer status report to indicate a reduced buffer status (e.g., less data in UE 120's buffer), thereby reducing the amount of uplink clearance provided to UE 120 and reducing uplink throughput. By reducing uplink throughput, processor usage of UE 120 can be reduced, thereby reducing temperature. However, reducing uplink throughput may increase the number of PDCP SDUs dropped based at least in part on timers associated with dropping PDCP SDUs, thereby increasing processor usage and reducing communication performance of UE 120.

[0188] As shown by reference numeral 430 in the attached figure, UE 120 can modify or disable a timer value, at least in part, based on the timer modification condition being met. For example, UE 120 can increase the timer value so that a given PDCP SDU is buffered for a longer period before being dropped, thereby reducing the number of dropped PDCP SDUs. As another example, UE 120 can disable a timer (e.g., disable a configured time period when the timer modification condition is met, and / or similar processing) so that PDCP SDUs are buffered until transmission, thereby reducing or eliminating uplink service interruptions for UE 120.

[0189] In some aspects, UE 120 may determine the modified timer value (e.g., by how much the timer value will be modified) based at least in part on timer modification conditions. For example, UE 120 may use multiple thresholds corresponding to different modified timer values ​​(e.g., different modifications to the timer value). As another example, UE 120 may use a first threshold to determine that the timer value will be modified and a second threshold to determine that the timer will be disabled. In Example 400, the second threshold may correspond to a higher temperature than the first threshold, thereby mitigating more aggressive thermal relief conditions. In some aspects, the modified timer value may be based at least in part on whether the buffer status report is modified to a non-zero value (indicating at least some buffered data at UE 120) or a zero value (associated with a critical condition and / or indicating that there is no data in the buffer of UE 120). For example, UE 120 may disable the timer at least in part based on the buffer status report being modified to a zero value and may increase the timer value at least in part based on the buffer status report being modified to a non-zero value.

[0190] As shown by reference numeral 440 in the attached figure, UE 120 can use modified timer values ​​to transmit communications. For example, the PDCP layer of UE 120 can generate PDCP PDUs of PDCP SDUs based on the modified timer values, allowing a larger proportion (or all) of the PDCP SDUs to be provided to lower layers for processing and transmission. In this way, the reliability of UE 120 is improved in uplink-permitted scenarios, which reduces processor usage associated with retransmission communications and improves the utilization of network resources.

[0191] Figure 5 Example 500 is an example in which the timer modification condition is at least in part based on the gap of UE 120 associated with a dual SIM dual standby (DSDS) configuration of UE 120. In Example 500, UE 120 is a DSDS UE, meaning that UE 120 is associated with two SIMs. One SIM can be active at a time. When the first SIM is active, the second SIM can enter a gap, called a tuning gap or long tuning off, until the second SIM is activated. During the gap, UE 120 can buffer traffic for the second SIM. However, buffering traffic may cause UE 120's PDCP drop timer to time out for that traffic, causing UE 120 to drop the traffic, thereby reducing the reliability of UE 120 on the uplink and using processing and communication resources associated with retransmitting the traffic.

[0192] As shown in the figure, UE 120 can receive configuration information from BS 110. Combined with... Figure 4 This configuration information is described in more detail.

[0193] As shown by reference numeral 510, UE 120 can determine that a timer modification condition is met. In Example 500, the timer modification condition relates to a gap (e.g., long tune-off) associated with the DSDS configuration. For example, UE 120 can determine that the length of the gap meets a threshold, the length of the gap is longer than the timer value of the timer associated with the discarded PDCP SDU, etc. Therefore, as shown by reference numeral 520, UE 120 can modify the timer value or disable the timer. In some aspects, UE 120 can increase the timer value such that the timer length exceeds the gap length. In some aspects, UE 120 can increase the timer value by an amount equal to the gap length. In some aspects, UE 120 can disable the timer at least in part based on the gap length meeting a threshold. Therefore, services associated with the gap (e.g., services associated with an inactive SIM associated with the gap) will not be dropped due to the timer associated with the discarded PDCP SDU, which improves the uplink reliability of UE 120 and saves communication and processing resources. As shown by reference numeral 530 in the attached figure, UE 120 can send communications based on a modified timer value (or based on a deactivated timer), such as in combination with... Figure 4 More detailed description.

[0194] Figure 6 Example 600 in the example is an instance where the timer modification conditions are at least partially based on the BLER of UE 120. The BLER of UE 120 is a physical layer parameter indicating how many blocks (e.g., TBs, etc.) have not been successfully received. A higher BLER corresponds to more unreceived blocks. UE 120 can perform retransmission of unreceived blocks based on feedback (such as HARQ feedback) indicating which blocks have been received. The BLER can be determined at least partially based on the feedback. However, retransmission of unreceived blocks can take precedence over the processing of PDCP SDUs in the PDCP layer of UE 120, meaning that in high BLER scenarios, these PDCP SDUs tend to be buffered for longer periods. Therefore, in high BLER scenarios, timers associated with discarded PDCP SDUs are more likely to time out, which further reduces the uplink reliability of UE 120 and consumes processing and communication resources.

[0195] As shown in the figure, UE 120 can receive configuration information from BS 110. Combined with... Figure 4 The configuration information is described in more detail.

[0196] As shown by reference numeral 610, UE 120 can determine that a timer modification condition is met. In Example 600, the timer modification condition relates to the BLER of UE 120. For example, UE 120 can determine that the BLER meets a threshold. Therefore, as shown by reference numeral 620, UE 120 can modify the timer value or disable the timer. In some aspects, UE 120 can increase the timer value at least partially based on the BLER meeting threshold. In some aspects, UE 120 can disable the timer at least partially based on the BLER meeting threshold. Therefore, in high BLER scenarios, services may not be frequently dropped due to timers associated with dropping PDCP SDUs, which improves the uplink reliability of UE 120 and saves communication and processing resources. As shown by reference numeral 630, UE 120 can send communication based on the modified timer value (or based on deactivating the timer), such as in combination with... Figure 4 More detailed description.

[0197] In some respects, UE 120 can determine the modified timer value based at least in part on timer modification conditions (e.g., it can determine how much the timer value will be modified). For example, UE 120 can use multiple thresholds for BLER, corresponding to different modified timer values ​​(e.g., different modifications to the timer value). As another example, UE 120 can use a first threshold to determine that the timer value will be modified and a second threshold to determine that the timer will be disabled. In Example 600, the second threshold can correspond to a higher BLER than the first threshold, thereby mitigating the greater latency associated with a higher BLER.

[0198] In some respects, the modified timer value can be configured at least in part based on uplink split bearer configuration. For example, in an uplink split bearer scenario (e.g., if an uplink split bearer is configured), if the uplink data splitting threshold (e.g., a threshold indicating how uplink data is split between two or more paths of the uplink split bearer) is set to infinity, and if the primary RLC path is associated with the threshold BLER, then UE 120 can disable the timer. As another example, in an uplink split bearer scenario, if the uplink data splitting threshold is set to T, if the primary RLC path is associated with the threshold BLER, and if the outstanding buffer size of UE 120 is less than T, then UE 120 can disable the timer.

[0199] The examples of uplink license-restricted scenarios provided in Examples 400, 500, and 600 are merely examples. The techniques and apparatus described in Examples 400, 500, and 600 can be applied to other uplink license-restricted scenarios, such as those associated with flow control for the processor, memory, or dual data readout of UE120, and virtual radio link failure (RLF) on a secondary carrier. A virtual RLF is a mechanism for flow control achieved by stopping reception or transmission on a secondary carrier.

[0200] Figure 7 Example 700 is an example of modifying a timer value associated with discarding a PDCP SDU based at least in part on compression / recompression conditions. For example, if a compression algorithm such as ROHC, UDC, or similar is activated for a given bearer, the timer modification conditions can be satisfied for that given bearer.

[0201] As shown in the figure, UE 120 can receive configuration information from BS 110. Combined with... Figure 4 The configuration information is described in more detail.

[0202] As shown by reference numeral 710, UE 120 can determine that a timer modification condition is met. In Example 700, the timer modification condition relates to ROHC or UDC being configured for UE 120. For example, UE 120 can determine that ROHC or UDC is configured for a given bearer (e.g., the given bearer is configured to compress packets transmitted on the given bearer). As another example, UE 120 can determine that a threshold number of PDCP SDUs are dropped in connection with ROHC or UDC being configured for a given bearer. Therefore, as shown by reference numeral 720, UE 120 can modify the timer value or disable the timer. In some aspects, UE 120 can increase the timer value at least in part based on ROHC or UDC being configured. In some aspects, UE 120 can disable the timer at least in part based on ROHC or UDC being configured. Therefore, when uplink compression is activated, the drop of PDCP SDUs can be reduced, which reduces processor usage associated with recompressing UE 120's transmissions. As shown by reference numeral 730 in the attached figure, UE 120 can send communications based on a modified timer value (or based on a deactivated timer), such as in combination with... Figure 4 More detailed description.

[0203] In some respects, UE 120 can increase or disable timer values, at least in part, based on the bearer being configured with integrity protection. In this case, UE 120 may have already calculated Message Authentication Code-Integrity (MAC-I), so dropping packets could result in costly reprocessing. By disabling the timer, the rate of packet dropping can be reduced, thereby reducing processor usage associated with reprocessing dropped packets and packets associated with dropped packets (e.g., after dropped packets).

[0204] As indicated above, Figure 4-7 This is provided as an example. Other examples may be provided in conjunction with [the relevant information]. Figure 4-7 The descriptions are different.

[0205] Figure 8 This is a diagram illustrating an example process 800 performed by a UE, for example, according to this disclosure. Example process 800 is an example in which a UE (e.g., UE 120) performs operations associated with timer adjustment techniques for packet loss.

[0206] like Figure 8 As shown, in some aspects, process 800 may include receiving information indicating a timer value associated with the discarding of the PDCP SDU (block 810). For example, as described above, the UE (e.g., using...) Figure 9 The receiving component 902 can receive information indicating the timer value associated with the discarded PDCP SDU.

[0207] like Figure 8 As further shown, in some aspects, process 800 may include determining that a timer modification condition is met (block 820). For example, as described above, the UE (e.g., using...) Figure 9 The determining component 908 can determine that the timer modification condition is met.

[0208] like Figure 8 As further shown, in some aspects, process 800 may include modifying a timer value at least in part based on the determination that a timer modification condition is met (block 830). For example, as described above, the UE (e.g., using...) Figure 9 The modification component 910 can modify the timer value at least in part based on the determination that the timer modification condition is met.

[0209] like Figure 8 As further shown, in some aspects, process 800 may include sending communication using a modified timer value (block 840). For example, as described above, the UE (e.g., using...) Figure 9The sending component 904 can use a modified timer value to send communication.

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

[0211] In the first aspect, the timer modification conditions are associated with uplink permission-restricted scenarios.

[0212] In the second aspect, either alone or in combination with the first aspect, the uplink permission-restricted scenario is based at least in part on the UE modifying the UE's buffer state report due to the thermal mitigation condition being met.

[0213] In a third aspect, alone or in combination with one or more of the first and second aspects, the timer modification condition is based at least in part on the thermal relief condition, and the timer modification condition indicates that the timer value is increased at least in part based on the thermal relief condition being met.

[0214] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the timer is disabled, at least in part, based on the fact that the buffer status report is modified to indicate that there is no data in the buffer of the UE.

[0215] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the uplink permission-restricted scenario is based at least in part on the gap associated with the dual-standby configuration of the dual-subscriber identification module.

[0216] In the sixth aspect, the timer is disabled, either alone or in combination with one or more of the first to fifth aspects, based at least in part on the fact that the length of the gap is uncertain when the gap is initiated.

[0217] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the timer modification condition is based at least in part on the length of the gap satisfying a threshold.

[0218] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the timer value is increased to a value equal to the length of the gap.

[0219] In the ninth aspect, the timer is disabled, either alone or in combination with one or more of the first to eighth aspects, at least in part based on the length of the gap satisfying a threshold.

[0220] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the uplink license-restricted scenario is at least partially based on the UE's BLER.

[0221] In the eleventh aspect, the timer value is incremented, either alone or in combination with one or more of the first to tenth aspects, at least in part based on the BLER satisfying a threshold.

[0222] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 800 includes determining, at least in part, based on multiple thresholds for BLER (e.g., using...). Figure 9 The timer value modified by component 908.

[0223] In the thirteenth aspect, the timer is disabled, either alone or in combination with one or more of the first to twelfth aspects, at least in part based on the BLER meeting a threshold.

[0224] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, at least in part based on the uplink segmented bearer configured for the UE, at least in part based on the main radio link control entity of the uplink segmented bearer associated with a BLER that meets a threshold, and at least in part based on the data segmentation threshold of the uplink segmented bearer being set to infinity, the timer being disabled.

[0225] In the fifteenth aspect, the timer is disabled, either alone or in combination with one or more of the first to fourteenth aspects, based at least in part on the uplink segmented bearer being configured for the UE, based at least in part on the primary radio link control entity of the uplink segmented bearer being associated with a BLER that meets a threshold, and based at least in part on the UE’s buffer size being less than the data segmentation threshold of the uplink segmented bearer.

[0226] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the timer modification condition is associated with the bearer being configured to compress packets transmitted on that bearer.

[0227] In the seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, the timer value is incremented, at least in part based on the bearer being configured to compress packets transmitted on the bearer.

[0228] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, at least in part based on the bearer being configured to compress packets transmitted on the bearer, the timer value is disabled.

[0229] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the bearer is configured for robust header compression.

[0230] In the twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the bearer is configured for uplink data compression.

[0231] In the twenty-first aspect, either alone or in combination with one or more of the first to twentieth aspects, at least in part based on the fact that the UE's bearer is configured with integrity protection, the timer value is incremented or the timer is disabled.

[0232] In aspect twenty-two, alone or in combination with one or more of aspects one through twenty-one, the communication is associated with non-real-time services.

[0233] although Figure 8 An example block diagram of process 800 is shown, but in some respects, process 800 may include more than Figure 8 The number of boxes shown can be more, fewer, different, or arranged differently. Additionally or alternatively, two or more boxes in process 800 can be executed in parallel.

[0234] Figure 9 This is a block diagram of an example device 900 for wireless communication. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902 and a transmitting component 904, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 900 can use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (such as a UE, a base station, or another wireless communication device). As further shown, device 900 may include one or more of the determining component 908 or modifying component 910, and other examples.

[0235] In some respects, device 900 can be configured to perform the functions described herein. Figure 4-7 The described one or more operations. Additionally or alternatively, the device 900 may be configured to perform one or more processes described herein, such as Figure 8 The process is 800. In some respects, Figure 9 The device 900 and / or one or more components shown may include the above-described combination. Figure 2 One or more components of the UE described. Additionally or alternatively, Figure 9 One or more components shown can be combined above. Figure 2 Implemented in one or more of the described components. Additionally or alternatively, one or more of the components in this group may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

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

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

[0238] Receiving component 902 can receive information indicating a timer value associated with the discarding of the PDCP SDU. Determining component 908 can determine that a timer modification condition is met. In some aspects, determining component 908 can determine the modified timer value based at least in part on multiple thresholds for BLER. In some aspects, determining component 908 can include the above-mentioned combination Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receive processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. Modification component 910 can modify a timer value based at least in part on the determination that a timer modification condition is met. In some aspects, modification component 910 may include the above-described combination... Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receive processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. Transmit component 904 can transmit communications using modified timer values.

[0239] Figure 9 The number and arrangement of components shown are provided as an example. In practice, with... Figure 9 Compared to what is shown, there can be additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The set (one or more) components shown can perform actions described by Figure 9 The other set of components shown performs one or more functions.

[0240] Figure 10 This is a block diagram of an example device 1000 for wireless communication. Device 1000 may be a BS, or a BS may include device 1000. In some aspects, device 1000 includes a receiving component 1002 and a transmitting component 1004, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1000 can use the receiving component 1002 and the transmitting component 1004 to communicate with another device 1006 (such as a UE, a base station, or another wireless communication device). As further shown, device 1000 may include a determining component 1008 or a modifying component 1010, among other examples.

[0241] In some respects, device 1000 can be configured to perform the functions described herein. Figure 3-7 One or more operations described herein. Additionally or alternatively, the device 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process 800 or a combination thereof. In some respects, Figure 10 The device 1000 and / or one or more components shown may include the above-described combination. Figure 2 The described BS or one or more components. Additionally or alternatively, Figure 10 One or more components shown can be combined above. Figure 2 Implemented in one or more of the described components. Additionally or alternatively, one or more of the components in this group may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

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

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

[0244] The transmitting component 1004 can transmit information indicating the timer value associated with the discarded PDCP SDU. The determining component 1008 can determine that the timer modification condition is met. In some aspects, the determining component 1008 may include the above-mentioned combination Figure 2 The described BS includes one or more antennas, demodulators, MIMO detectors, receiver processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. Modification component 1010 can modify a timer value based at least in part on the determination that a timer modification condition is met. In some aspects, modification component 1010 may include the above-described combination... Figure 2 The described BS includes one or more antennas, demodulators, MIMO detectors, receiver processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. The receiver component 1002 can receive communications at least in part based on modified timer values.

[0245] Figure 10The number and arrangement of components shown are provided as an example. In reality, with... Figure 10 Compared to what is shown, there can be additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 10 The two or more components shown can be implemented within a single component, or Figure 10 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 10 The set (one or more) components shown can perform actions described by Figure 10 The other set of components shown performs one or more functions.

[0246] Figure 11 An example of a wireless communication system 1100 supporting techniques for dynamic PDCP timer adjustment according to this disclosure is shown. In some examples, the wireless communication system 1100 may implement aspects of the wireless network 100. The wireless communication system 1100 may include a base station 1105 and a UE 1115, which may be examples of a UE 120 and a base station 110, as referenced. Figure 1 As described.

[0247] UE 1115 can communicate with base station 1105 using communication link 1110. In some cases, communication link 1110 may include an example of an access link (e.g., a Uu link). Communication link 1110 may include a bidirectional link, which may include both uplink and downlink communication. In one aspect, UE 1115 can use communication link 1110 to send uplink transmissions, such as uplink messages or uplink signals, to base station 1105, and base station 1105 can use communication link 1110 to send downlink data transmissions, such as downlink messages or downlink signals, to UE 1115.

[0248] In some aspects, UE 120 may determine a set of conditions associated with uplink licensing and / or UE 120 itself, which are related to the data rate (e.g., throughput) of the uplink license. Specifically, UE 120 may determine a set of conditions that may negatively impact the data rate associated with the uplink license. For example, the UE may identify conditions (e.g., radio link conditions, UE 120 conditions) that may cause brief, intermittent interruptions in radio transmission, which may prohibit data service transmission and cause a first PDCP drop timer to drop data units. This set of conditions may include the amount of data service in UE 120's buffer, the data rate allocated for uplink transmission by network configuration, the maximum data rate of the uplink license allocated to UE 120, the heat / power level at UE 120 that may prohibit uplink transmission, or any combination thereof.

[0249] For example, base station 1105 may send uplink grant 1120 to UE 1115, which will be used by UE 1115 to transmit uplink transmissions. Uplink grant 1120 may include a set of time resources, a set of frequency resources, a set of spatial resources, or any combination thereof. In some aspects, uplink grant 1120 may be associated with a given set of data services 1130 at UE 1115, a given type of data service 1130 at UE 1115, or both. In some aspects, UE 1115 may be configured to determine the maximum data rate (e.g., maximum throughput) associated with uplink grant 1120.

[0250] In some aspects, base station 1105 may send downlink transmission 1125 to UE 1115, wherein downlink transmission 1125 includes control information, configuration information, or both. For example, downlink transmission 1125 may include an indication of a first PDCP discard timer, which will be used by UE 1115 when sending uplink transmissions (e.g., uplink transmissions including data service 1130). As another example, downlink transmission 1125 may include an indication of the data rate of the uplink transmission to be performed by UE 1115. For example, the data rate indication in downlink transmission 1125 may be associated with a given type of data service 1130 (e.g., video messaging data service 1130) to be sent by UE 1115. Downlink transmissions may include RRC messages, configuration messages, or both. In some aspects, information indicated via downlink transmission 1125 may be associated with uplink transmissions performed pursuant to uplink permission 1120. In this respect, base station 1105 can send downlink transmission 1125 based on sending uplink permission 1120.

[0251] In some aspects, UE 1115 can determine the first PDCP drop timer. In some aspects, UE 1115 can determine the first PDCP drop timer based on uplink permission 1120, downlink transmission 1125 (e.g., configuration information, control information), or both. For example, base station 1105 can configure UE 1115 with the first PDCP drop timer based on the type of data service 1130 to be transmitted by UE 1115, field logs, terminal application QoS level requirements, sensitivity of data service 1130, or any combination thereof (e.g., via downlink transmission 1125). For example, when DRB is configured at UE 1115 for uplink transmissions, base station 1105 can configure UE 1115 with the first PDCP drop timer as part of the PDCP configuration. Additionally or alternatively, UE 1115 can be configured (e.g., pre-configured) with the first PDCP drop timer, such that UE 1115 determines the first PDCP drop timer autonomously (e.g., without signaling from base station 1105). In some cases, UE 1115 can be configured with a first PDCP drop timer for durations of 10ms, 110ms, 120ms, 40ms, 50ms, 75ms, 100ms, 150ms, 1100ms, 1150ms, 1200ms, 500ms, 750ms, 150ms or different durations.

[0252] In some aspects, UE 1115 can identify data service 1130 to be transmitted. In some aspects, UE 1115 can identify data service 1130 to be transmitted based on (e.g., according to) uplink permission 1120, downlink transmission 1125 (e.g., configuration information, control information), determining a first PDCP discard timer, or any combination thereof. For example, UE 1115 can determine that the identified data service 1130 will be transmitted based on uplink permission 1120 and / or using the first PDCP discard timer. In some aspects, UE 1115 can identify data service 1130 waiting to be transmitted within a buffer (e.g., a watermark) of UE 1115. Therefore, in some cases, UE 1115 can identify data service 1130 based on the BSR associated with the buffer of UE 1115. Additionally or alternatively, UE 1115 can determine the data rate associated with data service 1130. For example, UE 1115 can determine the data rate that will be transmitted in the uplink transmission of data service 1130. In this example, the data rate associated with data service 1130 can be indicated to UE 1115 via downlink transmission 1125.

[0253] UE 1115 may determine a set of conditions associated with uplink grant 1120, UE 1115 itself, or both. Specifically, this set of conditions may be associated with the data rate (e.g., throughput) of uplink grant 1120, the data rate of uplink transmissions including data service 1130, or both. In this regard, the set of conditions associated with uplink grant, uplink transmissions, and / or the data rate of data service 1130 may include conditions that may affect the data rate at which UE 1115 can transmit uplink transmissions, including radio link conditions, operating conditions at UE 1115, or any combination thereof. In some aspects, UE 1115 may determine the set of conditions associated with the data rate of uplink grant 1120 based on receiving uplink grant 1120, receiving downlink transmissions 1125, determining a first PDCP drop timer, identifying data service 1130, or any combination thereof.

[0254] In some aspects, this set of conditions may include the amount of data traffic 1130 in the buffer of UE 1115, the data rate allocated for uplink transmission at UE 1115, the maximum data rate associated with the uplink license 1120 allocated to UE 1115, the thermal level and / or power level at UE 1115, or any combination thereof. For example, UE 1115 may determine that the amount of data traffic 1130 to be transmitted according to uplink license 1120 is greater than or equal to a data traffic threshold. UE 1115 may determine the indication of the amount of data traffic 1130 based on the BSR. In this example, the condition associated with the data rate of uplink license 1120 may include the amount of data traffic 1130 exceeding the data traffic threshold (e.g., COndition(condition) = Quantity). DT ≥Thresh DT Such conditions may indicate or imply that data traffic 1130 may accumulate in the buffer at UE 1115, which could result in the loss (e.g., discarding) of data units if the first PDCP discard timer is used.

[0255] As another example, UE 1115 can determine the data rate of the uplink transmission performed by UE 1115 (e.g., the data rate associated with the identified data service 1130). UE 1115 can determine the uplink transmission data rate based on an indication received from base station 1105 via downlink transmission 1125. UE 1115 can further determine the maximum data rate associated with uplink grant 1120 received from base station 1105. In this example, UE 1115 can determine that the determined uplink transmission data rate (e.g., the determined data rate for transmitting the identified data service 1130) is greater than or equal to the maximum data rate associated with uplink grant 1120. In this example, the condition associated with the data rate of uplink grant 1120 may include the data rate of the uplink transmission performed by UE 1115 exceeding the maximum data rate of uplink grant 1120 (e.g., Condition = DataRate). UL Transmissions ≥MaxDataRate UL Grant Such conditions may indicate or imply that the accumulation of data service 1130 in the buffer at UE 1115 may be faster than the transmission of data service 1130 according to uplink permission 1120, which may result in the data unit being dropped (e.g., discarded) if the first PDCP drop timer is used.

[0256] As another example, UE 1115 can determine that the power level (e.g., power distribution) used at UE 1115 for transmitting uplink transmissions is less than or equal to a threshold power level (e.g., threshold power distribution). In this example, the condition associated with the data rate of uplink permission 1120 may include the power level used for transmitting uplink transmissions being less than or equal to a threshold power level (e.g., Condition = Power). UL Transmissions ≤Thresh Power Such conditions may indicate or imply that UE 1115 may be unable to transmit data service 1130 at a given data rate and may therefore experience uplink data throttling, resulting in the accumulation of data service 1130 in the buffer at UE 1115, which may result in the data unit being dropped (e.g., discarded) if the first PDCP drop timer is used.

[0257] As another example, UE 1115 can determine that the heat level (e.g., heat distribution) of UE 1115 is greater than or equal to a threshold heat level (e.g., threshold heat distribution). In this example, the conditions associated with the data rate of uplink permission 1120 may include a heat level for transmitting uplink transmissions that is greater than or equal to a threshold heat level (e.g., Condition = Thermal). UE≥Thresh Thermal Such conditions may indicate or imply that UE 1115 may be overheating or otherwise unable to transmit data service 1130 at a given data rate, and may therefore experience uplink data throttling, resulting in the accumulation of data service 1130 in the buffer at UE 1115, which may result in data units being dropped (e.g., discarded) if the first PDCP drop timer is used.

[0258] In some aspects, UE 1115 may determine a set of parameters associated with data service 1130. In some aspects, UE 1115 may determine a set of parameters (e.g., a set of features) associated with data service 1130 based on a determined set of conditions associated with uplink grant 1120, data service 1130, or both data rates. Additionally or alternatively, UE 1115 may determine the set of parameters associated with data service 1130 based on receiving uplink grant 1120, receiving downlink transmission 1125 (e.g., configuration information, control information), determining a first PDCP drop timer, identifying the data service 1130 to be transmitted, or any combination thereof. In some aspects, UE 1115 may determine a set of parameters associated with data service 1130 such that UE 1215 can use this set of parameters to determine whether the first PDCP drop timer should be selectively adjusted and / or replaced with a second PDCP drop timer.

[0259] In this regard, the parameter set may include any parameters or characteristics associated with the identified data service 1130, including but not limited to the bearer associated with data service 1130, the bearer type associated with data service 1130 (e.g., SRB, DRB), the QoS metric associated with data service 1130, the priority associated with data service 1130, the latency sensitivity metric associated with data service 1130, the reliability metric associated with data service 1130, or any combination thereof. These parameters and / or additional parameters may indicate to UE 1115 whether selectively adjusting the first PDCP drop timer and / or replacing the first PDCP drop timer is beneficial and / or to what extent.

[0260] For example, when data service 1130 is associated with higher priority, higher QoS metrics, higher latency sensitivity metrics (e.g., data service 1130 is very prone to performance degradation in the event of latency), higher reliability metrics (e.g., effective service requires highly reliable communication), or any combination thereof, UE 1115 may be more inclined to selectively adjust the first PDCP drop timer and / or select the second PDCP drop timer to reduce or eliminate the amount or percentage of data units dropped or lost in response to brief, intermittent interruptions in wireless communication. Conversely, when data service 1130 is associated with lower priority, lower QoS metrics, lower latency sensitivity metrics (e.g., data service 1130 is not prone to performance degradation in the event of latency), lower reliability metrics (e.g., effective service does not require ultra-reliable communication), or any combination thereof, UE 1115 may be less inclined to selectively adjust the first PDCP drop timer and / or select the second PDCP drop timer because the data service 1130 in question may be less prone to dropping and / or losing packets due to brief, intermittent interruptions in wireless communication.

[0261] In some cases, UE 1115 may receive indications of a set of parameters associated with a data service from an application or program (e.g., FaceTime) executed by UE 1115. In this regard, an application, service, or program executed by UE 1115 and associated with data service 1130 may notify UE 1115 of one or more parameters (e.g., features) associated with data service 1130. Applications, services, or programs executed by UE 1115 may include video messaging applications, gaming applications, internet browsing applications, etc. For example, UE 1115 may identify video messaging data service 1130 associated with a video messaging application (e.g., FaceTime) executed by UE 1115. In this example, the video messaging application may send indications of a set of parameters associated with data service 1130 to one or more components of UE 1115 (e.g., modem, processor, or other components of UE 1115). For example, in the context of video messaging data service 1130, a video messaging application may send indications of video messaging data service 1130 associated with high latency sensitivity metrics and high QoS metrics to one or more components of UE 1115.

[0262] In some respects, UE 1115 may determine a second PDCP drop timer, different from the first PDCP drop timer, based on a set of parameters associated with data service 1130. For example, if UE 1115 determines, based on this set of parameters, that data service 1130 is highly susceptible to quality degradation in the event of data unit loss or dropping (e.g., lost / dropped packets, PDUs, SDUs), UE 1115 may determine a second PDCP drop timer to reduce and / or eliminate lost data units. Additionally or alternatively, UE 1115 may determine the second PDCP drop timer based on receiving uplink grant 1120, receiving downlink transmission 1125 (e.g., configuration information, control information), determining the first PDCP drop timer, identifying the data service 1130 to be transmitted, determining a set of conditions associated with the uplink grant 1120 and / or the data rate of data service 1130, or any combination thereof.

[0263] In some respects, UE 1115 can determine the second PDCP discard timer by selecting a new PDCP discard timer (e.g., a second PDCP discard timer) different from the first PDCP discard timer, selectively modifying the first PDCP discard timer to generate the second PDCP discard timer, or both. For example, in some cases, UE 1115 can selectively adjust (e.g., extend, prolong) the first PDCP discard timer to generate the second PDCP discard timer such that the first duration of the first PDCP discard timer is less than the second duration of the second PDCP discard timer. PDCP1 <Duration PDCP2 For example, the first PDCP drop timer may have a duration of 500ms, while the second PDCP drop timer may have a duration of 1000ms. In this example, by selecting a new PDCP drop timer and / or selectively modifying the first PDCP drop timer so that the second PDCP drop timer is longer than the first PDCP drop timer, more time can be allowed between the arrival of data units (e.g., packets, PDUs, SDUs) in the buffer and their transmission before being dropped / discarded, which can thereby reduce the amount / percentage of dropped data units.

[0264] When determining the second PDCP discard timer, UE 1115 can use the second PDCP discard timer to send data service 1130 to base station 1105. For example, UE 1115 can use (e.g., according to, based on) the second PDCP discard timer to send data service 1130-a to base station 1105. UE 1115 can send data service 1130-a to base station 1105 based on uplink grant 1120, by using the second PDCP discard timer, or both. In this respect, UE 1115 can send data service 1130-a based on receiving uplink grant 1120, determining the second PDCP discard timer, or both. Additionally or alternatively, UE 1115 may transmit data service 1130-a based on receiving downlink transmission 1125 (e.g., configuration information, control information), determining a first PDCP discard timer, identifying the data service 1130 to be transmitted, determining a set of conditions associated with the uplink license 1120 and / or the data rate of data service 1130, determining a set of parameters associated with data service 1130, or any combination thereof.

[0265] As previously noted herein, UE 1115 can be configured to suppress the transmission of data units (e.g., packets, PDUs, SDUs) of data service 1130-a based on (e.g., according to, using) the second PDCP discard timer, thereby transmitting data service 1130-a based on (e.g., according to, using) the second PDCP discard timer. For example, UE 1115 can determine the reception time at which each data unit in data service 1130-a is received at a buffer in UE 1115. In this example, UE 1115 can determine the buffer duration associated with each data unit in data service 1130-a based on the reception time. The term "buffer duration" can be used herein to refer to the duration during which each data unit remains in the buffer before being transmitted. Therefore, the buffer duration of a data unit can be defined as the duration between the time the data unit arrives at the buffer and the time UE 1115 transmits the data unit. Continuing with the same example, after determining the buffer duration of the corresponding data unit, UE 1115 may discard (e.g., drop or otherwise suppress transmission) the data unit, including the data unit whose buffer duration is greater than or equal to the duration of the second PDCP discard timer (e.g., if the buffer duration of the data unit is greater than or equal to the duration of the second PDCP discard timer, then the data unit is discarded).

[0266] In some respects, UE 1115 can transmit data service 1130-a by applying a second PDCP drop timer to one or more bearers and / or bearer types associated with the data service. For example, as previously noted herein, UE 1115 can identify one or more bearers associated with data service 1130-a. In this example, UE 1115 can transmit data service 1130-a by applying a second PDCP drop timer to one or more bearers of data service 1130-a. At this point, UE 1115 can drop or discard data units transmitted via one or more identified bearers according to the second PDCP drop timer, as discussed previously herein.

[0267] In some aspects, UE 1115 can determine the expiration date of the validity period associated with the second PDCP discard timer. The validity period associated with the second PDCP discard timer can refer to the duration for which the PDCP discard timer is used to transmit data service 1130-a. In this respect, UE 1115 can initiate the validity period based on the start of using the second PDCP discard timer to transmit data service 1130-a, and can transmit data service 1130-a based on the second PDCP discard timer until the expiration date. In some aspects, UE 1115 can determine the validity period associated with the second PDCP discard timer based on determining the second PDCP discard timer. Alternatively or additionally, UE 1115 may determine the validity period associated with the second PDCP discard timer based on receiving uplink grant 1120, receiving downlink transmission 1125 (e.g., configuration information, control information), determining a first PDCP discard timer, identifying the data service 1130 to be transmitted, determining a set of conditions associated with the data rate of uplink grant 1120 and / or data service 1130, determining a set of parameters associated with data service 1130, or any combination thereof.

[0268] When the expiration of the validity period associated with the second PDCP discard timer is determined, UE 1115 may use the first PDCP discard timer to transmit data service 1130-b. In some aspects, UE 1215 may use the first PDCP discard timer to transmit data service 1130-b based on the determination of the expiration of the validity period associated with the second PDCP discard timer. Additionally or alternatively, when the validity period associated with the second PDCP discard timer expires, UE 1115 may use a third PDCP discard timer, different from the first and / or second PDCP discard timer, to transmit data service 1130-b.

[0269] The techniques described herein enable dynamic adjustment of the PDCP drop timer. Specifically, the techniques described herein allow UE 1115 to selectively adjust the PDCP drop timer (or select a new PDCP drop timer) to reduce or eliminate the amount of data units dropped in response to brief, intermittent interruptions in wireless communication. By implementing dynamic adjustment of the PDCP drop timer, the techniques described herein can improve the quality and efficiency of wireless communication within the wireless communication system 1100 and enhance the overall user experience.

[0270] Figure 12 An example of a process flow 1200 supporting techniques for dynamic PDCP timer adjustment according to this disclosure is shown. In some examples, process flow 1200 may be implemented in aspects of wireless network 100, wireless communication system 1100, or both, or implemented by them. Process flow 1200 may show determining a first PDCP drop timer, determining a set of conditions associated with the uplink permitted data rate, determining a set of parameters associated with the identified data service, determining a second PDCP drop timer, and using the second PDCP drop timer to transmit the data service, as referenced. Figure 1-11 As described, and other aspects.

[0271] In some respects, the processing flow 1200 may include a UE 1215 and a base station 1105, which may be examples of the corresponding devices described herein. Figure 12 The UE 1215 shown in the figure can be Figure 11 The example of UE 1115 is shown below. Similarly, Figure 12 The base station 1205 shown can be Figure 11 An example of base station 1105 shown.

[0272] In some aspects, the operations shown in processing flow 1200 can be performed by hardware (e.g., including circuitry, processing blocks, logic components, and other components), code executed by a processor (e.g., software or firmware), or any combination thereof. Alternative examples can be implemented below, in which some steps are performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.

[0273] At 1220, base station 1205 can send an uplink grant to UE 1215, which will be used by UE 1215 to send uplink transmissions. The uplink grant may include a set of time resources, a set of frequency resources, a set of spatial resources, or any combination thereof. In some aspects, the uplink grant may be associated with a given set of data services at UE 1215, a given type of data service at UE 1215, or both. In some aspects, UE 1215 may be configured to determine the maximum data rate (e.g., maximum throughput) associated with the uplink grant.

[0274] At 1225, base station 1205 may send downlink transmissions to UE 1215, wherein the downlink transmissions include control information, configuration information, or both. For example, the downlink transmissions may include an indication of a first PDCP discard timer, which will be used by UE 1215 when sending uplink transmissions. As another example, the downlink transmissions may include an indication of the data rate of the uplink transmission to be performed by UE 1215. For example, the indication of the data rate in the downlink transmission may be associated with a given type of data service (e.g., video messaging data service) to be sent by UE 1215. The downlink transmissions may include RRC messages, configuration messages, or both. In some aspects, the information indicated via the downlink transmissions may be associated with uplink transmissions performed based on an uplink license received at 1220. In this respect, base station 1205 may send downlink transmissions at 1225 based on sending an uplink license at 1220.

[0275] At 1230, UE 1215 can determine the first PDCP drop timer. In some aspects, UE 1215 can determine the first PDCP drop timer based on uplink permission received at 1220, downlink transmissions received at 1225 (e.g., configuration information, control information), or both. For example, base station 1205 can configure UE 1215 with the first PDCP drop timer based on the type of data to be transmitted by UE 1215, field logs, terminal application QoS level requirements, data service sensitivity, or any combination thereof (e.g., via downlink transmissions at 1225). In some aspects, base station 1205 can configure UE 1215 with the first PDCP drop timer as part of PDCP configuration. Additionally or alternatively, UE 1215 can determine the first PDCP drop timer autonomously (e.g., without signaling from base station 1205).

[0276] At 1235, UE 1215 can identify the data service to be transmitted. In some aspects, UE 1215 can identify the data service to be transmitted based on (e.g., according to) an uplink grant received at 1220, downlink transmissions received at 1225 (e.g., configuration information, control information), a first PDCP discard timer determined at 1230, or any combination thereof. For example, UE 1215 can determine that the identified data service will be transmitted based on an uplink grant and / or using a first PDCP discard timer. In some aspects, UE 1215 can identify data services waiting to be transmitted within a buffer (e.g., a watermark) of UE 1215. Therefore, in some cases, at 1235, UE 1215 can identify the data service based on the BSR. Additionally or alternatively, UE 1215 can determine the data rate associated with the data service. For example, UE 1215 can determine the data rate at which the uplink transmission of the data service will be transmitted. In this example, the data rate associated with the data service can be indicated to UE 1215 via a downlink transmission received at 1225.

[0277] At 1240, UE 1215 may determine a set of conditions associated with uplink grant, UE 1215 itself, or both. Specifically, this set of conditions may be associated with the uplink grant data rate (e.g., throughput). In this respect, the set of conditions associated with the uplink grant data rate may include conditions that could affect the data rate at which UE 1215 can transmit uplink transmissions, including radio link conditions, operating conditions at UE 1215, or any combination thereof. In some aspects, UE 1215 may determine the set of conditions associated with the uplink grant data rate based on receiving uplink grant at 1220, receiving downlink transmission at 1225, determining a first PDCP drop timer at 1230, identifying data traffic at 1235, or any combination thereof.

[0278] In some aspects, the set of conditions may include the amount of data traffic in the buffer of UE 1215, the data rate allocated for uplink transmission at UE 1215, the maximum data rate associated with the uplink license allocated to UE 1215, the thermal level and / or power level at UE 1215, or any combination thereof. For example, UE 1215 may determine that the amount of data traffic identified in 1235 that will be transmitted according to the uplink license is greater than or equal to a data traffic threshold. UE 1215 may determine the indication of the amount of data traffic based on the BSR. In this example, the condition associated with the uplink licensed data rate may include the amount of data traffic exceeding the data traffic threshold (e.g., Condition = Quantity). DT ≥ThreshDT Such conditions may indicate or imply that data traffic may accumulate in the buffer at UE1215, which could result in data units being dropped (e.g., discarded) if the first PDCP drop timer is used.

[0279] At 1245, UE 1215 can determine a set of parameters associated with the data service. In some aspects, UE 1215 can determine the set of parameters associated with the data service (e.g., a set of features) based on a set of conditions determined at 1240. Additionally or alternatively, UE 1215 can determine the set of parameters associated with the data service based on receiving uplink permission at 1220, receiving downlink transmissions (e.g., configuration information, control information) at 1225, determining a first PDCP discard timer at 1230, identifying the data service at 1235, or any combination thereof. Furthermore, in some cases, UE 1215 can receive an indication of the parameter set from an application or program (e.g., FaceTime) executed by UE 1215. In some aspects, UE 1215 can determine the set of parameters associated with the data service such that UE 1215 can use this set of parameters to determine whether the first PDCP discard timer should be selectively adjusted and / or replaced with a second PDCP discard timer.

[0280] In this regard, the parameter set may include any parameters or characteristics associated with the identified data service, including but not limited to the bearer associated with the data service, the bearer type associated with the data service (e.g., SRB, DRB), the QoS metric associated with the data service, the priority associated with the data service, the latency sensitivity metric associated with the data service, the reliability metric associated with the data service, or any combination thereof. These parameters and / or additional parameters may indicate to the UE 1215 whether selectively adjusting and / or replacing the first PDCP drop timer is beneficial and / or to what extent.

[0281] For example, when data services are associated with higher priority, higher QoS metrics, higher latency sensitivity metrics (e.g., data services are prone to performance degradation in the event of latency), higher reliability metrics (e.g., effective service requires highly reliable communication), or any combination thereof, UE 1215 may be more inclined to selectively adjust the first PDCP drop timer and / or select the second PDCP drop timer to reduce or eliminate the amount or percentage of data units dropped or lost in response to brief, intermittent interruptions in wireless communication. Conversely, when data services are associated with lower priority, lower QoS metrics, lower latency sensitivity metrics (e.g., data services are less prone to performance degradation in the event of latency), lower reliability metrics (e.g., effective service does not require ultra-reliable communication), or any combination thereof, UE 1215 may be less inclined to selectively adjust the first PDCP drop timer and / or select the second PDCP drop timer, because the data services in question may be less likely to drop and / or lose packets due to brief, intermittent interruptions in wireless communication.

[0282] In some aspects, applications, services, or programs performed by UE 1215 and associated with data services can notify UE 1215 of one or more parameters (e.g., features) associated with the data service. Applications, services, or programs performed by UE 1215 may include video messaging applications, gaming applications, internet browsing applications, etc. For example, in 1235, UE 1215 can identify a video messaging service associated with a video messaging application (e.g., FaceTime) performed by UE 1215. In this example, the video messaging application can send indications of a set of parameters associated with the data service to one or more components of UE 1215 (e.g., modem, processor, or other components of UE 1215). For example, in the context of a video messaging data service, the video messaging application can send indications to one or more components of UE 1215 that the video messaging data service is associated with high latency sensitivity metrics and high QoS metrics.

[0283] At 1250, UE 1215 can determine a second PDCP drop timer that is different from the first PDCP drop timer. In some aspects, UE 1215 can determine the second PDCP drop timer based on a set of parameters associated with data services determined at 1245. For example, if UE 1215 determines, based on this set of parameters, that data services are highly susceptible to quality degradation in the event of lost or discarded data units (e.g., lost / discarded packets, PDUs, SDUs), UE 1215 can determine the second PDCP drop timer at 1250 to reduce and / or eliminate lost data units. Additionally or alternatively, UE 1215 can determine the second PDCP drop timer based on receiving uplink permission at 1220, receiving downlink transmissions (e.g., configuration information, control information) at 1225, determining the first PDCP drop timer at 1230, identifying data services at 1235, determining a set of conditions associated with data rates at 1240, or any combination thereof.

[0284] In some respects, UE 1215 can determine the second PDCP discard timer by selecting a new PDCP discard timer (e.g., a second PDCP discard timer) different from the first PDCP discard timer, selectively modifying the first PDCP discard timer to generate the second PDCP discard timer, or both. For example, in some cases, UE 1215 can selectively adjust (e.g., extend, prolong) the first PDCP discard timer to generate the second PDCP discard timer such that the first duration of the first PDCP discard timer is less than the second duration of the second PDCP discard timer (e.g., Duration). PDCP1 <Duration PDCP2 For example, the first PDCP drop timer may have a duration of 500ms, while the second PDCP drop timer may have a duration of 1000ms. In this example, by selecting a new PDCP drop timer and / or selectively modifying the first PDCP drop timer so that the second PDCP drop timer is longer than the first PDCP drop timer, more time can be allowed between the arrival of data units (e.g., packets, PDUs, SDUs) in the buffer and their transmission before being dropped / discarded, which can thereby reduce the amount / percentage of dropped data units.

[0285] At 1255, UE 1215 can transmit data services to base station 1205. UE 1215 can transmit data services to base station 1205 based on uplink permission, by using a second PDCP discard timer, or both. At this point, UE 1215 can transmit data services at 1255 based on receiving uplink permission at 1220, determining a second PDCP discard timer at 1250, or both. Additionally or alternatively, UE 1215 can transmit data services at 1255 based on receiving downlink transmissions (e.g., configuration information, control information) at 1225, determining a first PDCP discard timer at 1230, identifying data services at 1235, determining a set of conditions associated with the data rate at 1240, determining a set of parameters associated with the data service at 1245, or any combination thereof.

[0286] As previously noted, UE 1215 can be configured to suppress the transmission of data units (e.g., packets, PDUs, SDUs) of a data service based on (e.g., according to, using) the second PDCP discard timer. For example, UE 1215 can determine the reception time at which each data unit in the data service is received at a buffer in UE 1215. In this example, UE 1215 can determine the buffer duration associated with each data unit in the data service based on the reception time. Upon determining the buffer duration of a corresponding data unit, UE 1215 can discard (e.g., drop or otherwise suppress transmission) data units that include a buffer duration greater than or equal to the duration of the second PDCP discard timer (e.g., discard the data unit if its buffer duration is greater than or equal to the duration of the second PDCP discard timer).

[0287] In some respects, UE 1215 can transmit data services at 1255 by applying a second PDCP drop timer to one or more bearers and / or bearer types associated with the data service. For example, as previously noted, at 1245, UE 1215 can identify one or more bearers associated with the data service. In this example, UE 1215 can transmit data services at 1255 by applying a second PDCP drop timer to one or more bearers of the data service. At this point, UE 1215 can discard or drop data units transmitted via one or more identified bearers according to the second PDCP drop timer, as discussed previously herein.

[0288] At 1260, UE 1215 can determine the expiration date of the validity period associated with the second PDCP discard timer. The validity period associated with the second PDCP discard timer can refer to the duration for which the PDCP discard timer is used to transmit data services. In this respect, UE 1215 can initiate the validity period based on the start of using the second PDCP discard timer to transmit data services, and can transmit data services based on the second PDCP discard timer until the expiration date. In some aspects, UE 1215 can determine the validity period associated with the second PDCP discard timer based on determining the second PDCP discard timer at 1250. Additionally or alternatively, UE 1215 can determine the validity period associated with the second PDCP discard timer based on receiving an uplink grant at 1220, receiving downlink transmissions (e.g., configuration information, control information) at 1225, determining a first PDCP discard timer at 1230, identifying a data service at 1235, determining a set of conditions associated with the data rate at 1240, determining a set of parameters associated with the data service at 1245, or any combination thereof.

[0289] At 1265, UE 1215 may use the first PDCP discard timer to transmit data services. In some aspects, UE 1215 may use the first PDCP discard timer to transmit data services at 1265 based on the expiration of the validity period associated with the second PDCP discard timer determined at 1260.

[0290] The techniques described herein enable dynamic adjustment of the PDCP drop timer. Specifically, the techniques described herein allow UE 1215 to selectively adjust the PDCP drop timer (or select a new PDCP drop timer) to reduce or eliminate the amount of data units dropped in response to brief, intermittent interruptions in wireless communication. By implementing dynamic adjustment of the PDCP drop timer, the techniques described herein can improve the quality and efficiency of wireless communication within a wireless communication system (e.g., wireless network 100, wireless communication system 1100) and enhance the overall user experience.

[0291] Figure 13 A block diagram 1300 of a device 1305 supporting technology for dynamic PDCP timer adjustment according to this disclosure is shown. Device 1305 may be an example of aspects of a UE 120 as described herein. Device 1305 may include a receiver 1310, a communication manager 1315, and a transmitter 1320. Device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0292] Receiver 1310 can receive information associated with various information channels (e.g., control channels, data channels, and information related to techniques used for dynamic PDCP timer adjustment), such as packets, user data, or control information. This information can be transmitted to other components of device 1305. Receiver 1310 can serve as a reference. Figure 16 Examples of various aspects of the transceiver 1620 are described. The receiver 1310 may utilize a single antenna or a set of antennas.

[0293] Communication manager 1315 may: identify a data service to be transmitted under an uplink license, the data service being associated with a first PDCP discard timer; determine a set of parameters associated with the data service based on a determined set of conditions; determine a set of conditions associated with the uplink license, the UE, or both, the set of conditions being associated with the data rate of the uplink license; determine a second PDCP discard timer different from the first PDCP discard timer based on the determined set of parameters; and use the second PDCP discard timer to transmit the data service under the uplink license. Communication manager 1315 may be an example of various aspects of communication manager 1610 described herein.

[0294] The actions performed by the communication manager 1315 as described herein can be implemented to achieve one or more potential advantages. For example, by implementing dynamic adjustment of the PDCP discard timer, the communication manager 1315 can eliminate or reduce the amount of data units dropped or lost due to brief, intermittent interruptions in wireless communication. This can lead to more reliable wireless communication and an overall improved user experience. Furthermore, by reducing the number of dropped data units and improving the reliability of wireless communication, the amount of retransmissions within the wireless communication system (e.g., wireless network 100) can be reduced, thereby reducing overall service and signaling overhead.

[0295] By dynamically adjusting the PDCP drop timer, the processor of UE 120 (e.g., the processor controlling receiver 1310, communication manager 1315, transmitter 1320, etc.) can reduce processing resources used for uplink communication. For example, by reducing or eliminating the amount of dropped data units, communication manager 1315 can reduce the amount and / or frequency of uplink retransmissions that can be performed, which can correspondingly reduce the number of times the processor increases processing power and activates processing units to handle uplink transmissions.

[0296] The communication manager 1315 or its sub-components may be implemented in hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented in processor-executable code, the functionality of the communication manager 1315 or its sub-components may be performed by any combination of a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or other components designed to perform the functions described in this disclosure.

[0297] The communication manager 1315 or its subcomponents may be physically located in various locations, including distributed locations, such that some functions are implemented by one or more physical components at different physical locations. In some examples, according to this disclosure, the communication manager 1315 or its subcomponents may be separate and distinct components. In some examples, according to this disclosure, the communication manager 1315 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0298] Transmitter 1320 can transmit signals generated by other components of device 1305. In some examples, transmitter 1320 may be co-located with receiver 1310 in a transceiver module. For example, transmitter 1320 may be a reference... Figure 16 Examples of various aspects of the transceiver 1620 are described. The transmitter 1320 may utilize a single antenna or a set of antennas.

[0299] Figure 14 A block diagram 1400 of a device 1405 supporting technology for dynamic PDCP timer adjustment according to this disclosure is shown. Device 1405 may be an example of aspects of device 1305 or UE 120 as described herein. Device 1405 may include receiver 1410, communication manager 1415, and transmitter 1440. Device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0300] Receiver 1410 can receive information associated with various information channels (e.g., control channels, data channels, and information related to techniques used for dynamic PDCP timer adjustment), such as packets, user data, or control information. This information can be transmitted to other components of device 1405. Receiver 1410 can serve as a reference. Figure 16 Examples of various aspects of the transceiver 1620 are described. The receiver 1410 can utilize a single antenna or a set of antennas.

[0301] Communication manager 1415 may be an example of aspects of communication manager 1315 described herein. Communication manager 1415 may include data service manager 1420, data rate manager 1425, PDCP discard timer manager 1430, and data service transmission manager 1435. Communication manager 1415 may be an example of aspects of communication manager 1610 described herein.

[0302] The data service manager 1420 can: identify data services that will be sent according to an uplink license, which are associated with a first PDCP drop timer; and determine a set of parameters associated with the data service based on a determined set of conditions.

[0303] The data rate manager 1425 can determine a set of conditions associated with the uplink license, the UE, or both, which are related to the data rate of the uplink license.

[0304] The PDCP discard timer manager 1430 can determine a second PDCP discard timer that is different from the first PDCP discard timer based on a determined set of parameters.

[0305] The data service transmission manager 1435 can use the second PDCP discard timer to transmit the data service according to the uplink license.

[0306] Transmitter 1440 can transmit signals generated by other components of device 1405. In some examples, transmitter 1440 may be co-located with receiver 1410 in a transceiver module. For example, transmitter 1440 may be a reference... Figure 16 Examples of various aspects of the transceiver 1620 are described. The transmitter 1440 can utilize a single antenna or a set of antennas.

[0307] Figure 15A block diagram 1500 of a communication manager 1505 supporting techniques for dynamic PDCP timer adjustment according to this disclosure is shown. The communication manager 1505 may be an example of aspects of the communication manager 1315, communication manager 1415, or communication manager 1610 described herein. The communication manager 1505 may include a data traffic manager 1510, a data rate manager 1515, a PDCP discard timer manager 1520, a data traffic transmission manager 1525, a validity period manager 1530, a bearer manager 1535, an application communication manager 1540, a power level manager 1545, and a thermal level manager 1550. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0308] Data service manager 1510 can identify data services to be transmitted according to an uplink license, which are associated with a first PDCP drop timer. In some examples, data service manager 1510 can determine a set of parameters associated with the data service based on a determined set of conditions. In some examples, data service manager 1510 can determine the bearer type associated with the data service, the service volume metric associated with the data service, the priority associated with the data service, the latency sensitivity metric associated with the data service, the reliability metric associated with the data service, or any combination thereof, wherein the determination of a second PDCP drop timer is based on the bearer type, the service quality metric, the latency sensitivity metric, the reliability metric, or any combination thereof. In some examples, data service manager 1510 can determine that the amount of data service to be transmitted according to the uplink license is greater than or equal to a data service threshold, wherein the determination of the set of conditions is based on determining that the amount of data service is greater than or equal to the data service threshold. In some examples, data service manager 1510 can determine an indication of the amount of data service based on a BSR, wherein determining that the amount of data service is greater than or equal to the data service threshold is based on the BSR.

[0309] Data rate manager 1515 can determine a set of conditions associated with an uplink license, a UE, or both, that set of conditions is associated with the data rate of the uplink license. In some examples, data rate manager 1515 can receive from a base station an indication of the data rate of an uplink transmission performed by the UE. In some examples, data rate manager 1515 can determine that the uplink transmission data rate is greater than or equal to the maximum data rate associated with the uplink license, wherein the determination of the set of conditions is based on determining that the uplink transmission data rate is greater than or equal to the maximum data rate associated with the uplink license.

[0310] The PDCP drop timer manager 1520 can determine a second PDCP drop timer that differs from the first PDCP drop timer based on a determined set of parameters. In some examples, the PDCP drop timer manager 1520 can selectively adjust the first PDCP drop timer to generate the second PDCP drop timer, wherein determining the second PDCP drop timer is based on selectively adjusting the first PDCP drop timer. In some cases, the first duration of the first PDCP drop timer is shorter than the second duration of the second PDCP drop timer.

[0311] The data service transmission manager 1525 may use a second PDCP discard timer to transmit data services based on an uplink license. In some examples, the data service transmission manager 1525 may use a first PDCP discard timer to transmit data services based on the expiration of a validity period. In some examples, the data service transmission manager 1525 may suppress the transmission of data units of the data service based on the second PDCP discard timer. In some examples, the data service transmission manager 1525 may determine the reception time of each data unit in the data service at the UE's buffer. In some examples, the data service transmission manager 1525 may determine the buffer duration associated with each data unit in the data service based on the reception time. In some examples, the data service transmission manager 1525 may discard data units that include a buffer duration greater than or equal to the duration of the second PDCP discard timer.

[0312] The expiry date manager 1530 can determine the expiry date associated with the second PDCP discard timer.

[0313] The bearer manager 1535 can identify one or more bearers associated with a data service, wherein the data service is transmitted based on an uplink license by applying a second PDCP drop timer to one or more bearers associated with the data service.

[0314] The application communication manager 1540 can receive an indication of the set of parameters associated with the data service from an application or program executed by the UE, wherein the determination of the set of parameters associated with the data service is based on receiving the indication.

[0315] The power level manager 1545 can determine that the power level used to transmit uplink transmissions is less than or equal to a threshold power level, wherein the set of determination conditions is based on determining that the power level is less than or equal to the threshold power level.

[0316] The thermal level manager 1550 can determine that the thermal level of the UE is greater than a threshold thermal level, wherein the set of determination conditions is based on determining that the thermal level is greater than the threshold thermal level.

[0317] Figure 16 A schematic diagram of a system 1600 including device 1605 is shown, which supports the techniques for dynamic PDCP timer adjustment according to this disclosure. Device 1605 may be an example of device 1305, device 1405, or UE 120 described herein, or a component including such devices. Device 1605 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 1610, an I / O controller 1615, a transceiver 1620, an antenna 1625, a memory 1630, and a processor 1640. These components may communicate electronically via one or more buses (e.g., bus 1645).

[0318] The communication manager 1610 may: identify a data service to be transmitted under an uplink license, the data service being associated with a first PDCP discard timer; determine a set of parameters associated with the data service based on a determined set of conditions; determine a set of conditions associated with the uplink license, the UE, or both, the set of conditions being associated with the data rate of the uplink license; determine a second PDCP discard timer different from the first PDCP discard timer based on the determined set of parameters; and use the second PDCP discard timer to transmit the data service under the uplink license.

[0319] I / O controller 1615 can manage the input and output signals of device 1605. I / O controller 1615 can also manage peripheral devices not integrated into device 1605. In some cases, I / O controller 1615 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1615 can utilize an operating system, such as... MS- MS- OS / , Or other known operating systems. In other cases, the I / O controller 1615 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1615 may be implemented as part of the processor. In some cases, the user may interact with the device 1605 via the I / O controller 1615 or via hardware components controlled by the I / O controller 1615.

[0320] Transceiver 1620 can communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, transceiver 1620 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1620 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and demodulate packets received from the antenna.

[0321] In some cases, a wireless device may include a single antenna 1625. However, in other cases, a device may have more than one antenna 1625, which may be able to transmit or receive multiple wireless transmissions in parallel.

[0322] Memory 1630 may include random-access memory (RAM) and read-only memory (ROM). Memory 1630 may store computer-readable, computer-executable code 1635, which includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1630 may contain a basic I / O system (BIOS), which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0323] Processor 1640 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, central processing units (CPUs), microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1640 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1640. Processor 1640 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1630) to cause device 1605 to perform various functions (e.g., functions or tasks supporting techniques for dynamic PDCP timer adjustment).

[0324] Code 1635 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 1635 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1635 may not be directly executable by processor 1640, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0325] Figure 17A flowchart illustrating a method 1700 for supporting dynamic PDCP timer adjustment according to this disclosure is shown. The operation of method 1700 can be implemented by UE 120 or its components as described herein. For example, the operation of method 1700 can be performed by, as referenced... Figures 13 to 16 The communication manager described herein is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional elements to perform the functions described below. Alternatively or alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0326] At 1705, the UE can identify a data service to be transmitted under an uplink license, which is associated with a first PDCP discard timer. The operation of 1705 can be performed according to the method described herein. In some examples, aspects of the operation of 1705 can be derived from, as referenced... Figures 13 to 16 The described data business manager is used to execute this.

[0327] In section 1710, the UE can determine a set of conditions associated with the uplink grant, the UE, or both, and this set of conditions is related to the uplink grant data rate. The operation of section 1710 can be performed according to the methods described herein. In some examples, aspects of the operation of section 1710 can be derived from, as referenced... Figures 13 to 16 The described data rate manager is used to perform this.

[0328] In 1715, the UE can determine the set of parameters associated with the data service based on a defined set of conditions. The operation of 1715 can be performed according to the methods described herein. In some examples, aspects of the operation of 1715 can be determined by reference to [reference needed]. Figures 13 to 16 The described data business manager is used to execute this.

[0329] At 1720, the UE can determine a second PDCP discard timer, different from the first PDCP discard timer, based on the determined set of parameters. The operation of 1720 can be performed according to the method described herein. In some examples, aspects of the operation of 1720 can be determined by reference to... Figures 13 to 16 The PDCP described uses a discard timer manager for execution.

[0330] At 1725, the UE can use a second PDCP drop timer to transmit data services based on uplink clearance. Operation at 1725 can be performed according to the methods described herein. In some examples, aspects of operation at 1725 can be derived from references... Figures 13 to 16 The described data service sending manager is used to execute this.

[0331] Figure 18A flowchart illustrating a method 1800 for supporting dynamic PDCP timer adjustment according to this disclosure is shown. Operation of method 1800 can be implemented by a UE 120 or its components as described herein. For example, operation of method 1800 can be performed by, as referenced... Figures 13 to 16 The communication manager described herein is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional elements to perform the functions described below. Alternatively or alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0332] At 1805, the UE can identify a data service to be transmitted under an uplink license, which is associated with a first PDCP discard timer. Operation at 1805 can be performed according to the method described herein. In some examples, aspects of operation at 1805 can be derived from, as referenced... Figures 13 to 16 The described data business manager is used to execute this.

[0333] In step 1810, the UE can determine a set of conditions associated with the uplink grant, the UE, or both, and this set of conditions is related to the uplink grant data rate. The operation of step 1810 can be performed according to the methods described herein. In some examples, aspects of the operation of step 1810 can be derived from, as referenced... Figures 13 to 16 The described data rate manager is used to perform this.

[0334] In step 1815, the UE can determine the set of parameters associated with the data service based on a defined set of conditions. The operation of step 1815 can be performed according to the methods described herein. In some examples, aspects of the operation of step 1815 can be determined by reference to [reference needed]. Figures 13 to 16 The described data business manager is used to execute this.

[0335] At 1820, the UE can determine a second PDCP discard timer, different from the first PDCP discard timer, based on the determined set of parameters. The operation of 1820 can be performed according to the method described herein. In some examples, aspects of the operation of 1820 can be determined by reference to... Figures 13 to 16 The PDCP described uses a discard timer manager for execution.

[0336] In step 1825, the UE can use a second PDCP drop timer to transmit data services based on uplink clearance. The operation of step 1825 can be performed according to the method described herein. In some examples, aspects of the operation of step 1825 can be derived from references... Figures 13 to 16 The described data service sending manager is used to execute this.

[0337] At 1830, the UE can determine the expiration of the validity period associated with the second PDCP discard timer. The operation at 1830 can be performed according to the method described herein. In some examples, aspects of the operation at 1830 can be derived from, as referenced... Figures 13 to 16 The described expiration manager is used to perform this.

[0338] In step 1835, the UE can use the first PDCP discard timer to send data services based on the expiration of the validity period. The operation of step 1835 can be performed according to the method described herein. In some examples, aspects of the operation of step 1835 can be derived from references... Figures 13 to 16 The described data service sending manager is used to execute this.

[0339] Figure 19 A flowchart illustrating a method 1900 for supporting dynamic PDCP timer adjustment according to this disclosure is shown. Operation of method 1900 can be implemented by a UE 120 or its components as described herein. For example, operation of method 1900 can be performed by, as referenced... Figures 13 to 16 The communication manager described herein is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional elements to perform the functions described below. Alternatively or alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0340] At 1905, the UE can identify a data service to be transmitted under an uplink license, which is associated with a first PDCP discard timer. Operation at 1905 can be performed according to the method described herein. In some examples, aspects of operation at 1905 can be derived from, as referenced... Figures 13 to 16 The described data business manager is used to execute this.

[0341] In step 1910, the UE can determine a set of conditions associated with the uplink grant, the UE, or both, and this set of conditions is related to the data rate of the uplink grant. Operation of step 1910 can be performed according to the methods described herein. In some examples, aspects of operation of step 1910 can be derived from, as referenced... Figures 13 to 16 The described data rate manager is used to perform this.

[0342] In 1915, the UE can determine the set of parameters associated with the data service based on a defined set of conditions. The operation of 1915 can be performed according to the method described herein. In some examples, aspects of the operation of 1915 can be determined by reference to... Figures 13 to 16 The described data business manager is used to execute this.

[0343] In step 1920, the UE can identify one or more bearers associated with data services. Operation of step 1920 can be performed according to the methods described herein. In some examples, aspects of operation of step 1920 can be derived from, as referenced... Figures 13 to 16 The described host manager is used to execute this.

[0344] In 1925, the UE can determine a second PDCP discard timer, different from the first PDCP discard timer, based on a determined set of parameters. Operation of 1925 can be performed according to the method described herein. In some examples, aspects of operation of 1925 can be determined by reference to... Figures 13 to 16 The PDCP described uses a discard timer manager for execution.

[0345] In 1930, the UE can use a second PDCP drop timer to transmit data services according to an uplink license, wherein the data service is transmitted according to an uplink license based on applying the second PDCP drop timer to one or more bearers associated with the data service. The operation of 1930 can be performed according to the method described herein. In some examples, aspects of the operation of 1930 can be derived from references... Figures 13 to 16 The described data service sending manager is used to execute this.

[0346] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects of two or more methods can be combined.

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

[0348] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving information indicating a timer value associated with a discarded Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU); determining that a timer modification condition is met; determining to modify the timer value based at least in part on the timer modification condition being met; and transmitting communication using the modified timer value.

[0349] Aspect 2: According to the method described in aspect 1, the timer modification condition is associated with an uplink permission-restricted scenario.

[0350] Aspect 3: According to the method of aspect 2, wherein the uplink permission-restricted scenario is based at least in part on the UE modifying the UE's buffer state report due to the thermal mitigation condition being met.

[0351] Aspect 4: The method according to aspect 3, wherein the timer modification condition is at least partially based on the heat relief condition, and wherein the timer modification condition indicates that the timer value is increased at least partially based on the heat relief condition being met.

[0352] Aspect 5: According to the method of aspect 4, wherein the timer is disabled at least in part based on the fact that the buffer status report is modified to indicate that there is no data in the buffer of the UE.

[0353] Aspect 6: According to the method of aspect 2, wherein the uplink permission-restricted scenario is based at least in part on the gap associated with the dual-standby configuration of the dual-subscriber identification module.

[0354] Aspect 7: According to the method of aspect 6, wherein the timer is disabled, at least in part based on the fact that the length of the gap is uncertain at the beginning of the gap.

[0355] Aspect 8: According to the method of aspect 6, wherein the timer modification condition is at least partially based on the length of the gap satisfying a threshold.

[0356] Aspect 9: According to the method described in aspect 8, the timer value is increased by a value equal to the length of the gap.

[0357] Aspect 10: According to the method of aspect 8, wherein the timer is disabled at least in part based on the length of the gap satisfying a threshold.

[0358] Aspect 11: The method according to aspect 2, wherein the uplink license-restricted scenario is based at least in part on the UE’s block error rate (BLER).

[0359] Aspect 12: The method according to aspect 11, wherein the timer value is modified at least in part based on the BLER satisfying a threshold.

[0360] Aspect 13: The method according to aspect 11 further includes: determining the modified timer value based at least in part on a plurality of thresholds for the BLER.

[0361] Aspect 14: The method according to aspect 11, wherein the timer is disabled at least in part based on the uplink segmented bearer being configured for the UE, at least in part based on the primary radio link control entity of the uplink segmented bearer being associated with a BLER that meets a threshold, and at least in part based on the buffer size of the UE being less than the data segmentation threshold of the uplink segmented bearer.

[0362] Aspect 15: The method according to aspect 1, wherein the timer modification condition is associated with a bearer configured to compress packets transmitted on that bearer.

[0363] Aspect 16: The method according to aspect 15, wherein the timer value is modified at least in part based on the bearer being configured to compress packets transmitted on the bearer.

[0364] Aspect 17: The method according to aspect 15, wherein the bearer is configured for at least one of robust header compression or uplink data compression.

[0365] Aspect 18: The method according to any one of aspects 1-17, wherein the timer value is modified based at least in part on the fact that the bearer of the UE is configured with integrity protection.

[0366] Aspect 19: The method according to any one of aspects 1-18 further includes: determining the expiration of the validity period associated with the modified timer value; and sending communication using the timer value before the modification, at least in part based on the expiration of the validity period.

[0367] Aspect 20: The method according to any one of aspects 1-19 further includes: determining a bearer type associated with the communication, a service volume metric associated with the communication, a priority associated with the communication, a latency sensitivity metric associated with the communication, a reliability metric associated with the communication, or any combination thereof, wherein modifying the timer value is at least partially based on the bearer type, the service volume metric, the latency sensitivity metric, the reliability metric, or any combination thereof.

[0368] Aspect 21: The method according to any one of aspects 1-20 further includes: determining that the amount of data service to be transmitted in the communication is greater than or equal to a data service threshold, wherein the timer modification condition is based at least in part on the data service amount being greater than or equal to the data service threshold.

[0369] Aspect 22: The method according to any one of aspects 1-21 further includes: determining that the power level for transmitting uplink transmission is less than or equal to a threshold power level, wherein the timer modification condition is based at least in part on the power level being less than or equal to the threshold power level.

[0370] Aspect 23: The method according to any one of aspects 1-22, wherein using a modified timer value to send communication includes: suppressing the transmission of data units for communication based at least in part on the modified timer value.

[0371] Aspect 24: The method according to aspect 23, wherein suppressing the transmission of data units for communication based at least in part on a modified timer value comprises: determining the reception time at which each data unit in the communication is received in the buffer of the UE; determining the buffer duration associated with each data unit in the communication based at least in part on the reception time; and discarding data units that include a buffer duration greater than or equal to the duration associated with the modified timer value.

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

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

[0374] Aspect 27: An apparatus for wireless communication, comprising: at least one component for performing the methods of one or more aspects of aspects 1-24.

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

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

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

[0378] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented as a combination of hardware, firmware, and / or hardware and software. It is evident that the systems and / or methods described herein can be implemented using various forms of hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, since the operation and behavior of the systems and / or methods described herein do not refer to specific software code, it should be understood that software and hardware can be designed to implement the systems and / or methods, at least in part, based on the descriptions herein.

[0379] As used in this article, depending on the context, a threshold can refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0380] Even if specific combinations of features are listed in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of each aspect. In fact, many of these features can be combined in ways not specifically stated in the claims and / or not disclosed in the specification. Although each dependent claim listed below may be directly dependent on only one claim, the disclosure of each aspect includes combinations of each dependent claim with each other claim in the claim set. As used herein, the phrase referring to “at least one” of a series of items means any combination of those items, including single members. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0381] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the article “a” is intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” / “the” is intended to include one or more items mentioned in connection with the article “the” / “the” and may be used interchangeably with “the one or more” / “the one or more”. Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” If referring to only one item, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “have,” “have,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise. Furthermore, as used herein, the term “or” when used in a series is intended to be inclusive and may be used interchangeably with “and / or” unless explicitly stated otherwise (e.g., if used in conjunction with “any” or “only one”).

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: Receive information indicating the timer value associated with the timer of the Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU); It is confirmed that the timer modification conditions have been met. The timer modification conditions are associated with uplink permission-restricted scenarios. The uplink permission-restricted scenario is at least in part based on the gap associated with the dual-standby configuration of the dual-subscriber identification module; The timer value is modified at least in part based on the determination that the timer modification condition is met; and Use the modified timer value to send communication.

2. The method according to claim 1, wherein, The uplink permission-restricted scenario is based at least in part on the UE modifying the UE's buffer status report because the hot mitigation conditions are met.

3. The method according to claim 2, wherein, The timer modification condition is based at least in part on the thermal mitigation condition, and wherein the timer modification condition indicates that the timer value is increased at least in part based on the thermal mitigation condition being met.

4. The method according to claim 3, wherein, The timer is disabled, at least in part, based on the fact that the buffer status report is modified to indicate that there is no data in the UE's buffer.

5. The method according to claim 1, wherein, The timer is disabled, at least in part, because the length of the gap is uncertain at the start of the gap.

6. The method according to claim 1, wherein, The timer modification condition is based at least in part on the fact that the length of the gap meets a threshold.

7. The method according to claim 6, wherein, The timer value is increased by a value equal to the length of the gap.

8. The method according to claim 6, wherein, The timer is disabled, at least in part, based on the fact that the length of the gap meets the threshold.

9. The method according to claim 1, wherein, The uplink permission-restricted scenario is based at least in part on the UE's block error rate (BLER).

10. The method according to claim 9, wherein, The timer value is modified, at least in part, based on the BLER meeting a threshold.

11. The method of claim 9, further comprising: The modified timer value is determined at least in part based on multiple thresholds for BLER.

12. The method according to claim 9, wherein, The timer is disabled at least in part based on the uplink segmented bearer being configured for the UE, at least in part based on the primary radio link control entity of the uplink segmented bearer being associated with a BLER that meets a threshold, and at least in part based on the UE's buffer size being less than the data segmentation threshold of the uplink segmented bearer.

13. The method according to claim 1, wherein, The timer modification condition is associated with a bearer configured to compress packets transmitted on that bearer.

14. The method according to claim 13, wherein, The timer value is modified, at least in part, based on the fact that the bearer is configured to compress packets transmitted on the bearer.

15. The method according to claim 13, wherein, The bearer is configured for at least one of robust header compression or uplink data compression.

16. The method according to claim 1, wherein, The timer value is modified at least in part because the UE's bearer is configured with integrity protection.

17. The method of claim 1, further comprising: Determine the expiration date of the validity period associated with the modified timer value; as well as The communication is sent using a timer value that was modified before the expiration date, at least in part, based on the expiration of the validity period.

18. The method of claim 1, further comprising: Determine the type of bearer associated with the communication, the volume of service metric associated with the communication, the priority associated with the communication, the latency sensitivity metric associated with the communication, the reliability metric associated with the communication, or any combination thereof, wherein the timer value is modified at least in part based on the type of bearer, the volume of service metric, the latency sensitivity metric, the reliability metric, or any combination thereof.

19. The method of claim 1, further comprising: The amount of data traffic to be transmitted in the communication is determined to be greater than or equal to a data traffic threshold, wherein the timer modification condition is based at least in part on the amount of data traffic being greater than or equal to the data traffic threshold.

20. The method of claim 1, further comprising: The power level used for transmitting uplink transmissions is determined to be less than or equal to a threshold power level, wherein the timer modification condition is based at least in part on the power level being less than or equal to the threshold power level.

21. The method according to claim 1, wherein, Sending the communication using a modified timer value includes: The transmission of data units for the communication is suppressed, at least in part, based on the modified timer value.

22. The method according to claim 21, wherein, The data units that suppress the transmission of the communication based at least in part on the modified timer value include: Determine the reception time of each data unit in the communication data unit when it is received at the buffer of the UE; The buffer duration associated with each data unit in the communication is determined at least in part based on the reception time; and Discard data units that include a buffer duration greater than or equal to the duration associated with the modified timer value.

23. A user equipment (UE) for wireless communication, comprising: At least one memory containing instructions; and One or more processors, the one or more processors being configured to execute the instructions such that the UE: Receive information indicating the timer value associated with the timer of the Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU); It is confirmed that the timer modification conditions have been met. The timer modification conditions are associated with uplink permission-restricted scenarios. The uplink permission-restricted scenario is at least in part based on the gap associated with the dual-standby configuration of the dual-subscriber identification module; The timer value is modified at least in part based on the determination that the timer modification condition is met; and Use the modified timer value to send communication.

24. The UE according to claim 23, wherein, The uplink permission-restricted scenario is based at least in part on the UE modifying the UE's buffer status report because the hot mitigation conditions are met.

25. The UE according to claim 24, wherein, The timer modification condition is based at least in part on the thermal mitigation condition, and wherein the timer modification condition indicates that the timer value is increased at least in part based on the thermal mitigation condition being met.

26. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: One or more instructions, when executed by one or more processors of a user equipment (UE), cause the UE to perform the method according to any one of claims 1-22.

27. An apparatus for wireless communication, comprising: Components for performing the method according to any one of claims 1-22.

28. A computer program product comprising computer-readable instructions, which, when executed, cause one or more processors to perform the method according to any one of claims 1-22.

Images