Quality of experience reporting during network overload
By pausing and restoring QoE reports in the UE RRC layer of the UE, the data loss problem during network overload is solved, and the stability and user experience of the wireless communication system are improved.
Patent Information
- Application Number
- CN202280095016.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-24
- Publication Date
- 2024-12-03
AI Technical Summary
In wireless communication systems, when the network is overloaded, it is difficult for user equipment (UE) to effectively manage quality of experience (QoE) reports, resulting in data loss and service interruption.
In the UE RRC layer of the UE, the QoE report is paused based on the network overload condition, and the data is buffered during the pause, and the buffered data is sent when the network is restored to ensure that the data is not lost.
Effectively manage QoE reports during network overload, avoid data loss, and improve service stability and user experience.
Smart Images

Figure CN119072950A_ABST
Abstract
Description
Technical Field
[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for quality of experience reporting during network overload. Background Art
[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
[0003] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.
[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) on the downlink (CP-OFDM), using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) on the uplink (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)), and supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the invention
[0005] In some specific implementations, an apparatus for wireless communication at a user equipment (UE) includes: a memory; and one or more processors coupled to the memory, the one or more processors configured to: determine, by a UE radio resource control (RRC) layer of the UE, to suspend quality of experience (QoE) reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the UE; receive, at the UE RRC layer, from a UE application layer of the UE, an attention command indicating a QoE measurement session stop indication for the QoE configuration; and send the buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the UE.
[0006] In some specific implementations, a method of wireless communication performed by a UE includes: determining, by a UE RRC layer of the UE, to suspend QoE reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the UE; receiving, at the UE RRC layer, an attention command indicating a stop indication of a QoE measurement session for the QoE configuration from a UE application layer of the UE; and sending the buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the UE.
[0007] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: determine, by a UE RRC layer of the UE, to suspend QoE reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the UE; receive, at the UE RRC layer, from a UE application layer of the UE, an attention command indicating a stop indication of a QoE measurement session for the QoE configuration; and send the buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the UE.
[0008] In some specific implementations, an apparatus for wireless communication includes: a component for determining, by a device RRC layer of the apparatus, to suspend QoE reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the apparatus; a component for receiving, at the device RRC layer, an attention command indicating a QoE measurement session stop indication for the QoE configuration from a device application layer of the apparatus; and a component for sending the buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the apparatus.
[0009] The various aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.
[0010] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.
[0011] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The devices incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be implemented in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0013] FIG. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
[0014] FIG. 2 is a diagram illustrating an example in which a base station communicates with a user equipment (UE) in a wireless network according to the present disclosure.
[0015] FIG. 3 is a diagram illustrating an example of a decomposed base station architecture according to the present disclosure.
[0016] 4 to 5 are diagrams illustrating examples of Quality of Experience (QoE) reporting according to the present disclosure.
[0017] 6 to 8 are diagrams illustrating examples associated with QoE reporting during network overload according to the present disclosure.
[0018] 9 is a diagram illustrating an example process associated with QoE reporting during network overload according to the present disclosure.
[0019] 10 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION
[0020] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.
[0021] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0022] Although various aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).
[0023] 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. Base stations 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, and / or transmit receive points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.
[0024] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. 1, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.
[0025] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to one device configured to perform one or more functions, such as those described herein in conjunction with base station 110. In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.
[0026] In some examples, the cells may not necessarily be stationary, and the geographic area of the cells may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).
[0027] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. In the example shown in FIG. 1 , a BS 110d (e.g., a relay base station) may communicate with a BS 110a (e.g., a macro base station) and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A base station 110 that relays communications may be referred to as a relay station, a relay base station, a relay, etc.
[0028] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).
[0029] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.
[0030] UE 120 may be distributed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.
[0031] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0032] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0033] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.
[0034] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).
[0035] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.
[0036] In view of the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0037] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: determine, by a UE radio resource control (RRC) layer of the UE, to suspend quality of experience (QoE) reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the UE; receive an attention command indicating a QoE measurement session stop indication for the QoE configuration from a UE application layer of the UE at the UE RRC layer; and send the buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the UE. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0038] As indicated above, Figure 1 is provided as an example. Other examples may differ from what is described with respect to Figure 1 .
[0039] 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).
[0040] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).
[0041] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.
[0042] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.
[0043] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as, for example, one or more components of FIG. 2).
[0044] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280 ) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to FIGS. 6-10 ).
[0045] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of an antenna 234, a modem 232, a MIMO detector 236, a receive processor 238, a transmit processor 220, and / or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and a memory 242 to perform aspects of any of the methods described herein (e.g., with reference to FIGS. 6-10 ).
[0046] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, and / or any other component of FIG. 2 may perform one or more techniques associated with QoE reporting during network overload, as described in more detail elsewhere herein. For example, controller / processor 240 of base station 110, controller / processor 280 of UE 120, and / or any other component of FIG. 2 may perform or direct the operation of, for example, process 900 of FIG. 9 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after being compiled, converted, and / or interpreted) by one or more processors of base station 110 and / or UE 120, may cause one or more processors, UE 120, and / or base station 110 to perform or direct operations such as process 900 of FIG. 9 and / or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.
[0047] In some aspects, a UE (e.g., UE 120) includes: means for determining, by a UE radio resource control (RRC) layer of the UE, to suspend quality of experience (QoE) reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the UE; means for receiving, at the UE RRC layer, from a UE application layer of the UE an attention command indicating a QoE measurement session stop indication for the QoE configuration; and / or means for sending the buffered QoE data without discarding the buffered QoE data stored at the UE based at least in part on the attention command. Means for the UE to perform operations described herein may include, for example, one or more of the following: communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.
[0048] Although the blocks in FIG2 are illustrated as distinct components, the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0049] As indicated above, FIG2 is provided as an example. Other examples may differ from what is described with respect to FIG2.
[0050] FIG. 3 is a diagram illustrating an example 300 of a disaggregated base station architecture according to the present disclosure.
[0051] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station (BS, e.g., base station 110) or one or more units (or one or more components) performing base station functions can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NR BS, a 5GNB, an access point (AP), a TRP, a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone BS or a monolithic BS) or a decomposed base station.
[0052] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, namely a virtual centralized unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0053] Base station type operations or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an IAB network, an O-RAN (such as a network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0054] The decomposed base station architecture shown in FIG3 may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed base station units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.
[0055] Each of these units (e.g., CU 310, DU 330, RU 340), as well as near-RT RIC 325, non-RTRIC 315, and SMO framework 305 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.
[0056] In some aspects, the CU 310 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.
[0057] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as that defined by 3GPP. In some aspects, the DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.
[0058] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).
[0059] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .
[0060] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.
[0061] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).
[0062] As indicated above, FIG3 is provided as an example. Other examples may differ from what is described with respect to FIG3.
[0063] FIG4 is a diagram illustrating an example 400 of QoE reporting according to the present disclosure. As shown in FIG4, example 400 includes communications between a UE (e.g., UE 120), a network entity (e.g., base station 110), and a QoE server. In some aspects, the UE, the network entity, and the QoE server may be included in a wireless network (such as wireless network 100).
[0064] The UE may be configured with a QoE configuration (e.g., a QoE measurement configuration) using an RRC reconfiguration, which may indicate a measurement configuration application layer (measConfigAppLayer) message. The UE may send a QoE report indicating a QoE measurement using a measurement report application layer (measReportAppLayer) message. The QoE report may be sent via signaling radio bearer 4 (SRB4).
[0065] As shown in reference numeral 402, the QoE server may send a QoE configuration to a network entity. As shown in reference numeral 404, the network entity may send an RRC reconfiguration to a UE RRC layer of the UE. The RRC reconfiguration may indicate a measConfigAppLayer message, which may indicate a QoE configuration and a service type. The service type may be a multimedia telephony service (MTSI), streaming, or multicast broadcast multicast service (MBMS) for an Internet Protocol (IP) Multimedia Subsystem (IMS). The UE RRC layer may receive the RRC reconfiguration when the UE is in an RRC connected state and SRB4 is configured. As shown in reference numeral 406, the UE RRC layer may send an attention (AT) command for initiating QoE measurement collection (QMC) to the UE application layer of the UE. The UE application may perform QMC based at least in part on the attention command. As shown in reference numeral 408, the UE application layer may send a QoE measurement for each service type to the UE RRC layer, wherein the QoE measurement may be based at least in part on the QMC. As shown by reference numeral 410, the UE RRC layer may send a measReportAppLayer message to a network entity via RRC signaling. The measReportAppLayer message may indicate a QoE report and a service type, wherein the QoE report may indicate a QoE measurement associated with the service type. As shown by reference numeral 412, the network entity may send a QoE report to a QoE server.
[0066] As indicated above, FIG4 is provided as an example. Other examples may differ from what is described with respect to FIG4.
[0067] FIG5 is a diagram illustrating an example 500 of QoE reporting according to the present disclosure. As shown in FIG5, example 500 includes communications between a UE (e.g., UE 120), a network entity (e.g., a next generation radio access network (NG-RAN), which may include base station 110), and an operation, administration, and maintenance (OAM) server. In some aspects, the UE, the network entity, and the OAM server may be included in a wireless network (such as wireless network 100).
[0068] The UE may indicate a QoE measurement session start / end indication to the network entity via a marker. The UE may send a QoE measurement session start / end indication via SRB4. The network entity may configure the UE with an associated minimization of drive tests (MDT) configuration after receiving a QoE measurement session start indication from the UE. The network entity may deactivate the associated MDT configuration after receiving a QoE measurement session end indication from the UE. The QoE measurement session end indication may be referred to as a QoE measurement session stop indication. When the network entity receives a QoE stop indication for a QoE configuration, the network entity may release the QoE configuration when the UE moves outside a specific area. Otherwise, the network entity may not release the QoE configuration.
[0069] As shown by reference numeral 502, the OAM may send an MDT configuration that may indicate a first tracking reference to the network entity. As shown by reference numeral 504, the OAM may send a first QoE configuration and a second QoE configuration to the network entity, wherein the first QoE configuration may be used for the first QoE reference and the first tracking reference, and the second QoE configuration may be used for the second QoE reference. As shown by reference numeral 506, the network entity may send the first QoE configuration and the second QoE configuration to a UE RRC layer of the UE, wherein the first QoE configuration may be used for the first QoE reference, and the second QoE configuration may be used for the second QoE reference. As shown by reference numeral 508, the UE RRC layer may send an attention command indicating the first QoE configuration and the second QoE configuration to a UE application layer of the UE, wherein the first QoE configuration may be used for the first QoE reference, and the second QoE configuration may be used for the second QoE reference.
[0070] As shown in reference numeral 510, the UE application layer may send an attention command indicating a first QoE report and a second QoE report to the UE RRC layer. The first QoE report may indicate a session start / end indication for a first QoE reference. The second QoE report may indicate a session start / end indication for a second QoE reference. As shown in reference numeral 512, the UE RRC layer may send an RRC message indicating the first QoE report and the second QoE report to the network entity. The first QoE report may indicate a session start / end indication for the first QoE reference. The second QoE report may indicate a session start / end indication for the second QoE reference. As shown in reference numeral 514, the network entity may send a first QoE report indicating the first QoE reference and a second QoE report indicating the second QoE reference to the OAM.
[0071] As indicated above, FIG5 is provided as an example. Other examples may differ from what is described with respect to FIG5.
[0072] QoE reporting may be suspended due to RAN overload. For example, when traffic at a network entity (e.g., NG-RAN, which may include a base station) meets a threshold, QoE reporting may be suspended. During the suspension, QoE data may be buffered at the UE, and QoE reports may not be sent immediately to the network entity. When the network entity resumes QoE reporting (e.g., after traffic does not meet the threshold), the UE may send the buffered QoE data to the network entity.
[0073] When QoE reporting is suspended due to RAN overload, the UE may buffer QoE data. During the suspension, when the UE RRC layer of the UE receives a QoE measurement session stop indication for the QoE configuration from the UE application layer of the UE, the UE RRC layer may send a QoE measurement session stop indication to the network entity. When the network entity receives the QoE measurement session stop indication from the UE RRC layer, and when the UE moves outside a specific area (e.g., moves outside the area range), the network entity may release the associated QoE configuration. The UE may receive a release command for the QoE configuration from the network entity, which may be based at least in part on the network entity releasing the QoE configuration. When the UE RRC layer receives the release command for the QoE configuration, the UE may discard the buffered QoE data, which may cause the buffered QoE data to be lost and not be sent to the network entity later after the RAN overload has ended.
[0074] In various aspects of the techniques and apparatus described herein, a UE may determine, by a UE RRC layer of the UE, that QoE reporting may be suspended based at least in part on network overload. When QoE reporting is suspended, buffered QoE data for a QoE configuration may be stored at the UE. The UE may receive an attention command at the UE RRC layer from a UE application layer of the UE indicating a stop indication of a QoE measurement session for the QoE configuration. The UE may send buffered QoE data from the UE RRC layer to a network entity based at least in part on the attention command without discarding the buffered QoE data stored at the UE.
[0075] In some aspects, after the UE RRC layer receives a QoE measurement session stop indication for the QoE configuration from the UE application layer, the UE RRC layer may resume transmitting buffered QoE data. In some aspects, the UE RRC layer may send a QoE measurement session stop indication to the network entity, which may include a buffered QoE data indication. The buffered QoE data indication may indicate that the buffered QoE data is stored at the UE. The network entity may resume QoE reporting before releasing the QoE configuration based at least in part on the buffered QoE data indication. In some aspects, when the QoE reporting is suspended, the UE RRC layer may suspend sending the QoE measurement session stop indication to the network entity. In some aspects, the UE RRC layer may send buffered QoE data after receiving a release command from the network entity, wherein the release command may release the QoE configuration. Therefore, the buffered QoE data may not be discarded at the UE and may be sent to the network entity.
[0076] FIG6 is a diagram illustrating an example 600 associated with QoE reporting during network overload according to the present disclosure. As shown in FIG6, example 600 includes communications between a UE (e.g., UE 120) and a network entity (e.g., NG-RAN, which may include base station 110). In some aspects, the UE and the network entity may be included in a wireless network (such as wireless network 100).
[0077] As indicated by reference numeral 602, a UE RRC layer of a UE may determine to suspend QoE reporting (e.g., due to RAN overload), during which buffered QoE data may be stored at the UE. For example, the UE may store buffered QoE data associated with a QoE configuration (e.g., a first QoE configuration). As indicated by reference numeral 604, a network entity may send an RRC message to the UE RRC layer indicating a first QoE configuration and a second QoE configuration, wherein the first QoE configuration may be used for a first QoE reference, and the second QoE configuration may be used for a second QoE reference. As indicated by reference numeral 606, the UE RRC layer may send an attention command to a UE application layer of the UE indicating the first QoE configuration and the second QoE configuration.
[0078] As shown by reference numeral 608, the UE application layer may send an attention command to the UE RRC layer indicating a QoE measurement session stop indication for the first QoE configuration. The UE RRC layer may receive an attention command indicating a QoE measurement session stop indication for the first QoE configuration. As shown by reference numeral 610, the UE RRC layer may resume transmitting buffered QoE data based at least in part on the QoE measurement session stop indication. As shown by reference numeral 612, the UE RRC layer may send an RRC message to the network entity, wherein the RRC message may indicate a first QoE report. The first QoE report may correspond to the first QoE configuration, and the first QoE report may indicate buffered QoE data. As shown by reference numeral 614, the UE RRC layer may send an RRC message indicating a QoE measurement session stop indication to the network entity. When the buffered QoE data (e.g., all buffered QoE data) is successfully sent to the network entity, the UE RRC layer may send an RRC message with a QoE measurement session stop indication. The UE RRC layer may send a QoE measurement session stop indication together with the last QoE report. In some aspects, the UE RRC layer may resume sending buffered QoE data based at least in part on receiving a QoE measurement session stop indication for one QoE configuration (e.g., the first QoE configuration) from the UE application layer.
[0079] In some aspects, the UE may receive an attention command indicating a QoE measurement session stop indication for a QoE configuration from a UE application layer of the UE at a UE RRC layer. The UE may send buffered QoE data from the UE RRC layer to a network entity based at least in part on the attention command without discarding the buffered QoE data stored at the UE. In some aspects, the UE may determine by the UE RRC layer to resume sending the buffered QoE data based at least in part on the attention command indicating a QoE measurement session stop indication for the QoE configuration. The UE may send a first RRC message from the UE RRC layer to the network entity, the first RRC message including a QoE report with buffered QoE data. The UE may send a second RRC message from the UE RRC layer to the network entity, the second RRC message including a QoE measurement session stop indication for indicating that the buffered QoE data has been successfully sent to the network entity. The second RRC message including the QoE measurement session stop indication may be optional because the first RRC message including the QoE report with buffered QoE data may imply the QoE measurement session stop indication. In some cases, a QoE measurement session stop indication may be transmitted along with the QoE report with the buffered QoE data.
[0080] As indicated above, FIG6 is provided as an example. Other examples may differ from what is described with respect to FIG6.
[0081] FIG7 is a diagram illustrating an example 700 associated with QoE reporting during network overload according to the present disclosure. As shown in FIG7, example 700 includes communications between a UE (e.g., UE 120) and a network entity (e.g., NG-RAN, which may include base station 110). In some aspects, the UE and the network entity may be included in a wireless network (such as wireless network 100).
[0082] As indicated by reference numeral 702, a UE RRC layer of a UE may determine to suspend QoE reporting (e.g., due to RAN overload), during which buffered QoE data may be stored at the UE. For example, the UE may store buffered QoE data associated with a QoE configuration (e.g., a first QoE configuration). As indicated by reference numeral 704, a network entity may send an RRC message to the UE RRC layer indicating a first QoE configuration and a second QoE configuration, wherein the first QoE configuration may be used for a first QoE reference, and the second QoE configuration may be used for a second QoE reference. As indicated by reference numeral 706, the UE RRC layer may send an attention command to a UE application layer of the UE indicating the first QoE configuration and the second QoE configuration.
[0083] As shown by reference numeral 708, the UE application layer may send an attention command indicating a QoE measurement session stop indication for the first QoE configuration to the UE RRC layer. The UE RRC layer may receive an attention command indicating a QoE measurement session stop indication for the first QoE configuration. As shown by reference numeral 710, the UE RRC layer may send an RRC message to the network entity. The RRC message may indicate a QoE measurement session stop indication and a buffered QoE data indication. The QoE measurement session stop indication may be for the first QoE configuration and may indicate whether buffered QoE data is available for the first QoE configuration.
[0084] As indicated by reference numeral 712, the network entity may process an RRC message received from the UE RRC layer. When the RRC message includes a QoE measurement session stop indication and a buffered QoE data indication, the network entity may send a resume command to the UE RRC layer, and the UE RRC layer may resume sending buffered QoE data to the network entity. When the RRC message includes a QoE measurement session stop indication but does not include a buffered QoE data indication, the network entity may release the first QoE configuration when the UE moves outside a specific area (e.g., outside the area range). In some aspects, the UE RRC layer may send a QoE measurement session stop indication and a buffered QoE data indication, which may enable the network entity to operate accordingly.
[0085] In some aspects, the UE may receive an attention command indicating a QoE measurement session stop indication for a QoE configuration from a UE application layer of the UE at a UE RRC layer. The UE may send buffered QoE data from the UE RRC layer to a network entity based at least in part on the attention command without discarding the buffered QoE data stored at the UE. In some aspects, the UE may send a first RRC message from the UE RRC layer to the network entity based at least in part on the attention command indicating a QoE measurement session stop indication for the QoE configuration, the first RRC message indicating a QoE measurement session stop indication for the QoE configuration and / or a buffered QoE data indication indicating whether the buffered QoE data is available for the QoE configuration. The UE may receive a second RRC message including a release command to release the QoE configuration from the network entity at the UE RRC layer based at least in part on the first RRC message indicating a QoE measurement session stop indication for the QoE configuration without indicating a buffered QoE data indication. Alternatively, the UE may receive a second RRC message indicating a resumption command from the network entity at the UE RRC layer based at least in part on a first RRC message indicating a QoE measurement session stop indication and a buffered QoE data indication for QoE configuration, wherein sending of the buffered QoE data from the UE RRC layer to the network entity may be resumed based at least in part on the resumption command.
[0086] In some aspects, when QoE reporting is suspended (e.g., due to RAN overload), the UE RRC layer may suspend sending QoE measurement session stop indications to the network entity. When QoE reporting is resumed (e.g., due to RAN no longer being overloaded), the UE RRC layer may resume sending QoE measurement session stop indications to the network entity. When QoE reporting is suspended, the UE may be configured by the network entity whether to suspend sending QoE measurement session stop indications. When QoE reporting is suspended, if the UE RRC layer receives multiple QoE measurement session start / stop indications (e.g., multiple QoE session state indications) from the UE application layer, the UE RRC layer may overwrite the previously received QoE measurement session start / stop indication with the most recently received QoE measurement session start / stop indication, and when QoE reporting is resumed, the UE RRC layer may send the most recently received QoE measurement session start / stop indication to the network entity.
[0087] In some aspects, the UE may determine, by the UE RRC layer, to suspend sending an RRC message including a QoE measurement session stop indication for a QoE configuration based at least in part on suspending QoE reporting. The UE may send an RRC message including a QoE measurement session stop indication for a QoE configuration from the UE RRC layer to a network entity based at least in part on resuming QoE reporting. In some aspects, the UE may receive a configuration from the network entity at the UE RRC layer, which configures the UE RRC layer to suspend sending an RRC message including a QoE measurement session stop indication for a QoE configuration based at least in part on suspending QoE reporting. In some aspects, the UE may receive multiple QoE measurement session indications for a QoE configuration from the UE application layer at the UE RRC layer during the suspension of sending the RRC message. The UE may overwrite a previously received QoE measurement session indication in the multiple QoE measurement session indications with a newly received QoE measurement session indication in the multiple QoE measurement session indications by the UE RRC layer.
[0088] As indicated above, FIG7 is provided as an example. Other examples may differ from what is described with respect to FIG7.
[0089] FIG8 is a diagram illustrating an example 800 associated with QoE reporting during network overload according to the present disclosure. As shown in FIG8, example 800 includes communications between a UE (e.g., UE 120) and a network entity (e.g., NG-RAN, which may include base station 110). In some aspects, the UE and the network entity may be included in a wireless network (such as wireless network 100).
[0090] As indicated by reference numeral 802, a UE RRC layer of a UE may determine to suspend QoE reporting (e.g., due to RAN overload), during which buffered QoE data may be stored at the UE. For example, the UE may store buffered QoE data associated with a QoE configuration (e.g., a first QoE configuration). As indicated by reference numeral 804, a network entity may send an RRC message to the UE RRC layer indicating a first QoE configuration and a second QoE configuration, wherein the first QoE configuration may be used for a first QoE reference, and the second QoE configuration may be used for a second QoE reference. As indicated by reference numeral 806, the UE RRC layer may send an attention command to a UE application layer of the UE indicating the first QoE configuration and the second QoE configuration.
[0091] As indicated by reference numeral 808, the UE application layer may send an attention command indicating a QoE measurement session stop indication for the first QoE configuration to the UE RRC layer. The UE RRC layer may receive an attention command indicating a QoE measurement session stop indication for the first QoE configuration. As indicated by reference numeral 810, the UE RRC layer may send an RRC message to the network entity. The RRC message may indicate a QoE measurement session stop indication for the first QoE configuration.
[0092] As shown by reference numeral 812, the network entity may detect that the UE has moved outside a specific area (e.g., outside the area range). In this case, the network entity may release the first QoE configuration. As shown by reference numeral 814, the network entity may send an RRC message indicating a release command for releasing the first QoE configuration to the UE RRC layer. In other words, the network entity may indicate that the first QoE configuration should be released based at least in part on the UE moving outside the specific area. The RRC message may also indicate whether the UE RRC layer should send buffered QoE data for the first QoE configuration. As shown by reference numeral 816, the UE RRC layer may send buffered QoE data for the first QoE configuration to the network entity, which may be based at least in part on the UE RRC layer receiving the RRC message from the network entity. In other words, the UE RRC layer may send buffered QoE data after receiving the release command from the network entity. After the UE RRC layer sends the buffered QoE data (eg, all buffered QoE data) for the first QoE configuration, the UE RRC layer may indicate to the network entity that the QoE data is no longer buffered at the UE, and the UE and the network entity may release the first QoE configuration.
[0093] In some aspects, the UE may receive an attention command indicating a QoE measurement session stop indication for a QoE configuration from a UE application layer of the UE at a UE RRC layer. The UE may send buffered QoE data from the UE RRC layer to a network entity based at least in part on the attention command without discarding the buffered QoE data stored at the UE. In some aspects, the UE may send a first RRC message from the UE RRC layer to the network entity based at least in part on the attention command indicating a QoE measurement session stop indication for the QoE configuration, the first RRC message indicating a QoE measurement session stop indication for the QoE configuration. In some aspects, the UE may receive a first RRC message from the network entity at a UE RRC layer, the first RRC message including a release command to release the QoE configuration based at least in part on the UE moving outside a specific area, wherein the first RRC message may include an indication to send buffered QoE data for the QoE configuration. The UE may send, based at least in part on the first RRC message, a second RRC message from the UE RRC layer to the network entity, the second RRC message including a QoE report having buffered QoE data for the QoE configuration. In some aspects, the UE may send, from the UE RRC layer to the network entity, an indication that all buffered QoE data for the QoE configuration has been sent to the network entity, wherein the UE and the network entity may release the QoE configuration based at least in part on the indication.
[0094] As indicated above, FIG8 is provided as an example. Other examples may differ from what is described with respect to FIG8.
[0095] 9 is a diagram illustrating an example process 900, performed, for example, by a UE, in accordance with the present disclosure. Example process 900 is an example in which a UE (eg, UE 120) performs operations associated with QoE reporting during network overload.
[0096] As shown in FIG9, in some aspects, process 900 may include determining, by a UE RRC layer of the UE, to suspend QoE reporting based at least in part on network overload, wherein when QoE reporting is suspended, buffered QoE data for the QoE configuration is stored at the UE (block 910). For example, the UE (e.g., using the communications manager 140 and / or processing component 1008 depicted in FIG10) may determine, by a UE RRC layer of the UE, to suspend QoE reporting based at least in part on network overload, wherein when QoE reporting is suspended, buffered QoE data for the QoE configuration is stored at the UE, as described above.
[0097] As further shown in FIG9, in some aspects, process 900 may include receiving, at the UE RRC layer, an attention command from a UE application layer of the UE indicating a stop indication of a QoE measurement session for a QoE configuration (block 920). For example, the UE (e.g., using the communication manager 140 and / or the processing component 1008 depicted in FIG10) may receive, at the UE RRC layer, an attention command from a UE application layer of the UE indicating a stop indication of a QoE measurement session for a QoE configuration, as described above.
[0098] As further shown in FIG9, in some aspects, process 900 may include sending buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the UE (block 930). For example, the UE (e.g., using the communication manager 140 and / or the sending component 1004 depicted in FIG10) may send the buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the UE, as described above.
[0099] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0100] In a first aspect, process 900 includes: determining, by a UE RRC layer, to resume sending buffered QoE data based at least in part on an attention command indicating a QoE measurement session stop indication for a QoE configuration; sending a first RRC message from the UE RRC layer to a network entity, the first RRC message including a QoE report with buffered QoE data; and sending a second RRC message from the UE RRC layer to the network entity, the second RRC message including a QoE measurement session stop indication indicating that the buffered QoE data has been successfully sent to the network entity.
[0101] In a second aspect, alone or in combination with the first aspect, process 900 includes: at least in part based on an attention command indicating a QoE measurement session stop indication for the QoE configuration, sending a first RRC message from the UE RRC layer to a network entity, the first RRC message indicating one or more of the following: a QoE measurement session stop indication for the QoE configuration, or a buffered QoE data indication indicating whether buffered QoE data can be used for the QoE configuration.
[0102] In a third aspect, alone or in combination with one or more of the first and second aspects, process 900 includes: receiving, at the UE RRC layer from a network entity, a second RRC message including a release command to release the QoE configuration based at least in part on a first RRC message indicating a QoE measurement session stop indication for the QoE configuration but not indicating a buffered QoE data indication.
[0103] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 900 includes: receiving, at the UE RRC layer, a second RRC message indicating a resume command from a network entity based at least in part on a first RRC message indicating a QoE measurement session stop indication and a buffered QoE data indication for a QoE configuration, wherein sending buffered QoE data from the UE RRC layer to the network entity is resumed based at least in part on the resume command.
[0104] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 900 includes: determining, by the UE RRC layer, to suspend sending an RRC message including a QoE measurement session stop indication for a QoE configuration based at least in part on suspending QoE reporting; and sending an RRC message including a QoE measurement session stop indication for a QoE configuration from the UE RRC layer to a network entity based at least in part on resuming QoE reporting.
[0105] In a sixth aspect, alone or in combination with one or more of aspects 1 to 5, process 900 includes: receiving a configuration from a network entity at a UE RRC layer, the configuration configuring the UE RRC layer to suspend sending an RRC message including a QoE measurement session stop indication for a QoE configuration based at least in part on suspending QoE reporting.
[0106] In a seventh aspect, alone or in combination with one or more of aspects 1 to 6, process 900 includes: receiving, at the UE RRC layer, a plurality of QoE measurement session indications for QoE configuration from a UE application layer during suspension of sending RRC messages; and overwriting, by the UE RRC layer, a previously received QoE measurement session indication in the plurality of QoE measurement session indications with a newly received QoE measurement session indication in the plurality of QoE measurement session indications.
[0107] In an eighth aspect, alone or in combination with one or more of aspects 1 to 7, process 900 includes: sending a first RRC message from a UE RRC layer to a network entity based at least in part on an attention command indicating a QoE measurement session stop indication for a QoE configuration, the first RRC message indicating a QoE measurement session stop indication for a QoE configuration.
[0108] In a ninth aspect, alone or in combination with one or more of aspects 1 to 8, process 900 includes: receiving, at a UE RRC layer, a first RRC message from a network entity, the first RRC message including a release command for releasing a QoE configuration based at least in part on the UE moving outside a specific area, wherein the first RRC message includes an indication of sending buffered QoE data for the QoE configuration; and sending, based at least in part on the first RRC message, a second RRC message from the UE RRC layer to the network entity, the second RRC message including a QoE report having buffered QoE data for the QoE configuration.
[0109] In a tenth aspect, either alone or in combination with one or more of aspects 1 to 9, process 900 includes sending an indication from a UE RRC layer to a network entity that all buffered QoE data for a QoE configuration has been sent to the network entity, wherein the UE and the network entity release the QoE configuration based at least in part on the indication.
[0110] Although Figure 9 shows example blocks of process 900, in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in Figure 9. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.
[0111] FIG. 10 is a diagram of an example apparatus 1000 for wireless communication. Apparatus 1000 may be a UE, or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 140. Communication manager 140 may include processing component 1008, etc.
[0112] In some aspects, the device 1000 may be configured to perform one or more operations described herein in conjunction with Figures 6 to 8. Additionally or alternatively, the device 1000 may be configured to perform one or more processes described herein, such as process 900 of Figure 9. In some aspects, the device 1000 and / or one or more components shown in Figure 10 may include one or more components of the UE described in conjunction with Figure 2. Additionally or alternatively, one or more components shown in Figure 10 may be implemented within one or more components described in conjunction with Figure 2. Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.
[0113] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on the received communications and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the UE described in conjunction with FIG. 2.
[0114] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications, and the generated communications may be provided to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications, and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the UE described in conjunction with FIG. 2. In some aspects, the transmitting component 1004 may be co-located with the receiving component 1002 in a transceiver.
[0115] The processing component 1008 may determine to suspend QoE reporting based at least in part on network overload, wherein when QoE reporting is suspended, buffered QoE data for the QoE configuration is stored at the UE. The processing component 1008 may receive an attention command indicating a QoE measurement session stop indication for the QoE configuration from a UE application layer of the UE at the UE RRC layer. The sending component 1004 may send the buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the UE.
[0116] The processing component 1008 may determine to resume sending the buffered QoE data based at least in part on the attention command indicating a QoE measurement session stop indication for the QoE configuration. The sending component 1004 may send a first RRC message from the UE RRC layer to the network entity, the first RRC message including a QoE report with the buffered QoE data. The sending component 1004 may send a second RRC message from the UE RRC layer to the network entity, the second RRC message including a QoE measurement session stop indication indicating that the buffered QoE data has been successfully sent to the network entity.
[0117] The sending component 1004 can send a first RRC message from the UE RRC layer to the network entity based at least in part on the attention command indicating the QoE measurement session stop indication for the QoE configuration, the first RRC message indicating one or more of the following: a QoE measurement session stop indication for the QoE configuration, or a buffered QoE data indication indicating whether the buffered QoE data can be used for the QoE configuration.
[0118] The receiving component 1002 may receive, at the UE RRC layer, from the network entity a second RRC message including a release command to release the QoE configuration based at least in part on the first RRC message indicating a QoE measurement session stop indication for the QoE configuration but not indicating a buffered QoE data indication. The receiving component 1002 may receive, at the UE RRC layer, from the network entity a second RRC message indicating a resume command based at least in part on the first RRC message indicating a QoE measurement session stop indication for the QoE configuration and a buffered QoE data indication, wherein the sending of the buffered QoE data from the UE RRC layer to the network entity is resumed based at least in part on the resume command.
[0119] The processing component 1008 can determine to suspend sending the RRC message including the QoE measurement session stop indication for the QoE configuration based at least in part on suspending the QoE reporting. The sending component 1004 can send the RRC message including the QoE measurement session stop indication for the QoE configuration from the UE RRC layer to the network entity based at least in part on resuming the QoE reporting.
[0120] The receiving component 1002 may receive a configuration from a network entity at a UE RRC layer, the configuration configuring the UE RRC layer to suspend sending an RRC message including a QoE measurement session stop indication for a QoE configuration based at least in part on suspending QoE reporting. The processing component 1008 may receive a plurality of QoE measurement session indications for a QoE configuration from a UE application layer at the UE RRC layer during the suspension of sending the RRC message. The processing component 1008 may overwrite a previously received QoE measurement session indication in the plurality of QoE measurement session indications with a newly received QoE measurement session indication in the plurality of QoE measurement session indications.
[0121] The sending component 1004 may send a first RRC message from the UE RRC layer to the network entity based at least in part on an attention command indicating a QoE measurement session stop indication for the QoE configuration. The receiving component 1002 may receive a first RRC message from the network entity at the UE RRC layer, the first RRC message including a release command to release the QoE configuration based at least in part on the UE moving outside a specific area, wherein the first RRC message includes an indication to send buffered QoE data for the QoE configuration. The sending component 1004 may send a second RRC message from the UE RRC layer to the network entity based at least in part on the first RRC message, the second RRC message including a QoE report with buffered QoE data for the QoE configuration. The sending component 1004 may send an indication from the UE RRC layer to the network entity that all buffered QoE data for the QoE configuration has been sent to the network entity, wherein the UE and the network entity release the QoE configuration based at least in part on the indication.
[0122] The number and arrangement of the components shown in Figure 10 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than the components shown in Figure 10. In addition, two or more components shown in Figure 10 may be implemented within a single component, or a single component shown in Figure 10 may be implemented as multiple distributed components. Additionally or alternatively, a component set (one or more components) shown in Figure 10 may perform one or more functions described as being performed by another component set shown in Figure 10.
[0123] The following provides an overview of some aspects of the disclosure:
[0124] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: determining, by a UE radio resource control (RRC) layer of the UE, to suspend quality of experience (QoE) reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the UE; receiving, at the UE RRC layer, an attention command indicating a QoE measurement session stop indication for the QoE configuration from a UE application layer of the UE; and sending the buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the UE.
[0125] Aspect 2: The method according to Aspect 1 also includes: determining by the UE RRC layer to resume sending the buffered QoE data at least partially based on the attention command indicating the QoE measurement session stop indication for the QoE configuration; and sending a first RRC message from the UE RRC layer to a network entity, wherein the first RRC message includes a QoE report having the buffered QoE data.
[0126] Aspect 3: The method according to any one of Aspects 1 to 2 also includes: sending a first RRC message from the UE RRC layer to a network entity based at least in part on the attention command indicating the QoE measurement session stop indication for the QoE configuration, the first RRC message indicating one or more of the following: the QoE measurement session stop indication for the QoE configuration, or a buffered QoE data indication indicating whether the buffered QoE data can be used for the QoE configuration.
[0127] Aspect 4: The method according to Aspect 3 further includes: receiving a second RRC message including a release command to release the QoE configuration from the network entity at the UE RRC layer based at least in part on the first RRC message indicating the QoE measurement session stop indication for the QoE configuration without indicating a buffered QoE data indication.
[0128] Aspect 5: The method according to Aspect 3 further includes: receiving a second RRC message indicating a resumption command from the network entity at the UE RRC layer based at least in part on the QoE measurement session stop indication and the buffered QoE data indication for the QoE configuration, wherein the sending of the buffered QoE data from the UE RRC layer to the network entity is resumed based at least in part on the resumption command.
[0129] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: determining, by the UE RRC layer, to suspend sending the RRC message including the QoE measurement session stop indication for the QoE configuration, at least in part based on suspending the QoE report; and sending the RRC message including the QoE measurement session stop indication for the QoE configuration from the UE RRC layer to a network entity, at least in part based on resuming the QoE report.
[0130] Aspect 7: The method according to Aspect 6 also includes: receiving a configuration from the network entity at the UE RRC layer, wherein the configuration configures the UE RRC layer to suspend sending the RRC message including the QoE measurement session stop indication for the QoE configuration based at least in part on suspending the QoE report.
[0131] Aspect 8: The method according to Aspect 6 also includes: receiving multiple QoE measurement session indications for the QoE configuration from the UE application layer at the UERRC layer during the suspension of sending the RRC message; and the UERRC layer using the newly received QoE measurement session indication in the multiple QoE measurement session indications to overwrite the previously received QoE measurement session indication in the multiple QoE measurement session indications.
[0132] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: sending a first RRC message from the UE RRC layer to a network entity based at least in part on the attention command indicating the QoE measurement session stop indication for the QoE configuration, wherein the first RRC message indicates the QoE measurement session stop indication for the QoE configuration.
[0133] Aspect 10: The method according to Aspect 9 also includes: receiving a first RRC message from the network entity at the UE RRC layer, the first RRC message including a release command for releasing the QoE configuration based at least in part on the UE moving outside a specific area, wherein the first RRC message includes an indication of sending the buffered QoE data for the QoE configuration; and sending a second RRC message from the UE RRC layer to the network entity based at least in part on the first RRC message, the second RRC message including a QoE report having the buffered QoE data for the QoE configuration.
[0134] Aspect 11: The method according to Aspect 9 further includes: sending an indication from the UE RRC layer to the network entity that all buffered QoE data for the QoE configuration has been sent to the network entity, wherein the UE and the network entity release the QoE configuration at least in part based on the indication.
[0135] Aspect 12: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 11.
[0136] Aspect 13: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 11.
[0137] Aspect 14: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 11.
[0138] Aspect 15: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 11.
[0139] Aspect 16: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 11.
[0140] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.
[0141] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.
[0142] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.
[0143] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).
[0144] Any element, action or instruction used herein should not be interpreted as critical or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").
Claims
1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; and one or more processors coupled to the memory and configured to: determining, by a UE radio resource control (RRC) layer of the UE, to suspend quality of experience (QoE) reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the UE; receiving, at the UE RRC layer from a UE application layer of the UE, an attention command indicating a QoE measurement session stop indication for the QoE configuration; as well as The buffered QoE data is sent based at least in part on the attention command without discarding the buffered QoE data stored at the UE.
2. The apparatus of claim 1 , wherein the one or more processors are further configured to: determining, by the UE RRC layer, to resume sending the buffered QoE data based at least in part on the attention command indicating the QoE measurement session stop indication for the QoE configuration; and A first RRC message is sent from the UE RRC layer to a network entity, the first RRC message including a QoE report having the buffered QoE data.
3. The apparatus of claim 1 , wherein the one or more processors are further configured to: At least in part based on the attention command indicating the QoE measurement session stop indication for the QoE configuration, sending a first RRC message from the UE RRC layer to a network entity, the first RRC message indicating one or more of the following: the QoE measurement session stop indication for the QoE configuration, or a buffered QoE data indication indicating whether the buffered QoE data can be used for the QoE configuration.
4. The apparatus of claim 3, wherein the one or more processors are further configured to: Based at least in part on the first RRC message indicating the QoE measurement session stop indication for the QoE configuration without indicating a buffered QoE data indication, receiving, at the UE RRC layer from the network entity, a second RRC message including a release command to release the QoE configuration.
5. The apparatus of claim 3, wherein the one or more processors are further configured to: Based at least in part on the first RRC message indicating the QoE measurement session stop indication and the buffered QoE data indication for the QoE configuration, receiving a second RRC message indicating a resume command from the network entity at the UE RRC layer, wherein sending the buffered QoE data from the UE RRC layer to the network entity is resumed based at least in part on the resume command.
6. The apparatus of claim 1, wherein the one or more processors are further configured to: At least in part based on suspending the QoE reporting, determining, by the UE RRC layer, to suspend sending an RRC message including the QoE measurement session stop indication for the QoE configuration; and Based at least in part on resuming the QoE reporting, sending the RRC message including the QoE measurement session stop indication for the QoE configuration from the UE RRC layer to a network entity.
7. The apparatus of claim 6, wherein the one or more processors are further configured to: A configuration is received at the UE RRC layer from the network entity, the configuration configuring the UE RRC layer to suspend sending the RRC message including the QoE measurement session stop indication for the QoE configuration based at least in part on suspending the QoE reporting.
8. The apparatus of claim 6, wherein the one or more processors are further configured to: During the suspension of sending the RRC message, receiving, at the UE RRC layer, a plurality of QoE measurement session indications for the QoE configuration from the UE application layer; and The UE RRC layer overwrites a previously received QoE measurement session indication among the multiple QoE measurement session indications with a newly received QoE measurement session indication among the multiple QoE measurement session indications.
9. The apparatus of claim 1, wherein the one or more processors are further configured to: Based at least in part on the attention command indicating the QoE measurement session stop indication for the QoE configuration, sending a first RRC message from the UE RRC layer to a network entity, the first RRC message indicating the QoE measurement session stop indication for the QoE configuration.
10. The apparatus of claim 9, wherein the one or more processors are further configured to: receiving, at the UE RRC layer, a first RRC message from the network entity, the first RRC message comprising a release command to release the QoE configuration based at least in part on the UE moving outside a specific area, wherein the first RRC message comprises an indication to send the buffered QoE data for the QoE configuration; and Based at least in part on the first RRC message, sending a second RRC message from the UE RRC layer to the network entity, the second RRC message including a QoE report with the buffered QoE data for the QoE configuration.
11. The apparatus of claim 9, wherein the one or more processors are further configured to: An indication is sent from the UE RRC layer to the network entity that all buffered QoE data for the QoE configuration has been sent to the network entity, wherein the UE and the network entity release the QoE configuration based at least in part on the indication.
12. A method of wireless communication performed by a user equipment (UE), comprising: determining, by a UE radio resource control (RRC) layer of the UE, to suspend quality of experience (QoE) reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the UE; receiving, at the UE RRC layer from a UE application layer of the UE, an attention command indicating a QoE measurement session stop indication for the QoE configuration; as well as The buffered QoE data is sent based at least in part on the attention command without discarding the buffered QoE data stored at the UE.
13. The method according to claim 12, further comprising: determining, by the UE RRC layer, to resume sending the buffered QoE data based at least in part on the attention command indicating a stop indication of the QoE measurement session for the QoE configuration; as well as A first RRC message is sent from the UE RRC layer to a network entity, the first RRC message including a QoE report having the buffered QoE data.
14. The method according to claim 12, further comprising: At least in part based on the attention command indicating the QoE measurement session stop indication for the QoE configuration, sending a first RRC message from the UE RRC layer to a network entity, the first RRC message indicating one or more of the following: the QoE measurement session stop indication for the QoE configuration, or a buffered QoE data indication indicating whether the buffered QoE data can be used for the QoE configuration.
15. The method according to claim 14, further comprising: Based at least in part on the first RRC message indicating the QoE measurement session stop indication for the QoE configuration without indicating a buffered QoE data indication, receiving, at the UE RRC layer from the network entity, a second RRC message including a release command to release the QoE configuration.
16. The method according to claim 14, further comprising: Based at least in part on the first RRC message indicating the QoE measurement session stop indication and the buffered QoE data indication for the QoE configuration, receiving a second RRC message indicating a resume command from the network entity at the UE RRC layer, wherein sending the buffered QoE data from the UE RRC layer to the network entity is resumed based at least in part on the resume command.
17. The method according to claim 12, further comprising: At least in part based on suspending the QoE reporting, determining, by the UE RRC layer, to suspend sending an RRC message including the QoE measurement session stop indication for the QoE configuration; and Based at least in part on resuming the QoE reporting, sending the RRC message including the QoE measurement session stop indication for the QoE configuration from the UE RRC layer to a network entity.
18. The method according to claim 17, further comprising: A configuration is received at the UE RRC layer from the network entity, the configuration configuring the UE RRC layer to suspend sending the RRC message including the QoE measurement session stop indication for the QoE configuration based at least in part on suspending the QoE reporting.
19. The method according to claim 17, further comprising: During the suspension of sending the RRC message, receiving, at the UE RRC layer, from the UE application layer, a plurality of QoE measurement session indications for the QoE configuration; as well as The UE RRC layer overwrites a previously received QoE measurement session indication among the multiple QoE measurement session indications with a newly received QoE measurement session indication among the multiple QoE measurement session indications.
20. The method of claim 12, further comprising: Based at least in part on the attention command indicating the QoE measurement session stop indication for the QoE configuration, sending a first RRC message from the UE RRC layer to a network entity, the first RRC message indicating the QoE measurement session stop indication for the QoE configuration.
21. The method according to claim 20, further comprising: receiving, at the UE RRC layer, a first RRC message from the network entity, the first RRC message comprising a release command to release the QoE configuration based at least in part on the UE moving outside a specific area, wherein the first RRC message comprises an indication to send the buffered QoE data for the QoE configuration; and Based at least in part on the first RRC message, sending a second RRC message from the UE RRC layer to the network entity, the second RRC message including a QoE report with the buffered QoE data for the QoE configuration.
22. The method according to claim 20, further comprising: An indication is sent from the UE RRC layer to the network entity that all buffered QoE data for the QoE configuration has been sent to the network entity, wherein the UE and the network entity release the QoE configuration based at least in part on the indication.
23. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: determining, by a UE radio resource control (RRC) layer of the UE, to suspend quality of experience (QoE) reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the UE; receiving, at the UE RRC layer from a UE application layer of the UE, an attention command indicating a QoE measurement session stop indication for the QoE configuration; as well as The buffered QoE data is sent based at least in part on the attention command without discarding the buffered QoE data stored at the UE.
24. The non-transitory computer readable medium of claim 23, wherein the one or more instructions further cause the UE to: determining, by the UE RRC layer, to resume sending the buffered QoE data based at least in part on the attention command indicating the QoE measurement session stop indication for the QoE configuration; and A first RRC message is sent from the UE RRC layer to a network entity, the first RRC message including a QoE report having the buffered QoE data.
25. The non-transitory computer readable medium of claim 23, wherein the one or more instructions further cause the UE to: At least in part based on the attention command indicating the QoE measurement session stop indication for the QoE configuration, sending a first RRC message from the UE RRC layer to a network entity, the first RRC message indicating one or more of the following: the QoE measurement session stop indication for the QoE configuration, or a buffered QoE data indication indicating whether the buffered QoE data can be used for the QoE configuration.
26. The non-transitory computer readable medium of claim 23, wherein the one or more instructions further cause the UE layer to: At least in part based on suspending the QoE reporting, determining, by the UE RRC layer, to suspend sending an RRC message including the QoE measurement session stop indication for the QoE configuration; and Based at least in part on resuming the QoE reporting, determining from the UE RRC layer to a network entity the RRC message including the QoE measurement session stop indication for the QoE configuration.
27. An apparatus for wireless communication, comprising: means for determining, by a device radio resource control (RRC) layer of the device, to suspend quality of experience (QoE) reporting based at least in part on network overload, wherein when the QoE reporting is suspended, buffered QoE data for a QoE configuration is stored at the device; means for receiving, at the device RRC layer from a device application layer of the device, an attention command indicating a QoE measurement session stop indication for the QoE configuration; and Means for sending the buffered QoE data based at least in part on the attention command without discarding the buffered QoE data stored at the device.
28. The apparatus according to claim 27, further comprising: means for determining, by the device RRC layer, to resume sending the buffered QoE data based at least in part on the attention command indicating the QoE measurement session stop indication for the QoE configuration; and Means for sending, from the device RRC layer to a network entity, a first RRC message including a QoE report having the buffered QoE data.
29. The apparatus of claim 27, further comprising: Means for sending a first RRC message from the device RRC layer to a network entity based at least in part on the attention command indicating the QoE measurement session stop indication for the QoE configuration, the first RRC message indicating one or more of: the QoE measurement session stop indication for the QoE configuration, or a buffered QoE data indication indicating whether the buffered QoE data is available for the QoE configuration.
30. The apparatus of claim 27, further comprising: means for determining, by the device RRC layer, to suspend sending an RRC message including the QoE measurement session stop indication for the QoE configuration based at least in part on suspending the QoE reporting; and Means for sending, from the device RRC layer to a network entity, the RRC message including the QoE measurement session stop indication for the QoE configuration based at least in part on resuming the QoE reporting.
Citation Information
Cited By
QoE configuration method and apparatus during RRC resuming process
US12726858B2
