Discarding parameter adaptation

Abstract

Autonomous adjustment of configurable parameters at a user equipment (UE). In an embodiment, an apparatus (e.g., a UE) is configured to receive information defining preconfigured remaining time threshold configurations for a delay status reporting procedure; detect a network condition based on communication with a radio access network node; adjust a remaining time threshold corresponding to the delay status reporting procedure in response to the network condition and based on one of the preconfigured remaining time threshold configurations; and perform the delay status reporting procedure based on the adjusted remaining time threshold to trigger a delay status report to the radio access network node when a discard timer associated with a buffered data unit is below the adjusted remaining time threshold.

Description

Technical Field

[0001] This disclosure relates to the field of communication systems, and more particularly to next-generation networks. Background Technology

[0002] Mobile telecommunications networks or cellular networks (generally referred to herein as communication networks or mobile networks) enable communication between two or more communication devices, provide communication devices with access to data networks, deliver services provided by third-party applications to communication devices, and / or provide services supplied by the communication network to communication devices. Communication networks and communication devices can operate according to cellular technologies (also known as radio access technologies), such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications Service (UTMS), Long Term Evolution (LTE or LTE-A), and New Radio (NR). Cellular technologies are standardized by various standards organizations such as the 3rd Generation Partnership Project (3GPP) or ETSI (European Telecommunications Standards Institute). 3GPP is currently developing standards for 5th generation cellular technologies (generally referred to as 5G or NR standards) and 6th generation cellular technologies (generally referred to as 6G standards). Communication networks operating according to 5G or NR standards are generally referred to as 5G networks or 5G systems, and communication networks operating according to 6G standards are generally referred to as 6G networks or 6G systems; both can generally be collectively referred to as next-generation networks (i.e., beyond the fourth generation (4G) standard).

[0003] It may be beneficial to establish that communication networks and / or communication devices are aware of network conditions (e.g., congestion) and adjust their behavior accordingly. Summary of the Invention

[0004] This document describes improvements to the mechanisms for addressing network conditions (such as bit rate variations, congestion, etc.) in communication networks and / or communication devices. As an overview, different layers of the radio protocol stack between the communication device (often referred to herein as User Equipment (UE)) and the Radio Access Network (RAN) node operate based on configurable parameters. As an example, the Packet Data Convergence Protocol (PDCP) layer at the UE may include configurable parameters for PDCP procedures (such as drop procedures). In another example, the Media Access Control (MAC) layer at the UE may include configurable parameters for MAC procedures, such as delay status reporting. In the embodiments provided herein, the UE is configured and / or authorized to act autonomously to adjust one or more configurable parameters, such as in response to network conditions. Conventionally, configurable parameters in the UE are static until the RAN node updates them via signaling. This can lead to high signaling overhead when responding to network conditions and may negatively impact the user experience. In the embodiments provided herein, configurable parameters are adjusted autonomously at the UE side without further interaction with the RAN node. One technical benefit of adjusting configurable parameters at the UE is that signaling overhead is minimized.

[0005] In one embodiment (also referred to as an aspect), an apparatus includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: receive information defining a pre-configured remaining time threshold configuration for a delay status reporting procedure; detect network conditions based on communication with a radio access network node; adjust the remaining time threshold corresponding to the delay status reporting procedure in response to the network conditions and based on one of the pre-configured remaining time threshold configurations; and execute the delay status reporting procedure based on the adjusted remaining time threshold to trigger a delay status report to the radio access network node when a drop timer associated with a buffered data unit falls below the adjusted remaining time threshold.

[0006] In one embodiment, a method includes: receiving information defining a pre-configured remaining time threshold configuration for a delay status reporting procedure; detecting network conditions based on communication with a radio access network node; adjusting the remaining time threshold corresponding to the delay status reporting procedure in response to the network conditions and based on one of the pre-configured remaining time threshold configurations; and performing the delay status reporting procedure based on the adjusted remaining time threshold to trigger a delay status report to the radio access network node when a drop timer associated with a buffered data unit falls below the adjusted remaining time threshold.

[0007] In one embodiment, an apparatus includes: components for receiving information defining a pre-configured remaining time threshold configuration for a delay status reporting procedure; components for detecting network conditions based on communication with a radio access network node; components for adjusting a remaining time threshold corresponding to the delay status reporting procedure in response to the network conditions and based on one of the pre-configured remaining time threshold configurations; and components for performing the delay status reporting procedure based on the adjusted remaining time threshold to trigger a delay status report to the radio access network node when a drop timer associated with a buffered data unit falls below the adjusted remaining time threshold.

[0008] Other embodiments may include computer-readable media, other systems or apparatuses, or other methods or components described below. Furthermore, one or more embodiments as described above may be composable, as illustrated herein.

[0009] The foregoing summary provides a basic understanding of some aspects of this specification. This summary is not a broad overview of this specification. It is not intended to establish key or essential elements of this specification, nor is it intended to depict any scope of any particular embodiment or claim. Its sole purpose is to present some concepts of this specification in a simplified form as an introduction to the specific embodiments presented later. Attached Figure Description

[0010] Some embodiments of this disclosure will now be described by way of example only and with reference to the accompanying drawings. Throughout the drawings, the same reference numerals denote the same elements or elements of the same type.

[0011] Figure 1 The advanced architecture of the 5G system is shown.

[0012] Figure 2 The non-roaming architecture of a 5G system is shown.

[0013] Figure 3 The NG-RAN architecture is shown.

[0014] Figure 4 This is a block diagram illustrating the 5G NR radio protocol stack.

[0015] Figure 5 The control plane on the RAN is shown.

[0016] Figure 6 The user plane on the RAN is shown.

[0017] Figure 7 This is a block diagram of the system in the illustrative embodiment.

[0018] Figure 8 This is a block diagram of the UE in an illustrative embodiment.

[0019] Figure 9 This is a block diagram of the UE in another illustrative embodiment.

[0020] Figure 10 This is a structural view of the PDCP layer.

[0021] Figure 11 A functional view of the PDCP entity is shown.

[0022] Figure 12 This is a structural view of the MAC layer.

[0023] Figure 13 This is a diagram illustrating the interaction between the UE and the RAN node in an illustrative embodiment.

[0024] Figure 14 A to Figure 14B This is a flowchart illustrating a method for automatically adjusting configurable parameters in an illustrative embodiment.

[0025] Figure 15 The discarding process for transmission operations at the PDCP layer is illustrated.

[0026] Figure 16 This is a block diagram illustrating the discarding process based on the discard timer.

[0027] Figure 17 The PDU set is shown.

[0028] Figure 18 This is a block diagram illustrating the discarding process based on the discard timer and the low-importance discard timer.

[0029] Figure 19 This is a flowchart illustrating a method for performing a sending operation in an illustrative embodiment.

[0030] Figure 20 This is a flowchart illustrating a method for performing a discard operation in an illustrative embodiment.

[0031] Figure 21 This is a diagram illustrating the interaction between the UE and the RAN node in an illustrative embodiment.

[0032] Figure 22 A to Figure 22B This is a flowchart illustrating a method for adjusting a low-importance discard timer in an illustrative embodiment.

[0033] Figure 23 This is a flowchart illustrating a method for adjusting the discarding process at the UE in an illustrative embodiment.

[0034] Figures 24 to 25 This is a diagram illustrating the interaction between the UE and the RAN node in an illustrative embodiment.

[0035] Figure 26 This is a block diagram of the MAC PDU.

[0036] Figure 27 The discard timer configuration in the illustrative embodiment is shown.

[0037] Figure 28 A discard timer configuration in another illustrative embodiment is shown.

[0038] Figure 29 A discard timer configuration in another illustrative embodiment is shown.

[0039] Figure 30 Additional details on adjusting the low-importance discard timer in the illustrative embodiment are shown.

[0040] Figure 31 The DSR process at the MAC layer is shown.

[0041] Figure 32 This is a flowchart illustrating a method for performing a delayed status report in an illustrative embodiment.

[0042] Figure 33 This is a diagram illustrating the interaction between the UE and the RAN node in an illustrative embodiment.

[0043] Figure 34 A to Figure 34B This is a flowchart illustrating a method for adjusting a remaining time threshold in an illustrative embodiment.

[0044] Figure 35 This is a flowchart illustrating a method for performing a delay status report at the UE in an illustrative embodiment.

[0045] Figures 36 to 37 This is a diagram illustrating the interaction between the UE and the RAN node in an illustrative embodiment.

[0046] Figure 38 The remaining time threshold configuration 3310 in the illustrative embodiment is shown.

[0047] Figure 39 A remaining time threshold configuration is shown in another illustrative embodiment.

[0048] Figure 40 A remaining time threshold configuration is shown in another illustrative embodiment.

[0049] Figure 41 Additional details on adjusting the remaining time threshold in the illustrative embodiment are shown.

[0050] Figure 42 An RRC message is shown in an illustrative embodiment.

[0051] Figure 43 An RRC message is shown in another illustrative embodiment.

[0052] Figure 44 The PDCP configuration information element (IE) in the illustrative embodiment is shown.

[0053] Figure 45 An RRC message is shown in another illustrative embodiment.

[0054] Figure 46 The MAC configuration information element (IE) is shown in an illustrative embodiment.

[0055] Figure 47 A to Figure 47B This is a flowchart illustrating the RRC processing method in an illustrative embodiment. Detailed Implementation

[0056] The accompanying drawings and the following description illustrate specific exemplary embodiments. Therefore, it should be understood that those skilled in the art will be able to design various arrangements, which, although not explicitly described or shown herein, embody the principles of the embodiments and are included within the scope of the embodiments. Furthermore, any examples described herein are intended to aid in understanding the principles of the embodiments and should be construed as not being limited to these specific examples and conditions. Therefore, the inventive concept is not limited to the specific embodiments or examples described below, but is limited by the claims and their equivalents.

[0057] Figure 1 The high-level architecture of a 5G system 100 is illustrated. The 5G system (5GS) 100 is a communication system (e.g., a 3GPP system) comprising an access network ((R)AN) 102 (often referred to herein as RAN, 5G access network, etc.) and a core network 104 (often referred to herein as 5G core network or 5GC) communicating with user equipment (UE) 106 (e.g., a 5G-enabled UE). RAN 102 and core network 104 together may be referred to as a 5G network 101, a 5G mobile network, a 5G communication network, a next-generation network, etc. Although the term “5G” is used herein as an example, any next-generation or future-generation network beyond 4G, such as 6G, is considered. Therefore, the “mobile network” and concepts described herein apply to 5G and above.

[0058] RAN 102 provides radio or wireless connectivity to UE 106 and connects UE 106 to core network 104. RAN 102 may include Next Generation Radio Access Network (NG-RAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Non-3GPP Access Network (N3AN), Non-Terrestrial Access Network (NTN), and / or another type of RAN connected to core network 104. RAN 102 may support access through at least one RAN node (e.g., gNodeB (gNB), ng-eNodeB (ng-eNB)), eNodeB (eNB), and / or Wireless Local Area Network (WLAN) access point. RAN 102 may support satellite radio access, New Radio Access Technology (RAT), etc. 5G access networks may also support fixed access. Core network 104 interconnects RAN 102 with data network (DN) 108. Core network 104 includes network functions (NFs) 110, which can be implemented as network elements on dedicated hardware, as chips or chipsets included in network elements, as software instances running on dedicated hardware, or as virtualized network functions (VNFs) instantiated on dedicated or general virtualization platforms (e.g., cloud infrastructure). Data network 108 can be an external public or private data network or an intra-operator data network (e.g., for IP Multimedia Subsystem (IMS) services). UE 106 (also referred to as a mobile terminal) includes a 5G-enabled device configured to register with core network 104 to access services. UE 106 can include end-user equipment such as mobile phones (e.g., smartphones), tablets, computers with mobile broadband adapters, etc. UE 106 can be enabled for voice services, data services, machine-to-machine (M2M) or machine-type communication (MTC) services, and / or other services.

[0059] Figure 2 The non-roaming architecture 200 of the 5G system 100 is shown. Figure 2Architecture 200 is a service-based representation, as further described in 3GPP TS 23.501 (Release 19), which is incorporated herein by reference in its entirety. Architecture 200 includes network functions (NFs) for the core network 104, and the NFs for the control plane (CP) are decoupled from the user plane (UP). The control plane of the core network 104 includes Authentication Server Function (AUSF) 210, Access and Mobility Management Function (AMF) 212, Session Management Function (SMF) 214, Policy Control Function (PCF) 216, Unified Data Management (UDM) 218, Network Slice Selection Function (NSSF) 220, and Application Function (AF) 222. The control plane of core network 104 also includes Network Exposure Function (NEF) 224, NF Repository Function (NRF) 226, Serving Communication Agent (SCP) 228, Network Slice Admission Control Function (NSACF) 230, Network Slice Dedicated and SNPN Authentication and Authorization Function (NSSAAF) 232, and Edge Application Server Discovery Function (EASDF) 234. The user plane of core network 104 includes one or more User Plane Functions (UPF) 240 that communicate with data network 108. UE 106 can access the control plane and user plane of core network 104 via RAN 102.

[0060] Figure 3 The NG RAN architecture 300 is illustrated. NG RAN 302 is an example of RAN 102 as described above and includes multiple RAN nodes 304 (also referred to as NG RAN nodes). RAN nodes 304 can be gNB 306 configured to provide new radio user plane and control plane protocol termination to UE 106, or ng-eNB 308 configured to provide E-UTRA user plane and control plane protocol termination to UE 106. gNB 306 and ng-eNB 308 are interconnected to each other via Xn interfaces. gNB 306 and ng-eNB 308 are also connected to core network 104 via NG interfaces, more specifically to AMF 212 via NG-C interfaces, and to UPF 240 via NG-U interfaces.

[0061] Figure 4This is a block diagram illustrating the 5G NR radio protocol stack 400. The RAN protocol architecture is further described in 3GPP TS 38.300 (Release 19), which is incorporated herein by reference in its entirety. The radio protocol stack 400 is divided into a protocol stack for the control plane 401 and a protocol stack for the user plane 402. The radio protocol stack 400 is primarily divided into three layers: the Physical (PHY) layer 404 (L1), the Data Link Layer 406 (L2), and the Network Layer 408 (L3). The Data Link Layer 406 includes the following layers or sublayers: the Media Access Control (MAC) layer 410, the Radio Link Control (RLC) layer 412, and the Packet Data Convergence Protocol (PDCP) layer 414. In the protocol stack for the control plane 401, the Network Layer 408 (L3) includes the Radio Resource Control (RRC) layer 416 (or its sublayer). The protocol stack for control plane 401 also includes a Non-Access Stratum (NAS) layer 418 (i.e., the NAS control protocol), which terminates in AMF 212 on the network side. RRC layer 416, PDCP layer 414, RLC layer 412, and MAC layer 410 terminate in gNB 306 on the network side. In the protocol stack for user plane 402, network layer 408 (L3) includes a Service Data Adaptation Protocol (SDAP) layer 420 (or a sublayer). SDAP layer 420, PDCP layer 414, RLC layer 412, and MAC layer 410 terminate in gNB 306 on the network side.

[0062] Figure 5 Control plane 401 on RAN 102 is shown. Communication on control plane 401 occurs on a radio bearer between UE 106 and RAN node 304, referred to as signaling radio bearer (SRB) 502. SRB 502 is a type of radio bearer that carries signaling messages (i.e., RRC and / or NAS messages). For example, SRB 502 may include SRB 0 504 for RRC messages using the common control channel (CCCH), SRB1 506 for RRC messages and NAS messages using the dedicated control channel (DCCH) (before the establishment of SRB2), and SRB2 508 for NAS messages using the DCCH logical channel. Communication between RAN node 304 and core network 104 (i.e., AMF 212) occurs on NG control plane interface (NG-C) 510.

[0063] Figure 6User plane 402 on RAN 102 is shown. Communication on user plane 402 occurs on a radio bearer between UE 106 and RAN node 304 (referred to as Data Radio Bearer (DRB) 602). DRB 602 is a type of radio bearer that carries user plane messages or services (e.g., packets). Communication between RAN node 304 and core network 104 (i.e., UPF 240) occurs on the GPRS Tunneling Protocol (GTP) user plane interface (GTP-U) 610.

[0064] Quality of Service (QoS) 608 refers to a measurement of the overall performance of the service experienced by users of the network. In 5G NR, QoS 608 is implemented at the QoS-flow level. QoS flow 604 is a logical pipeline defined for data flows or data streams between RAN node 304 and UPF 240 (i.e., via the N3 interface). For the radio portion, data flows are managed in DRB 602. There is a link or mapping between QoS flow 604 and DRB 602, and the mapping is notified to UE 106 via signaling messages (such as RRCSetup or RRCReconfiguration). The mapping is managed using QoS flow identifiers (QFIs). Core network 104 establishes PDU session 606 for UE 106, and RAN node 304 and UE 106 exchange signaling messages to establish DRB 602 for QoS flow 604 for PDU session 606. RAN node 304 maps packets belonging to different PDU sessions 606 to different DRB 602.

[0065] Figure 7 This is a block diagram of system 700 in an illustrative embodiment. More specifically, Figure 7 System 700 includes at least one UE 106, at least one RAN node 304, and multiple network elements / functions 110 (i.e., first network element / function 110-1 and second network element / function 110-N). It should be understood that the UE 106, RAN node 304, and network elements / functions 110 are configured to interact to provide communication management. Examples of network elements / functions 110 (typically referred to as core NFs) may include, but are not limited to, AMF 212, AUSF 210, UDM 218, UPF 240, etc. RAN node 304 is a RAN element / function configured to provide the UE with access to the core network 104. Examples of RAN nodes 304 may include gNB 306, ng-eNB 308, eNB, etc. Network element / function 110-1 includes a processor 722-1 coupled to memory 726-1 and interface circuitry 720-1. The processor 722-1 of network element / function 110-1 includes a communication management processing module 724-1, which may be implemented at least partially in the form of software executed by the processor 722-1. The communication management processing module 724-1 performs communication management in conjunction with the following figures and other methods described herein. Memory 726-1 includes a communication management storage module 728-1, which stores data generated or otherwise used during communication management operations.

[0066] Network element / function 110-N includes a processor 722-N coupled to memory 726-N and interface circuitry 720-N. The processor 722-N of network element / function 110-N includes a communication management processing module 724-N, which may be implemented at least partially in the form of software executed by the processor 722-N. The communication management processing module 724-N performs communication management in conjunction with the following figures and other methods described herein. Memory 726-N includes a communication management storage module 728-N, which stores data generated or otherwise used during communication management operations.

[0067] The processors 722-1 and 722-N of the corresponding network elements / functions 110-1 and 110-N may include, for example, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), or other types of processing devices or integrated circuits, as well as portions or combinations of these elements. Such integrated circuit devices and portions or combinations thereof are examples of the term "circuit" as used herein. Various other arrangements of hardware and associated software or firmware may be used to implement the illustrative embodiments.

[0068] The memories 726-1 and 726-N of the corresponding network elements / functions 110-1 and 110-N can be used to store one or more software programs executed by the corresponding processors 722-1 and 722-N to implement at least a portion of the functions described herein. For example, communication management operations and other functions, as described in conjunction with the following figures and otherwise herein, can be implemented directly using software code executed by processors 722-1 and 722-N.

[0069] Therefore, a given memory in memories 726-1 and 726-N can be considered as an example of what is more generally referred to herein as a computer program product, or more broadly, as a processor-readable non-transitory storage medium in which executable program code is embodied. Other examples of processor-readable non-transitory storage media may include magnetic disks or other types of magnetic or optical media (in any combination). Illustrative embodiments may include articles of manufacture comprising such computer program products or other processor-readable storage media.

[0070] The memories 726-1 and 726-N may more specifically include, for example, electronic random access memory (RAM), such as static RAM (SRAM), dynamic RAM (DRAM), or other types of volatile or non-volatile electronic memory. The latter may include, for example, non-volatile memory, such as flash memory, magnetic RAM (MRAM), phase-change RAM (PC-RAM), or ferroelectric RAM (FRAM). As used herein, the term "memory" is intended to be interpreted broadly and may additionally or alternatively encompass, for example, read-only memory (ROM), disk-based memory, or other types of storage devices, as well as portions or combinations of such devices.

[0071] The interface circuits 720-1 and 720-N of the corresponding network elements / functions 110-1 and 110-N illustratively include transceivers or other communication hardware or firmware, application programming interfaces (APIs), etc., which allow associated system elements to communicate with each other in the manner described herein.

[0072] Network element / function 110-1 is configured to communicate with network element / function 110-N via their respective interface circuits 720-1 and 720-N, and vice versa. This communication involves network element / function 110-1 sending data to network element / function 110-N, and network element / function 110-N sending data to network element / function 110-1. However, in alternative embodiments, other network elements may be operatively coupled between network elements / functions 110-1 and 110-N. The term "data" as used herein is intended to be interpreted broadly to encompass any type of information that may be sent between network elements / functions (and between UE 106 and core network 104), including but not limited to messages, identifiers, keys, indicators, user data, control data, etc.

[0073] RAN node 304 includes a processor 712 coupled to memory 716 and interface circuitry 710. The processor 712 of RAN node 304 includes a communication management processing module 714, which may be implemented at least partially as software executed by the processor 712. The communication management processing module 714 performs communication management in conjunction with the following figures and other methods described herein. Memory 716 includes a communication management storage module 718, which stores data generated or otherwise used during communication management operations. RAN node 304 is configured to communicate with UE 106 and one or more network elements / functions 110 via interface circuitry 710. For example, interface circuitry 710 may be configured to perform radio communication over an air interface to communicate with UE 106 and may be configured to perform backhaul communication with one or more network elements / functions 110 of core network 104.

[0074] It should be understood that Figure 7 The specific arrangement of the components shown is an example, and many alternative configurations can be used in other embodiments. For example, any given network element / function can be configured to incorporate additional or alternative components and support other communication protocols.

[0075] Other system components can also be configured individually to include components such as processors, memory, and network interfaces. These components do not need to be implemented on separate, independent processing platforms, but can instead represent, for example, different functional parts of a single common processing platform.

[0076] Figure 8This is a block diagram of UE 106 in an illustrative embodiment. From a functional perspective, UE 106 comprises at least two parts: a mobile device (ME) 800 and a Universal Subscriber Identity Module (USIM) 860. ME 800 includes a radio interface component 802, one or more processors 804, and memory 806, and may also include a user interface component 808. UE 106 may also include a battery 810. Radio interface component 802 is a hardware component or device representing the local radio resources of UE 106, such as a radio frequency (RF) unit 820 (e.g., one or more radio transceivers) and one or more antennas 822. Radio interface component 802 can be configured for 5G New Radio (NR), Long Term Evolution (LTE), WiFi, Bluetooth, etc. Processor 804 represents the internal circuitry, logic, hardware, devices, etc., that provide the functionality of UE 106. Processor 804 can be configured to execute instructions 840 for software loaded into memory 806. Processor 804 may execute UE 106 for managing hardware and software resources and operating system (OS) 834 for one or more application clients 835 for applications. Processor 804 may also execute communication management controller 836, which includes components or units for establishing and / or performing communication with RAN node 304. User interface component 808 is a hardware component for interacting with an end user. For example, user interface component 808 may include display 850, screen, touchscreen, etc. (e.g., liquid crystal display (LCD), light-emitting diode (LED) display, etc.). User interface component 808 may include keyboard or keypad, tracking device (e.g., trackball or touchpad), speaker, microphone, etc. USIM 860 is an integrated circuit that provides security and integrity functions for UE 106. USIM 860 includes or is supplied with a subscription profile associated with a subscriber's subscription. The subscription profile may include various information such as subscription credentials (e.g., a Subscription Permanent Identifier (SUPI) used to uniquely identify the subscription and mutually authenticate UE 106 and the network).

[0077] UE 106 may include Figure 8 Various other components not specifically shown in the text.

[0078] Figure 9This is a block diagram of UE 106 in another illustrative embodiment. In this embodiment, UE 106 is configured to or operates one or more PDCP entities 914 in PCDP layer 414. UE 106 is also configured to or operates one or more MAC entities 910 in MAC layer 410. These and / or other layers of radio protocol stack 400 operate based on one or more configurable parameters 904. More specifically, PCDP layer 414 may operate based on one or more PDCP configurable parameters 916, and MAC layer 410 may operate based on one or more MAC configurable parameters 912.

[0079] In the embodiments described herein, UE 106 is configured to autonomously operate to adjust, change, modify, or update one or more configurable parameters 904, such as in response to network conditions (e.g., bit rate changes, congestion, etc.). In other words, UE 106 does not need to receive signaling from RAN node 304 to adjust configurable parameters 904, and uses local configuration at UE 106 to adjust configurable parameters 904. Local configuration may include one or more autonomous configurations 902 stored at UE 106, which describe information, data, rules, policies, conditions, triggers, actions, attributes, etc., regarding the autonomous adjustment, change, or modification of configurable parameters 904. Autonomous configuration 902 may describe one or more automated actions at UE 106 to adjust (e.g., automatically) one or more configurable parameters 904 upon triggering or triggering conditions. When adjusting configurable parameters 904 at UE 106, such as in response to network conditions, a technical benefit is that signaling overhead is minimized.

[0080] Figure 10 This is a structural view of PDCP layer 414. PDCP is further described in 3GPP TS 38.323 (Release 18), which is incorporated herein by reference in its entirety. PDCP layer 414, as described herein, can be implemented in UE 106 and / or RAN node 304 as described herein. As mentioned above, PDCP layer 414 is located between the upper RRC layer 416 and the lower RLC layer 412 of control plane 401, and between the SDAP layer 420 and the RLC layer 412 of user plane 402. Therefore, upper layer 1030 may include either RRC layer 416 or SDAP layer 420, and lower layer 1032 may include RLC layer 412.

[0081] PDCP layer 414 provides the following services to the upper layer 1030 (i.e., RRC or SDAP): transmission of user plane data, transmission of control plane data, header compression, encryption, and integrity protection. PDCP layer 414 expects at least the following services from the lower layer 1032 (i.e., RLC): acknowledged data transmission services (including indications of successful delivery of PDCP PDUs) and unacknowledged data transmission services. Examples of PDCP functions performed in PDCP layer 414 are listed below: data transmission (user plane or control plane), maintenance of PDCP sequence numbers, header compression and decompression, encryption and decryption, integrity protection and integrity verification, timer-based SDU dropping, routing for split bearers, replication, reordering and ordered delivery, out-of-order delivery, and duplicate dropping.

[0082] PDCP sublayer 1014 is configured by upper layer 1030 and is used to map radio bearers on logical channels of the DCCH, Dedicated Traffic Channel (DTCH), MBS Traffic Channel (MTCH), Sidelink Control Channel (SCCH), and Sidelink Traffic Channel (STCH) types. PDCP entity 914 resides in PDCP sublayer 1014, and each radio bearer (except for SRB0 used for the Uu interface) is associated with one PDCP entity 914. Several PDCP entities 914 can be defined for UE 106. PDCP entity 914 depends on which radio bearer it carries to be associated with control plane 401 or user plane 402. A Serving Access Point (SAP) is a logical connection (interface) between any two layers. PDCP Serving Access Point (PDCP-SAP) 1004 is a logical connection (interface) between PDCP layer 414 and SDAP layer 420. Control Serving Access Point (C-SAP) 1006 is a logical connection (interface) between PDCP layer 414 and RRC layer 416. Further reference Figure 10 The RLC Unacknowledged Mode SAP (RLC UM-SAP) is the logical connection (interface) between RLC layer 412 and PDCP layer 414, and the RLC Acknowledged Mode SAP (RLC AM-SAP) is the logical connection (interface) between RLC layer 412 and PDCP layer 414. PDCP layer 414 (and other layers) operates based on data units called Service Data Units (SDUs) and Packet Data Units (PDUs). The input to PDCP sublayer 1014 is called PDCP SDU 1008, and the output of PDCP sublayer 1014 is called PDCP PDU 1010 or RLC SDU 1034. Figure 10 An example of PDCP layer 414 is provided, and other structural or functional configurations of PDCP layer 414 are considered in this paper.

[0083] Figure 11A functional view of PDCP entity 914 is shown. As an example of the functions performed in PDCP sublayer 1014, PDCP SDU 1008 entering PDCP sublayer 1014 is first stored in transmission buffer 1108 of sending PDCP entity 1102, and then undergoes sequence numbering functionality, where sending PDCP entity 1102 adds a sequence number to each incoming PDCP SDU 1008. Sending PDCP entity 1102 is configured to perform a header compression process on user plane data. After header compression, there are two paths: 1) through an integrity / encryption process, and 2) directly to the PDCP header addition process. The PDCP header addition process adds a PDCP header to the data to generate PDCP PDU 1010. The PDCP routing function routes PDCP PDU 1010 to the intended bearer. Receiving PDCP entity 1104 reverses the transmission process as described above.

[0084] Figure 12 This is a structural view of MAC layer 410. MAC entity 910 of MAC layer 410 handles the following transport channels 1202: Broadcast Channel (BCH), Downlink Shared Channel (DL-SCH), Paging Channel (PCH), Uplink Shared Channel (UL-SCH), and Random Access Channel (RACH). MAC entity 910 of MAC layer 410 handles the following logical channels 1204: Broadcast Control Channel (BCCH), Paging Control Channel (PCCH), Common Control Channel (CCCH), Dedicated Control Channel (DCCH), Dedicated Traffic Channel (DTCH), MBS Control Channel (MCCH), and MBS Traffic Channel (MTCH). MAC layer 410 expects the following services from physical layer 404: data transmission service, signaling for Hybrid Automatic Repeat Request (HARQ) feedback, signaling for Scheduling Request (SR), and measurements (e.g., Channel Quality Indicator (CQI)). MAC layer 410 supports at least the following functions: mapping between logical channels 1204 and transport channels 1202; multiplexing MAC SDUs from one or more logical channels 1204 onto transport blocks (TBs) for delivery to physical layer 404 on transport channel 1202; demultiplexing MAC SDUs from transport channels 1202 to transport blocks (TBs) delivered from physical layer 404 onto one or more logical channels 1204; scheduling information reporting; error correction via HARQ; logical channel priority sorting; priority handling among overlapping resources of a UE; and radio resource selection. An example of MAC layer 410 is shown in... Figure 12 The MAC layer 410 is provided in the document, and other structural or functional configurations of the MAC layer 410 are considered in this document.

[0085] Figure 13This is a diagram illustrating the interaction between UE 106 and RAN node 304 in an illustrative embodiment. Figure 14A to Figure 14B This is a flowchart illustrating a method 1400 / 1430 for automatically adjusting configurable parameter 904 in an illustrative embodiment. The steps of method 1400 are described with reference to RAN node 304, and the steps of method 1430 are described with reference to UE 106; however, these methods may also be performed in other systems or devices. The steps in the flowcharts described herein are not exhaustive and may include other steps not shown, and these steps may be performed in an alternative order.

[0086] exist Figure 13 In this embodiment, UE 106 is pre-configured or pre-equipped with one or more autonomous configurations 902 from RAN node 304 for (e.g., automatically) adjusting one or more configurable parameters 904. In this embodiment, RAN node 304 may send a control plane message 1302 containing the autonomous configurations 902 to UE 106 (see [link to relevant documentation]). Figure 14A Step 1402 in the process. For example, RAN node 304 can send an RRC message containing autonomous configuration 902 to UE 106 (see step 1402 in the process). Figure 14A (Optional step 1404). As will be described in further detail below, a new RRC Information Element (IE) can be defined for the autonomous configuration 902, or the RRC IE can be extended to include or describe the autonomous configuration 902. UE 106 receives a control plane message 1302 containing the autonomous configuration 902 from RAN node 304 (see...). Figure 14B Step 1432 in the process. For example, UE 106 can receive an RRC message containing autonomous configuration 902 from RAN node 304 (see step 1432 in the process). Figure 14B (Optional step 1434 in the text). UE 106 parses control plane message 1302 to extract autonomous configuration 902 and stores autonomous configuration 902 in local memory (see [link]). Figure 14B (Step 1436 in the text). Utilizing the autonomous configuration 902 of local storage, UE 106 is able to act autonomously in response to one or more triggers or trigger conditions.

[0087] exist Figure 13 After UE 106 is pre-configured, UE 106 detects network status 1304 (see [link]). Figure 14B (Step 1438 in the original text). Network condition 1304 (also known as update condition) includes conditions or conditions related to communication between UE 106 and RAN node 304. UE 106 can detect network condition 1304 in response to condition information 1305 sent from RAN node 304 (see step 1438 in the original text). Figure 14A(Optional step 1406 in the example). In this embodiment, UE 106 may detect network condition 1304 as a change in the recommended bit rate (RBR) received from RAN node 304. For example, RAN node 304 may send or provide a recommended bit rate 1310 (RBR) to UE 106 (e.g., indicating a change to the RBR) (see [reference]). Figure 14A (Optional step 1408). As will be described in further detail below, RAN node 304 may send a recommended bit rate 1310 to UE 106 in the MAC control element (CE). In embodiments, RAN node 304 may send or provide a congestion indication to UE 106. Congestion indications include messages, data, information, signaling, etc., indicating congestion conditions, such as in the RAN, RAN node 304, and in the backhaul to the core network. For example, RAN node 304 may send an explicit congestion notification (ECN) 1312 to UE 106 (see [link to relevant documentation]). Figure 14A Optional step 1410). In another example, RAN node 304 may send RAN node congestion indicator 1314 to UE 106 (see 1410). Figure 14A (Optional step 1412).

[0088] To detect network conditions 1304, UE 106 can receive condition information 1305 sent from RAN node 304. For example, UE 106 can receive the Recommended Bit Rate (RBR) from RAN node 304 (e.g., indicating a change to the RBR) (see [link to relevant documentation]). Figure 14B Optional step 1440). In another example, UE 106 can receive explicit congestion notification (ECN) 1312 from RAN node 304 (see 1440). Figure 14B Optional step 1442). In another example, UE 106 can receive RAN node congestion indicator 1314 from RAN node 304 (see 1442). Figure 14B Optional step 1444).

[0089] In response to network condition 1304, UE 106 is based on the self-configuration 902 pre-configured on UE 106 (see [link]). Figure 14B Step 1446 in the above steps) or a selected autonomous configuration from among a plurality of autonomous configurations 902 pre-configured on UE 106 adjusts one or more configurable parameters 904. In other words, UE 106 is triggered on network condition 1304 and uses autonomous configuration 902 (or one of the plurality of autonomous configurations 902) to adjust one or more configurable parameters 904 without further external control from RAN node 304. In one example, UE 106 may adjust one or more PDCP configurable parameters 916 based on autonomous configuration 902 (see step 1446 in the above steps). Figure 14BOptional step 1448 in the example. In another example, UE 106 can adjust one or more MAC configurable parameters 912 based on self-configuration 902 (see [link]). Figure 14B (Optional step 1450).

[0090] RAN node 304 updates its local configuration parameters associated with UE 106 to align with the adjustments made to UE 106 (see [link]). Figure 14A (Step 1414 in the original text). For example, when RAN node 304 provides UE 106 with multiple autonomous configurations 902, RAN node 304 may store copies of multiple autonomous configurations 902 (or portions thereof) associated with UE 106. Therefore, RAN node 304 is able to predict or determine adjustments made on the UE side in response to network condition 1304.

[0091] After adjusting one or more configurable parameters 904, UE 106 performs uplink (UL) processing (i.e., uplink transmission 1306) based on the adjusted configurable parameters 904 (see [reference]). Figure 14B (Step 1452 in the previous section). Similarly, RAN node 304 performs uplink processing based on the adjusted configuration parameters (see step 1452 in the previous section). Figure 14A (Step 1416 in the text). The technical benefit is that UE 106 can automatically adapt to network conditions while minimizing signaling overhead.

[0092] In the following examples, additional procedures, systems, and methods can be described within the context of the configurable parameter 904 being autonomously adjusted at UE 106. The procedures, systems, and methods described in these examples may be incorporated into the embodiments described above as needed.

[0093] Discard timer In an embodiment, one or more configurable parameters 904 may be associated with a discarding process performed in PDCP layer 414 (i.e., PDCP configurable parameters 916 for the discarding process). Figure 15A discard procedure 1500 for transmission operations at PDCP layer 414 is illustrated. Upon receiving data unit 1504 (e.g., PDCP SDU 1008) from upper layer 1030, the transmitting PDCP entity 1102 buffers data unit 1504 (i.e., in buffer 1506) and starts a discard timer 1508. The data unit 1504 buffered in PDCP layer 414 may generally be referred to as a buffered data unit. If / when the discard timer 1508 expires, the transmitting PDCP entity 1102 monitors the discard timer 1508 and (at least) discards data unit 1504. Depending on the discard procedure 1500 or which functions are activated for the discard procedure, different discard timers 1508 may be configured or maintained in the transmitting PDCP entity 1102. One discard procedure 1500 is a timer-based discard procedure 1510. For the timer-based discard procedure 1510, the sending PDCP entity 1102 maintains a discard timer 1512 (e.g., "discardTimer"), which may be referred to herein as the first discard timer, PDCP discard timer, SDU discard timer, etc. The discard timer 1512 primarily reflects the QoS requirements of packets belonging to the service. The discard timer 1512 is configured for one or more DRBs 602. The duration 1514 of the discard timer 1512 is configured by the upper layer 1030, and the discard timer 1512 is started upon receipt of data unit 1504. When the discard timer 1512 associated with data unit 1504 expires or the successful delivery of data unit 1504 is confirmed by the PDCP status report 1530, the sending PDCP entity 1102 discards data unit 1504. In other words, the sending PDCP entity 1102 removes or removes data unit 1504 from the buffer 1506.

[0094] Figure 16 This is a block diagram illustrating a discarding process 1500 according to discarding timer 1512. When SDU 1602 (e.g., SDU-1) is received at transmitting PDCP entity 1102, discarding timer 1512 is started. When the discarding timer 1512 associated with SDU 1602 expires, transmitting PDCP entity 1102 discards SDU 1602.

[0095] exist Figure 15 Another dropping process 1500 is an importance-based dropping process 1520, also known as a PSI-based SDU dropping process. Importance can refer to PDU set importance (PSI), which identifies the relative importance of a PDU set within the same QoS flow 604 compared to other PDU sets. Figure 17PDU set 1704 is shown. PDU set 1704 includes one or more PDUs 1706 (e.g., PDU-1, PDU-2, PDU-3, etc.), which carry a payload of a single unit of information generated at the application layer (e.g., frames, video slices, etc. for extended reality (XR) services). PDUs 1706 in PDU set 1704 correspond to PDCP SDU 1008. PSI 1708 (also known as PSI indicator or PSI field) is an importance value that can be associated with PDU set 1704. For example, a smaller value indicates a higher importance set of PDUs, where, for example, a value "1" indicates the most important set of PDUs, and a value "15" indicates the least important set of PDUs.

[0096] exist Figure 15 In the importance-based discarding process 1520, the sending PDCP entity 1102 maintains another discarding timer 1508, referred to as the low importance (LI) discarding timer 1522 (e.g., "discardTimerForLowImportance"). The low importance discarding timer 1522 may be referred to herein as a second discarding timer, an importance discarding timer, an importance-related discarding timer, etc. As used herein, the term "low importance" refers to a specific term for data types that have lower importance relative to other data. The criteria for determining "low importance" are determined by the implementation. Therefore, the low importance discarding timer 1522 refers to a timer used to discard "low importance" data. The low importance discarding timer 1522 is configured for one or more DRBs 602. The duration 1524 of the low importance discarding timer 1522 is configured by the upper layer 1030. When the sending PDCP entity 1102 receives a data unit 1504 belonging to a low-importance PDU set from the upper layer 1030, the low-importance PDU set has relatively lower importance (e.g., based on threshold importance) compared to other PDU sets within the same QoS flow 604. For example, the low-importance PDU set may have PSI 1708 within a threshold importance range (e.g., in the range of "10-15"), above a threshold importance value (e.g., above "8", "9", "10", etc.). When the low-importance discard timer 1522 associated with the data unit 1504 expires or the successful delivery of the data unit 1504 is confirmed by the PDCP status report 1530, the sending PDCP entity 1102 discards the data unit 1504. In other words, the sending PDCP entity 1102 removes or removes the data unit 1504 from the buffer 1506.

[0097] Figure 18This is a block diagram illustrating a discarding process 1500 based on discard timer 1512 and low importance discard timer 1522. The duration 1524 of low importance discard timer 1522 is set or configured to be shorter than the duration 1514 of discard timer 1512. Low importance discard timer 1522 is started when an SDU 1602 (e.g., SDU-2) belonging to a low importance PDU set is received at the sending PDCP entity 1102. When the low importance discard timer 1522 associated with SDU 1602 expires, the sending PDCP entity 1102 discards SDU 1602.

[0098] For the aforementioned discarding process 1500, the sending PDCP entity 1102 can be configured with one or more PDU set discarding parameters 1532 (e.g., pdu-SetDiscard) indicating whether PDU set discarding is activated or deactivated. When the PDU set discarding parameter 1532 is deactivated, the sending PDCP entity 1102 can discard PDCP SDU 1008 along with its corresponding PDCP PDU 1010 when the discarding timer 1512 or the low importance discarding timer 1522 expires. When the PDU set discarding parameter 1532 is activated, the sending PDCP entity 1102 can discard all PDCP SDU 1008 (i.e., all) and their corresponding PDCP PDU 1010 belonging to the PDU set 1704 to which PDCP SDU 1008 belongs when the discarding timer 1512 or the low importance discarding timer 1522 expires.

[0099] Figure 19 This is a flowchart illustrating a method 1900 for performing a transmission operation in an illustrative embodiment. The steps of method 1900 are described with reference to the transmitting PDCP entity 1102, but this method can be performed in other systems or devices. The transmitting PDCP entity 1102 receives a PDCP SDU 1008 from the upper layer 1030 (step 1902). Upon receiving the PDCP SDU 1008, the transmitting PDCP entity 1102 determines whether a low importance discard timer 1522 is configured (and PSI-based SDU discarding is activated) and whether the PDCP SDU 1008 belongs to the low importance PDU set 1704 (step 1904). When the low importance discard timer 1522 is configured and the PDCP SDU 1008 belongs to the low importance PDU set 1704, the transmitting PDCP entity 1102 starts the low importance discard timer 1522 associated with the PDCP SDU 1008 (step 1906). Otherwise, the sending PDCP entity 1102 starts the discard timer 1512 associated with PDCPSDU 1008 (step 1908). Although an example of the sending operation has been provided above, variations of the sending operation are also considered in this document.

[0100] Figure 20 This is a flowchart illustrating a method 2000 for performing a discard operation in an illustrative embodiment. The steps of method 2000 are described with reference to the sending PDCP entity 1102, but this method can be performed in other systems or devices. Sending PDCP entity 1102 determines whether the successful delivery of PDCP SDU 1008 has been acknowledged by PDCP status report 1530 (step 2002). When PDCP status report 1530 acknowledges successful delivery of PDCP SDU 1008, sending PDCP entity 1102 discards PDCP SDU 1008 (step 2006) and the corresponding PDCP PDU 1010. When the successful delivery of PDCP SDU 1008 has not been acknowledged by PDCP status report 1530, sending PDCP entity 1102 determines whether discard timer 1512 or low-importance discard timer 1522 expires for PDCP PDU 1008 (step 2004). When the discard timer 1512 or the low-importance discard timer 1522 expires, the sending PDCP entity 1102 discards PDCP SDU 1008 (step 2006) and the corresponding PDCP PDU 1010. More specifically, when the PDU set discard parameter 1532 (e.g., pdu-SetDiscard) is configured or activated, the sending PDCP entity 1102 discards all PDCP SDU 1008 (i.e., all) and the corresponding PDCP PDU 1010 belonging to the PDU set 1704 to which PDCP SDU 1008 belongs. When the PDU set discard parameter 1532 is not configured or is deactivated, the sending PDCP entity 1102 discards PDCP SDU 1008 and the corresponding PDCP PDU 1010. Although an example of the discard procedure 1500 is provided above, variations of the discard procedure 1500 are considered herein.

[0101] In the embodiments described herein, UE 106 is configured to adjust or update the low importance discard timer 1522, and more specifically, the duration 1524 of the low importance discard timer 1522. In the following description, the adjustment of the duration 1524 of the low importance discard timer 1522 may generally be referred to as an adjustment of the low importance discard timer. Figure 21 Figure 22A-22B is a diagram illustrating the interaction between UE 106 and RAN node 304 in an illustrative embodiment. Figures 22A-22B are flowcharts illustrating method 2200 / 2230 for adjusting low-importance discard timer 1522 in an illustrative embodiment. The steps of method 2200 are described with reference to RAN node 304, and the steps of method 2230 are described with reference to UE 106, but this method may be performed in other systems or devices.

[0102] exist Figure 21 In this embodiment, UE 106 is pre-configured or has one or more drop timer configurations 2110 to adjust (e.g., automatically) one or more low-importance drop timers 1522 used for drop procedure 1500 in PDCP layer 414. In this embodiment, RAN node 304 may send a control plane message 1302 (or control plane signaling) to UE 106 containing information defining the drop timer configuration 2110 (see [link to documentation]). Figure 22A Step 2202 in the process. For example, RAN node 304 can send an RRC message containing discard timer configuration 2110 to UE 106 (see step 2202 in the process). Figure 22A (Optional step 2204). UE 106 receives control plane message 1302 containing discard timer configuration 2110 from RAN node 304 (see...). Figure 22B Step 2232 in the text). For example, UE 106 can receive an RRC message containing discard timer configuration 2110 from RAN node 304 (see step 2232 in the text). Figure 22B (Optional step 2234 in the text). UE 106 parses control plane message 1302 to extract discard timer configuration 2110 and stores discard timer configuration 2110 in local memory (see...). Figure 22B (Step 2236 in the process). With the local storage discard timer configured 2110, the UE 106 is able to act autonomously in response to one or more triggers or trigger conditions.

[0103] exist Figure 21 After UE 106 is pre-configured, UE 106 detects network status 1304 (see [link]). Figure 22B Step 2238 in the document). UE 106 can detect network condition 1304 in response to condition information 1305 sent from RAN node 304 (see step 2238 in the document). Figure 22A (Optional step 2206 in the example). In this embodiment, UE 106 can detect network condition 1304 as a change in the recommended bit rate (RBR) received from RAN node 304. For example, RAN node 304 can notify UE 106 (see [link to example]). Figure 22A In optional step 2208, a recommended bit rate 1310 (e.g., indicating a change to the RBR) is sent for a specific logical channel 1204 and a specific direction (such as uplink or downlink). In an embodiment, RAN node 304 may send or provide a congestion indication to UE 106. For example, RAN node 304 may send an explicit congestion notification (ECN) 1312 to UE 106 (see [link to UE 106]). Figure 22AOptional step 2210). In another example, RAN node 304 may send RAN node congestion indicator 1314 to UE 106 (see 10000). Figure 22A (Optional step 2212 in the document). However, it should be understood that this document takes into account other types of conditional information 1305 or network conditions 1304.

[0104] To detect network status 1304, UE 106 can receive status information 1305 sent from RAN node 304. For example, UE 106 can receive a recommended bit rate 1310 from RAN node 304 (e.g., indicating a change to the RBR) (see [link to relevant documentation]). Figure 22B Optional step 2240 in the example. In another example, UE 106 can receive explicit congestion notification (ECN) 1312 from RAN node 304 (see [link]). Figure 22B Optional step 2242). In another example, UE 106 can receive RAN node congestion indicator 1314 from RAN node 304 (see ...). Figure 22B Optional step 2244).

[0105] In response to network condition 1304, UE 106 is configured with drop timer 2110 pre-configured on UE 106 (see [link]). Figure 22B Step 2246 in the process can be used to adjust one or more low-importance drop timers 1522, or based on a selected drop timer configuration from among a plurality of drop timer configurations 2110 pre-configured on UE 106. In other words, UE 106 is triggered on network condition 1304 and uses drop timer configuration 2110 (or one of the multiple drop timer configurations 2110), information about network condition 1304, etc., to adjust the duration 1524 of one or more low-importance drop timers 1522 without further external control from RAN node 304.

[0106] RAN node 304 updates the low importance drop timer 1522 associated with one or more DRBs of UE 106 to align with the adjustments made by UE 106 (see [link]). Figure 22A (Step 2214 in the previous section). For example, when RAN node 304 provides UE 106 with (multiple) drop timer configurations 2110, RAN node 304 can store copies of (multiple) drop timer configurations 2110 (or portions thereof) associated with UE 106. Therefore, RAN node 304 can predict or determine adjustments to be made on the UE side in response to network condition 1304. After adjusting the low importance drop timer 1522, UE 106 uses the adjusted low importance drop timer 1522 (see step 2214 in the previous section). Figure 22BStep 2248) in the process is used to perform the drop procedure 1500 for uplink transmission 1306. One technical benefit is that the UE 106 can automatically adapt to network conditions while minimizing signaling overhead.

[0107] Figure 23 This is a flowchart illustrating a method 2300 for adjusting the discard process 1500 at UE 106 in an illustrative embodiment. The steps of method 2300 are described with reference to UE 106, but the method can be performed in other systems or devices. Method 2300 describes the adjustment of the duration 1524 of a low importance discard timer 1522 for a single DRB or multiple DRBs; however, it should be understood that a similar process can occur for low importance discard timers 1522 associated with other DRBs.

[0108] As described above, UE 106 (via PDCP layer 414) is configured to perform one or more drop procedures 1500, such as an importance-based drop procedure 1520. UE 106 receives information defining pre-configured drop timer configurations 2110 for the drop procedure 1500 (step 2302). As described above, UE 106 can receive a control plane message 1302 (or control plane signaling) from RAN node 304 containing information defining multiple drop timer configurations 2110. After pre-configuring UE 106, UE 106 detects network conditions 1304 based on communications from RAN node 304 (step 2304). As described above, UE 106 can detect network conditions 1304 in response to condition information 1305 sent from RAN node 304.

[0109] In response to network condition 1304, UE 106 adjusts the duration of a drop timer (e.g., the duration 1524 of a low-importance drop timer 1522) based on one of the pre-configured drop timer configurations 2110 (see step 2306). In the example, as part of the drop procedure 1500, UE 106 is configured to maintain a drop timer 1508, such as a low-importance drop timer 1522 in PDCP layer 414. UE 106 can be triggered on network condition 1304 and adjust the duration 1524 of the low-importance drop timer 1522 using one of the drop timer configurations 2110, information about network condition 1304, etc., without further external control from RAN node 304. Therefore, UE 106 is able to adjust the duration 1524 of the low-importance drop timer 1522 based on UE 106's local configuration (e.g., drop timer configuration 2110) instead of receiving additional signaling from RAN node 304. UE 106 then performs a drop procedure 1500 to drop one or more buffered data units (e.g., PCDP SDU 1008) based on the duration of an adjusted drop timer (e.g., the duration 1524 of an adjusted low-importance drop timer 1522) (step 2308). One technical benefit is that UE 106 can autonomously operate to modify the drop timer at PDCP layer 414, which minimizes signaling overhead. For example, if congestion exists in the RAN, UE 106 can automatically shorten or reduce the duration 1524 of the low-importance drop timer 1522, causing the PDCP SDU 1008 associated with the low-importance PDU set to be dropped more quickly.

[0110] Figures 24 to 25 This is a diagram illustrating the interaction between UE 106 and RAN node 304 in an illustrative embodiment. For example... Figure 9 As shown, PDCP layer 414 includes PDCP configurable parameters 916, such as parameters for the discard procedure 1500. The PDCP configurable parameters 916 of UE 106 can be configured or equipped by RAN node 304 in control plane signaling. Figure 24The standard configuration of UE 106 is shown. RAN node 304 can configure the PDCP layer 414 of UE 106 using RRC message 2402. RRC message 2402 contains a PDCP configuration information element (IE), which includes field descriptions (e.g., discardTimer) for one or more discard timers 1512, indicating the value or duration 1514 used for discarding timers 1512 (e.g., ms10, ms20, ms30, ms40, ms50, ms60, ms75, ms100, ms150, ms200, ms250, ms300, ms500, ms750, ms1500, infinity). Similarly, the PDCP configuration IE includes field descriptions (e.g., DiscardTimerForLowImportance) for one or more low-importance discard timers 1522, indicating the value or duration 1524 (e.g., ms0, ms2, ms4, ms6, ms8, ms10, ms12, ms14, ms18, ms22, ms26, ms30, ms40, ms50, ms75, ms100) for the low-importance discard timer 1522. Again, note that the duration 1524 of the low-importance discard timer 1522 is configured to be shorter than the duration 1514 of the discard timer 1512. UE 106 stores the information from the PDCP configuration IE in memory as a legacy or default discard timer configuration 2410. Therefore, UE 106 will perform the discard process 1500 based on the durations of the low-importance discard timer 1522 and the discard timer 1512 as specified in the PDCP configuration IE.

[0111] Figure 25An enhanced configuration of UE 106 in an illustrative embodiment is shown. In this embodiment, RRC message 2402 includes an enhanced or extended PDCP configuration IE, which includes a field description of the low-importance discard timer 1522 (e.g., DiscardTimerForLowImportance) as described above. The extended MAC configuration IE also includes a field description for one or more discard timer configurations 2110 (also referred to as autonomous discard timer configurations). It should also be noted that the enhanced or extended PDCP configuration IE may also include a field description of a discard timer 1512 (e.g., discardTimer) indicating the value or duration 1514 of the discard timer 1512. The discard timer configuration 2110 includes information, data, rules, policies, conditions, triggers, actions, etc., that control, describe, or otherwise specify adjustments to one or more low-importance discard timers 1522. However, UE 106 may receive the discard timer configuration 2110 in other ways or in other types of signaling messages. In any case, UE 106 is equipped with or pre-equipped with one or more drop timer configurations 2110, and the drop timer configurations 2110 are stored in memory as local configurations (i.e., UE 106 is authorized to operate based on local configurations without network authorization or intervention).

[0112] Typically, it can be beneficial to adjust UE 106 and / or the network according to various network conditions. One way to adjust according to network conditions is to use a recommended bit rate procedure at MAC layer 410. The recommended bit rate procedure is described in more detail in 3GPP TS 38.321 (Release 18), which is incorporated herein by reference in its entirety. The recommended bit rate procedure is used to provide MAC entity 910 with information about the recommended bit rate for RAN node 304 (e.g., gNB). The bit rate is the recommended bit rate at physical layer 404.

[0113] One way to provide the recommended bit rate of 1310 is by using the MAC control element (MAC CE) 2504. Figure 26This is a block diagram of MAC PDU 2600. MAC PDU 2600 is a bit string of byte-aligned length (i.e., a multiple of 8 bits). MAC PDU 2600 includes one or more MAC sub-PDUs 2602. MAC sub-PDU 2602 begins with MAC subheader 2604(H). Following MAC subheader 2604 is sub-PDU payload 2606. Sub-PDU payload 2606 may include MAC SDU 2610, MAC CE 2504, or padding bits 2614. MAC SDU 2610 is a data unit (i.e., the actual or raw data that the application layer wants to send or receive) passed between layers of the radio protocol stack. MAC CE 2504 is a dedicated data structure within MAC PDU 2600 used to communicate control information between the UE and RAN (e.g., gNB306). 5G NR has defined a list of MAC CEs in 3GPP TS 38.321. MAC CE facilitates faster signaling and thus reduces latency in beam switching, bandwidth portion (BWP) activation, serving cell (SCell) activation / deactivation, etc. Padding bit 2614 appears at the end of the MAC PDU 2600. A MAC sub-PDU 2602 with padding bit 2614 is included when a set of MAC sub-PDUs 2602 cannot exactly fill a transport block (TB). A MAC sub-PDU 2602 with only MAC subheader 2604 implies zero-length padding. MAC subheader 2604, MAC SDU 2610, and MAC CE 2504 are byte-aligned bit strings. The leftmost bit is the most significant bit. The order of MAC sub-PDUs 2602 in the MAC PDU 2600 is defined. In sidelinks (SL) and uplinks (UL), the concatenation order is MAC SDU 2610, MAC CE 2504, and then padding bit 2614. In the downlink (DL), the sequence is MAC CE 2504, MAC SDU 2610, followed by padding bit 2614. In each case, padding bit 2614 is the final MAC sub-PDU 2602.

[0114] exist Figure 25In this configuration, RAN node 304 can use RBR MAC CE 2504 to indicate a recommended bit rate 1310 for logical channel 1204 to UE 106. UE 106's MAC entity 910 can request or query RAN node 304 to indicate the recommended bit rate 1310 for logical channel 1204. RAN node 304 (e.g., in response to network conditions) can modify or change the recommended bit rate 1310 for one or more logical channels 1204. For example, RAN node 304 can send RBR MAC CE 2504 to UE 106 indicating a change in the recommended bit rate 1310 for logical channel 1204. Upon receiving RBR MAC CE 2504, UE 106's MAC entity 910 indicates the recommended bit rate 1310 for the indicated logical channel and direction to the upper layer (e.g., PDCP layer 414).

[0115] In response to a change in the recommended bit rate 1310, UE 106 (i.e., PDCP entity 914 within UE 106) is configured to adjust, change, update, or modify the low importance drop timer 1522 in response to a change in the recommended bit rate 1310. The drop timer configuration 2110 corresponds to a range of values ​​for a bit rate indicator, such as the recommended bit rate 1310 from RAN node 304. UE 106 is configured to adjust the low importance drop timer 1522 based on the drop timer configuration 2110 (i.e., when the recommended bit rate 1310 falls within the range of values ​​for the drop timer configuration 2110), and to perform the drop procedure 1500 in PDCP layer 414 based on the adjusted low importance drop timer 1522. In other words, UE 106 is configured to autonomously act in response to a change in the recommended bit rate 1310 to adjust the low importance drop timer 1522 upwards or downwards. No further signaling is required between UE 106 and RAN node 304 to adjust the low importance drop timer 1522 because UE 106 is configured to act autonomously. For example, RAN node 304 does not need to send additional RRC signaling to UE 106 to adjust the low importance drop timer 1522, saving bandwidth and processing resources. Another benefit is that UE 106 can gradually adjust the low importance drop timer 1522 to better handle congestion conditions. However, DRB reconfiguration can be avoided when modifying the recommended bit rate 1310 for DRB, especially when the increment of the recommended bit rate 1310 is within the configuration range.

[0116] Figure 27A discard timer configuration 2110 is illustrated in an illustrative embodiment. The discard timer configuration 2110 includes configuration information 2702 authorizing adjustments to one or more low-importance discard timers 1522 at UE 106. The configuration information 2702 may authorize adjustments to the low-importance discard timers 1522 for each DRB or DRB group. In embodiments, the configuration information 2702 may include a configuration scope 2704, which may include a specific DRB or DRB group for UE 106. In some embodiments, one or more configurations may be assigned to DRBs to set more detailed UE behavior for discarding low-importance data. The configuration information 2702 may include a configuration target 2706, wherein UE 106 is authorized to take certain actions without requiring signaling exchange with the network. For example, configuration target 2706 may include one or more RBR values ​​2710 (“autonomous” values) that trigger adjustments to the low importance drop timer 1522, a range 2712 (“autonomous range”) of RBR values ​​that trigger adjustments to the low importance drop timer 1522, and an RBR threshold 2714 (“autonomous” threshold) where RBR values ​​higher than or lower than an RBR threshold 2714 trigger adjustments to the low importance drop timer 1522. Configuration information 2702 may include configuration validity. Validity timer 2708 may be assigned to drop timer configuration 2110 (or each of drop timer configurations 2110). When validity timer 2708 expires, UE 106 may deactivate drop timer configuration 2110 and fall back or switch to default configuration 2410 (e.g., legacy behavior / configuration).

[0117] In this embodiment, configuration information 2702 may include one or more configuration triggers 2720 and one or more corresponding configuration actions 2722. Configuration triggers 2720 may be based on a recommended bit rate 1310. For example, UE 106 may compare the recommended bit rate 1310 with an RBR threshold 2714, a range of RBR values ​​2712, etc. In this embodiment, configuration triggers indirectly related to network information / conditions (e.g., ECN tags, RAN node congestion indicators, etc.) may be considered triggers for configuration actions 2722. UE 106 and RAN node 304 align on how to apply configuration triggers 2720 on the UE side (e.g., agreed-upon expected behavior).

[0118] When configuration trigger 2720 has occurred, one or more configuration actions 2722 are performed. For example, when configuration trigger 2720 has occurred, UE 106 can change or adjust the low importance discard timer 1522.

[0119] There are several alternatives to adjusting the low-importance discard timer 1522. Figure 28A drop timer configuration 2110 is shown in another illustrative embodiment. Drop timer configuration 2110 can specify values ​​that UE 106 is authorized to use when adjusting the low-importance drop timer 1522. Because drop timer configuration 2110 is pre-configured or pre-configured on UE 106, the values ​​described in drop timer configuration 2110 can be referred to as pre-configured values.

[0120] In an embodiment, the drop timer configuration 2110 may specify a list or set 2802 of duration values. The UE 106 may select a value from the set 2802 of duration values ​​(i.e., a value different from the current value) and use the selected value to adjust the low importance drop timer 1522. For example, if the duration 1524 of the low importance drop timer 1522 is currently assigned a value of 75 milliseconds (ms), the UE 106 may select a value of 50 ms from the set 2802 of duration values. In one embodiment, the set 2802 of duration values ​​may include values ​​specified for the low importance drop timer 1522 in the 5G specification (i.e., ms0, ms2, ms4, ms6, ms8, ms10, ms12, ms14, ms18, ms22, ms26, ms30, ms40, ms50, ms75, ms100). In an embodiment, the set 2802 of duration values ​​may include additional values ​​that supplement or replace the values ​​specified in the 5G specification (e.g., with a more progressive adaptation). One technical benefit is that RAN node 304 can specify adjustments to be made within UE 106.

[0121] In an embodiment, the drop timer configuration 2110 may specify an offset value 2804. The offset value 2804 is obtained by subtracting x ms from or adding x ms to the current duration value of the low-importance drop timer 1522. For example, assuming the current duration value of the low-importance drop timer 1522 is 40 ms, when the offset value 2804 is -5 ms, the adjusted duration 1524 of the low-importance drop timer 1522 will be 35 ms. One technical benefit is that the RAN node 304 can fine-tune adjustments made within the UE 106 for configurations in the DRB (e.g., when the DRB is established).

[0122] In an embodiment, the drop timer configuration 2110 can specify a list or set of duration values ​​2802 and an offset value 2804. For example, UE 106 can select a value of 50ms from the set of duration values ​​2802 and apply an offset value of 5ms 2804. Therefore, the value of the duration 1524 of the adjusted low importance drop timer 1522 will be 25ms. One technical benefit is that RAN node 304 can fine-tune the adjustments made within UE 106 for configurations in the DRB (e.g., when the DRB is established).

[0123] Figure 29 Another illustrative embodiment of the drop timer configuration 2110 is shown. In this example, a first configuration trigger 2720 specifies that UE 106 does not adjust the low importance drop timer 1522 when the RBR value is within the range 2712 of the RBR value (e.g., V1 to V2). A second configuration trigger 2720 specifies that UE 106 adjusts the low importance drop timer 1522 when the RBR value is within another range 2712 of the RBR value (e.g., V3 to V4). As described above, UE 106 can add or subtract an offset value 2804 based on the current duration 1524 of the low importance drop timer 1522 to calculate the adjusted duration 1524 of the low importance drop timer 1522. UE 106 can select a value (a value different from the current value) from the set of duration values ​​2802 as the adjusted duration 1524 of the low importance drop timer 1522. UE 106 can select a value (a value different from the current value) from the set of duration values ​​2802 and apply the offset value 2804 to calculate the duration 1524 of the adjusted low importance discard timer 1522.

[0124] Figure 30 Additional details are shown regarding adjusting the low-importance discard timer 1522 in an illustrative embodiment. To adjust the duration of the discard timer (see...),... Figure 23 In step 2306), UE 106 can adjust the duration based on an offset value 2804 specified in one of the pre-configured drop timer configurations 2110 (optional step 3002). In an alternative embodiment, UE 106 can adjust the duration by selecting a duration value from the set 2802 of duration values ​​specified in one of the pre-configured drop timer configurations 2110 (optional step 3004). In an alternative embodiment, UE 106 can adjust the duration by selecting a duration value from the set 2802 of duration values ​​and applying the offset value 2804 to the selected duration value as specified in one of the pre-configured drop timer configurations 2110 (optional step 3006). One technical benefit is that UE 106 is able to adjust the low-importance drop timer 1522 based on pre-configured information.

[0125] Delay status report threshold In an embodiment, one or more configurable parameters 904 may be associated with a Delayed State Report (DSR) procedure performed in MAC layer 410 (i.e., MAC configurable parameters 912 for the DSR procedure). Figure 31The DSR procedure 3100 at MAC layer 410 is illustrated. Similar to PDCP layer 414, MAC layer 410 operates based on data units called Service Data Units (SDUs) and Packet Data Units (PDUs). Typically, the inputs to MAC layer 410 are referred to as MAC SDUs 2610, and the outputs of MAC layer 410 are referred to as MAC PDUs 2600 or Transport Blocks (TBs). Figure 31 An example of MAC layer 410 is provided in this document, and other structural or functional configurations of MAC layer 410 are also considered in this document.

[0126] The DSR procedure 3100 is used to provide the RAN node 304 (e.g., serving gNB 306) with the delay status 3116 of logical channels 1204 or logical channel groups (LCGs) 3104 (e.g., 3104-1, 3104-2, 3104-3, etc.). An LCG 3104 is a set of logical channels 1204 for which it reports the delay status 3116 (see [link to relevant documentation]). Figure 12 The delay state 3116 of LCG 3104 includes a remaining time 3118, which is the minimum remaining value of the running PDCP discard timer 1512 (e.g., discard timer 1512-1, 1512-2, etc.) in the PDCP SDU1008 buffered for LCG 3104 but not yet transmitted in any MAC PDU 2600, and the total amount of delay-critical UL data for LCG 3104 calculated according to the data volume calculation process of RLC layer 412 and PDCP layer 414. PDCP data volume 3134 is the amount of data available for transmission in PDCP entity 914 (PDCP layer 414), and the data volume calculation process for PDCP is further described in 3GPP TS38.323. RLC data volume 3132 is the amount of data available for transmission in RLC entity (RLC layer 412). The data volume calculation process for RLC is further described in 3GPP TS 38.322 (Revision 18), which is incorporated herein by reference in its entirety.

[0127] RRC layer 416 (see...) Figure 4 The DSR process 3100 is controlled by configuring a MAC configurable parameter 912 referred to as the Remaining Time Threshold (TH) 3122 (e.g., Remaining Time Threshold) for each logical channel 1204 or LCG 3104. The Remaining Time Threshold 3122 (also referred to as the DSR Remaining Time Threshold) is a threshold on the remaining time 3118 used to trigger the DSR 3120 for logical channel 1204 within LCG 3104.

[0128] Figure 32This is a flowchart illustrating a method 3200 for performing delay status reporting in an illustrative embodiment. The steps of method 3200 are described with reference to MAC entity 910, although the method may be performed in other systems or devices. If LCG 3104 is configured for delay status reporting, then MAC entity 910 determines for each logical channel 1204 within LCG 3104 whether the minimum remaining value of the running PDCP discard timer 1512 in the (e.g., all) PDCP SDUs 1008 buffered for logical channel 1204 that has not yet been transmitted in any MAC PDU 2600 and has not yet been reported as data volume in DSR MAC CE 2504 becomes lower than the remaining time threshold 3122 of LCG 3104 (step 3202). When the minimum remaining value of the running PDCP discard timer 1512 is lower than the remaining time threshold 3122, MAC entity 910 determines whether there is an pending DSR 3120 for logical channel 1204 (step 3204). When there is no pending DSR 3120, MAC entity 910 triggers DSR 3120 for logical channel 1204 (step 3206). When at least one pending DSR 3120 exists, MAC entity 910 determines whether the UL SCH resource is available for a new transmission, and that the UL SCH resource can accommodate DSR MAC CE 2504 plus its sub-header due to logical channel prioritization (step 3208). When the UL SCH resource is available, MAC entity 910 instructs a multiplexing and reassembly process to generate DSR MACCE 2504 (step 3210). When the UL SCH resource is unavailable, if the DSR process 3100 for the same logical channel 1204 as the DSR 3120 has not yet triggered a pending SR, MAC entity 910 triggers a scheduling request (SR) (step 3212).

[0129] After DSR 3120 is triggered, it is considered pending until it is cancelled. The MAC entity 910 cancels the pending DSR 3120 when all PDCP SDU 1008 associated with DSR 3120 are discarded, or when MAC PDU 2600 is sent and includes a DSR MAC CE 2504 containing delay information for all PDCP SDU 1008 associated with DSR 3120, or when MAC PDU 2600 is sent and includes all PDCP SDU 1008 associated with DSR 3120. Although an example of DSR procedure 3100 is provided above, variations of DSR procedure 3100 are considered herein.

[0130] In the embodiments described herein, UE 106 is configured to adjust or update the remaining time threshold 3122 for DSR procedure 3100. Figure 33 This is a diagram illustrating the interaction between UE 106 and RAN node 304 in an illustrative embodiment. Figures 34A-34B This is a flowchart illustrating a method 3400 / 3430 for adjusting a remaining time threshold 3122 in an illustrative embodiment. The steps of method 3400 are described with reference to RAN node 304, and the steps of method 3430 are described with reference to UE 106, but this method may be performed in other systems or devices.

[0131] exist Figure 33 In this embodiment, UE 106 is pre-configured or pre-configured with one or more remaining time threshold configurations 3310 to adjust (e.g., automatically) one or more remaining time thresholds 3122 of the DSR procedure 3100 in MAC layer 410. In this embodiment, RAN node 304 may send a control plane message 1302 (or control plane signaling) to UE 106 containing information defining the remaining time threshold configuration 3310 (see [link to relevant documentation]). Figure 34A Step 3402 in the process. For example, RAN node 304 can send an RRC message containing the remaining time threshold configuration 3310 to UE 106 (see step 3402 in the process). Figure 34A (Optional step 3404). UE 106 receives control plane message 1302 containing remaining time threshold configuration 3310 from RAN node 304 (see...). Figure 34B Step 3432 in the process). For example, UE106 can receive an RRC message containing the remaining time threshold configuration 3310 from RAN node 304 (see step 3432 in the process). Figure 34B (Optional step 3434 in the text). UE 106 parses control plane message 1302 to extract the remaining time threshold configuration 3310, and stores the remaining time threshold configuration 3310 in local memory (see...). Figure 34B (Step 3436 in the process). With the local storage remaining time threshold configured 3310, UE 106 is able to act autonomously in response to one or more triggers or trigger conditions.

[0132] exist Figure 33 After UE 106 is pre-configured, UE 106 detects network status 1304 (see [link]). Figure 34B Step 3438 in the process). UE 106 can detect network condition 1304 in response to condition information 1305 sent from RAN node 304 (see step 3438). Figure 34A(Optional step 3406 in the example). In this embodiment, UE 106 may detect network condition 1304 as a change in the recommended bit rate (RBR) received from RAN node 304. For example, RAN node 304 may send a signal to UE 106 (see [link to example]). Figure 34A In optional step 3408, a recommended bit rate 1310 (e.g., indicating a change to the RBR) is sent for a specific logical channel 1204 and a specific direction (such as uplink or downlink). In an embodiment, RAN node 304 may send or provide a congestion indication to UE 106. For example, RAN node 304 may send an explicit congestion notification (ECN) 1312 to UE 106 (see [link to UE 106]). Figure 34A Optional step 3410). In another example, RAN node 304 may send RAN node congestion indicator 1314 to UE 106 (see step 3410). Figure 34A (Optional step 3412). However, it should be understood that other types of conditional information 1305 are considered in this document.

[0133] To detect network status 1304, UE 106 can receive status information 1305 sent from RAN node 304. For example, UE 106 can receive a recommended bit rate 1310 from RAN node 304 (e.g., indicating a change to the RBR) (see [link to relevant documentation]). Figure 34B Optional step 3440 in the example. In another example, UE 106 can receive explicit congestion notification (ECN) 1312 from RAN node 304 (see step 3440). Figure 34B Optional step 3442). In another example, UE 106 can receive RAN node congestion indicator 1314 from RAN node 304 (see ...). Figure 34B Optional step 3444).

[0134] In response to network condition 1304, UE 106 configures 3310 based on the remaining time threshold pre-configured on UE 106 (see [link]). Figure 34B Step 3446 in the process can be used to adjust one or more remaining time thresholds 3122, or based on one of a plurality of remaining time threshold configurations 3310 pre-configured on UE 106. In other words, UE 106 is triggered on network condition 1304 and uses remaining time threshold configuration 3310 (or one of a plurality of remaining time threshold configurations 3310), information from network condition 1304, etc., to adjust one or more remaining time thresholds 3122 without further external control from RAN node 304.

[0135] RAN node 304 updates the remaining time threshold 3122 associated with LCG 3104 to align with the adjustment made by UE 106 (see [link]). Figure 34A(Step 3414 in the previous section). For example, when RAN node 304 provides UE 106 with the remaining time threshold configuration 3310, RAN node 304 may store a copy of the remaining time threshold configuration 3310 (or a portion thereof) associated with UE 106. Therefore, RAN node 304 is able to predict or determine adjustments to be made on the UE side in response to network condition 1304.

[0136] After adjusting the remaining time threshold 3122, UE 106 performs DSR procedure 3100 based on the adjusted remaining time threshold 3122 (see [link]). Figure 34B (Step 3448 in the original text). For example, when the minimum remaining value of the PDCP drop timer 1512 for logical channel 1204 within LCG 3104 is lower than the adjusted remaining time threshold 3122, UE 106 can trigger DSR 3120 for logical channel 1204 toward RAN node 304. One technical benefit is that UE 106 can automatically adapt to network conditions while minimizing signaling overhead. Another technical benefit is that the adjustment of the remaining time threshold 3122 helps the network improve its chances of scheduling time-delayed critical data in a timely manner.

[0137] Figure 35 This is a flowchart illustrating a method 3500 for performing a delay state report at the UE in an illustrative embodiment. The steps of method 3500 are described with reference to UE 106, but the method can be performed in other systems or devices. Method 3500 describes the adjustment of the remaining time threshold 3122 for an individual LCG 3104, but it should be understood that a similar process can occur for the remaining time threshold 3122 of other LCGs 3104.

[0138] As described above, UE 106 (via PDCP layer 414) is configured to perform drop procedure 1500. As part of drop procedure 1500, UE 106 maintains one or more (running) drop timers 1512 in PDCP layer 414 regarding PDCP SDU 1008 buffered for LCG 3104. UE 106 (via MAC layer 410) is also configured to perform DSR procedure 3100.

[0139] UE 106 receives information defining a pre-configured remaining time threshold configuration 3310 for the DSR procedure 3100 (step 3502). As described above, UE 106 can receive a control plane message 1302 (or control plane signaling) from RAN node 304 containing information defining multiple remaining time threshold configurations 3310. After pre-configuring UE 106, UE 106 detects network conditions 1304 based on communication from RAN node 304 (step 3504). As described above, UE 106 can detect network conditions 1304 in response to condition information 1305 sent from RAN node 304.

[0140] In response to network condition 1304, UE 106 adjusts the remaining time threshold 3122 corresponding to DSR procedure 3100 based on one of the pre-configured remaining time threshold configurations 3310 (see step 3506). UE 106 can trigger on network condition 1304 and adjust the remaining time threshold 3122 using one of the remaining time threshold configurations 3310, information from network condition 1304, etc., without further external control from RAN node 304. Therefore, UE 106 can adjust the remaining time threshold 3122 based on UE 106's local configuration (e.g., remaining time threshold configuration 3310) instead of receiving additional signaling from RAN node 304. Then, when the drop timer 1512 associated with the buffered data unit falls below the adjusted remaining time threshold 3122, UE 106 executes DSR procedure 3100 based on the adjusted remaining time threshold 3122 to trigger a delay status report 3120 to RAN node 304 (step 3508). One technical benefit is that UE 106 can act autonomously to modify the remaining time threshold 3122, which minimizes signaling overhead.

[0141] Figures 36 to 37 This is a diagram illustrating the interaction between UE 106 and RAN node 304 in an illustrative embodiment. For example... Figure 9 As shown, MAC layer 410 includes MAC configurable parameters 912, such as parameters used for DSR procedure 3100. MAC configurable parameters 912 of UE 106 can be configured or equipped by RAN node 304 in control plane signaling. Figure 36The standard configuration of UE 106 is shown. RAN node 304 can configure the MAC layer 410 of UE 106 using RRC message 2402. RRC message 2402 contains a MAC configuration information element (IE), which includes field descriptions for one or more remaining time thresholds 3122 (e.g., remainingTimeThreshold). The field descriptions indicate the value of the remaining time threshold 3122 for one or more LCGs 3104, such as an integer between 1 and 64. UE 106 stores the information from the MAC configuration IE in memory as a conventional or default remaining time threshold configuration 3610. Therefore, UE 106 will perform the DSR procedure 3100 based on the remaining time threshold 3122 specified in the MAC configuration IE.

[0142] Figure 37 An enhanced configuration of UE 106 in an illustrative embodiment is shown. In this embodiment, RRC message 2402 includes an enhanced or extended MAC configuration IE. The extended MAC configuration IE may include field descriptions for one or more remaining time thresholds 3122 (e.g., remaining time thresholds) as described above. The extended MAC configuration IE also includes field descriptions for one or more remaining time threshold configurations 3310 (also referred to as autonomous remaining time threshold configurations). The remaining time threshold configuration 3310 includes information, data, rules, policies, conditions, triggers, actions, etc., that control, describe, or otherwise specify adjustments to one or more remaining time thresholds 3122. However, UE 106 may receive the remaining time threshold configuration 3310 in other ways or in other types of signaling messages. In any case, UE 106 is equipped with or pre-equipped with one or more remaining time threshold configurations 3310 and stores the remaining time threshold configuration 3310 as a local configuration in memory (i.e., UE 106 is authorized to operate based on the local configuration without network authorization or intervention).

[0143] RAN node 304 can use RBR MAC CE 2504 to indicate to UE 106 the recommended bit rate 1310 for logical channel 1204. UE 106's MAC entity 910 can request or query RAN node 304 to indicate the recommended bit rate 1310 for logical channel 1204. RAN node 304 (e.g., in response to network conditions) can modify or change the recommended bit rate 1310 for one or more logical channels 1204. For example, RAN node 304 can send RBR MAC CE 2504 to UE 106 indicating a change to the recommended bit rate 1310 for logical channel 1204.

[0144] In response to a change in the recommended bit rate 1310, UE 106 (i.e., MAC entity 910 within UE 106) is configured to adjust, change, update, or modify the remaining time threshold 3122 of the LCG 3104 to which logical channel 1204 belongs in response to the change in the recommended bit rate 1310. The remaining time threshold configuration 3310 corresponds to a range of values ​​for a bit rate indicator, such as the recommended bit rate 1310 from RAN node 304. UE 106 is configured to adjust the remaining time threshold 3122 based on the remaining time threshold configuration 3310 (i.e., when the recommended bit rate 1310 falls within the range of values ​​for the remaining time threshold configuration 3310), and to perform a DSR procedure 3100 in MAC layer 410 based on the adjusted remaining time threshold 3122. A technical advantage is that no further signaling is required between UE 106 and RAN node 304 to adjust the remaining time threshold 3122, as UE 106 is configured to act autonomously. For example, RAN node 304 does not need to send additional RRC signaling to UE 106 to adjust the remaining time threshold 3122, which saves bandwidth and processing resources.

[0145] Figure 38 A remaining time threshold configuration 3310 is illustrated in an illustrative embodiment. The remaining time threshold configuration 3310 includes configuration information 3802 authorizing the adjustment of one or more remaining time thresholds 3122 at UE 106. The configuration information 3802 may authorize the adjustment of the remaining time threshold 3122 for each logical channel 1204 or LCG 3104. In embodiments, the configuration information 3802 may include a configuration range 3804, which may include a specific LCG 3104 or multiple LCGs 3104 for UE 106. The configuration information 3802 may include a configuration target 3806, wherein UE 106 is authorized to take certain actions without requiring signaling exchange with the network. For example, configuration target 3806 may include one or more RBR values ​​3810 (“autonomous” values) that trigger adjustment of remaining time threshold 3122, a range 3812 (“autonomous range”) of RBR values ​​that trigger adjustment of remaining time threshold 3122, and an RBR threshold 3814 (“autonomous” threshold) where RBR values ​​higher than or lower than RBR threshold 3814 trigger adjustment of remaining time threshold 3122. Configuration information 3802 may include configuration validity. Validity timer 3808 may be assigned to remaining time threshold configuration 3310 (or each of the remaining time threshold configurations 3310). When validity timer 3808 expires, UE 106 may deactivate remaining time threshold configuration 3310 and fall back or switch to default configuration 3610 (e.g., legacy behavior / configuration).

[0146] In an embodiment, configuration information 3802 may include one or more configuration triggers 3820 and one or more corresponding configuration actions 3822. Configuration triggers 3820 may be based on a recommended bit rate 1310. For example, UE 106 may compare the recommended bit rate 1310 with an RBR threshold 3814, a range of RBR values ​​3812, etc. In an embodiment, configuration triggers indirectly related to network information / conditions (e.g., ECN tags, RAN node congestion indicators, etc.) may be considered triggers for configuration actions 3822. UE 106 and RAN node 304 align on how to apply configuration triggers 3820 on the UE side (e.g., agreed-upon expected behavior).

[0147] When configuration trigger 3820 has occurred, perform one or more configuration actions 3822. For example, when configuration trigger 3820 of LCG 3104 has occurred, UE 106 can change or adjust the remaining time threshold 3122 of LCG 3104.

[0148] There are several alternatives to adjusting the remaining time threshold 3122. Figure 39 A remaining time threshold configuration 3310 is shown in another illustrative embodiment. The remaining time threshold configuration 3310 can specify the value that the UE 106 is authorized to use when adjusting the remaining time threshold 3122. Because the remaining time threshold configuration 3310 is pre-configured or pre-configured on the UE 106, the values ​​described in the remaining time threshold configuration 3310 can be referred to as pre-configured values.

[0149] In an embodiment, the remaining time threshold configuration 3310 can specify a list or set of thresholds 3902. UE 106 can select a value (i.e., different from the current value) from the set of thresholds 3902 and use the selected value to adjust the remaining time threshold 3122. For example, if the remaining time threshold 3122 of LCG 3104 is currently assigned the value "45", then UE 106 can select the value "30" from the set of thresholds 3902. One technical benefit is that RAN node 304 can specify adjustments made within UE 106.

[0150] In an embodiment, the remaining time threshold configuration 3310 may specify an offset value 3904. The offset value 3904 is obtained by subtracting x from or adding x to the current value assigned to the remaining time threshold 3122. For example, suppose the current value of the remaining time threshold 3122 is "45". When the offset value 3904 is "-10", the adjusted value of the remaining time threshold 3122 will be "35". One technical benefit is that the RAN node 304 can fine-tune adjustments made within the UE 106.

[0151] In an embodiment, the remaining time threshold configuration 3310 can specify a list or set of thresholds 3902 and an offset value 3904. For example, UE 106 can select the value "40" from the threshold set 3902 and apply the offset value 3904 "-5". Therefore, the adjusted remaining time threshold 3122 will have a value of "35". One technical benefit is that RAN node 304 can fine-tune the adjustments made within UE 106.

[0152] In an embodiment, the remaining time threshold configuration 3310 can specify the multiplier 3906. For example, suppose the current value of the remaining time threshold 3122 is "30". When the multiplier 3906 is "0.5", the adjusted value of the remaining time threshold 3122 will be "15". When the multiplier 3906 is "2", the adjusted value of the remaining time threshold 3122 will be "60". One technical benefit is that the RAN node 304 can specify adjustments made within the UE 106.

[0153] Figure 40 A remaining time threshold configuration 3310 is shown in another illustrative embodiment. In this example, a first configuration trigger 3820 specifies that UE 106 does not adjust the remaining time threshold 3122 when the RBR value is within the range 3812 of the RBR value (e.g., V1 to V2). A second configuration trigger 3820 specifies that UE 106 adjusts the remaining time threshold 3122 when the RBR value is within another range 3812 of the RBR value (e.g., V3 to V4). As described above, UE 106 can add or subtract an offset value 3904 from the current value of the remaining time threshold 3122 to calculate the adjusted remaining time threshold 3122. UE 106 can select a value (a value different from the current value) from the threshold set 3902 as the adjusted remaining time threshold 3122. UE 106 can select a value (a value different from the current value) from the threshold set 3902 and apply the offset value 3904 to calculate the adjusted remaining time threshold 3122.

[0154] Figure 41 Additional details are shown regarding the adjustment of the remaining time threshold 3122 in the illustrative embodiment. To adjust the remaining time threshold 3122 (see...),... Figure 35In step 3506, UE 106 may adjust the remaining time threshold 3122 based on an offset value 3904 specified in one of the pre-configured remaining time threshold configurations 3310 (optional step 4102). In an alternative embodiment, UE 106 may adjust the remaining time threshold 3122 by selecting a threshold value from a set 3902 of threshold values ​​specified in one of the pre-configured remaining time threshold configurations 3310 (optional step 4104). In an alternative embodiment, UE 106 may adjust the remaining time threshold 3122 by selecting a threshold value from a set 3902 of threshold values ​​and applying the offset value 3904 to the value of the selected threshold as specified in one of the pre-configured remaining time threshold configurations 3310 (optional step 4106). In an alternative embodiment, UE 106 may adjust the remaining time threshold 3122 based on a multiplier 3906 specified in one of the pre-configured remaining time threshold configurations 3310 (optional step 4108). One technical benefit is that UE 106 is able to adjust the remaining time threshold 3122 based on pre-configured information.

[0155] Extended RRC signaling In the above embodiments, RRC message 2402 can be used to preconfigure UE 106 to operate autonomously as described above. The RRC protocol is described in 3GPP TS 38.331 (Release 18), which is incorporated herein by reference in its entirety. To preconfigure UE 106, the RRC protocol can be extended or enhanced as described below.

[0156] Figure 42 RRC message 2402 is shown in an illustrative embodiment. Typically, RRC message 2402 includes multiple RRC Information Elements (IEs) 4204. One or more RRC IEs 4204 can be used to set configurable parameters 904 in UE 106. This is in Figure 42 The default configuration 4210 is shown in the diagram. Default configuration 4210 allows RAN node 304 to set one or more configurable parameters 904 in UE 106. In an embodiment, one or more RRC IE 4204 can be used to configure UE 106 to autonomously adjust, modify, or change one or more configurable parameters 904. This is in... Figure 42The RAN node 304 is shown as one or more autonomous configurations 4212 (also referred to as alternative configurations). Autonomous configuration 4212 allows the RAN node 304 to provide the UE 106 with information, data, rules, policies, conditions, triggers, actions, attributes, etc., that permit, authorize, supervise, or control the UE 106 to autonomously act to modify one or more configurable parameters 904. For example, suppose the RAN node 304 uses the default configuration 4210 to set a configurable parameter 904 (e.g., PARAM-A) in the UE 106 to a value (e.g., VALUE-1). The RAN node 304 can also use autonomous configuration 4212 to provide the UE 106 with guidance or direction regarding autonomously modifying configurable parameters 904. For example, autonomous configuration 4212 may specify that the UE 106 adjusts the configurable parameter 904 (e.g., PARAM-A) to a different value (e.g., VALUE-2) in response to a trigger bar. Therefore, the autonomous configuration 4212 is configured to provide UE 106 with information for adjusting one or more configurable parameters 904 at UE 106 without further assistance from RAN node 304. One technical advantage is that RRC message 2402 allows RAN node 304 to "program" UE 106 to act in adjusting configurable parameters 904 without additional network control, which reduces signaling overhead.

[0157] In an embodiment, configurable parameter 904 may include one or more PDCP configurable parameters 916. Figure 43 RRC message 2402 is shown in another illustrative embodiment. As described above, RRC message 2402 includes a plurality of RRC IEs 4204. In this embodiment, one or more RRC IEs 4204 can be used to set PDCP configurable parameters 916 in UE 106. More specifically, RRC IE 4204 may include PDCP configuration IE 4302. RAN node 304 can use PDCP configuration IE 4302 to set one or more PDCP configurable parameters 916 in UE 106. This is in Figure 43 The PDCP default configuration 4310 is shown as included or carried in or carried by the PDCP configuration IE 4302. In an embodiment, the PDCP configuration IE 4302 can be used to configure the UE 106 to autonomously adjust, modify, or change one or more PDCP configurable parameters 916. This is in Figure 43The PDCP autonomous configuration 4312 (also known as PDCP alternative configuration) is shown as being included or carried in PDCP configuration IE 4302. The PDCP autonomous configuration 4312 allows RAN node 304 to provide UE 106 with information, data, rules, policies, conditions, triggers, actions, attributes, etc., thereby allowing, authorizing, supervising, or controlling UE 106 to autonomously act to modify one or more PDCP configurable parameters 916. One technical benefit is that RRC message 2402 allows RAN node 304 to "program" UE 106 to act to adjust PDCP configurable parameters 916 without additional network control, which reduces signaling overhead.

[0158] As described above, the type of PDCP configurable parameter 916 is a low-importance drop timer 1522 for PDCP drop procedure 1500. In this example, the PDCP default configuration 4310 may include a drop timer configuration 4318, which is configured to set one or more low-importance drop timers 1522 for PDCP drop procedure 1500. Furthermore, the PDCP autonomous configuration 4312 may include one or more drop timer configurations 2110, which are configured to provide the UE 106 with information for adjusting one or more low-importance drop timers 1522 for PDCP drop procedure 1500. Therefore, drop timer configuration 2110 may be included or carried in the PDCP configuration IE 4302. In an embodiment, the PDCP configuration IE 4302 may include a new PDCP configuration IE defined for PDCP autonomous configuration 4312 and / or drop timer configuration 2110. In an embodiment, the existing PDCP configuration IE 4302 may be extended to include or support PDCP autonomous configuration 4312 and / or drop timer configuration 2110. For example, the "PDCP Configuration" IE is defined in RRC protocols as setting configurable PDCP parameters, such as in 3GPP TS 38.331. In embodiments, the "PDCP Configuration" IE can be enhanced or extended to include or support PDCP autonomous configuration 4312 and / or discard timer configuration 2110.

[0159] Figure 44 The PDCP configuration IE 4302 in the illustrative embodiment is shown. Figure 44The PDCP configuration IE 4302 can represent a new IE or an extension of an existing IE. In this example, Abstract Syntax Mark 1 (ASN.1) is used to specify the content of RRC message 2402. ASN.1 uses tables, if necessary, to specify the message syntax to provide further details about the fields specified in the message syntax. PDCP configuration IE 4302 may include field descriptions 4420 (e.g., discardTimerForLowImportance) for low-importance discard timer configuration 4318, which can be used to set one or more low-importance discard timers 1522. PDCP configuration IE 4302 may include field descriptions 4422 (e.g., discardTimerForLAdjustConfig) for low-importance discard timer configuration 2110, which provides UE 106 with information for adjusting one or more low-importance discard timers 1522. For example, the discard timer configuration 2110 may include at least one configuration trigger 2720 (e.g., confTriggerType and / or confTriggerValue) and at least one configuration action 2722 (e.g., confAction) to adjust one or more low-importance discard timers 1522. Figure 44 The format or content of the discard timer configuration 2110 in this document is provided as an example, and other formats or content are also considered in this document.

[0160] In an embodiment, configurable parameter 904 may include one or more MAC configurable parameters 912. Figure 45 RRC message 2402 is shown in another illustrative embodiment. As described above, RRC message 2402 includes a plurality of RRC IEs 4204. In this embodiment, one or more RRC IEs 4204 can be used to set MAC configurable parameters 912 in UE 106. More specifically, RRC IE 4204 may include MAC configuration IE 4502. RAN node 304 can use MAC configuration IE 4502 to set one or more MAC configurable parameters 912 in UE 106. This is in Figure 45 The MAC default configuration 4510 is shown as included or carried in or in the MAC configuration IE 4502. In an embodiment, the MAC configuration IE 4502 can be used to configure the UE 106 to autonomously adjust, modify, or change one or more MAC configurable parameters 912. This is in Figure 45The diagram shows one or more MAC autonomous configurations 4512 (also known as MAC alternative configurations) included or carried in or carried by MAC configuration IE 4502. MAC autonomous configuration 4512 allows RAN node 304 to provide UE 106 with information, data, rules, policies, conditions, triggers, actions, attributes, etc., thereby allowing, authorizing, supervising, or controlling UE 106 to autonomously operate to modify one or more MAC configurable parameters 912. One technical benefit is that RRC message 2402 allows RAN node 304 to "program" UE 106 to act to adjust MAC configurable parameters 912 without additional network control, which reduces signaling overhead.

[0161] As described above, the type of MAC configurable parameter 912 is a remaining time threshold 3122 for the MAC DSR procedure 3100. In this example, the MAC default configuration 4510 may include a remaining time threshold configuration 4518, which is configured to set one or more remaining time thresholds 3122 for the MAC DSR procedure 3100. Furthermore, the MAC autonomous configuration 4512 may include one or more remaining time threshold configurations 3310, which are configured to provide the UE 106 with information for adjusting one or more remaining time thresholds 3122 for the MAC DSR procedure 3100. Therefore, the remaining time threshold configuration 3310 may be included or carried in the MAC configuration IE 4502. In an embodiment, the MAC configuration IE 4502 may include a new MAC configuration IE defined for the MAC autonomous configuration 4512 and / or the remaining time threshold configuration 3310. In an embodiment, an existing MAC configuration IE 4502 may be extended to include or support the MAC autonomous configuration 4512 and / or the remaining time threshold configuration 3310. For example, the "MAC-CellGroupConfig" IE is defined in RRC protocols for configuring MAC parameters for cell groups, such as in 3GPP TS38.331. In embodiments, the "MAC-CellGroupConfig" IE can be enhanced or extended to include or support MAC self-configuration 4512 and / or remaining time threshold configuration 3310.

[0162] Figure 46 The MAC configuration IE 4502 in the illustrative embodiment is shown. Figure 46The MAC configuration IE 4502 in the UE 106 can represent a new IE or an extension of an existing IE. The MAC configuration IE 4502 may include a field description 4620 for a remaining time threshold configuration 4518 (e.g., remaining time threshold), which can be used to set one or more remaining time thresholds 3122. The MAC configuration IE 4502 may also include a field description 4622 for a remaining time threshold configuration 3310 (e.g., dsrRemainingTimeThresholdAdjuConfig), which provides the UE 106 with information for adjusting one or more remaining time thresholds 3122. For example, the remaining time threshold configuration 3310 may include at least one configuration trigger 3820 (e.g., confTriggerType and / or confTriggerValue) and at least one configuration action 3822 (e.g., confAction) to adjust one or more remaining time thresholds 3122. Figure 46 The format or content of the remaining time threshold configuration 3310 in this document is provided as an example, and other formats or content are considered in this document.

[0163] Figures 47A to 47B This is a flowchart illustrating method 4700 / 4730 of RRC processing in an illustrative embodiment. The steps of method 4700 are described with reference to RAN node 304, and the steps of method 4730 are described with reference to UE 106, but this method can be performed in other systems or devices.

[0164] exist Figure 47A In this process, RAN node 304 may format or assemble RRC message 2402 (step 4702) and send or otherwise provide RRC message 2402 to UE 106 (step 4714). During formatting, RAN node 304 may insert or include autonomous configuration 4212 in one or more RRC IE 4204 (step 4704). In an embodiment, RAN node 304 may insert or include PDCP autonomous configuration 4312 in PDCP configuration IE 4302 (optional step 4706). For example, RAN node 304 may insert or include discard timer configuration 2110 in PDCP configuration IE 4302 (optional step 4708). In an embodiment, RAN node 304 may insert or include MAC autonomous configuration 4512 in MAC configuration IE 4502 (optional step 4710). For example, RAN node 304 may insert or include remaining time threshold configuration 3310 in MAC configuration IE 4502 (optional step 4712).

[0165] exist Figure 47BIn this process, UE 106 receives RRC message 2402 from RAN node 304 (step 4732). In response to RRC message 2402, UE 106 parses RRC message 2402 to extract information contained in RRC message 2402 (step 4734). While parsing RRC message 2402, UE 106 can extract autonomous configuration 4212 from one or more RRC IEs 4204 (step 4736). Autonomous configuration 4212 may be associated with a drop procedure 1500 for buffered data units at PDCP layer 414. For example, autonomous configuration 4212 may include at least one configuration trigger corresponding to network conditions, and at least one configuration action configured to adjust one or more configurable parameters 904 associated with drop procedure 1500 when at least one configuration trigger occurs.

[0166] UE 106 can extract PDCP autonomous configuration 4312 from PDCP configuration IE 4302 to autonomously adjust, modify, or change one or more PDCP configurable parameters 916 (optional step 4738). In an embodiment, configurable parameter 904 may include a low importance drop timer 1522 for drop procedure 1500. For example, UE 106 can extract one or more drop timer configurations 2110 from PDCP configuration IE 4302 (optional step 4740). In drop timer configuration 2110, configuration action 2722 can be configured to adjust the duration 1524 of low importance drop timer 1522 when configuration trigger 2720 occurs (e.g., a change to the recommended bit rate 1310).

[0167] UE 106 can extract MAC autonomous configuration 4512 from MAC configuration IE 4502 to autonomously adjust, modify, or change one or more MAC configurable parameters 912 (optional step 4742). In an embodiment, configurable parameter 904 may include a remaining time threshold 3122 for DSR procedure 3100. For example, UE 106 can extract one or more remaining time threshold configurations 3310 from MAC configuration IE 4502 (optional step 4744). In the remaining time threshold configuration 3310, configuration action 3822 can be configured to adjust the remaining time threshold 3122 (e.g., a change to the recommended bit rate 1310) when configuration trigger 3820 occurs.

[0168] One technical advantage is that RRC message 2402 allows RAN node 304 to “program” UE 106 to act without additional network control to adjust configurable parameters 904, which reduces signaling overhead.

[0169] Any of the various elements or modules shown in the accompanying drawings or described herein can be implemented as hardware, software, firmware, or some combination thereof. For example, an element can be implemented as dedicated hardware. A dedicated hardware element may be referred to as a “processor,” a “controller,” or some similar term. When provided by a processor, functionality may be provided by a single dedicated processor, by a single shared processor, or by multiple separate processors, some of which may be shared. Furthermore, the explicit use of the terms “processor” or “controller” should not be construed as exclusively referring to hardware capable of executing software, and may implicitly include, but is not limited to, digital signal processor (DSP) hardware, network processors, application-specific integrated circuits (ASICs) or other circuitry, field-programmable gate arrays (FPGAs), read-only memory (ROM) for storing software, random access memory (RAM), non-volatile storage devices, logic, or some other physical hardware component or module.

[0170] Furthermore, an element can be implemented as instructions that can be executed by a processor or computer to perform the element's functions. Some examples of instructions are software, program code, and firmware. Instructions, when executed by a processor, are operable to instruct the processor to perform the element's functions. Instructions can be stored on a processor-readable storage device. Some examples of storage devices are digital or solid-state memory, magnetic storage media (such as disks and tapes), hard disk drives, or optically readable digital data storage media.

[0171] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware circuit implementation only (e.g., implemented with purely analog and / or digital circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions) and (c) The operation requires software (e.g., firmware) for the operation of (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts thereof, but the software may be absent when the operation does not require the software.

[0172] This definition of "circuit" applies to all uses of the term in this application. As a further example, as used in this application, the term "circuit" also covers only hardware circuitry or processors (or processors), or portions of hardware circuitry or servers and their accompanying software and / or firmware implementations. For example, where applicable to certain claim elements, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0173] Although specific embodiments have been described herein, the scope of this disclosure is not limited to those specific embodiments. The scope of this disclosure is defined by the appended claims and any equivalents thereof.

[0174] Examples of some embodiments for implementing this disclosure are provided below.

[0175] Example 1. An apparatus for communication, comprising: At least one processor; and At least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least the following: Receive information defining a pre-configured remaining time threshold for the delay status reporting process; Detecting network conditions based on communication with radio access network nodes; In response to the network conditions and based on one of the pre-configured remaining time threshold settings, adjust the remaining time threshold corresponding to the latency status reporting process; and When the discard timer associated with the buffered data unit falls below the adjusted remaining time threshold, the delay status reporting process is performed based on the adjusted remaining time threshold to trigger a delay status report for the radio access network node.

[0176] Example 2. The apparatus according to Example 1, wherein the adjustment includes: The remaining time threshold is adjusted based on a multiplier specified in one of the pre-configured remaining time threshold settings.

[0177] Example 3. The apparatus according to Example 1, wherein the adjustment includes: The remaining time threshold is adjusted based on an offset value specified in one of the pre-configured remaining time threshold settings.

[0178] Example 4. The apparatus according to Example 1, wherein the adjustment includes: Select a different threshold value for the remaining time threshold from a set of threshold values ​​specified in one of the pre-configured remaining time threshold configurations.

[0179] Example 5. According to the apparatus of Example 1, wherein: One of the pre-configured remaining time threshold settings corresponds to a value range for the bit rate indicator.

[0180] Example 6. The apparatus according to Example 1, wherein the detection includes: Receive changes to the recommended bit rate from radio access network nodes.

[0181] Example 7. According to the apparatus of Example 1, wherein: At least one of the pre-configured remaining time threshold settings includes authorization to adjust the remaining time threshold.

[0182] Example 8. According to the apparatus of Example 1, wherein: At least one of the pre-configured remaining time threshold configurations includes authorization to adjust the remaining time threshold based on changes to the recommended bit rate from radio access network nodes.

[0183] Example 9. According to the apparatus of Example 1, wherein: At least one of the pre-configured remaining time threshold configurations includes authorization to adjust the remaining time threshold according to a logical channel or logical channel group.

[0184] Example 10. According to the apparatus of Example 1, wherein: One of the pre-configured remaining time threshold settings indicates one or more recommended bit rate values ​​that trigger an adjustment to the remaining time threshold.

[0185] Example 11. According to the apparatus of Example 1, wherein: One of the pre-configured remaining time thresholds indicates a recommended bit rate threshold, where a recommended bit rate value higher or lower than the recommended bit rate threshold triggers an adjustment to the remaining time threshold.

[0186] Example 12. According to the apparatus of Example 1, wherein: The information includes validity timers, which indicate the validity of each of the pre-configured remaining time thresholds.

[0187] Example 13. A device according to Example 1, wherein the instructions, when executed by at least one processor, cause the device to perform at least: Information from a radio access network node is received in the extended Media Access Control (MAC) configuration information element of a radio resource control message. The MAC configuration information element includes at least a field description configured for a pre-configured remaining time threshold.

[0188] Example 14. A method for communication, comprising: Receive information defining a pre-configured remaining time threshold for the delay status reporting process; Detecting network conditions based on communication with radio access network nodes; In response to network conditions and based on one of the pre-configured remaining time threshold settings, adjust the remaining time threshold corresponding to the delay status reporting process; and When the discard timer associated with the buffered data unit falls below an adjusted remaining time threshold, a delay status reporting procedure is performed based on the adjusted remaining time threshold to trigger a delay status report to the radio access network node.

[0189] Example 15. Based on the method of Example 14, the adjustments include: The remaining time threshold is adjusted based on a multiplier specified in one of the pre-configured remaining time threshold settings.

[0190] Example 16. Following the method of Example 14, the adjustments include: The remaining time threshold is adjusted based on an offset value specified in one of the pre-configured remaining time threshold settings.

[0191] Example 17. Following the method of Example 14, the adjustments include: Select a different threshold value for the remaining time threshold from a set of threshold values ​​specified in one of the pre-configured remaining time threshold configurations.

[0192] Example 18. Following the method of Example 14, where: One of the pre-configured remaining time threshold settings corresponds to a value range for the bit rate indicator.

[0193] Example 19. According to the method of Example 14, the detection includes: Receive changes to the recommended bit rate from radio access network nodes.

[0194] Example 20. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the following operations: Receive information defining a pre-configured remaining time threshold for the delay status reporting process; Detecting network conditions based on communication with radio access network nodes; In response to network conditions and based on one of the pre-configured remaining time threshold settings, adjust the remaining time threshold corresponding to the delay status reporting process; and When the discard timer associated with the buffered data unit falls below an adjusted remaining time threshold, a delay status reporting procedure is performed based on the adjusted remaining time threshold to trigger a delay status report to the radio access network node.

Claims

1. A device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least the following: Receive information defining a pre-configured remaining time threshold for the delay status reporting process; Detecting network conditions based on communication with radio access network nodes; In response to the network conditions and based on one of the pre-configured remaining time threshold settings, adjust the remaining time threshold corresponding to the delay status reporting process; as well as When the discard timer associated with the buffered data unit falls below the adjusted remaining time threshold, the delay status reporting process is performed based on the adjusted remaining time threshold to trigger a delay status report for the radio access network node.

2. The apparatus of claim 1, wherein the adjustment comprises: The remaining time threshold is adjusted based on the multiplier specified in one of the pre-configured remaining time threshold configurations.

3. The apparatus of claim 1, wherein the adjustment comprises: The remaining time threshold is adjusted based on the offset value specified in one of the pre-configured remaining time threshold configurations.

4. The apparatus of claim 1, wherein the adjustment comprises: Select different threshold values ​​for the remaining time threshold from the set of threshold values ​​specified in one of the pre-configured remaining time threshold configurations.

5. The apparatus according to claim 1, wherein: The value range corresponding to the bit rate indicator in the pre-configured remaining time threshold configuration.

6. The apparatus of claim 1, wherein the detection comprises: Receive changes to the recommended bit rate from the radio access network node.

7. The apparatus according to claim 1, wherein: At least one of the pre-configured remaining time threshold settings includes authorization to adjust the remaining time threshold.

8. The apparatus according to claim 1, wherein: At least one of the pre-configured remaining time threshold configurations includes authorization to adjust the remaining time threshold based on changes to the recommended bit rate from the radio access network node.

9. The apparatus according to claim 1, wherein: At least one of the pre-configured remaining time threshold configurations includes authorization to adjust the remaining time threshold according to a logical channel or a logical channel group.

10. The apparatus according to claim 1, wherein: One of the indications in the pre-configured remaining time threshold configuration is one or more recommended bit rate values ​​that trigger an adjustment to the remaining time threshold.

Images