Method for bit rate control support for xr

Abstract

A method includes determining, by a user equipment (UE) operating at a first bitrate, that a congestion condition exists. The UE transmits a first message to a network apparatus, the first message including an indication that a bit rate is to be lowered, receives, from the network apparatus, a second message indicating a second bitrate, and adjusts the first bitrate to the second bitrate for operation.

Description

METHOD FOR BIT RATE CONTROL SUPPORT FOR XRFIELD

[0001] Various example embodiments relate generally to wireless networks and, more particularly, for a method and apparatus for recommended bit rate support for extended reality (XR).BACKGROUND

[0002] With radio access network (RAN) aware extended reality (XR) rate control, the XR application can dynamically adjust its codec bit rate and encoding parameters to ensure a seamless and high-quality XR user experience. This is achieved by monitoring the network conditions and adapting the application's behavior accordingly, such as reducing the resolution or frame rate when the network is congested.

[0003] XR applications are latency sensitive. Latency indication, specifically, RAN congestion information, is one of the key RAN awareness information that would benefit XR application rate-control performance and improve its quality of service (QoS) and user experience. Other RAN metrics (e.g., recommended bitrate) can be considered and enhanced for XR traffic, as well. In XR applications, such as augmented calling use cases, the traffic is bi-directional and UL is, often, the performance bottleneck.SUMMARY

[0004] In an aspect of the present disclosure, a method includes determining, by a user equipment (UE) operating at a first bitrate, that a congestion condition exists. The UE transmits a first message to a network apparatus, the first message including an indication that a bit rate is to be lowered, receives, from the network apparatus, a second message indicating a second bitrate, and adjusts the first bitrate to the second bitrate for operation.

[0005] In an aspect of the method, the determining includes a determination of one or more of the following: cell congestion, cell recovery, or an indication from an application.

[0006] In an aspect of the method, the determining includes monitoring at least one of a buffer status or delay status at lower layers of the UE protocol stack.

[0007] In an aspect of the method, upon the size of the buffered data or delay status increasing, the UE determines that the congestion condition exists.

[0008] In an aspect of the method, the determining includes monitoring application related parameters.

[0009] In an aspect of the method, the application parameters include one or more of the following: quality of experience (QoE), initial playout delay, average throughput, buffer level, or playout delay for media start-up.

[0010] In an aspect of the method, the determining includes the UE receiving broadcast information.

[0011] In an aspect of the method, the UE receives a broadcast of an access class barring in the cell.

[0012] In an aspect of the method, the first message is an uplink (UL) bit rate recommendation query.

[0013] In an aspect of the method, the UL bit rate recommendation query includes a first lower bitrate indication indicating at least a first lower bitrate.

[0014] In an aspect of the method, the bit rate recommendation includes a second lower bitrate indication indicating a second lower bitrate.

[0015] In an aspect of the method, the second message is a UL bit rate recommendation message.

[0016] In an aspect of the method, the method further includes returning, by the UE, to the first bitrate upon the congestion condition no longer existing.

[0017] In an aspect of the present disclosure, a method includes determining, by a network apparatus, that a congestion condition exists for a first user equipment (UE) operating at a first bitrate, determining, by the network apparatus, a second bitrate, and transmitting, by the network apparatus, a first message to at least the first UE, the first message indicating the second bitrate.

[0018] In an aspect of the method, the method further includes receiving, by the network apparatus, a second message from the first UE, the second message including an indication that a bit rate is to be lowered.

[0019] In an aspect of the method, the second bitrate includes a bitrate recommended by the UE in the second message.

[0020] In an aspect of the method, the network apparatus rejects the bitrate recommended by the UE in the second message.

[0021] In an aspect of the method, the second bitrate is determined by analyzing one or more of 5QI associated with an interactive service or a quality of service (QoS) profile configured for a QoS flow.

[0022] In an aspect of the method, the method further includes upon an existence of multimodal traffic, transmitting by the network apparatus, the second message to at least a second UE belonging to a same multi-modal service of the first UE.

[0023] In an aspect of the present disclosure, a UE includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, causes the UE at least to perform any of the foregoing methods.

[0024] In an aspect of the present disclosure, an apparatus includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, causes the apparatus at least to perform any of the foregoing methods.

[0025] In an aspect of the present disclosure, a processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform any of the foregoing methods.

[0026] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Some example embodiments will now be described with reference to the accompanying drawings.

[0028] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0029] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0030] FIG. 3 is a diagram of an example system for bit rate application for an extended reality (XR) case, according to one illustrated aspect of the disclosure;

[0031] FIG. 4 is a diagram of an example embodiment of signals and operations among a user equipment (UE1) and a gNB, according to one illustrated aspect of the disclosure;

[0032] FIG. 5 is a diagram of an example embodiment of signals and operations among UE1, UE 2 and a gNB, according to one illustrated aspect of the disclosure; and

[0033] FIG. 6 is a diagram of an example block diagram of a wireless station or node (e.g., network node (such as gNB), user node or UE, relay node, or other node), according to one illustrated aspect of the present disclosure.DETAILED DESCRIPTION

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

[0035] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0036] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband- code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0037] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0038] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shallbe understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0039] FIG. l is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5GNR and embodiments that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0040] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2, which is hereby incorporated by reference herein.

[0041] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0042] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control(MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g. : o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC quality of service (QoS) flows; o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0043] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0044] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0045] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en- gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0046] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, or a gNB-DU, or any combination of them. A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 5 below.

[0047] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open- RAN (0-RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0048] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support acandidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0049] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 6. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0050] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0051] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0052] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”,and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0053] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0054] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0055] Additional components and functions of the core network 210 may include an application function 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, and operations and management function (0AM) 223.

[0056] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The DN 226 identifies services from service providers, Internet access, and third party services, for example.

[0057] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0058] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. TheNRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0059] The UDM 217 generates authentication vectors for use by the AUSF 211 and ADM 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0060] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The 0AM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0061] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0062] As mentioned above, in extended reality (XR) applications, such as augmented calling use cases, traffic is bi-directional and uplink (UL) is, often, the performance bottleneck. Current specified bit rate recommendation media access control (MAC) control elements (CEs) and the bit rate recommendation query allow a bit rate recommendation message from the gNB to the UE or a bit rate recommendation query message from the UE to the gNB, respectively.

[0063] In various embodiments, bit rate recommendation MAC CEs can be reused for the XR case extending the UE and gNB behavior related to these MAC CEs for an XR scenario and challenges.

[0064] Accordingly, described herein in further detail below is a method for defining UE and gNB behaviors when extending bit rate recommendation methods to XR applications. In various embodiments, a recommended bit rate method is described to adjust the operation of, for example, the UE and gNB for XR service provisioning. In various embodiments, this XRservice provisioning may include updates when the cell conditions are changing (e.g., event of congestion or recovery from congestion).

[0065] In various embodiments, triggers to query a recommended bit rate from the UE to the gNB based on for example implicit determination of cell congestion, cell congestion recovery, or indication received from upper layers (e.g., application) may be utilized.

[0066] In various embodiments, the bit rate recommendation query message may enable the UE to query the gNB for an updated recommended bit rate that decreases or increases the applicable bit rate, and / or enable the UE to include more than one bit rate in the query to the gNB, like a list of values in the MAC CE.

[0067] New gNB triggers to send an update for the recommended bit rate for a UE or a group of UEs based on available information on the type of XR traffic the UEs have and cell congestion status, or cell recovery from congestion status.

[0068] In various embodiments, the gNB can select LCHs from one or multiple UEs that belong to the same Multi-modal Service e.g. with the same Multi-modal Service ID (MMSID).

[0069] In various embodiments, gNB logic may be added to facilitate transmitting an update for the recommended bit rate to a UE or a group of UEs. The gNB may initiate signaling procedures with the UE and / or CN to reconfigure QoS handling or PDU Set handling to modify e.g. the packet delay budget (PDB) / PDU set delay budget (PSDB) and / or packet error rate (PER) / PDU set error rate (PSER) to a more relaxed / stringent value accordingly to the newly recommended bit rate, and / or reconfigure the UL grant configuration (e.g. periodic and / or on- demand) towards the UEs accordingly to the newly recommended bit rate.

[0070] FIG. 3 is a diagram of an example system 300 for bit rate application for an extended reality (XR) case, according to one illustrated aspect of the disclosure. Although further detail is described below herein, as shown in FIG. 3, A UE (UE1) at time T1 is operating in normal radio conditions and is in communication with a gNB and operates at a bit rate in accordance with a received UL grant for XR LCH. UE1 monitors performance at the upper or lower layers.

[0071] At time T2, UE1 detects and experiences congested radio conditions. UE1 receives an UL grant from the gNB, and transmits a recommended bit rate query to the gNB, which analyzes XR service provisioning in the cell and sends an update on a recommended bit rate to UE1.

[0072] FIG. 4 is a diagram of an example embodiment of signals and operations among a user equipment (UE1) and a gNB, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 4 may correspond to similarcomponents described above in FIGS. 1-2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[0073] At operation 401, a protocol data unit (PDU) session and a dedicated quality of service (QoS) flow for an extended reality (XR) service is configured between UE1 and the gNB. At operation 402, a normal UL grant request / grant process is effected between UE1 and gNB (it includes UE1 sending a buffer status report (BSR) or a delay status report (DSR) towards the gNB). In various embodiments, persons of skill in the art may appreciate the signaling (e.g., buffer status report (BSR), delay status report (DSR), UL grant, UL data) that may be utilized at operation 402.

[0074] At operation 403, UE1 detects congestion. In various embodiments, for example, during XR service provisioning, the UE may have different internal means to detect the cell may be congested or the cell is recovered from a congested condition without an explicit notification coming from the gNB.

[0075] In various embodiments, the UE may monitor the buffer status of the logical channels (LCHs) (e.g., if the size of the buffered increases or decreases), where the UE determination of the congestion may rely on the buffer status at lower layers of the UE protocol stack. The UE can monitor if the buffer size is increasing / decreasing along with the BSRs or DSRs sent to the gNB (the resources requested for the data available). For example, if the UE is requesting for resources that are within the authorized QoS Profile but the gNB cannot provide UL grants with enough resources, limited radio resources can be detected. This detection may depend on additional configuration parameters the UE may have such as a buffer threshold, or an analysis of the offset from the estimated number of PRBs the UE should receive given its modulation and coding scheme (MCS), or buffer evolution through time (e.g., within a sliding time window), or dropped packets in the network, or the transport block (TB) size or increase of delay-critical PDUs within the LCHs to be served.

[0076] In various embodiments, the UE determination of the congestion may rely on an application status at an application layer of the UE protocol stack. For example, application related parameters that are already being monitored for quality of experience (QoE) or application statistics such as initial playout delay, average throughput, buffer level, playout delay for media start-up. The analysis of those attributes at application layer could trigger a notification from application towards the lower layers.

[0077] In various embodiments, based on broadcasted information in the cell, the UE may determine that there is congestion. For example, if the gNB applies access class barring in the cell.

[0078] Accordingly, at operation 404, UE1 transmits a UL bit rate recommendation query that includes a lower bitrate indication to the gNB and the gNB receives the UL bit rate recommendation query that includes a lower bitrate indication.

[0079] For example, based on logic at, for example UE1 (at higher or lower layer), the UE1 can trigger a query to the gNB to reduce the recommended bit rate. The query information and the message may be a specified bit rate recommendation query message to indicate a reduced bit rate value. In various embodiments, the query could include more than one bit rate.

[0080] At operation 405, the gNB determines if the query can be accepted or another recommendation is more suitable. In various embodiments, the gNB may accept / reject this query depending on the radio conditions (e.g., if there is a misunderstanding from the UE side, depending on traffic prediction, etc.). If the UE query is accepted, this may be a trigger to update other LCHs for the same UE or multiple UEs running XR services.

[0081] In various embodiments, the gNB determines the radio interface is congested and there are not enough UL resources for the UEs being served, in which case the recommended bit rate MAC CE can be used to indicate to an interactive XR application to reduce the rate. The gNB may determine the radio interface is not congested and send the recommended bit rate MAC CE with the recommended bit rate which can be applied by the XR application. Upon congestion recovery, an update of the recommended bit rate can be used to adjust again the recommended bit rate to the default agreed value or a larger value indicated for example by the MAC CE.

[0082] There are additional attributes in the configuration of a XR service that may also influence the updates on the recommended bit rate for a UE or a group of UEs served by the gNB. For example, the XR service may have a 5QI associated with interactive services and alternative QoS Profiles configured for the QoS Flow. The gNB can combine this information to send a fast recommended bit rate update matching the rate of an alternative QoS profile.

[0083] In various embodiments, the XR service may have multi-modal traffic (within the same UE or for a group of UEs). When the gNB needs to update the recommended bit rate, the Multi-modal Service ID (MMSID) can be used to identify other LCHs from the same UE or a group of UEs that should also be updated accordingly to not imbalance the service experience.

[0084] Accordingly, at operation 406, the gNB transmits a UL bit rate recommendation message to the UE1 and UE1 receives the UL bit rate recommendation message.

[0085] At operation 407, UE1 and the gNB may reconfigure for UEl ’s QoS flow for XR. In various embodiments, once the gNB has updated the recommended bit rate for a UE (e.g., UE1), either due to its own determination of congestion condition or based on a UE query, thegNB may initiate additional signaling procedures with the UE and / or the CN to align the QoS operation for the XR service. This may include the gNB initiating a radio resource control (RRC) Reconfiguration with the UE to update LCH(s) configuration, the gNB may update its internal logic for UL grant towards the UE, the gNB initiates PDU session modification with the CN to reconfigure the QoS Flow (e.g., to request an update on PDU set / QoS flow handling), the gNB initiates QoS notification control to the CN (as it may have change to an alternative QoS Profile), etc.

[0086] The operations of FIG. 4 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 4. In embodiments, the operations may not include every operation illustrated in FIG. 4. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 4. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 4.

[0087] FIG. 5 is a diagram of an example embodiment of signals and operations among UE1, UE 2 and a gNB, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 5 may correspond to similar components described above in FIGS. 1-2. It will be understood that a described signal may have associated operations and a described operation may have associated signals. In various embodiments the RM may be any network entity as a resource management entity.

[0088] At operation 501, a protocol data unit (PDU) session and quality of service (QoS) flow for an XR service is configured between UE1, UE2 (part of the same multi-modal service with the same MMSID) and the gNB. At operation 502, a normal UL grant request (e.g. via BSR or DSR) / grant process is effected between UE1 and the gNB. In various embodiments, persons of skill in the art may appreciate the signaling (e.g., BSR, DSR, UL grant, UL data) that may be utilized at operation 502.

[0089] Similarly, at operation 503, a normal UL grant request / grant process is effected between UE2 and the gNB. In various embodiments, persons of skill in the art may appreciate the signaling (e.g., BSR, DSR, UL grant, UL data) that may be utilized at operation 503.

[0090] At operation 504, UE1 detects congestion. In various embodiments, the congestion detection may be similar to the congestion detection described above in FIG. 3.

[0091] Accordingly, at operation 505, UE1 transmits a UL bit rate recommendation query that includes a lower bitrate indication to the gNB and the gNB receives the UL bit rate recommendation query that includes a lower bitrate indication.

[0092] At operation 506, the gNB determines that if bitrate is updated for UE1 LCH corresponding to the configured QoS flow of the multi-modal service , for all UEs / LCHs with the same MMSID, the gNB will trigger bit rate recommendation updates as described above.

[0093] Accordingly, at operation 507, the gNB transmits a UL bit rate recommendation message to the UE1 and UE1 receives the UL bit rate recommendation message. At operation 508, the gNB transmits a UL bit rate recommendation message to the UE2 and UE2 receives the UL bit rate recommendation message.

[0094] At operation 509, UE1 and the gNB may reconfigure for UEl ’s QoS flow for XR, and at operation 510, UE2 and the gNB may reconfigure for UE2’s QoS flow for XR.

[0095] In various embodiments, once the gNB has updated the recommended bit rate for a group of UEs (e.g., UE1 and UE2), either due to its own determination or based on a UE query, the gNB may initiate additional signaling procedures with the UE and / or the CN to align the QoS operation for the XR service. This may include the gNB initiating a RRC Reconfiguration with the UE to update LCH(s) configuration, the gNB may update its internal logic for UL grant towards the UE, the gNB initiates PDU session modification with the CN to reconfigure the QoS Flow (e.g., to request an update on PDU set / QoS flow handling), the gNB initiates QoS notification control to the CN (as it may have change to an alternative QoS Profile), etc.

[0096] The operations of FIG. 5 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 5. In embodiments, the operations may not include every operation illustrated in FIG. 5. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 5. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 5.

[0097] The following describes operations from the perspective of a UE. From such a perspective, a method includes determining, by the UE operating at a first bitrate, that a congestion condition exists. The UE transmits a first message to a network apparatus, the first message including an indication that a bit rate is to be lowered, receives, from the network apparatus, a second message indicating a second bitrate, and adjusts the first bitrate to the second bitrate for operation.

[0098] The following describes operations from the perspective of a network apparatus. From such a perspective, a method includes determining, by the network apparatus, that a congestion condition exists for a first UE operating at a first bitrate, determining, by the network apparatus, a second bitrate, and transmitting, by the network apparatus, a first message to at least the first UE, the first message indicating the second bitrate.

[0099] FIG. 6 is a block diagram of a wireless station or node (e.g., UE, user device, AP, BS, eNB, gNB, RAN node, network node, TRP, or other node) 600, according to one illustrated aspect of the present disclosure. The wireless station 600 may include, for example, one or more (e.g., two as shown in FIG. 6) RF (radio frequency) or wireless transceivers 602A, 602B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit / entity (controller) 604 to execute instructions or software and control transmission and receptions of signals, and a memory 606 to store data and / or instructions.

[0100] Processor 604 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 604, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 602 (602A or 602B). Processor 604 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 602, for example). Processor 604 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 604 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination of these. Using other terminology, processor 604 and transceiver 602 together may be considered as a wireless transmitter / receiver system, for example.

[0101] In addition, referring to FIG. 6, a controller (or processor) 608 may execute software and instructions, and may provide overall control for the station 600, and may provide control for other systems not shown in FIG. 6, such as controlling input / output devices (e.g., display, keypad), and / or may execute software for one or more applications that may be provided on wireless station 600, such as, for example, an email program, audio / video applications, a word processor, a Voice over IP application, or other application or software.

[0102] In addition, a storage medium may be provided that includes stored instructions,which when executed by a controller or processor may result in the processor 604, or other controller or processor, performing one or more of the functions or tasks described above.

[0103] According to another example embodiment, RF or wireless transceiver(s) 602A / 602B may receive signals or data and / or transmit or send signals or data. Processor 604 (and possibly transceivers 602A / 602B) may control the RF or wireless transceiver 602A or 602B to receive, send, broadcast or transmit signals or data.

[0104] Example embodiments are provided or described for each of the example methods, including: An apparatus (e.g., 600, FIG. 6) including means (e.g., processor 604, RF transceivers 602A and / or 602B, and / or memory 606, in FIG. 6) for carrying out any of the methods; a non-transitory computer-readable storage medium (e.g., memory 606, FIG. 6) comprising instructions stored thereon that, when executed by at least one processor (processor 604, FIG. 6), are configured to cause a computing system (e.g., 600, FIG. 6) to perform any of the example methods; and an apparatus (e.g., 600, FIG. 6) including at least one processor (e.g., processor 604, FIG. 6), and at least one memory (e.g., memory 606, FIG. 6) including computer program code, the at least one memory (606) and the computer program code configured to, with the at least one processor (604), cause the apparatus (e.g., 600) at least to perform any of the example methods.

[0105] Further embodiments of the present disclosure include the following examples.

[0106] Example 1.1. A user equipment (UE), comprising: means for determining, by a user equipment (UE) operating at a first bitrate, that a congestion condition exists; means for transmitting, by the UE, a first message to a network apparatus, the first message including an indication that a bit rate is to be lowered; means for receiving, from the network apparatus, a second message indicating a second bitrate; and means for adjusting, by the UE, the first bitrate to the second bitrate for operation.

[0107] Example 1.2. The UE of example 1.1, wherein the determining includes a determination of one or more of the following: cell congestion, cell recovery, or an indication from an application.

[0108] Example 1.3. The UE of any one of examples 1.1 or 1.2, wherein the determining includes monitoring at least one of a buffer status or delay status at lower layers of the UE protocol stack.

[0109] Example 1.4. The UE of example 1.3, wherein upon the size of the buffered data or delay status increasing, the UE determines that the congestion condition exists.

[0110] Example 1.5. The UE of any one of examples 1.1 to 1.4, wherein the determining includes monitoring application related parameters.

[0111] Example 1.6. The UE of example 1.5, wherein the application parameters include one or more of the following: quality of experience (QoE), initial playout delay, average throughput, buffer level, or playout delay for media start-up.

[0112] Example 1.7. The UE of any one of examples 1.1 to 1.6, wherein the determining includes the UE receiving broadcast information.

[0113] Example 1.8. The UE of example 1.7, wherein the UE receives a broadcast of an access class barring in the cell.

[0114] Example 1.9. The UE of any one of examples 1.1 to 1.8, wherein the first message is an uplink (UL) bit rate recommendation query.

[0115] Example 1.10. The UE of example 1.9, wherein the UL bit rate recommendation query includes a first lower bitrate indication indicating at least a first lower bitrate.

[0116] Example 1.11. The UE of example 1.10, wherein the bit rate recommendation includes a second lower bitrate indication indicating a second lower bitrate.

[0117] Example 1.12. The UE of any one of examples 1.1 to 1.11, wherein the second message is a UL bit rate recommendation message.

[0118] Example 1.13. The UE of any one of examples 1.1 to 1.12, further comprising returning, by the UE, to the first bitrate upon the congestion condition no longer existing.

[0119] Example 2.1. An apparatus, comprising: means for determining, by a network apparatus, that a congestion condition exists for a first user equipment (UE) operating at a first bitrate; means for determining, by the network apparatus, a second bitrate; and means for transmitting, by the network apparatus, a first message to at least the first UE, the first message indicating the second bitrate.

[0120] Example 2.2. The apparatus of example 2.1, further comprising means for receiving, by the network apparatus, a second message from the first UE, the second message including an indication that a bit rate is to be lowered.

[0121] Example 2.3. The apparatus of example 2.2, wherein the second bitrate includes a bitrate recommended by the UE in the second message.

[0122] Example 2.4. The apparatus of example 2.2, wherein the network apparatus rejects the bitrate recommended by the UE in the second message.

[0123] Example 2.5. The apparatus of example 2.1, wherein the second bitrate is determined by analyzing one or more of 5QI associated with an interactive service or a qualityof service (QoS) profile configured for a QoS flow.

[0124] Example 2.6. apparatus of any one of example 2.1 to 2.5, further comprising means for upon an existence of multi-modal traffic, transmitting by the network apparatus, the second message to at least a second UE belonging to a same multi-modal service of the first UE.

[0125] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[0126] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[0127] In various embodiments, the terms “first message” and “second message”, as well as any subsequent messages may refer to any messages that are transmitted or received in an order and are not necessarily limited to any particular message.

[0128] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B) .” A phrase in 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) ”

[0129] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta-languages. No distinction is made between languages which are interpreted, compiled, or use both compiledand interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[0130] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

WHAT IS CLAIMED IS:

1. A method, comprising: determining, by a user equipment (UE) operating at a first bitrate, that a congestion condition exists; transmitting, by the UE, a first message to a network apparatus, the first message including an indication that a bit rate is to be lowered; receiving, from the network apparatus, a second message indicating a second bitrate; and adjusting, by the UE, the first bitrate to the second bitrate for operation.

2. The method of claim 1, wherein the determining includes a determination of one or more of the following: cell congestion, cell recovery, or an indication from an application.

3. The method of any one of claims 1 or 2, wherein the determining includes monitoring at least one of a buffer status or delay status at lower layers of the UE protocol stack.

4. The method of claim 3, wherein upon the size of the buffered data or delay status increasing, the UE determines that the congestion condition exists.

5. The method of any one of claims 1 to 4, wherein the determining includes monitoring application related parameters.

6. The method of claim 5, wherein the application parameters include one or more of the following: quality of experience (QoE), initial playout delay, average throughput, buffer level, or playout delay for media start-up.

7. The method of any one of claims 1 to 6, wherein the determining includes the UE receiving broadcast information.

8. The method of claim 7, wherein the UE receives a broadcast of an access class barring in the cell.

9. The method of any one of claims 1 to 8, wherein the first message is an uplink (UL) bit rate recommendation query.

10. The method of claim 9, wherein the UL bit rate recommendation query includes a first lower bitrate indication indicating at least a first lower bitrate.

11. The method of claim 10, wherein the bit rate recommendation includes a second lower bitrate indication indicating a second lower bitrate.

12. The method of any one of claims 1 to 11, wherein the second message is a UL bit rate recommendation message.

13. The method of any one of claims 1 to 12, further comprising returning, by the UE, to the first bitrate upon the congestion condition no longer existing.

14. A method, comprising: determining, by a network apparatus, that a congestion condition exists for a first user equipment (UE) operating at a first bitrate; determining, by the network apparatus, a second bitrate; and transmitting, by the network apparatus, a first message to at least the first UE, the first message indicating the second bitrate.

15. The method of claim 14, further comprising receiving, by the network apparatus, a second message from the first UE, the second message including an indication that a bit rate is to be lowered.

16. The method of claim 15, wherein the second bitrate includes a bitrate recommended by the UE in the second message.

17. The method of claim 15, wherein the network apparatus rejects the bitrate recommended by the UE in the second message.

18. The method of claim 14, wherein the second bitrate is determined by analyzing one or more of 5QI associated with an interactive service or a quality of service (QoS) profile configured for a QoS flow.

19. The method of any one of claims 14 to 18, further comprising upon an existence of multi-modal traffic, transmitting by the network apparatus, the second message to at least a second UE belonging to a same multi-modal service of the first UE.

20. A user equipment (UE), comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the UE at least to perform a method as in any one of claims 1 to 13.

21. A network apparatus, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the network apparatus at least to perform a method as in any one of claims 14 to 19.

22. A processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform a method as in any one of claims 1 to 19.

Images