Minimize the recommended bitrate request from user equipment to the network.

By negotiating adaptation time between user equipment and network and using a timer ban to limit UE RBR requests, the signaling overhead and power consumption problems caused by excessive UE requests are resolved, achieving more efficient bit rate adaptation and resource optimization.

CN123075558APending Publication Date: 2026-11-10NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610626239.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-08
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In the prior art, when the user equipment (UE) sends too many Recommended Bit Rate (RBR) requests to the network, it leads to increased signaling overhead and power consumption. The network is unable to effectively manage the UE's bit rate adaptation time, resulting in outdated or unnecessary RBR messages.

Method used

A timer-disable mechanism is adopted to restrict the UE from sending RBR requests within a specific time period. The UE adaptation time is determined through a strategy negotiated with the network. The network sends RBR information before and after the adaptation time, reducing explicit requests and optimizing bit rate adaptation.

Benefits of technology

It reduces signaling overhead, lowers UE power consumption, ensures the timeliness of RBR information, allows UEs to send requests freely when needed, and optimizes network resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123075558A_ABST
    Figure CN123075558A_ABST
Patent Text Reader

Abstract

Embodiments of this disclosure relate to minimizing recommended bit rate requests from a user equipment to a network. An apparatus includes at least one processor and at least one memory storing instructions. When executed by the at least one processor, the instructions cause the apparatus to: acquire information including: the configuration of a disable timer for recommended bit rate (RBR) requests; receive RBR information from the network; and, based on the disable timer configuration, start the disable timer after receiving the RBR information from the network. The apparatus avoids requesting additional RBR information from the network until the disable timer expires.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Various example implementations generally involve the Recommended Bit Rate (RBR), and more specifically involve using a disable timer to minimize or avoid excessive RBR requests from the User Equipment (UE) to the network. Background Technology

[0002] Wireless networks offer significant advantages to user mobility. The ability to stay connected while on the move not only benefits users but also contributes to greater efficiency and productivity across society. As users' expectations for processing power, connection reliability, data speed, and battery life increase, wireless network technology must keep pace. Therefore, there is a continued interest in improving wireless network technology. Summary of the Invention

[0003] The independent claims provide the subject matter for several aspects. Additional aspects are defined in the dependent claims. Further aspects are illustrated in the example section, which is incorporated herein by reference. Attached Figure Description

[0004] Some exemplary embodiments will now be described with reference to the accompanying drawings.

[0005] Figure 1 This is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE) according to an illustrative aspect of this disclosure;

[0006] Figure 2 This is a diagram illustrating an example component of a network system according to an aspect of this disclosure;

[0007] Figure 3 This is an example diagram illustrating multiple instances of periodic timing according to one aspect of this disclosure when the UE can adapt to the RBR provided by the network and / or when the UE prefers to adapt to the RBR provided by the network;

[0008] Figure 4 This is an example diagram illustrating multiple instances of non-periodic timing according to one aspect of this disclosure when the UE can adapt to the RBR provided by the network and / or when the UE prefers to adapt to the RBR provided by the network;

[0009] Figure 5 This is a diagram illustrating an example operation related to bit rate adaptability in a UE according to one aspect of this disclosure;

[0010] Figure 6 This is a flowchart illustrating an example of communication between a UE and a network according to one aspect of this disclosure;

[0011] Figure 7This is a flowchart illustrating another example of communication between a UE and a network according to one aspect of this disclosure;

[0012] Figure 8 This is a flowchart illustrating another example of communication between a UE and a network according to one aspect of this disclosure;

[0013] Figure 9 This is a flowchart illustrating another example of communication between a UE and a network according to one aspect of this disclosure;

[0014] Figure 10 This is a flowchart illustrating another example of communication between a UE and a network according to one aspect of this disclosure; and

[0015] Figure 11 This is a block diagram of an example component of a network node or user equipment according to an illustrative aspect of this disclosure. Detailed Implementation

[0016] This application relates to using a disable timer to minimize or avoid excessive recommended bit rate (RBR) requests from user equipment (UE).

[0017] UEs (such as smartphones) may exhibit variable data bitrate behavior as they perform different tasks throughout the day. During periods of low activity, the required data bitrate is relatively low. However, for example, when a user streams video or joins a video call, the data bitrate increases significantly to support the higher data demands. Activities such as watching HD or 4K video, using augmented reality applications, or downloading large files can result in consistently high data bitrates. Furthermore, the data bitrate may briefly spike during software updates, cloud backups, or other activities.

[0018] Some UEs can dynamically adjust their data bit rate based on signal strength and network congestion. 3GPP Technical Specification (TS) 38.321 specifies a mechanism for coordinating data rate requirements between the UE and the network. Based on this mechanism, the network can send a Recommended Uplink (UL) bit rate message to the UE, and the UE can adapt its data bit rate usage based on the network's Recommended Bit Rate (RBR). In various situations, such as when the network experiences increased congestion or when congestion is alleviated, the network may choose to send this Recommended UL bit rate message to the UE. In various scenarios, the UE can send a request for the network's Recommended Bit Rate (RBR). Such requests can also include requests for specific UL bit rates. In various scenarios, the UE can implement an RBR request disable timer that prevents the UE from sending another RBR request for a period of time after sending a previous RBR request. The disable timer allows the network to limit the number of RBR requests sent by the UE to reduce overhead.

[0019] "UE adaptation time" refers to the time instance / opportunity when a UE can adapt and / or prefers to adapt to a new uplink (UL) recommended bit rate (RBR). The information indicating the UE adaptation time may be referred to herein as timing information related to bit rate adaptation, or as the bit rate adaptation strategy agreed upon between the UE and the network. The "instance" or "opportunity" of timing when a UE can adapt and / or prefers to adapt to a new UL RBR may be a time window, or may be indicated by a point in time, or other possibilities. The terms "instance" and "opportunity" are used interchangeably herein.

[0020] The UE and the network can communicate regarding future UE adaptation times. This information can be included in a policy agreed upon between the UE and the network. The network can send an RBR at, during, or immediately before the UE adaptation time, allowing the UE to receive the RBR at a time when it is capable of adapting to the RBR and / or prefers to adapt to it. This avoids / reduces situations where the network sends an RBR when the UE is unable to process or use it, and where these RBRs become obsolete when the UE is finally able to process and use them.

[0021] Knowing the future UE adaptation time (e.g., through a strategy agreed upon with the UE), the network can send an RBR to the UE without an explicit RBR request from the UE. This has the advantages of reducing signaling overhead, lower power consumption at the UE, and reduced network processing. Furthermore, by reducing excessive explicit RBR requests from the UE, the RBR request injunction timer can run less frequently, allowing the UE more freedom to send explicit RBR requests when needed without being potentially prevented from doing so by the RBR request injunction timer.

[0022] In this disclosure, various aspects of the disclosure utilize a timer disablement mechanism to minimize potentially less important and / or less effective RBR requests sent by the UE to the network, while still allowing the UE to send potentially more effective RBR requests.

[0023] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, those skilled in the art will recognize that the aspects can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers are not shown or described in detail to avoid unnecessarily obscuring the description of the aspects.

[0024] In this specification, references to "an aspect" or "one aspect" indicate that a particular feature, structure, or characteristic described in conjunction with that aspect is included in at least one aspect. Therefore, the appearance of the phrase "in an aspect" or "in one aspect" in various places in this specification does not necessarily refer to the same aspect. Furthermore, a particular feature, structure, or characteristic may be combined in any suitable manner with one or more aspects.

[0025] The embodiments described in this disclosure can be implemented in wireless network devices, such as, but not limited to, devices utilizing: Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, Enhanced LTE (eLTE), 5G New Radio (5G NR), Advanced 5G, 6G (and higher), and 802.11ax (Wi-Fi 6), etc. The term 'eLTE' here refers to LTE evolution connected to a 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0026] This disclosure may use the term "serving network device" to refer to a network node or network device (or part thereof) serving a UE. As used herein, the terms "send to," "receive from," and "cooperate with" (and variations thereof) include communication that may or may not involve communication via one or more intermediate devices or nodes. The term "acquire" (and variations thereof) includes initial acquisition or reacquisition after initial acquisition. The term "connection" may refer to a physical connection or a logical connection.

[0027] This disclosure uses 5G NR as an example of a wireless network, and may use smartphones and / or extended reality headsets as examples of user equipment (UE). It should be understood that such examples are merely illustrative, and this disclosure applies to other wireless networks and user equipment.

[0028] Figure 1 This is a diagram illustrating an example of wireless networking between network system 100 and user equipment (UE) 150. Network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network devices 130 (e.g., test equipment). Network node 120 will be described in more detail below. As used herein, the term "network apparatus" can refer to any component of network system 100, such as server 110, network node 120, network device 130, any(multiple) components of the foregoing, and / or any(multiple) other components of network system 100. Examples of network apparatus include, but are not limited to, apparatuses for implementing various aspects of 5G NR. This disclosure describes embodiments related to 5G NR and embodiments relating to aspects defined by the 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments related to other wireless network technologies are also covered within the scope of this disclosure.

[0029] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as a gNB) may include, for example, a node that provides New Radio (NR) user plane and control plane protocol termination toward the UE and is connected to the 5G core (5GC) via an NG interface, such as according to Section 3.2 of 3GPP TS 38.300 V16.6.0 (2021-06), which is incorporated herein by reference.

[0030] gNB supports various protocol layers, such as Layer 1 (L1) (i.e., the physical layer), Layer 2 (L2), and Layer 3 (L3).

[0031] NR's Layer 2 (L2) is divided into the following sublayers: Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), among which: ○ The physical layer provides a transmission channel to the MAC sublayer; ○ The MAC sublayer provides logical channels to the RLC sublayer; ○ The RLC sublayer provides RLC channels to the PDCP sublayer; ○ The PDCP sublayer provides radio bearers to the SDAP sublayer; ○ The SDAP sublayer provides Quality of Service (QoS) flows to 5GC; ○ The control channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0032] Layer 3 (L3) includes, for example, Radio Resource Control (RRC) conforming to Section 6 of 3GPP TS 38.300 V16.6.0 (2021-06), which is incorporated herein by reference.

[0033] The gNB Central Unit (gNB-CU) includes, for example, a logical node that hosts, for example, the gNB's Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols, or the en-gNB's RRC and PDCP protocols. This logical node controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as a CU, Central Unit, Centralized Unit, or Control Unit.

[0034] A gNB Distributed Unit (gNB-DU) includes, for example, a logical node that hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers of the gNB or en-gNB, and its operation is partially controlled by the gNB-CU. A gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to herein as a DU or Distributed Unit.

[0035] As used herein, the term "network node" may refer to any gNB, gNB-CU, or gNB-DU, or any combination thereof. RAN (Radio Access Network) nodes or network nodes (such as, for example, gNB, gNB-CU, or gNB-DU, or portions thereof) may be implemented using means, for example, having at least one processor and / or at least one memory with processor-readable instructions ("program") configured to support and / or supply and / or process CU and / or DU related functions and / or features, and / or at least one protocol (sub) layer of the RAN (Radio Access Network), such as Layer 2 and / or Layer 3. Different functional divisions may exist between central units and distributed units.

[0036] The gNB-CU and gNB-DU portions can be co-located or physically separated. The gNB-DU can even be further divided into two parts, for example, one part including processing equipment and the other including an antenna. The Central Unit (CU) can also be referred to as a Baseband Unit / Radio Equipment Controller / Cloud RAN / Virtual RAN (BBU / REC / C-RAN / V-RAN), Open RAN (O-RAN), or a portion thereof. The Distributed Unit (DU) can also be referred to as a Remote Radio Headend / Remote Radio Unit / Radio Equipment / Radio Unit (RRH / RRU / RE / RU), or a portion thereof. In the various exemplary embodiments of this disclosure, a network node supporting at least one of the Central Unit functions or Layer 3 protocols of a radio access network can be, for example, a gNB-CU. Similarly, a network node supporting at least one of the Distributed Unit functions or Layer 2 protocols of a radio access network can also be, for example, a gNB-DU.

[0037] A gNB-CU can support one or more gNB-DUs. A gNB-DU can support one or more cells, and therefore can support the serving cell of a user equipment (UE), or a candidate cell for procedures such as handover, dual connectivity, and / or carrier aggregation.

[0038] User equipment (UE) 150 may be or include wireless or mobile devices, devices having a radio interface for interacting with a RAN (Radio Access Network), smartphones, in-vehicle devices, IoT devices, or machine-to-machine (M2M) devices, and other types of user equipment. Such a UE 150 may include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the device to perform at least certain operations, such as, for example, an RRC connection with the RAN. Examples of UE components will be combined. Figure 11 The following description is provided. In an embodiment, UE 150 may be configured to generate messages (e.g., including a cell ID) to be transmitted to the RAN via radio (e.g., to reach and communicate with the serving cell). In an embodiment, UE 150 may generate, transmit, and receive RRC messages containing one or more RRC PDUs (Packet Data Units). Those skilled in the art will understand the RRC protocol and other processes that the UE may perform.

[0039] Continue to refer to Figure 1In an example of a 5G NR network, network system 100 provides one or more cells that define the coverage area of ​​network system 100. As described above, network system 100 may include a gNB of the 5G NR network, or may include any other means configured to control radio communications and manage radio resources within the cell. As used herein, the term "resource" may refer to radio resources such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In embodiments, network node 120 may be referred to as a base station.

[0040] Figure 1 An example is provided and is only for illustrative purposes regarding network system 100 and UE 150. Those skilled in the art will understand that network system 100 includes... Figure 1 Components not shown in the diagram, and it will be understood that other user devices can communicate with network system 100.

[0041] Figure 2 yes Figure 1 A block diagram of example components of network system 100. A 5G NR network can be described as an example of network system 100, and the aspects described below should also apply to other types of network systems. The network system can be configured according to... Figure 1 The signals and connections shown operate to enable UE 150 to communicate with network system 100 via radio access network (RAN) 225. Furthermore, as shown and described herein, the network system can be divided into user plane components and functions, and control plane components and functions. Unless otherwise stated, the terms “component,” “function,” and “service” are used interchangeably herein, and they can refer to instructions executed by and implemented by one or more processors.

[0042] The following describes example functionality of these components. This example functionality is illustrative only, and it should be understood that the components described herein can perform additional operations and functions. Furthermore, connections between components can be virtual connections via service-based interfaces, allowing any component to communicate with any other component. In this way, any component can act as a service "producer" for any other component acting as a service "consumer" to provide services for network functions.

[0043] For example, core network 210 is described in the control plane of the network system. Core network 210 may include Authentication Server Function (AUSF) 211, Access and Mobility Function (AMF) 212, and Session Management Function (SMF) 213. Core network 210 may also include Network Slice Selection Function (NSSF) 214, Network Exposure Function (NEF) 215, Network Repository Function (NRF) 216, and Unified Data Management Function (UDM) 217, which may include Unified Data Repository (UDR) 224.

[0044] Additional components and functions of the core network 210 may include application functions (AF) 218, policy control functions (PCF) 219, network data analysis functions (NWDAF) 220, analytical data repository functions (ADRF) 221, management data analysis functions (MDAF) 222, and operation and management functions (OAM) 223.

[0045] The user plane includes UE 150, Radio Access Network (RAN) 225, User Plane Function (UPF) 226, and Data Network (DN) 227. RAN 225 may include a combination of Figure 1 The RAN 225 describes one or more components, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connectivity for data transmitted through the RAN 225. For example, the UPF 226 identifies services from service providers, internet access, and third-party services.

[0046] AMF 212 handles connectivity and mobility tasks. AUSF 211 receives authentication requests from AMF 212 and interacts with UDM 217 to authenticate and verify network responses to determine successful authentication. SMF 213 performs Packet Data Unit (PDU) session management and manages the session context with UPF 226.

[0047] NSSF 214 can select a Network Slice Instance (NSI) and determine the allowed Network Slice Selection Auxiliary Information (NSSAI). This selection and determination are used to set up AMF 212 to provide services to UE 150. NEF 215 ensures third-party access to network services to create specialized network services. NRF 216 acts as a repository for storing network functions to allow these functions to register and discover each other.

[0048] UDM 217 generates authentication vectors for use by AUSF 211 and AMF 212 and provides user identity processing. UDM 217 can connect to UDR 224, which stores data associated with authentication, applications, etc. AF 218 provides application services (e.g., streaming services) to users. PCF 219 provides policy control functions. For example, PCF 219 can assist with network slicing and mobility management, and provide Quality of Service (QoS) and accounting functions.

[0049] NWDAF 220 collects data (e.g., from UE 150 and network systems) to perform network analytics and provide insights into the capabilities that utilize that analytics during service provision. ADRF 221 allows consumers to store, retrieve, and remove data and analytics. MDAF 222 provides additional data analytics services for network functions. OAM 223 provides provisioning and management processing capabilities to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0050] Figure 2 These are merely examples of components of a network system, and variations are considered to be within the scope of this disclosure. In embodiments, the network system may include... Figure 2 Other components not shown in the diagram. In embodiments, the network system may not include... Figure 2 Each component is shown. In an embodiment, components and connections can be used with... Figure 2 The connections shown are implemented using different connections. Such and other embodiments are considered to be within the scope of this disclosure.

[0051] As mentioned above, "UE adaptation time" is the time instance / opportunity when the UE can adapt and / or prefers to adapt to the new uplink (UL) recommended bit rate (RBR). The information indicating the UE adaptation time may be referred to in this document as timing information related to bit rate adaptation, or as the bit rate adaptation strategy agreed upon between the UE and the network.

[0052] Figure 3This is a diagram illustrating three instances / timings of UE adaptation time. The three instances of adaptation time shown are illustrated as time windows. In various embodiments, instances of UE adaptation time can be indicated by the point in time when the UE can begin adapting to the RBR. The UE adaptation time shown is periodic, where a time interval T occurs between the three instances. Periodic instances of adaptation time can be applicable to certain activities. For example, the HTTP Adaptive Streaming (HAS) compression level can be adapted once per segment, such as every 2-10 seconds. Instances of UE adaptation time can be timed before the start of each new segment, at which time the application can attempt to estimate the possible UL bit rate on the next segment. This example is merely illustrative, and other scenarios involving periodic adaptation time are also considered to be within the scope of this disclosure.

[0053] Figure 4 An example of non-periodic (i.e., not periodic) UE adaptation time is illustrated. For example, if a UE application expects future activity on a non-periodic scheduled time, the UE can set its UE adaptation time exactly before each activity according to the scheduled time. This example is merely illustrative, and other scenarios involving non-periodic adaptation time are also considered to be within the scope of this disclosure.

[0054] It should be noted that the UE adaptation time may include a combination of some periodic instances and some non-periodic instances.

[0055] It should also be noted that the UE can determine the UE adaptation time at the Access (AS) layer. In various embodiments, the UE adaptation time may or may not be determined at the AS layer, but the UE can obtain the UE adaptation time at the AS layer. Such and other embodiments are considered to be within the scope of this disclosure.

[0056] Furthermore, it should be noted that UE adaptation time can be determined and / or obtained for a Quality of Service (QoS) flow, a set of QoS flows, a resource block, a set of resource blocks, a logical channel, and / or a set of logical channels. In various embodiments, for multiple QoS flows, different UE set adaptation times can be determined and / or obtained for each QoS flow. In various embodiments, for multiple resource blocks, different UE set adaptation times can be determined and / or obtained for each resource block. In various embodiments, for multiple logical channels, different UE set adaptation times can be determined and / or obtained for each logical channel. Such and other embodiments are considered to be within the scope of this disclosure.

[0057] Figure 3 and Figure 4 The above description is merely an example, and variations can be expected within the scope of this disclosure.

[0058] As mentioned above, there is no existing mechanism in 3GPP TS 38.321 for the network to know the future timing when the UE can adapt to or prefers to receive the RBR from the network.

[0059] If the network does not know the UE's adaptation time, it may send multiple UL RBR messages, for example, before the UE's next adaptation time. This is inefficient because the UE will only use the last such message from the network. Furthermore, in various situations, when the UE uses the last message, it may be somewhat stale or outdated.

[0060] As described above, the UE and the network can communicate regarding future UE adaptation times. This information can be included in a policy agreed upon between the UE and the network. The network can send RBRs at, during, or before the UE adaptation time, allowing the UE to receive RBRs at a time when it is capable of adapting to and / or prefers to adapt to them. This avoids / reduces situations where the network sends RBRs when the UE is unable to process or use them, and situations where these RBRs become obsolete when the UE is finally able to process and use them.

[0061] It should be noted that knowing the future UE adaptation time (e.g., through a strategy agreed upon with the UE), the network can send an RBR to the UE without an explicit RBR request from the UE. This has the advantages of reducing signaling overhead, lower power consumption at the UE, and reduced network processing. Furthermore, by reducing excessive explicit RBR requests from the UE, the RBR request injunction timer can run less frequently, allowing the UE more freedom to send explicit RBR requests when needed without being potentially prevented from doing so by the RBR request injunction timer.

[0062] Leveraging some of the features disclosed herein offers advantages such as avoiding unnecessary or unavailable RBR requests and / or RBR messages, providing fresh and up-to-date RBRs when the UE uses RBRs to adapt to bit rates, allowing the UE to receive new RBRs from the network after network congestion has subsided, enabling the UE to use the information at the next adaptation time, avoiding additional overhead, reducing UE battery usage, and allowing the UE more freedom to send RBR requests without being prevented from doing so by an RBR request prohibition timer. In various embodiments, the UE can send RBR requests in a MAC CE, which can be an RBR query or another MAC CE.

[0063] Figure 5 This is a schematic diagram of an example operation related to bit rate adaptability in the UE.

[0064] At operation 501, the UE receives from the network a message indicating that the UE is permitted to send timing information related to bit rate adaptation.

[0065] At operation 502, the UE sends an RBR request, which contains timing information and / or bit rate information related to bit rate adaptation.

[0066] At operation 503, the UE starts, restarts, or continues to monitor the RBR request prohibit timer and / or RBR request prohibit condition.

[0067] At operation 504, the UE assesses whether the RBR request prohibition timer has expired and / or whether the RBR request prohibition conditions are no longer applicable. If the RBR request prohibition timer has expired and / or the RBR request prohibition conditions are no longer applicable, the operation proceeds to operation 505. Otherwise, the operation returns to operation 503.

[0068] At operation 505, the UE determines whether a new RBR request needs to be sent, for example, to provide updated timing information and / or updated bit rate information. If yes, the operation proceeds to operation 502. Otherwise, the operation proceeds to operation 506.

[0069] At operation 506, the UE does not send any RBR request.

[0070] At operation 507, the UE assesses whether the last UE adaptation time configured by the RBR request has been reached. If so, then... Figure 5 The operation ends. If not, the operation returns to operation 503.

[0071] Figure 5 The above description is merely illustrative, and variations are considered to be within the scope of this disclosure. In various embodiments, operation may include... Figure 5 Other operations not shown. In various embodiments, operations may not include... Figure 5 Each operation is shown. In various embodiments, Figure 5 The operations shown as single or combined operations can be implemented as individual operations. In various embodiments, Figure 5 The individual operations shown can be combined. Such and other variations are considered to be within the scope of this disclosure.

[0072] This disclosure includes various embodiments that utilize a disable timer to help minimize the transmission of RBR requests from the UE to the network, thereby freeing up network resources. Furthermore, the various embodiments disclosed herein help allow the network to limit the number of RBR requests it receives from the UE that may be less important and / or less beneficial, while still allowing RBR requests that are more beneficial to the UE and / or the network.

[0073] For example, if the UE recently received an RBR value from the network (as specified in the configuration), it can be considered less important for the UE to be allowed to send an RBR request to the network, since the last known RBR value may still be accurate. Furthermore, if the UE recently sent a desired RBR value to the network that is relatively similar to its current desired RBR value, it can be considered less important.

[0074] Furthermore, if the UE's current expected RBR is less than the most recently sent expected RBR value and / or received RBR value, allowing the UE to send an RBR request can be considered less important, as the UE does not need to increase the network's RBR value. However, allowing the UE to send an RBR request in this case can benefit the network, as it can free up resources by providing the UE with a lower RBR value.

[0075] In all aspects of this disclosure, after the UE receives RBR information from the network, the UE may be blocked from requesting or may trigger an RBR request for a certain period of time. The duration for which the RBR request is blocked may be determined based on various conditions.

[0076] In some aspects of this disclosure, multiple disable timers are used to prevent the UE from sending RBR requests to the network at pre-requested intervals, which may correspond to the time intervals of pre-planned requests for RBR information.

[0077] Figure 6 An embodiment of this disclosure is illustrated. Here, the timer is disabled to start or restart after the UE receives RBR information (e.g., Media Access Control (MAC) CE) from the network. As used herein, "after" means "at any point after," "when," or "upon." That is, in this case, "after" means that the timer is disabled to start or restart at any time after the UE receives the RBR information from the network, the timer is disabled to start or restart when the UE receives the RBR information from the network, or the timer is disabled to start or restart when the UE receives the RBR information from the network. At operation 610, the network sends and the UE receives the configuration for the disabled timer for the Recommended Bit Rate (RBR) request. At operation 620, the network sends and the UE receives the RBR information (such as MAC CE). At operation 630, the UE starts (or restarts) the disabled timer. That is, the timer is disabled to start or restart after the UE receives the RBR information from the network.

[0078] Figure 6 The above description is merely illustrative, and variations are considered to be within the scope of this disclosure. In various embodiments, operation may include... Figure 6Other operations not shown. In various embodiments, operations may not include... Figure 6 Each operation is shown. In various embodiments, Figure 6 The operations shown as single or combined operations can be implemented as individual operations. In various embodiments, Figure 6 The individual operations shown can be combined. Such and other variations are considered to be within the scope of this disclosure.

[0079] exist Figure 6 In the illustrated embodiment, an apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: acquire information including: a configuration of a disable timer for a Recommended Bit Rate (RBR) request; receive RBR information from a network; and, based on the disable timer configuration, start the disable timer after receiving the RBR information from the network. The apparatus avoids requesting additional RBR information from the network before the disable timer expires. In some aspects, the information includes at least one rule applicable to the disable timer. In some aspects, the at least one rule relates to when the disable timer will be started. In some aspects, the at least one rule specifies that the disable timer will be started or restarted based on the apparatus receiving RBR information from the network. In some aspects, the at least one rule specifies that the disable timer will be started or restarted based on the apparatus requesting RBR information from the network.

[0080] In some aspects, at least one rule includes additional rules for determining the duration of a timer disablement based on the value of the RBR in the RBR information. In some aspects, the additional rules specify that the duration of the timer disablement is determined based on a comparison between the bit rate value expected by the device and the RBR value received by the device from the network. In some aspects, the additional rules specify that the duration of the timer disablement is determined as follows: a first duration of timer disablement if the RBR value received by the device from the network is equal to or greater than the bit rate value expected by the device; and a second duration of timer disablement if the RBR value received by the device from the network is less than the bit rate value expected by the device, wherein the first duration is longer than the second duration.

[0081] In some aspects, the at least one memory stores instructions that, when executed by the at least one processor, cause the device to: acquire information including an RBR value offset, wherein an additional rule specifies that the duration of the timer to be disabled is determined as follows: a first duration of disabling the timer if the difference between the RBR received by the device from the network and the bit rate value desired by the device is less than the RBR value offset; and a second duration of disabling the timer if the difference between the RBR received by the device from the network and the bit rate value desired by the device is greater than the RBR value offset, wherein the first duration is longer than the second duration.

[0082] In some respects, at least one rule specifies that the duration of the disable timer should be determined based on at least one of the RBR value received by the device from the network and the RBR value expected by the device.

[0083] In some aspects, the at least one memory storage instruction, when executed by the at least one processor, causes the device to: acquire information including the configuration of a second disable timer. In some aspects, the at least one memory storage instruction, when executed by the at least one processor, causes the device to: send a request for RBR information to the network; and based on the device sending the request for RBR information to the network, start the second disable timer. In some aspects, the duration of the disable timer used in response to the device receiving RBR information from the network is different from (e.g., less than) the duration of the second disable timer used in response to the device sending the request for RBR information to the network. In some aspects, the second disable timer is configured to start at a predetermined time after at least one of the start of the disable timer and the expiration of the disable timer.

[0084] In some aspects, the at least one memory-stored instruction, when executed by the at least one processor, causes the device to: send a request for RBR information to the network. In some aspects, the at least one memory-stored instruction, when executed by the at least one processor, causes the device to avoid sending an additional request for additional RBR information to the network before a disable timer expires, and to send an additional request for additional RBR information to the network after the disable timer expires.

[0085] In some respects, RBR information is included in at least one Media Access Control (MAC) element (CE). In some respects, the device is a User Equipment (UE).

[0086] exist Figure 6In an example embodiment shown, a method includes: obtaining information including: a configuration of a disable timer for RBR requests; the UE receiving RBR information from the network; and, based on the configuration, initiating a disable timer based on the received RBR information from the network. The UE avoids requesting additional RBR information from the network before the disable timer expires. In some aspects, the configuration of the disable timer includes at least one rule or condition applicable to the disable timer. In some aspects, at least one rule relates to when the disable timer will be started or restarted, such as when the UE receives RBR information from the network, or when the UE requests RBR information from the network. In some aspects, at least one rule or condition applicable to the disable timer relates to determining the duration of the disable timer based on the value of the RBR in the RBR information. In some aspects, the rule or condition specifies that the duration of the disable timer is determined based on a comparison between a bit rate value desired by the UE and the value of the RBR received by the UE from the network. In some aspects, the rule or condition specifies that the duration of the timer disablement is determined as follows: a first duration of timer disablement when the RBR value received by the UE from the network is equal to or greater than the UE's desired bit rate value; and a second duration of timer disablement when the RBR value received by the UE from the network is less than the UE's desired bit rate value; the first duration is longer than the second duration. In some aspects, the method includes: acquiring information including an RBR value offset, and the rule or condition specifies that the duration of the timer disablement is determined as follows: a first duration of timer disablement when the difference between the RBR value received by the UE from the network and the UE's desired bit rate value is less than the RBR value offset; and a second duration of timer disablement when the difference between the RBR value received by the UE from the network and the UE's desired bit rate value is greater than the RBR value offset; the first duration is longer than the second duration.

[0087] In some aspects, at least one rule or condition specifies that the duration of the disable timer is determined based on at least one of the RBR value received by the UE from the network and the RBR value expected by the UE. In some aspects, the method further includes obtaining information including a configuration of a second disable timer. In some aspects, the method further includes the UE sending a request for RBR information to the network; and starting the second disable timer based on the UE's request for RBR information to the network. In some aspects, the duration of the disable timer used in response to the UE receiving RBR information from the network is different from (e.g., less than) the duration of the second disable timer used in response to the UE's request for RBR information to the network. In some aspects, the second disable timer is configured to start at a predetermined time after at least one of the start of the disable timer and the expiration of the disable timer.

[0088] In some respects, the method also includes: the UE avoiding sending additional requests for additional RBR information from the network before the prohibition timer expires; and the UE sending additional requests for additional RBR information to the network after the prohibition timer expires.

[0089] In some respects, RBR information is included in at least one Media Access Control (MAC) control element (CE).

[0090] exist Figure 6 In other embodiments of the illustrated example, the method includes providing information including a configuration of a disable timer for a Recommended Bit Rate (RBR) request, wherein the information includes at least one rule applicable to the disable timer. The method also includes sending RBR information and the configuration of the disable timer to a User Equipment (UE) from the network. The configured at least one rule specifies that the disable timer is to be started based on the UE receiving RBR information from the network or the UE requesting RBR information from the network. In some aspects, the method includes receiving a request for additional RBR information from the UE by the network after the disable timer in the UE expires. In some aspects, at least one rule specifies that the disable timer is to be started based on the UE receiving RBR information from the network or the UE requesting RBR information from the network. In some aspects, an additional rule to the configured at least one rule specifies that the duration of the disable timer is determined based on the value of the RBR.

[0091] Figure 7Another embodiment of this disclosure is illustrated. Here, a first disable timer starts or restarts after the UE sends a request for RBR information to the network but before the UE receives the RBR information from the network, and a second disable timer starts or restarts after the user receives the RBR information from the network. As described above, "after" as used herein means "at any point after," "when," or "upon." For example, in this case, "after" means that the disable timer starts or restarts at any time after the UE sends a request for RBR information to the network, the disable timer starts or restarts when the UE sends a request for RBR information to the network, or the disable timer is prevented from starting or restarting when the UE sends a request for RBR information to the network. The disable timers may include duration values ​​that are different from each other. At operation 710, the network sends and the UE receives a configuration of disable timers for the RBR request. In the illustrated embodiment, this configuration includes a first disable timer and a second disable timer, the first disable timer having a first duration value for when the UE sends an RBR request to the network, and the second disable timer having a second duration value for when the UE receives the RBR information from the network. At operation 720, the UE sends a request for RBR information to the network. At operation 730, the UE starts a first prohibition timer with a first duration value. At operation 740, the network sends and the UE receives RBR information (e.g., including the bit rate MAC CE of the Quality of Service (QoS) stream). At operation 750, the UE starts a second prohibition timer with a second duration value. That is, the first prohibition timer starts after the UE requests the RBR information and before the UE receives the RBR information from the network. The second prohibition timer starts after the UE receives the RBR information from the network. In this embodiment, the duration of the second prohibition timer is longer than the duration of the first prohibition timer.

[0092] Figure 7 The above description is merely illustrative, and variations are considered to be within the scope of this disclosure. In various embodiments, operation may include... Figure 7 Other operations not shown. In various embodiments, operations may not include... Figure 7 Each operation is shown. In various embodiments, Figure 7 The operations shown as single or combined operations can be implemented as individual operations. In various embodiments, Figure 7 The individual operations shown can be combined. Such and other variations are considered to be within the scope of this disclosure.

[0093] exist Figure 7In the example embodiment shown, an apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: acquire information including: the configuration of a disable timer for a Recommended Bit Rate (RBR) request; send a request for RBR information to the network; and, based on the configuration of the disable timer, start the disable timer if the apparatus does not receive RBR information from the network, or wait for the disable timer to start until the apparatus receives RBR information from the network.

[0094] In some aspects, the information includes at least one rule to be applied to disable the timer. In some aspects, the at least one memory stores an instruction that, when executed by the at least one processor, causes the device to: receive RBR information from the network. In some aspects, the at least one memory stores an instruction that, when executed by the at least one processor, causes the device to: determine whether to restart the disable timer by comparing a desired RBR value with the RBR value in the RBR information received from the network. In some aspects, the at least one memory stores an instruction that, when executed by the at least one processor, causes the device to: determine whether to start the disable timer by comparing a desired RBR value with the RBR value in a request for RBR information sent by the device to the network. In some aspects, the at least one memory stores an instruction that, when executed by the at least one processor, causes the device to: determine whether to start the disable timer by comparing the current time with the time of a future RBR request provided to the network in an earlier UE Assistance Information (UAI) request.

[0095] In some aspects, the at least one memory-stored instruction, when executed by the at least one processor, causes the device to: determine to restart the disable timer when the difference between the expected RBR value and the RBR value in the RBR information received from the network is as defined in the configuration of the disable timer. In some aspects, the at least one memory-stored instruction, when executed by the at least one processor, causes the device to: determine to restart the disable timer when the difference between the expected RBR value and the RBR value in the last RBR information sent to the network is as defined in the configuration of the disable timer.

[0096] In some respects, at least one rule to be applied to the disable timer is based on the level of congestion in the network. In some respects, the device activates the disable timer when the level of congestion in the network falls below a threshold amount defined in the configuration of the disable timer.

[0097] In some aspects, after the device sends a request for RBR information to the network, the device starts a disable timer. In some aspects, the at least one memory stores instructions that, when executed by the at least one processor, cause the device to: receive RBR information from the network, wherein at least one rule includes additional rules for determining the duration of the disable timer based on the value of RBR in the RBR information.

[0098] In some aspects, the additional rules specify that the duration of the timer disablement is determined based on a comparison between the bit rate value expected by the device and the RBR value received by the device from the network. In some aspects, the additional rules specify that the duration of the timer disablement is determined as follows: a first duration of timer disablement if the RBR value received by the device from the network is equal to or greater than the bit rate value expected by the device; and a second duration of timer disablement if the RBR value received by the device from the network is less than the bit rate value expected by the device, wherein the first duration is longer than the second duration. In some aspects, the at least one memory stores an instruction that, when executed by the at least one processor, causes the device to perform: acquiring information including an RBR value offset, wherein the additional rules specify that the duration of the timer disablement is determined as follows: a first duration of timer disablement if the RBR value received by the device from the network minus the bit rate value expected by the device is less than the RBR value offset; and a second duration of timer disablement if the RBR value received by the device from the network minus the bit rate value expected by the device is greater than the RBR value offset, wherein the first duration is longer than the second duration.

[0099] In some aspects, the at least one memory storage instruction, when executed by the at least one processor, causes the device to: acquire configuration information including a second disable timer. In some aspects, the at least one memory storage instruction, when executed by the at least one processor, causes the device to: send a request for RBR information to the network; and based on the device sending the request for RBR information to the network, start the second disable timer. In some aspects, the duration of the disable timer used in response to the device receiving RBR information from the network is different from (e.g., less than) the duration of the second disable timer used in response to the device sending the request for RBR information to the network.

[0100] In some respects, RBR information is included in at least one Media Access Control (MAC) element (CE). In some respects, the device is a User Equipment (UE).

[0101] exist Figure 7In an embodiment of the method shown, one approach includes: obtaining information including: a configuration of a disable timer for an RBR request; a request for RBR information sent by the UE to the network; and, based on the disable timer configuration, starting the disable timer if the UE does not receive RBR information from the network, or waiting to start the disable timer until the UE receives RBR information from the network. In some aspects, the information includes at least one rule to be applied to the disable timer. In some aspects, the method includes the UE receiving RBR information from the network.

[0102] In some aspects, the method includes the UE determining whether to restart the disable timer by comparing the expected RBR value with the RBR value in RBR information received from the network. In some aspects, the method includes the UE determining whether to start the disable timer by comparing the expected RBR value with the RBR value in an RBR request for RBR information sent by the UE to the network. In some aspects, the method includes the UE determining whether to start the disable timer by comparing the current time with the time of a future RBR request provided to the network in an earlier UE Assistance Information (UAI) request.

[0103] In some aspects, the method includes the UE determining whether to restart the disable timer by comparing the current time with the time of a future RBR request provided in a previous request to the network. In some aspects, the UE determines to restart the disable timer when the difference between the expected RBR value and the RBR value in RBR information received from the network is as defined in the disable timer configuration. In some aspects, the UE determines to restart the disable timer when the difference between the expected RBR value and the RBR value in the last RBR information sent to the network is as defined in the disable timer configuration.

[0104] In some respects, at least one rule to be applied to the disable timer is based on the level of congestion in the network. In some respects, the disable timer is activated when the level of congestion in the network falls below a threshold amount as defined in the disable timer configuration. In this respect, and in other respects described herein, the disable timer configuration includes defining values ​​or ranges of values ​​such as “small,” “large,” “threshold amount,” “similar,” etc.

[0105] In some aspects, the timer is disabled after the UE sends a request for RBR information to the network. In some aspects, the method includes the UE receiving RBR information from the network, wherein at least one rule includes an additional rule for determining the duration of the timer disabling based on the value of the RBR in the RBR information. In some aspects, the additional rule specifies that the duration of the timer disabling is determined based on a comparison between a bit rate value desired by the UE and the value of the RBR received by the UE from the network.

[0106] In some aspects, the additional rules specify that the duration of the timer disablement is determined as follows: a first duration of timer disablement when the RBR value received by the UE from the network is equal to or greater than the UE's desired bit rate value; and a second duration of timer disablement when the RBR value received by the UE from the network is less than the UE's desired bit rate value, wherein the first duration is longer than the second duration. In some aspects, the additional rules specify that the duration of the timer disablement is determined as follows: a first duration of timer disablement when the RBR value received by the UE from the network is equal to or greater than the UE's desired bit rate value; and a second duration of timer disablement when the RBR value received by the UE from the network is less than the UE's desired bit rate value; wherein the first duration is longer than the second duration. In some aspects, the method includes: acquiring information including an RBR value offset, wherein the additional rules specify that the duration of the timer disablement is determined as follows: a first duration of timer disablement when the RBR value received by the UE from the network minus the UE's desired bit rate value is less than the RBR value offset; and a second duration of timer disablement when the RBR value received by the UE from the network minus the UE's desired bit rate value is greater than the RBR value offset, wherein the first duration is longer than the second duration.

[0107] In some aspects, the method includes obtaining configuration information including a second disable timer. In some aspects, the method includes the UE sending a request for RBR information to the network; and based on the UE's request for the RBR information to the network, starting the second disable timer. In some aspects, the duration of the disable timer used in response to the UE receiving RBR information from the network is different from (e.g., less than) the duration of the second disable timer used in response to the UE's request for the RBR information to the network. In some aspects, the RBR information is included in at least one Media Access Control (MAC) element (CE).

[0108] exist Figure 7In other embodiments of the method shown, one method includes providing information including: a configuration of a prohibition timer for a Recommended Bit Rate (RBR) request, wherein the network fails to receive a request for RBR information from a User Equipment (UE) before the prohibition timer expires; and the network receives a request for RBR information from the UE after the prohibition timer expires. In some aspects, the information includes at least one rule to be applied to the prohibition timer. In some aspects, the at least one rule to be applied to the prohibition timer is based on congestion levels in the network. In some aspects, the at least one rule to be applied to the prohibition timer indicates that a probability timer is started when congestion levels in the network are below a threshold amount. In some aspects, the at least one rule to be applied to the prohibition timer specifies that the duration of the prohibition timer is determined based on an RBR value in the RBR information. In some aspects, the at least one rule to be applied to the prohibition timer specifies that the duration of the prohibition timer is determined based on a comparison between a bit rate value desired by the UE and an RBR value sent by the network to the UE.

[0109] Figure 8 Another embodiment of this disclosure is illustrated. Here, the UE selects a first duration or a second duration of the disable timer based on the difference between the value of the RBR information received by the UE from the network and the bit rate desired by the UE. In this embodiment, when the RBR value received from the network is greater than or equal to the bit rate desired by the UE, the UE selects a disable timer with a longer duration. At operation 810, the network sends and the UE receives a configuration for the disable timer for the RBR request. This configuration includes a first disable timer and a second disable timer, the first disable timer having a larger first duration value for use when the RBR value received from the network is greater than or equal to the bit rate desired by the UE, and the second disable timer having a shorter second duration value for use when the RBR value received from the network is less than the bit rate desired by the UE. At operation 820, the network sends and the UE receives RBR information (e.g., including the bit rate MAC CE of the QoS flow). At operation 830a, the UE determines that the RBR value received from the network is greater than or equal to the bit rate desired by the UE and starts the first disable timer. At Operation 830b (an alternative to Operation 830a), the UE determines that the RBR value received from the network is less than the bit rate value expected by the UE, and starts a second disable timer.

[0110] Figure 8 The above description is merely illustrative, and variations are considered to be within the scope of this disclosure. In various embodiments, operation may include... Figure 8 Other operations not shown. In various embodiments, operations may not include... Figure 8 Each operation is shown. In various embodiments, Figure 8The operations shown as single or combined operations can be implemented as individual operations. In various embodiments, Figure 8 The individual operations shown can be combined. Such and other variations are considered to be within the scope of this disclosure.

[0111] Figure 9 Another embodiment of this disclosure is illustrated. Here, after the prohibition timer expires, the UE can restart the prohibition timer if the conditions included in the prohibition timer's configuration are met. At operation 910, the network sends and the UE receives the prohibition timer's configuration, which includes conditions for starting or restarting the prohibition timer. In this embodiment, the condition may relate to how much the RBR value expected by the UE has changed relative to the latest RBR value received by the UE from the network or relative to the latest RBR value requested by the UE from the network. For example, if the RBR value expected by the UE has not changed (significantly) compared to the RBR value included when the UE sent its latest request to the network, the UE must use a longer RBR prohibition timer before issuing subsequent requests, thus prohibiting the UE from sending subsequent RBR requests to the network for a longer period. In other embodiments, the prohibition timer's condition may relate to the amount of congestion detected by the UE in the network. At operation 920, the network sends and the UE receives RBR information. At operation 930, the UE starts the prohibition timer. At operation 940, the prohibition timer expires. At operation 950, the UE determines whether the conditions included in the prohibition timer's configuration are met. At operation 960, the UE determines that the conditions included in the configuration of the disable timer are met and starts the disable timer. If the conditions included in the configuration of the disable timer are not met, the UE will be allowed to send a request for RBR information to the network without starting (or restarting) the disable timer.

[0112] Figure 9 The above description is merely illustrative, and variations are considered to be within the scope of this disclosure. In various embodiments, operation may include... Figure 9 Other operations not shown. In various embodiments, operations may not include... Figure 9 Each operation is shown. In various embodiments, Figure 9 The operations shown as single or combined operations can be implemented as individual operations. In various embodiments, Figure 9 The individual operations shown can be combined. Such and other variations are considered to be within the scope of this disclosure.

[0113] Figure 10Another embodiment of this disclosure is illustrated. Here, when the disable timer is active (i.e., after the disable timer starts and before it expires), the UE can stop the disable timer if certain conditions are met. That is, in some cases, the UE can stop the disable timer and send a request for RBR information to the network before the disable timer expires. At operation 1010, the network sends and the UE receives a configuration for the disable timer, which includes conditions for stopping the disable timer. In an embodiment, this condition may relate to the RBR value expected by the UE relative to the latest RBR value received by the UE from the network. If the difference between these values ​​exceeds a threshold amount (as set in the configuration), the UE can stop the disable timer and send a request for RBR information to the network. At operation 1020, the network sends and the UE receives RBR information (e.g., including the bit rate MAC CE of the QoS flow). At operation 1030, the UE starts the disable timer. At operation 1040, the UE checks the status of the disable timer to determine whether the UE is allowed to stop the disable timer. At operation 1050, the UE determines that the conditions for the disable timer are met and stops the disable timer. At operation 1060, the UE sends a request for RBR information to the network. Furthermore, if the UE has not stopped the disable timer, the UE's request transmission at operation 1060 occurs before the disable timer expires.

[0114] In certain aspects of this disclosure, when multiple disable timers are used to prevent the UE from sending an RBR request to the network at a pre-requested future interval, the UE has the ability to stop these timers. For example, if the difference between the UE's expected RBR for a future time interval and the RBR value last requested by the UE for that future time interval exceeds a threshold defined in the configuration, the UE can stop the disable timer associated with that future time interval, thereby allowing the UE to send an RBR request at that time. Alternatively or additionally, if the difference between the UE's expected RBR for a future time interval and the RBR value last provided by the UE for that future time interval exceeds a threshold defined in the configuration, the UE can stop the disable timer associated with that future time interval, thereby allowing the UE to send an RBR request at that time.

[0115] Figure 10 The above description is merely illustrative, and variations are considered to be within the scope of this disclosure. In various embodiments, operation may include... Figure 10 Other operations not shown. In various embodiments, operations may not include... Figure 10 Each operation is shown. In various embodiments, Figure 10 The operations shown as single or combined operations can be implemented as individual operations. In various embodiments, Figure 10 The individual operations shown can be combined. Such and other variations are considered to be within the scope of this disclosure.

[0116] exist Figure 10 In the example embodiment shown, an apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: acquire information including: a configuration of a disable timer for a Recommended Bit Rate (RBR) request and a configuration of an RBR threshold; receive RBR information from a network; start a disable timer, wherein the apparatus avoids requesting additional RBR information from the network before the disable timer expires; and determine, based on the configuration, whether to stop the disable timer.

[0117] In some aspects, the device determines whether to stop the timer disable by comparing the expected RBR value with the RBR value in the RBR information received from the network. In some aspects, the at least one memory stores an instruction that, when executed by the at least one processor, causes the device to: stop the timer disable when the difference between the expected RBR value and the RBR value in the RBR information received from the network is greater than an RBR threshold.

[0118] In some aspects, the device determines whether to stop the timer disable by comparing the expected RBR value with the final RBR value sent to the network. In some aspects, the at least one memory stores an instruction that, when executed by the at least one processor, causes the device to: stop the timer disable when the difference between the expected RBR value and the final RBR value sent to the network is greater than an RBR threshold.

[0119] In some aspects, the at least one memory-stored instruction, when executed by the at least one processor, causes the device to: stop disabling a timer. In some aspects, stopping the timer allows the device to request additional RBR information from the network. In some aspects, stopping the timer causes the device to request additional RBR information from the network. In some aspects, the at least one memory-stored instruction, when executed by the at least one processor, causes the device to: acquire information including at least one rule to be applied to the timer disabling function.

[0120] In some aspects, at least one rule includes additional rules for determining the duration of a timer disablement based on the value of the RBR in the RBR information. In some aspects, the additional rules specify that the duration of the timer disablement is determined based on a comparison between the bit rate value expected by the device and the RBR value received by the device from the network. In some aspects, the additional rules specify that the duration of the timer disablement is determined as follows: a first duration of timer disablement if the RBR value received by the device from the network is equal to or greater than the bit rate value expected by the device; and a second duration of timer disablement if the RBR value received by the device from the network is less than the bit rate value expected by the device, wherein the first duration is longer than the second duration.

[0121] In some aspects, the at least one memory storage instruction, when executed by the at least one processor, causes the device to: acquire information including an RBR value offset, wherein an additional rule specifies that the duration of the disable timer is determined as follows: a first duration of disabling the timer if the RBR value received by the device from the network minus the bit rate value expected by the device is less than the RBR value offset; and a second duration of disabling the timer if the RBR value received by the device from the network minus the bit rate value expected by the device is greater than the RBR value offset, wherein the first duration is longer than the second duration. In some aspects, the at least one memory storage instruction, when executed by the at least one processor, causes the device to: acquire information including a configuration of a second disable timer. In some aspects, the at least one memory storage instruction, when executed by the at least one processor, causes the device to: send a request for RBR information to the network; and based on the device sending the request for RBR information to the network, start the second disable timer. In some respects, the duration of the disable timer used in response to the device receiving RBR information from the network is different from (for example, less than) the duration of the second disable timer used in response to the device sending a request for RBR information to the network.

[0122] In some aspects, the configuration of the second disable timer includes a request for a future time interval (RBR) and a configuration of an RBR threshold for the future time interval. In some aspects, the at least one memory stores an instruction that, when executed by the at least one processor, causes the device to: stop the second disable timer when the difference between the expected RBR value during the future time interval and the RBR value in the future time interval's RBR information received from the network is greater than the future time interval's RBR threshold. In some aspects, the at least one memory stores an instruction that, when executed by the at least one processor, causes the device to: stop the second disable timer when the difference between the expected RBR value during the future time interval and the last RBR value sent to the network is greater than the future time interval's RBR threshold.

[0123] In some respects, RBR information is included in at least one Media Access Control (MAC) element (CE). In some respects, the device is a User Equipment (UE).

[0124] exist Figure 10 In an embodiment of the method shown, the method includes: acquiring information including: a configuration of a disable timer for a Recommended Bit Rate (RBR) request and a configuration of an RBR threshold; receiving RBR information from the network by a User Equipment (UE); starting a disable timer, wherein the UE avoids requesting additional RBR information from the network before the disable timer expires; and determining by the UE whether to stop the disable timer based on the configuration. In some aspects, the UE determines whether to stop the disable timer by comparing a desired RBR value with an RBR value in the RBR information received from the network. In some aspects, the UE stops the disable timer when the difference between the desired RBR value and the RBR value in the RBR information received from the network is greater than an RBR threshold.

[0125] In some respects, the UE determines whether to stop the timer disable by comparing the expected RBR value with the last RBR value sent to the network. In other respects, the UE stops the timer disable when the difference between the expected RBR value and the expected last RBR value provided to the network is greater than an RBR threshold.

[0126] In some aspects, the method includes having the UE disable the timer. In some aspects, the method includes having the UE disable the timer, thereby allowing the UE to request additional RBR information from the network. In some aspects, the method includes having the UE disable the timer, thereby enabling the UE to request additional RBR information from the network.

[0127] In some aspects, the method includes acquiring information including at least one rule to be applied to disable the timer. In some aspects, the at least one rule includes an additional rule for determining the duration of the disable timer based on the value of the RBR in the RBR information. In some aspects, the additional rule specifies that the duration of the disable timer is determined based on a comparison between a bit rate value desired by the UE and the RBR value received by the UE from the network.

[0128] In some aspects, the additional rules specify that the duration of the timer disablement is determined as follows: a first duration of timer disablement is specified when the RBR value received by the UE from the network is equal to or greater than the UE's desired bit rate value; a second duration of timer disablement is specified when the RBR value received by the UE from the network is less than the UE's desired bit rate value; the first duration is longer than the second duration. In some aspects, the method includes acquiring information including an RBR value offset, wherein the additional rules specify that the duration of the timer disablement is determined as follows: a first duration of timer disablement is specified when the RBR value received by the UE from the network minus the UE's desired bit rate value is less than the RBR value offset; and a second duration of timer disablement is specified when the RBR value received by the UE from the network minus the UE's desired bit rate value is greater than the RBR value offset, the first duration being longer than the second duration.

[0129] In some aspects, the method includes acquiring configuration information including a second disable timer. In some aspects, the method includes the UE sending a request for RBR information to the network; and based on the device sending the request for RBR information to the network, starting the second disable timer. In some aspects, the duration of the disable timer used in response to the UE receiving RBR information from the network is different from (e.g., less than) the duration of the second disable timer used in response to the UE sending the request for RBR information to the network.

[0130] In some aspects, the configuration of the second disable timer includes configuring RBR requests for future time intervals and configuring an RBR threshold for future time intervals. In some aspects, the UE stops the second disable timer when the difference between the expected RBR value during the future time interval and the RBR value in the RBR information received from the network for the future time interval is greater than the RBR threshold for the future time interval. In some aspects, the UE stops the second disable timer when the difference between the expected RBR value during the future time interval and the last RBR value sent to the network is greater than the RBR threshold for the future time interval.

[0131] In some respects, RBR information is included in at least one Media Access Control (MAC) control element (CE).

[0132] The various embodiments disclosed herein, individually or in combination with other embodiments, can benefit the network and the UE in various ways. Some embodiments can avoid or help avoid excessively frequent and / or excessively low RBR requests from the UE, while allowing RBR requests with higher values. Some embodiments can avoid or help avoid situations where the disable timer has not started or is not running, even if the RBR value from the network is relatively new and therefore more likely to be up-to-date. Some aspects allow for a shorter (less stringent) disable timer after the UE receives RBR information from the network to help compensate for the disable timer preventing the UE from sending an updated RBR request to the network. Some embodiments can avoid or help avoid situations where the disable timer has not started or is not running, even if the RBR value in the request sent by the UE to the network is similar to the latest RBR value requested by the UE. In some aspects, situations are avoided or minimized where the disable timer does not run long enough after the UE sends a request for an RBR value to the network, or where the UE receives RBR information from the network and the RBR value requested by the UE has not changed significantly. Some embodiments provide a mechanism to balance these useful features, wherein the value of the bit rate desired by the UE has changed (e.g., changed significantly) since the last RBR value reported by the UE and / or is higher than the last known RBR value received from the network.

[0133] Figure 11 This is a block diagram of example components of an apparatus 1100 according to one aspect of this disclosure, such as user equipment or network nodes (e.g., UE, AP, BS, eNB, gNB, RAN node, network node, TRP, or other nodes). Apparatus 1100 may include, for example, one or more radio frequency (RF) or wireless transceivers 1102A, 1102B (e.g., RF transceivers), wherein each wireless transceiver includes a transmitter for transmitting signals and a receiver for receiving signals. The apparatus also includes a processor 1104 and / or a control unit / entity for executing instructions or software and controlling the transmission and reception of signals, and a memory 1106 for storing data and / or instructions.

[0134] Processor 1104 may also make decisions or determinations, generate frames, packets, or messages for transmission, decode received frames or messages for further processing, and perform other tasks or functions described herein. For example, processor 1104, which may be a baseband processor, may generate messages, packets, frames, or other signals for transmission via wireless transceiver 1102 (1102A or 1102B). Processor 1104 may control the transmission of signals or messages over a wireless network and may control the reception of signals or messages over a wireless network (e.g., after down-conversion by wireless transceiver 1102). Processor 1104 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 1104 may be (or may include) hardware, programmable logic, a programmable processor executing software or firmware, and / or any combination of these. Using other terms, for example, processor 1104 and wireless transceiver 1102 may be considered together as a wireless transmitter / receiver system.

[0135] In addition, refer to Figure 11 The controller (or processor) 1104 can execute software and instructions, and can provide overall control for the device 1100, and can also... Figure 11 Other systems, not shown, provide control, such as controlling input / output devices (e.g., a display, a keypad), and / or can execute software for one or more applications that may be available on device 1100, such as email programs, audio / video applications, word processors, VoIP applications, or other applications or software.

[0136] In addition, a storage medium may be provided that includes storage instructions, which, when executed by a controller or processor, may cause processor 1104 or other controllers or processors to perform one or more of the functions or tasks described above.

[0137] According to another example embodiment, multiple RF or wireless transceivers 1102A / 1102B can receive signals or data and / or transmit signals or data. Processor 1104 (and possibly transceivers 1102A / 1102B) can control the RF or wireless transceivers 1102A or 1102B to receive, transmit, broadcast, or transmit signals or data.

[0138] Example embodiments are provided or described for each example method, including: an apparatus (e.g., Figure 11 1100 in the middle), which includes components for performing any method (e.g., Figure 11The processor 1104, wireless transceiver 1102A and / or 1102B and / or memory 1106 shown; a non-transitory computer-readable storage medium (e.g., Figure 11 The memory 1106 includes instructions stored thereon, which are processed by at least one processor (e.g., Figure 11 When the processor 1104 executes, it is configured to cause the computing system (e.g., Figure 11 (1100) executes any example method; and a device (e.g., Figure 11 The 1100), which includes at least one processor (e.g., Figure 11 The processor 1104 in the memory and at least one memory including computer program code (e.g., Figure 11 The at least one memory (1106) and computer program code are configured together with the at least one processor (1104) such that the device (e.g., 1100) performs at least any of the example methods.

[0139] Further embodiments of this disclosure include the following examples. Unless the context otherwise requires, a "component" may be implemented by a processor and a memory storing instructions executable by the processor. A component for transmitting or receiving may be implemented by a transceiver.

[0140] Example 1.1: An apparatus comprising: At least one processor; and At least one memory stores instructions that, when executed by the at least one processor, cause the device to perform at least the following: Obtain information including: the configuration of the disable timer used for Recommended Bit Rate (RBR) requests; Receive RBR information from the network; and Based on the configuration of the prohibition timer, the prohibition timer is started after the RBR information is received from the network, wherein the device avoids requesting additional RBR information from the network before the prohibition timer expires.

[0141] Example 1.2: The apparatus according to Example 1.1, wherein the information includes at least one rule applicable to the disable timer.

[0142] Example 1.3: The apparatus according to Example 1.2, wherein the at least one rule relates to when the disable timer will be activated.

[0143] Example 1.4: The apparatus according to Example 1.3, wherein the at least one rule specifies that the disable timer will be started or restarted based on the apparatus receiving RBR information from the network.

[0144] Example 1.5: The apparatus according to Example 1.3, wherein the at least one rule specifies that the disable timer will be started or restarted based on the apparatus requesting RBR information from the network.

[0145] Example 1.6: An apparatus according to any one of Examples 1.2 to 1.5, wherein the at least one rule includes an additional rule for determining the duration of the disabled timer based on the value of the RBR in the RBR information.

[0146] Example 1.7: The apparatus according to Example 1.6, wherein the additional rule specifies that the duration of the disable timer is determined based on a comparison between a bit rate value desired by the apparatus and the value of the RBR received by the apparatus from the network.

[0147] Example 1.8: The apparatus according to Example 1.7, wherein the additional rule specifies that the duration of the disable timer is determined as: The first duration of the disable timer is determined when the value of the RBR received by the device from the network is equal to or greater than the bit rate value expected by the device; and If the value of the RBR received by the device from the network is less than the bit rate value expected by the device, the second duration of the disable timer is specified, wherein the first duration is longer than the second duration.

[0148] Example 1.9: The apparatus according to Example 1.7, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to perform: Obtain information including the RBR value offset, wherein the additional rule specifies that the duration of the disable timer is determined as follows: The first duration of the disable timer is determined when the difference between the RBR received by the device from the network and the bit rate value expected by the device is less than the RBR value offset; and If the difference between the RBR received by the device from the network and the bit rate value expected by the device is greater than the RBR value offset, the second duration of the disable timer is specified, wherein the first duration is longer than the second duration.

[0149] Example 1.10: The apparatus according to Example 1.2, wherein the at least one rule specifies that the duration of the disable timer is determined based on at least one of the RBR value received by the apparatus from the network and the RBR value expected by the apparatus.

[0150] Example 1.11: An apparatus according to any one of Examples 1.1 to 1.10, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to perform: acquire information including a configuration of a second disable timer.

[0151] Example 1.12: The apparatus according to Example 1.11, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to: send a request for the RBR information to the network; and, based on the request for the RBR information sent by the apparatus to the network, start the second disable timer.

[0152] Example 1.13: The apparatus according to Example 1.12, wherein the duration of the disable timer used in response to the apparatus receiving the RBR information from the network is different from the duration of the second disable timer used in response to the apparatus sending the request for the RBR information to the network.

[0153] Example 1.14: The apparatus according to Example 1.11, wherein the second disable timer is configured to start at a predetermined time after at least one of the start of the disable timer and the expiration of the disable timer.

[0154] Example 1.15: An apparatus according to any one of Examples 1.1 to 1.2, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to: send a request for the RBR information to the network.

[0155] Example 1.16: An apparatus according to any one of Examples 1.1 to 1.15, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to avoid sending an additional request for additional RBR information to the network before the prohibition timer expires, and to send the additional request for the additional RBR information to the network after the prohibition timer expires.

[0156] Example 1.17: An apparatus according to any one of Examples 1.1 to 1.16, wherein the RBR information is included in at least one Media Access Control (MAC) control element (CE).

[0157] Example 1.18: An apparatus according to any one of Examples 1.1 to 1.17, wherein the apparatus is a user equipment (UE).

[0158] Example 1.19: A processor-readable medium storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least one of Examples 1.1 to 1.18.

[0159] Example 2.1: A method comprising: Obtain information including: the configuration of the disable timer used for Recommended Bit Rate (RBR) requests; The user equipment (UE) receives RBR information from the network; and Based on the configuration, the prohibition timer is started based on the RBR information received from the network, wherein the UE avoids requesting additional RBR information from the network before the prohibition timer expires.

[0160] The embodiments and aspects disclosed herein are examples of this disclosure and may be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each embodiment herein may be combined with one or more other embodiments herein. The specific structural and functional details disclosed herein should not be construed as limiting, but rather serve as the basis for the claims and as a representative basis for teaching those skilled in the art to use this disclosure in various ways in virtually any suitably detailed structure. Throughout the description of the drawings, the same reference numerals may refer to similar or identical elements.

[0161] According to this disclosure, the phrases “in one aspect,” “in some aspects,” “in all aspects,” “in some aspects,” or “in other aspects” can each refer to one or more of the same or different aspects. The phrase “multiple” can refer to two or more.

[0162] In various embodiments, the terms "first message" and "second message" as well as any subsequent messages can refer to any message sent or received in sequence, and are not necessarily limited to any particular message.

[0163] According to this disclosure, the phrases “in one embodiment,” “in an embodiment,” “in various embodiments,” “in some embodiments,” or “in other embodiments” can each refer to one or more of the same or different embodiments. A phrase of the form “A or B” means “(A), (B), or (A and B).” A phrase of the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).”

[0164] Any method, program, algorithm, or code described herein can be translated into or represented in a programming language or computer program. The terms "programming language" and "computer program" as used herein each include any language used to specify computer instructions, and include (but are not limited to) the following languages ​​and their derivatives: assembly language, Basic, batch files, BCPL, C, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, meta-languages ​​that specify the program itself, and all first-, second-, third-, fourth-, fifth-, or later computer languages. Databases and other data schemas, and any other meta-languages, are also included. No distinction is made between interpreted, compiled, or both compiled and interpreted languages. No distinction is made between a compiled version of a program and a source code version. Therefore, if a programming language can exist in more than one state (such as source, compilation, object, or link), a reference to a program is a reference to any and all such states. A reference to a program can encompass the actual instructions and / or the intent of those instructions.

[0165] While various aspects of this disclosure are shown in the accompanying drawings, they are not intended to limit the disclosure thereto, as the scope of this disclosure should be as broad as possible, and the specification should be read in the same manner. Therefore, the above description should not be construed as limiting, but merely as examples of specific aspects. Those skilled in the art will be able to conceive of other modifications within the scope and spirit of the appended claims.

Claims

1. A device for communication, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to perform at least the following: Obtain information including: the configuration of the disable timer used for the Recommended Bit Rate (RBR) request; Receive RBR information from the network; as well as Based on the configuration of the prohibition timer, the prohibition timer is started after the RBR information is received from the network, wherein the device avoids requesting additional RBR information from the network before the prohibition timer expires.

2. The apparatus of claim 1, wherein the information includes at least one rule applicable to the disable timer; The at least one of the rules pertains to when the disable timer will be activated; The at least one of the rules specifies that the disable timer will be started or restarted based on the device receiving RBR information from the network; or The at least one of the rules specifies that the disable timer will be started or restarted based on the device requesting RBR information from the network.

3. The apparatus of claim 2, wherein the at least one rule includes an additional rule for determining the duration of the disable timer based on the value of the RBR in the RBR information; The additional rule specifies that the duration of the disable timer is determined based on a comparison between the bit rate value expected by the device and the value of the RBR received by the device from the network; The additional rule specifies that the duration of the prohibited timer is determined as follows: The first duration of the disable timer is when the value of the RBR received by the device from the network is equal to or greater than the bit rate value expected by the device. as well as If the value of the RBR received by the device from the network is less than the bit rate value expected by the device, the second duration of the disable timer, wherein the first duration is longer than the second duration; as well as The at least one memory stores an instruction that, when executed by the at least one processor, causes the device to perform: Obtain information including the RBR value offset, wherein the additional rule specifies that the duration of the disable timer is determined as follows: The first duration of the disable timer is when the difference between the RBR received by the device from the network and the bit rate value expected by the device is less than the RBR value offset; as well as If the difference between the RBR received by the device from the network and the bit rate value expected by the device is greater than the RBR value offset, the second duration of the disable timer is specified, wherein the first duration is longer than the second duration.

4. The apparatus of claim 2, wherein the at least one rule specifies that the duration of the disable timer is determined based on at least one of the RBR value received by the apparatus from the network and the RBR value expected by the apparatus.

5. The apparatus according to any one of claims 1 to 4, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the apparatus to perform: Obtain information including the configuration of the second disable timer.

6. The apparatus of claim 5, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to perform: Send a request for the RBR information to the network; as well as Based on the request for the RBR information sent by the device to the network, the second disable timer is started; The duration of the disable timer used in response to the device receiving the RBR information from the network is different from the duration of the second disable timer used in response to the device sending the request for the RBR information to the network.

7. The apparatus of claim 5, wherein the second disable timer is configured to start at a predetermined time after at least one of the start of the disable timer and the expiration of the disable timer.

8. The apparatus according to any one of claims 1 to 2, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the apparatus to perform: Send a request for the RBR information to the network.

9. The apparatus according to any one of claims 1 to 4, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to avoid sending an additional request for additional RBR information to the network before the prohibition timer expires, and to send the additional request for additional RBR information to the network after the prohibition timer expires; The RBR information is contained in at least one Media Access Control (MAC) control element (CE); and The device mentioned is a user equipment (UE).

10. A method for communication, comprising: Obtain information including: the configuration of the disable timer used for the Recommended Bit Rate (RBR) request; The user equipment (UE) receives the RBR information from the network. as well as Based on the configuration, the prohibition timer is started based on the RBR information received from the network, wherein the UE avoids requesting additional RBR information from the network before the prohibition timer expires.