Quality of experience measurement and reporting in idle and inactive states

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can, when operating in a connected state, perform a first set of Quality of Experience (QoE) measurements according to a first QoE measurement and reporting configuration associated with the connected state. The UE can then transition from the connected state to one of an idle state or an inactive state. The UE can then perform a second set of QoE measurements according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both when operating in the idle state or the inactive state, where the second QoE measurement and reporting configuration is different from the first QoE measurement and reporting configuration. The UE can then send a QoE report comprising at least the second set of QoE measurements to a network entity.

Description

Technical Field

[0001] The following content relates to wireless communications, including quality of experience (QoE) measurement and reporting in idle and inactive states. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may use techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for a communication device, which may be referred to as a user equipment (UE).

[0003] Some wireless communication systems enable UEs to report quality of experience (QoE) measurements to the network. Compared to quality of service (QoS) metrics, which are referred to as minimization of drive tests (MDT) measurements in 3GPP systems, which are associated with the relative quality of wireless communications within lower layers such as the packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC) layer, and physical layer, QoE measurements are associated with the quality of experience of application services at the application layer provided to the UE via wireless communication, such as IMS multimedia telephony service (MTSI), streaming services, virtual reality (VR) services, multicast broadcast services (MBS), etc. Several examples of QoE measurements may include, but are not limited to, block error rate (BLER) at the UE, quality of streaming video at the UE, buffering delay at the UE, and playback delay. Summary of the invention

[0004] The present invention is defined by the claims. Embodiments, examples, and aspects that deviate from (eg, do not fall within) the scope of the claims are merely examples for explaining the present invention.

[0005] The described technology relates to improved methods, systems, devices and apparatuses that support technology for quality of experience (QoE) measurement and reporting in idle and inactive states. In general, aspects of the present disclosure support technologies that enable user equipment (UE) to perform quality of experience (QoE) measurements, report QoE measurements, or both when operating in an idle state or an inactive state. In particular, the technology described herein may enable a UE to be configured with QoE measurement and reporting configurations that enable the UE to perform QoE measurements during an idle / inactive state. In addition, the QoE measurement and reporting configurations described herein may enable the UE to transition to a connected state to send a QoE report, and / or send a QoE report when operating in an idle / inactive state. In some aspects, a UE may be configured with a single QoE measurement and reporting configuration that can be used for a connected state, an idle state, and an inactive state. In such cases, the parameters of the QoE measurement and reporting configuration (e.g., the periodicity of the QoE measurements and / or the QoE measurement metrics) may be updated as the UE transitions between states (such as via a radio resource control (RRC) release message that releases the UE from a connected state to an idle / inactive state and via an RRCReconfiguration message when the UE transitions from the idle / inactive state back to the connected state). In addition or alternatively, the UE may be configured with separate QoE measurement and reporting configurations for the connected state and the idle / inactive state. In some cases, the UE may perform QoE measurements while in the idle / inactive state, and the QoE measurements may be stored in a memory until the UE transitions to the connected state and a QoE report indicating the stored measurements may be transmitted. The QoE measurement and reporting configuration may include trigger conditions that cause the UE to transition from the idle / inactive state to the connected state to send the QoE report.

[0006] A method for wireless communication at a UE is described. The method may include: when operating in a connected state, performing a first QoE measurement set according to a first QoE measurement and reporting configuration associated with the connected state; transitioning from the connected state to one of an idle state or an inactive state; when operating in the idle state or the inactive state, performing a second QoE measurement set according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration; and sending a QoE report including at least the second QoE measurement set to a network entity.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: when operating in a connected state, perform a first QoE measurement set according to a first QoE measurement and reporting configuration associated with the connected state; transition from the connected state to one of an idle state or an inactive state; when operating in the idle state or the inactive state, perform a second QoE measurement set according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration; and send a QoE report including at least the second QoE measurement set to a network entity.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for performing a first QoE measurement set according to a first QoE measurement and reporting configuration associated with the connected state when operating in a connected state; means for transitioning from the connected state to one of an idle state or an inactive state; means for performing a second QoE measurement set according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both when operating in the idle state or the inactive state, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration; and means for sending a QoE report including at least the second QoE measurement set to a network entity.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to perform the following operations: when operating in a connected state, perform a first QoE measurement set according to a first QoE measurement and reporting configuration associated with the connected state; transition from the connected state to one of an idle state or an inactive state; when operating in the idle state or the inactive state, perform a second QoE measurement set according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration; and send a QoE report including at least the second QoE measurement set to a network entity.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a control message from the network entity commanding the UE to transition from the connected state to the idle state or the inactive state, the control message modifying one or more parameters associated with the first QoE measurement and reporting configuration, wherein the transition to the idle state or the inactive state may be based on the control message, and wherein the second QoE measurement and reporting configuration includes a modified version of the first QoE measurement and reporting configuration based on the control message.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control message includes an RRC release message.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a control message indicating the first QoE measurement and reporting configuration and the second QoE measurement and reporting configuration from the network entity, wherein performing the first QoE measurement set, performing the second QoE measurement set, or both may be based on the control message.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a control message from the network entity commanding the UE to transition from the connected state to the idle state or the inactive state, the control message indicating the second QoE measurement and reporting configuration, wherein transitioning to the idle state or the inactive state and performing the second QoE measurement set may be based on the control message.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: while operating in the idle state or the inactive state, storing the second QoE measurement set in the memory according to the second QoE measurement and reporting configuration; and transitioning from the idle state or the inactive state to the connected state, wherein sending the QoE report occurs after transitioning to the connected state, and may be based on storing the second QoE measurement set in the memory while operating in the idle state or the inactive state.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: while operating in the idle state or the inactive state, identifying satisfaction of a trigger condition for a QoE report; and based on the satisfaction of the trigger condition, transitioning from the idle state or the inactive state to the connected state, wherein sending the QoE report occurs after transitioning to the connected state.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a control message from the network entity indicating a set of multiple trigger conditions for QoE reporting, the set of multiple trigger conditions including the trigger condition, wherein identifying the satisfaction of the trigger condition may be based on the control message.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that at least one QoE measurement in the second QoE measurement set may be less than or equal to a QoE threshold, wherein identifying that the satisfaction of the trigger condition may be based on the at least one QoE measurement being less than or equal to the QoE threshold.

[0018] In some examples of the methods, devices, and non-transitory computer-readable media described herein, and the methods, devices, and non-transitory computer-readable media may include further operations, features, components, or instructions for: when operating in the idle state or the inactive state, establishing a wireless connection with a second cell different from the first cell, wherein the QoE report may be sent to at least the second cell based on establishing the wireless connection with the second cell, and wherein the QoE report includes a cell identifier associated with the second cell.

[0019] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: when operating in the idle state or the inactive state, sending a request to the network entity to establish or resume a wireless connection with the network entity; and based on sending the request, transitioning from the idle state or the inactive state to the connected state, wherein sending the QoE report occurs after transitioning to the connected state.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: when operating in the idle state or the inactive state, sending a request to the network entity to establish or resume a wireless connection with the network entity; and based on the request, receiving an indication of a signaling radio bearer for QoE reporting from the network entity, wherein the QoE measurement and reporting configuration may be sent via the indicated signaling radio bearer.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving an indication of a signaling radio bearer associated with wireless communication between the UE and the network entity from the network entity; and sending the QoE report via the signaling radio bearer when operating in the inactive state based on maintaining the signaling radio bearer as active when operating in the inactive state.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second QoE measurement and reporting configuration may be associated with at least radio access network-aware QoE information decodable by the network entity, and the second QoE measurement set includes at least one radio access network-visible QoE measurement decodable by the network entity.

[0023] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the first QoE measurement and reporting configuration may be associated with a first parameter set, the second QoE measurement and reporting configuration may be associated with a second parameter set different from the first parameter set, and the first parameter set, the second parameter set, or both include measurement periodicity, reporting periodicity, measurement quantity, measurement quality, or any combination thereof.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first QoE measurement and reporting configuration may be associated with a first power consumption at the UE, and the second QoE measurement and reporting configuration may be associated with a second power consumption at the UE that may be less than the first power consumption.

[0025] A method for wireless communication at a network entity is described. The method may include: outputting a first control message to a UE, the first control message indicating a first QoE measurement and reporting configuration for the UE to perform QoE measurement when in a connected state; outputting a second QoE measurement and reporting configuration to the UE via the first control message or a second control message for the UE to perform QoE measurement when in an idle state, an inactive state, or both; and obtaining a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in the idle state or the inactive state and according to the second QoE measurement and reporting configuration.

[0026] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: output a first control message to a UE, the first control message indicating a first QoE measurement and reporting configuration for the UE to perform QoE measurement when in a connected state; output a second QoE measurement and reporting configuration to the UE via the first control message or the second control message for the UE to perform QoE measurement when in an idle state, an inactive state, or both; and obtain a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in the idle state or the inactive state and according to the second QoE measurement and reporting configuration.

[0027] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a means for outputting a first control message to a UE, the first control message indicating a first QoE measurement and reporting configuration for the UE to perform QoE measurements when in a connected state; a means for outputting a second QoE measurement and reporting configuration to the UE via the first control message or a second control message for the UE to perform QoE measurements when in an idle state, an inactive state, or both; and a means for obtaining a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in the idle state or the inactive state and according to the second QoE measurement and reporting configuration.

[0028] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that can be executed by a processor to perform the following operations: output a first control message to a UE, the first control message indicating a first QoE measurement and reporting configuration for the UE to perform QoE measurement when in a connected state; output a second QoE measurement and reporting configuration to the UE via the first control message or the second control message for the UE to perform QoE measurement when in an idle state, an inactive state, or both; and obtain a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in the idle state or the inactive state and according to the second QoE measurement and reporting configuration.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second control message commands the UE to transition from the connected state to the idle state or the inactive state, and the second control message modifies one or more parameters associated with the first QoE measurement and reporting configuration, and the second QoE measurement and reporting configuration includes a modified version of the first QoE measurement and reporting configuration based on the second control message.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second control message includes an RRC release message.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second control message commands the UE to transition from the connected state to the idle state or the inactive state, and the second control message indicates the second QoE measurement and reporting configuration, and obtaining the QoE report can be based on the second control message.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for indicating to the UE via the first control message, the second control message, an additional control message, or any combination thereof, a set of multiple trigger conditions for QoE reporting, wherein receiving the QoE report may be based on satisfying a trigger condition from the set of multiple trigger conditions.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining, from the UE, a request to establish or resume a wireless connection with the network entity, wherein obtaining the QoE report occurs after the wireless connection may be established or resumed.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining, from the UE, a request to establish or resume a wireless connection with the network entity; and based on the request, outputting to the UE an indication of a signaling radio bearer for QoE reporting, wherein the QoE measurement and reporting configuration may be obtained via the indicated signaling radio bearer.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: outputting to the UE an indication of a signaling radio bearer associated with wireless communication between the UE and the network entity; and obtaining the QoE report from the UE via the signaling radio bearer based on the signaling radio bearer being maintained as active when the UE may be in the inactive state.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second QoE measurement and reporting configuration may be associated with at least radio access network-aware QoE information decodable by the network entity, and the QoE measurement set includes at least one radio access network-visible QoE measurement decodable by the network entity.

[0037] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the first QoE measurement and reporting configuration may be associated with a first parameter set, the second QoE measurement and reporting configuration may be associated with a second parameter set different from the first parameter set, and the first parameter set, the second parameter set, or both include measurement periodicity, reporting periodicity, measurement quantity, measurement quality, or any combination thereof.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first QoE measurement and reporting configuration may be associated with a first power consumption at the UE, and the second QoE measurement and reporting configuration may be associated with a second power consumption at the UE that may be less than the first power consumption. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 An example of a wireless communication system supporting techniques for quality of experience (QoE) measurement and reporting in idle and inactive states in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 2 An example of a network architecture supporting techniques for QoE measurement and reporting in idle and inactive states according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 3 An example of a wireless communication system supporting techniques for QoE measurement and reporting in idle and inactive states according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 4 An example of a process flow supporting techniques for QoE measurement and reporting in idle and inactive states in accordance with one or more aspects of the present disclosure is illustrated.

[0043] Figure 5 An example of a process flow supporting techniques for QoE measurement and reporting in idle and inactive states in accordance with one or more aspects of the present disclosure is illustrated.

[0044] Figure 6 An example of a process flow supporting techniques for QoE measurement and reporting in idle and inactive states in accordance with one or more aspects of the present disclosure is illustrated.

[0045] Figure 7 and Figure 8 A block diagram of a device supporting techniques for QoE measurement and reporting in idle and inactive states in accordance with one or more aspects of the present disclosure is shown.

[0046] Fig. 9A block diagram of a communications manager supporting techniques for QoE measurement and reporting in idle and inactive states in accordance with one or more aspects of the present disclosure is shown.

[0047] Fig.10 A diagram of a system including a device supporting techniques for QoE measurement and reporting in idle and inactive states is shown in accordance with one or more aspects of the present disclosure.

[0048] Fig.11 and Fig.12 A block diagram of a device supporting techniques for QoE measurement and reporting in idle and inactive states in accordance with one or more aspects of the present disclosure is shown.

[0049] Fig.13 A block diagram of a communications manager supporting techniques for QoE measurement and reporting in idle and inactive states in accordance with one or more aspects of the present disclosure is shown.

[0050] Fig.14 A diagram of a system including a device supporting techniques for QoE measurement and reporting in idle and inactive states is shown in accordance with one or more aspects of the present disclosure.

[0051] Figures 15 to 18 A flow chart illustrating a method of supporting techniques for QoE measurement and reporting in idle and inactive states in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0052] A wireless communication system may enable a user equipment (UE) to report quality of experience (QoE) measurements to a network. For example, QoE measurements may be associated with the quality of experience of application services (such as IMS Multimedia Telephony Service (MTSI), streaming services, virtual reality (VR) services, multicast broadcast services (MBS), etc.) at an application layer provided to a UE via wireless communication (e.g., from the perspective of a user of the UE), as compared to quality of service (QoS) metrics or parameters that may instead be associated with the relative quality of wireless communication at lower layers (e.g., packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC) layer, and physical layer), such as block error rate (BLER) at the UE, quality of streaming video at the UE, or buffering delay at the UE, among other possible examples. QoE reports may include QoE measurements decoded and identified by a base station (e.g., "RAN visible" QoE parameters), as well as QoE measurements that are not decoded by the base station but passed to a measurement collection entity (MCE) for processing (e.g., "RAN invisible" QoE parameters).

[0053] Some communication systems may only enable the UE to perform and report QoE measurements when operating in a radio resource control (RRC) connected state (e.g., RRC_CONNECTED). However, the UE may also receive communications when operating in other states such as RRC idle and inactive states (e.g., RRC_IDLE, RRC_INACTIVE). For example, the UE may receive emergency broadcast messages while in an idle / inactive state. For wireless communication systems that enable QoE reporting only during a connected state, the UE may not be able to measure and / or report degraded QoE experienced during an idle / inactive state, which may reduce the UE's ability to receive and decode such emergency broadcast messages.

[0054] In addition to supporting the performance, reporting, or both of QoE measurements when the UE is in an idle state or an inactive state, techniques as described herein may also advantageously support the use of different QoE measurement and reporting configurations when the UE is in different states (e.g., when in an idle state or an inactive state versus when in a connected state). Using different QoE measurement and reporting configurations when in different states may be beneficial, for example, because when in an idle / inactive state, utilizing the same QoE measurement and reporting configuration across all states may result in increased power consumption (e.g., due to using the same QoE measurement and reporting configuration that is also used in a connected state), thereby reducing the power saving benefits that may otherwise be associated with the idle state and the inactive state, and resulting in increased power consumption at the UE.

[0055] In addition, the performance, reporting, or both of QoE measurements when the UE is in an idle state or an inactive state as described herein may provide additional or alternative benefits compared to other types of measurements. For example, in some cases, the UE may perform minimization of drive tests (MDT) measurements (referred to as logged measurements or logged MDT) when in an idle state or an inactive state, and may send the MDT measurements via a QoE report after transitioning to a connected state. However, MDT measurements are associated with a different layer from QoE measurements and serve a different purpose than QoE measurements. In particular, QoE measurements may include higher layer measurements (e.g., application layer measurements), while MDT measurements may include lower layer measurements (e.g., PDCP, RLC, MAC, and physical layer measurements). Additionally, MDT measurements are primarily used for coverage optimization purposes (e.g., to improve coverage across the network), while QoE measurements are related to the relative quality of application services performed (e.g., supplied by) via wireless communications sensed or measured at the UE, and may therefore be used, for example, for encoding / decoding to verify or optimize encoder and decoder operations at a network entity (e.g., an application server). Thus, the performance, reporting, or both of QoE measurements while the UE is in an idle or inactive state as described herein may serve different purposes and provide different benefits than other types of measurements, and may enable the network to improve the quality of application services provided through wireless communications experienced at the UE when operating in an idle / inactive state in a manner that such other types of measurements may not support.

[0056] Thus, aspects of the present disclosure may support techniques that enable a UE to perform QoE measurements, report QoE measurements, or both in association with operating in an idle state or an inactive state. In particular, the techniques described herein may enable a UE to be configured with QoE measurement and reporting configurations that enable the UE to perform QoE measurements during an idle / inactive state while enabling the UE to reduce power consumption when operating in an idle state and an inactive state. In addition, the QoE measurement and reporting configurations described herein may enable the UE to transition to a connected state to send a QoE report, and / or send a QoE report when operating in an idle / inactive state.

[0057] In some aspects, a UE may be configured with a single QoE measurement and reporting configuration that may be used for a connected state, an idle state, and an inactive state, wherein the single QoE measurement and reporting configuration is modified or updated when the UE transitions between states so as to implement different QoE measurement and reporting configurations for different states based on such transition-related modifications or updates. For example, in such cases, parameters of the QoE measurement and reporting configuration (e.g., periodicity of QoE measurements and / or QoE measurement metrics) may be updated as the UE transitions between states (such as via an RRC release message that releases the UE from a connected state to an idle / inactive state). In additional or alternative cases, the UE may be configured (e.g., via a single configuration message) with separate QoE measurement and reporting configurations for a connected state and an idle / inactive state. In some cases, the UE may perform QoE measurements while in an idle / inactive state, and may store the QoE measurements in a memory until the UE transitions to a connected state and may transmit a QoE report indicating the stored measurements. The QoE measurement and reporting configuration may include trigger conditions that cause the UE to transition from an idle / inactive state to a connected state to send a QoE report. For example, if the QoE measurement drops below a threshold while in the idle / inactive state, the UE may transition from the idle / inactive state to the connected state to report the degraded QoE measurement experienced during the idle / inactive state.

[0058] Aspects of the disclosure are first described in the context of a wireless communication system. Additional aspects of the disclosure are described in the context of an example process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to techniques for QoE measurement and reporting in idle and inactive states.

[0059] Figure 1 An example of a wireless communication system 100 supporting techniques for QoE measurement and reporting in an idle state and an inactive state according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0060] The network entities 105 may be dispersed throughout a geographic area to form a wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other names. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area, and the network entity 105 and the UE 115 may support signal communications over the geographic area according to one or more radio access technologies (RATs).

[0061] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein can communicate with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0062] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0063] In some examples, the network entities 105 may communicate with the core network 130 or with each other or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0064] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0065] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0066] The split of functions between CU 160, DU 165, and RU 170 is flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by the other of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate over these communication links.

[0067] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0068] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of part of a backhaul link).

[0069] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0070] For example, the IAB node 104 may be referred to as a parent node that supports child IAB node communications and as a child IAB node associated with an IAB donor. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, and may directly signal the UE 115 of the transmissions. The CU 160 of the IAB donor may signal the IAB node 104 of the communication link establishment via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling on the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0071] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support the techniques described herein for QoE measurement and reporting in idle and inactive states. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0072] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, among other examples, which may be implemented in various objects such as appliances or vehicles, meters, and among other examples.

[0073] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, and other examples, such as Figure 1 shown.

[0074] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control messages for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0075] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0076] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

[0077] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0078] The signal waveform sent on the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate for the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0079] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0080] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0081] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may also be divided into multiple mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0082] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0083] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0084] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, as well as other examples.

[0085] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0086] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0087] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0088] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UEs 115 include entering a power saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0089] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety applications or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency are used interchangeably herein.

[0090] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may occur between UEs 115 without involving network entity 105 .

[0091] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW) or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming media services.

[0092] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0093] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, as well as other examples.

[0094] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0095] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such technology may be referred to as spatial multiplexing. Multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0096] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0097] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0098] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0099] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or non-precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0100] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0101] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate on a logical channel. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between a UE 115 and a network entity 105 or a core network 130. At the PHY layer, a transport channel may be mapped to a physical channel.

[0102] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0103] In some aspects, the UE 115 and the network entity 105 (e.g., a base station) of the wireless communication system 100 may support signaling and techniques that enable the UE 115 to perform QoE measurements, report QoE measurements, or both in association with operating in an idle state or an inactive state. In particular, the techniques described herein may enable the UE 115 of the wireless communication system 100 to be configured with QoE measurement and reporting configurations that enable the UE 115 to perform QoE measurements during an idle / inactive state while reducing power consumption while in the idle / inactive state. In addition, the QoE measurement and reporting configurations described herein may enable the UE 115 to transition to a connected state to send a QoE report, and / or send a QoE report when operating in an idle / inactive state.

[0104] In some aspects, a UE 115 of the wireless communication system 100 may be configured with a single QoE measurement and reporting configuration that may be used for a connected state, an idle state, and an inactive state, wherein parameters of the single QoE measurement and reporting configuration (e.g., periodicity of QoE measurements and / or QoE measurement metrics) are updated or modified when the UE 115 transitions between states. For example, the network entity 105 may release the UE 115 from the connected state to the idle state or the inactive state via an RRC release message, wherein the RRC release message selectively adjusts or updates one or more parameters of the QoE measurement and reporting configuration (e.g., periodicity of QoE measurements and / or QoE measurement metrics). In addition or alternatively, the UE 115 may be configured with separate QoE measurement and reporting configurations for the connected state and the idle / inactive state. For example, the UE 115 may be configured with a first QoE measurement and reporting configuration that may be used during the time when the UE 115 is in the connected state, and a second QoE measurement and reporting configuration that may be used when the UE 115 is in the idle state or the inactive state. In this example, the second QoE measurement and reporting configuration can be associated with a less frequent QoE measurement periodicity compared to the first QoE configuration to reduce power consumption of the UE 115 during an idle / inactive state.

[0105] In some implementations, the UE 115 may perform QoE measurements while in an idle / inactive state, and the QoE measurements may be stored in a memory until the UE 115 transitions to a connected state and is able to transmit a QoE report indicating the stored measurements. In some aspects, the QoE measurement and reporting configurations described herein may include trigger conditions that cause the UE 115 to transition from an idle / inactive state to a connected state to send a QoE report. For example, if a QoE measurement falls below a threshold while in an idle / inactive state, the UE 115 may identify satisfaction of the trigger condition, which causes the UE 115 to transition from the idle / inactive state to a connected state to report the degraded QoE measurements experienced during the idle / inactive state.

[0106] The techniques described herein may enable UE 115 to perform QoE measurements when operating in an idle state, an inactive state, or both. Thus, the techniques described herein may enable UE 115 to inform the network about the relative quality of wireless communications received at UE 115 during an idle state and an inactive state, including the relative quality of emergency broadcast messages. Thus, aspects of the present disclosure may enable the network to adjust parameters of wireless communications to improve the relative quality of such wireless communications received by UE 115 during an idle state and an inactive state. In this regard, aspects of the present disclosure may facilitate improved coordination between UE 115 and the network, and improve the efficiency and reliability of application services provided by wireless communications received by UE 115 during an inactive state and an idle state.

[0107] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting techniques for QoE measurement and reporting in an idle state and an inactive state according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. A RU 170-a may be associated with a respective coverage area 110-a and may communicate with a UE 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.

[0108] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to send signals to one or more network entities in other network entities 105 via a wireless transmission medium, or to do both.

[0109] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a 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, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0110] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented with an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0111] In some examples, lower layer functions may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., 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 functional splitting (such as lower layer functional splitting). In this architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0112] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a 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 (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0113] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0114] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0115] Figure 3 An example of a wireless communication system 300 that supports techniques for QoE measurement and reporting in an idle state and an inactive state in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the wireless communication system 300 may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, or both. In particular, the wireless communication system 300 may support QoE measurement and reporting configurations that enable a UE 115-a to perform (and / or report) QoE measurements when operating in an idle state or an inactive state, as described herein.

[0116] The wireless communication system 300 may include a network entity 105-a and a UE 115-a, which may be as described in reference Figure 1 An example of a network entity 105 and a UE 115 described. The UE 115-a may communicate with the network entity 105-a using a communication link 305, which may be an example of an NR or LTE link between the UE 115-a and the network entity 105-a. In some cases, the communication link 305 between the UE 115-a and the network entity 105-a may include an example of an access link (e.g., a Uu link), which may include a bidirectional link that implements both uplink and downlink communications. For example, the UE 115-a may use the communication link 305 to send an uplink signal, such as an uplink control signal or an uplink data signal, to one or more components of the network entity 105-a, and one or more components of the network entity 105-a may use the communication link 305 to send a downlink signal, such as a downlink control signal or a downlink data signal, to the UE 115-a.

[0117] The UE 115-a and the network entity 105-a of the wireless communication system 300 may support wireless communications for various service types, including augmented reality (AR) applications, mixed reality (MR) applications, multicast broadcast services (MBS), and other service types (e.g., other service types supported by 3GPP TSG SA WG4 (SA4)). For example, the wireless communication system 300 may support new service types in conjunction with high mobility scenarios (such as high-speed trains) and existing service types defined by SA4 or to be supported by SA4.

[0118] To support various service types, and to facilitate improved wireless communications at UE 115-a, UE 115-a may be configured to report QoE measurements to network entity 105-a. In contrast to QoS metrics (which are associated with the relative quality of wireless communications at the network), QoE measurements are associated with the QoE of application services provided to UE 115-a via wireless communications, including but not limited to BLER at UE 115-a, quality of streaming video at UE 115-a, buffering delay at UE 115-a, and playback delay. Additionally or alternatively, QoE measurements may be associated with execution of at least one application or operation that can be executed by UE 115-a.

[0119] In some aspects, the UE 115-a may perform QoE measurements and report the QoE measurements to the network entity 105-a via the QoE report 315. The QoE report 315 may include QoE measurements decoded and identified by the network entity 105-a (e.g., "RAN-visible" or "RAN-aware" QoE parameters), as well as QoE measurements that are not decoded (e.g., are not capable of being decoded) by the network entity 105-a but are passed to the MCE for processing (e.g., "RAN-invisible" or "RAN-unaware" QoE parameters). In other words, the UE 115-a may send a QoE report 315 that includes a container of RAN-invisible measurements / parameters and a set of RAN-visible measurements / parameters outside of the container. In such a case, the network entity 105-a may be configured to decode the set of RAN-visible measurements outside of the container and forward or relay the container including the RAN-invisible measurements to the MCE. In some aspects, the wireless communication system 300 may support RAN-visible parameters for additional service types (eg, AR, MR, MBS) through coordination with the UE application layer.

[0120] As previously described herein, some wireless communication systems may only enable UE 115 to perform and report QoE measurements when operating in an RRC connected state (e.g., RRC_CONNECTED). UE 115 may also receive communications when operating in other states such as RRC idle and inactive states (e.g., RRC_IDLE, RRC_INACTIVE). For example, UE 115-a may receive emergency broadcast messages while in an idle / inactive state. However, due to the fact that some conventional wireless communication systems only enable QoE reporting during a connected state, UE 115-a may not be able to measure and / or report the degraded QoE experienced during an idle / inactive state, which may cause UE 115-a to consistently receive poor QoE for services provided in the idle and inactive states.

[0121] In addition to supporting the performance, reporting, or both of QoE measurements when the UE is in an idle state or an inactive state, techniques as described herein may also advantageously support the use of different QoE measurement and reporting configurations when the UE is in different states (e.g., when in an idle state or an inactive state versus when in a connected state). Using different QoE measurement and reporting configurations when in different states may be beneficial, for example, because when in an idle / inactive state, utilizing the same QoE measurement and reporting configuration across all states may result in increased power consumption (e.g., due to using the same QoE measurement and reporting configuration that is also used in a connected state), thereby reducing the power saving benefits that may otherwise be associated with the idle state and the inactive state, and resulting in increased power consumption at the UE.

[0122] In addition, the performance, reporting, or both of QoE measurements when the UE is in an idle state or an inactive state as described herein may provide additional or alternative benefits compared to other types of measurements. For example, in some cases, the UE may perform minimization of drive test (MDT) measurements (referred to as logged measurements or logged MDT in 3GPP systems) when in an idle state or an inactive state, and may send the MDT measurements together with the QoE report after transitioning to a connected state. However, MDT measurements are associated with a different layer from QoE measurements and serve a different purpose from QoE measurements. In particular, QoE measurements may include higher layer measurements (e.g., application layer measurements), while MDT measurements may include lower layer measurements (e.g., PDCP, RLC, MAC, and physical layer measurements). Additionally, MDT measurements are primarily used for coverage optimization purposes (e.g., to improve coverage across the network), while QoE measurements are related to the relative quality of application services provided by wireless communications sensed or measured at the UE, and therefore may be used, for example, for encoding / decoding to verify or optimize encoder and decoder operations at a network entity (e.g., an application server). Thus, the performance, reporting, or both of QoE measurements while the UE is in an idle or inactive state as described herein may serve different purposes and provide different benefits than other types of measurements, and may enable the network to improve the quality of application services provided through wireless communications experienced to the UE when operating in an idle / inactive state in a manner that such other types of measurements may not support.

[0123] Thus, the wireless communication system 300 may support QoE measurement configurations (e.g., QoE measurement collection) in the RRC_INACTIVE state and the RRC_IDLE state for various applications, including MBS and other broadcast services. In particular, aspects of the present disclosure may support alignment of existing radio-related measurements and QoE reports in the context of QoE measurement configurations that may be used for idle and inactive states. In other words, the techniques described herein may enable the UE 115-a to be configured with QoE measurement and reporting configurations that enable the UE 115-a to perform QoE measurements during the idle / inactive state while enabling the UE 115-a to reduce power consumption when operating in the idle / inactive state. In addition, the QoE measurement and reporting configurations described herein may enable the UE 115-a to transition to a connected state to send a QoE report 315, and / or send a QoE report 315 when operating in an idle / inactive state.

[0124] In some aspects, the UE 115-a may be configured with a single QoE measurement and reporting configuration that may be used for a connected state, an idle state, and an inactive state, wherein parameters of the QoE measurement and reporting configuration (e.g., periodicity of QoE measurements and / or QoE measurement metrics) may be updated as the UE 115-a transitions between states (such as via an RRC release message that releases the UE 115-a from the connected state to the idle / inactive state). In addition or alternatively, the UE 115-a may be configured with separate QoE measurement and reporting configurations for the connected state and the idle / inactive state. In some cases, the UE 115-a may perform QoE measurements while in the idle / inactive state, and the QoE measurements may be stored in a memory until the UE 115-a transitions to the connected state and may transmit a QoE report 315 indicating the stored measurements. The QoE measurement and reporting configuration may include trigger conditions that cause the UE to transition from the idle / inactive state to the connected state to send the QoE report 315. For example, if the QoE measurement drops below a threshold while in the idle / inactive state, the UE 115-a may transition from the idle / inactive state to the connected state to report the degraded QoE measurement experienced during the idle / inactive state.

[0125] Various aspects of the present disclosure may support QoE reporting for a dual connectivity (DC) mode (e.g., NR-DC) at a UE 115-a, which may enable QoE reporting via a secondary node (SN) and in a mobile scenario. Therefore, various aspects of the present disclosure may support QoE measurement configurations for QoE measurement reporting on a master node (MN) and SN for an NR-DC architecture, and these QoE measurement configurations enable QoE measurement reporting over a DC branch to maintain reporting continuity. In other words, various aspects of the present disclosure may support RAN-visible QoE and radio-related measurement configurations and reporting in NR-DC scenarios. In some cases, in the context of NR-DC, UE 115-a may not be configured to perform QoE measurements separately for each branch. The QoE measurement and reporting configurations described herein may specify the alignment of QoE measurements (including traditional QoE and RAN-visible QoE measurements) and radio-related measurements in NR-DC. In addition, the QoE measurement and reporting configuration described in this document may support the continuity of traditional or conventional QoE measurements for streaming media and application services during the intra-5GC inter-RAT handover process.

[0126] In addition, aspects of the present disclosure may support QoE measurement and reporting configurations for various service types defined by SA4 or to be supported by SA4, such as AR, MR, and MBS. In particular, aspects of the present disclosure may enable UE 115-a to report RAN-visible QoE parameters for additional service types, such as MBS services in idle and inactive states. The QoE measurement and reporting configurations described herein may facilitate QoE measurement collection and reporting for all RRC states, such as QoE measurement collection (QMC) and reporting in RRC_INACTIVE and RRC_IDLE states for MBS.

[0127] For example, with reference to the wireless communication system 300, the UE 115-a may receive a control message 310 from the network entity 105-a, wherein the control signaling indicates one or more QoE measurement and reporting configurations. In some implementations, the UE 115-a may receive the control message 310 when operating in a connected state. The control message 310 may include an RRC message (e.g., an RRCReconfiguration message, an RRCRelease message), a DCI message, a MAC-CE message, or any combination thereof. In some aspects, the UE 115-a may be configured with a single QoE measurement and reporting configuration (e.g., a QoE measurement configuration) that may be used for all RRC states, or may be configured with multiple QoE measurement and reporting configurations associated with different states (e.g., usable for different states).

[0128] For example, in some cases, the control message 310 may instruct or configure the UE 115-a with a single QoE measurement and reporting configuration that may be used for all RRC states. In other words, the control message 310 may indicate a single QoE measurement and reporting configuration that may be used for a connected state, an idle state, and an inactive state (e.g., a QoE measurement and reporting configuration that may be used for MBS for all RRC states). In such cases, the control message 310 may include an RRCReconfiguration message, wherein the QoE measurement and reporting configuration is indicated via the OtherConfig field of the RRCReconfiguration message. In some aspects, a single QoE measurement and reporting configuration may be used for all RRC states to measure and report both RAN-visible QoE measurements and RAN-invisible QoE measurements.

[0129] In the case where UE 115-a is configured with a single QoE measurement and reporting configuration for all states, network entity 105-a may update the QoE measurement and reporting configuration when UE 115-a transitions between states. For example, network entity 105-a may release UE 115-a from a connected state to an idle state or an inactive state via an RRCRelease message, wherein the RRCRelease message updates or adjusts one or more parameters of the QoE measurement and reporting configuration for the idle / inactive state. For example, the RRCRelease message may reduce the QoE measurement periodicity or frequency and / or reduce the QoE measurement metric associated with the QoE measurement and reporting configuration, so that UE 115-a can reduce power consumption when operating in an idle / inactive state.

[0130] In additional or alternative implementations, the control message 310 may indicate or configure the UE 115-a with multiple QoE measurement and reporting configurations. For example, the control message 310 may indicate a first QoE measurement and reporting configuration that can be used during a connected state, and a second QoE measurement and reporting configuration that can be used during an idle state and / or an inactive state. In this example, the UE 115-a may be configured to switch between QoE measurement and reporting configurations when the UE 115-a transitions between a connected state and an idle / inactive state. The corresponding QoE measurement and reporting configuration may be indicated via the OtherConfig field of the RRCReconfiguration message. Compared to an implementation in which the UE 115-a is configured with a single QoE measurement and reporting configuration that is adjusted or updated as the UE 115-a transitions between states, configuring the UE 115-a with multiple QoE measurement and reporting configurations may prevent or reduce the need to update the QoE measurement and reporting configurations when the UE 115-a transitions between states.

[0131] In some cases, a first QoE measurement and reporting configuration associated with a connected state may cause the UE 115-a to send both RAN visible QoE measurements and RAN invisible QoE measurements when the UE 115-a is in the connected state (but separately for the MBS in the connected state). Similarly, a second QoE measurement and reporting configuration associated with an idle / inactive state may cause the UE 115-a to send both RAN visible QoE measurements and RAN invisible QoE measurements when the UE 115-a is in the idle / inactive state. In some specific implementations, the network entity 105-a may update the corresponding QoE measurement and reporting configuration, such as via an RRCRelease message sent to the UE 115-a.

[0132] In some specific implementations, the QoE measurement and reporting configuration for both RAN-visible QoE measurement and RAN-invisible QoE measurement (e.g., QoE measurement and reporting configuration for MBS in idle state and inactive state) may be indicated in the RRCRelease message (e.g., control message 310). In the case where the UE 115-a expects but does not receive the RAN-visible QoE configuration in the RRCRelease, the UE 115-a may still consider itself to be configured with the RAN-visible QoE measurement and reporting configuration, or may consider itself to be not configured with the RAN-visible QoE measurement and reporting configuration. That is, in the case where the UE 115-a is released to the idle / inactive state via the RRCRelease message but does not receive the QoE measurement and reporting configuration via the RRCRelease message, the UE 115-a may be configured to perform QoE reporting during the idle / inactive state using the previously configured QoE measurement and reporting configuration, or may be configured to avoid performing QoE reporting during the idle / inactive state based on the absence of the QoE measurement and reporting configuration within the RRCRelease message.

[0133] In some implementations, upon receiving an RRCRelease message (e.g., control message 310) that releases UE 115-a from a connected state to an idle / inactive state, the access stratum (AS) of UE 115-a may transmit an RRCRelease notification to the application (APP) layer of UE 115-a. In such cases, QoE reporting may be suspended, and QoE measurements (e.g., QoE report 315) may be stored at the UE 115-a AS or APP layer until UE 115-a returns to a connected state. In other words, UE 115-a may be configured to perform QoE measurements when operating in an idle / inactive state, and may be configured to store QoE measurements (e.g., in a memory, AS, APP layer) until UE 115-a transitions to a connected state and is able to send a QoE report 315 indicating the stored QoE measurements.

[0134] In some aspects, the control message 310 may indicate one or more trigger conditions associated with the QoE measurement and reporting configuration for reporting QoE measurements to the network. In other words, the UE 115-a may be configured with one or more trigger conditions (e.g., event triggers) that, if met, cause the UE 115-a to transition from an idle / inactive state to a connected state so that the UE 115-a may send a QoE report 315. The trigger conditions for sending the QoE report 315 and / or transitioning to the connected state may be based on any parameters or characteristics, including, but not limited to, the QoE measurements performed by the UE 115-a, the amount of buffered data (e.g., the amount of stored QoE measurements). For example, in some cases, if the quality of the MBS service degrades below a threshold associated with the corresponding QoE measurement and reporting configuration, the trigger conditions for transitioning to the connected state and sending the QoE report 315 may be met. In other words, if the QoE measurement is less than or equal to the threshold, the UE 115-a may identify that the trigger condition for transitioning to the connected state is satisfied. As another example, if the amount of buffered data (e.g., the amount of stored QoE measurements, the size of the QoE report 315) is greater than or equal to the threshold, the UE 115-a may identify that the trigger condition is satisfied. In such cases, the threshold associated with the trigger condition may be configured (e.g., pre-configured) at the UE 115-a, indicated via the control message 310, or both.

[0135] In order to reduce power consumption at UE 115-a while supporting timely reporting of QoE measurements (e.g., RAN-visible QoE measurements, RAN-invisible QoE measurements), the network entity 105-a may be configured to define trigger conditions for QoE measurement and reporting configuration by performing RRC establishment or recovery.

[0136] In some aspects, trigger conditions may be defined for certain service types such as MBS (particularly, when RAN-visible QoE is configured at UE 115-a for MBS). Additionally, in some implementations, control message 310 may indicate separate sets of trigger conditions for RAN-visible QoE measurements and RAN-invisible QoE measurements. For example, in some implementations, the QoE measurement and reporting configuration indicated via control message 310 may include a first set of trigger conditions for RAN-visible QoE measurements and a second set of trigger conditions for RAN-invisible QoE measurements. In such cases, UE 115-a may be configured to transition to a connected state and send a QoE report 315 if a trigger condition from either set of trigger conditions is met.

[0137] Trigger conditions associated with QoE measurement and reporting configurations (e.g., trigger conditions for QoE measurement reporting) may be provided from the MCE to a RAN component of the network entity 105-a, where the RAN component configures the UE 115-a with the QoE measurement and reporting configurations (e.g., the RAN component sends the QoE measurement and reporting configurations to the UE 115-a). For RAN-invisible QoE measurements, the trigger conditions may be defined in a QoE configuration container (e.g., a container for RAN-invisible measurements within a QoE report 315). In contrast, trigger conditions for reporting RAN-visible QoE measurements may be determined by the RAN component of the network entity 105-a and communicated to the UE 115-a via a control message 310 (e.g., OtherConfig in an RRC message, RRCRelease, or RRCReconfiguration message).

[0138] In additional or alternative implementations, trigger conditions associated with QoE measurement and reporting configuration may be configured at the AS layer of UE 115-a. In such cases, the AS layer may be configured to determine whether to trigger RRC establishment or recovery when data is received from the application layer. Alternatively, the trigger conditions may be configured at the application layer of UE 115-a, in which case the application layer may be configured to determine whether to trigger RRC establishment or recovery when data is received from other layers.

[0139] In some implementations, the UE 115-a may change cells (e.g., perform a cell reselection process) while operating in an idle / inactive state. In such cases, upon cell reselection at the UE 115-a, the AS of the UE 115-a may notify the application layer of the UE 115-a of the identity of the new cell (e.g., indicating a new cell identifier (ID)). In such cases, the UE 115-a may be configured to store the new cell ID in a memory / QoE report and add the new cell ID to the next transmitted QoE report 315. In other words, upon transitioning to a connected state, the UE 115-a may be configured to send a QoE report 315 including the stored QoE measurements to the new cell associated with the new cell ID.

[0140] In some aspects, the techniques described herein may allow RRC establishment or resumption for QoE measurements when the UE 115-a is operating in an idle state or an inactive state. Enabling RRC establishment or resumption in the idle / inactive state may improve the execution of ongoing services (e.g., MBS services), including scheduler optimization for ongoing MBS services by transmitting RAN-visible QoE measurements. However, such techniques may result in more frequent QoE reports 315 being sent by the UE 115-a, which may result in increased power consumption at the UE 115-a.

[0141] This article will be about Figure 4 Various aspects of the QoE measurement and reporting configuration described herein (including triggering conditions, inclusion of a global cell ID (GCI) in QoE reports after a cell reselection procedure, and RRC establishment / recovery) are described in further detail.

[0142] In some aspects, a QoE measurement and reporting configuration capable of being used by a UE 115-a during an inactive state (e.g., RRC_INACTIVE) may include or define a unified access control (UAC)-based RRC establishment or resumption for reporting QoE measurements. For example, the RRC layer of the UE 115-a may set the access category value to "8" or another reserved value (e.g., values ​​3 to 10), and the UE 115-a may use an access identifier received from the NAS layer or the RRC layer to request a connection resumption for reporting QoE measurements (e.g., a connection resumption for sending a QoE report 315). In this example, in Msg3 of the random access procedure (e.g., RRCResumeRequest or RRCResumeRequest1), the UE 115-a may be configured to set a new cause value (e.g., QoE-data) to ResumeCause. The new ResumeCause value may be used by the network entity 105-a for access control in an overload scenario. In addition, when the network entity 105-a receives the cause value as "QoE-data", the network entity 105-a can be configured to set up a signaling radio bearer (SRB) (e.g., SRB4) during the recovery process, where the SRB will be used by the UE 115-a to send the QoE report 315.

[0143] Additionally or alternatively, the UE 115-a may be configured to utilize an existing cause value (e.g., MO-data) for RRC resumption in RRCResumeRequest or RRCResumeRequest1 as the resumption cause. In such a case, the UE 115-a may indicate the availability of QoE data (e.g., stored QoE measurements waiting to be reported via the QoE report 315) in Msg5 (e.g., RRCResumeComplete) of the random access procedure. Upon receiving the indication (e.g., via Msg5), the network entity 105-a may be configured to set an SRB (e.g., SRB4) for sending / retrieving the stored QoE measurements (e.g., setting SRB4 for the QoE report 315). In some aspects, if RRC resumption is performed at a different network entity 105 other than the configuring network entity 105-a, the new network entity 105-a may be configured to retrieve the UE 115-a context information (including the QoE configuration) from the previous network entity 105-a.

[0144] In some aspects, the wireless communication system 300 may support techniques for configuring SRBs (e.g., SRB4) for small data transmissions carrying QoE measurements (e.g., setting sdt-SRB4-Indication-r18 ENUMERATED for small data transmissions carrying QoE measurements (at least for RAN-visible QoE measurements)). For example, in some implementations, SRB4 may not be suspended and / or deactivated once UE115-a enters an inactive state.

[0145] This article will be about Figure 5 Techniques associated with QoE reporting during an inactive state (eg, RRC_INACTIVE), including RRC establishment / recovery and establishment of SRBs (eg, SRB4) for QoE reporting, are described in further detail.

[0146] In some aspects, a QoE measurement and reporting configuration capable of being used by a UE 115-a during an idle state (e.g., RRC_IDLE) may include or define a UAC-based RRC establishment for reporting QoE measurements (e.g., for sending a QoE report 315). For example, the UE 115-a may set an access category value to "8" or another reserved value (e.g., values ​​3 to 10). In this example, in Msg3 (e.g., RRCSetupRequest) of a random access procedure, the UE 115-a may be configured to set a new cause value (e.g., QoE-data) to EstablishmentCause, where the new EstablishmentCause value may be used by the network entity 105-a for access control in an overload scenario. In addition, when the network entity 105-a receives the cause value as "QoE-data", the network entity 105-a can be configured to set up an SRB (e.g., SRB4) during the RRCSetup procedure, where the SRB will be used by the UE 115-a to send the QoE report 315.

[0147] Additionally or alternatively, the UE 115-a may be configured to use an existing cause value (e.g., MO-data) for RRC establishment in the RRCSetupRequest as the establishment cause and indicate this. In such a case, the UE 115-a may indicate the availability of QoE data in Msg5 (e.g., RRCSetupComplete) of the random access procedure. Upon receiving the indication (e.g., via Msg5), the network entity 105-a may be configured to set an SRB (e.g., SRB4) for sending / retrieving stored QoE measurements (e.g., setting SRB4 for QoE report 315). During RRC connection establishment, QoE context information (including corresponding QoE configurations that can be used by the UE 115-a) may be passed by the AMF to the NG-RAN in the Initial Context Setup Request message.

[0148] This article will be about Figure 6 Techniques associated with QoE reporting during an idle state (eg, RRC_IDLE), including RRC establishment / resumption and establishment of SRBs (eg, SRB4) for QoE reporting, are described in further detail.

[0149] The techniques described herein may enable UE 115-a to perform QoE measurements when operating in an idle state, an inactive state, or both. Thus, the techniques described herein may enable UE 115-a to inform a network (e.g., network entity 105-a) about the relative quality of application services (e.g., the relative quality of emergency broadcast messages) provided via wireless communications received at UE 115-a during idle and inactive states. Thus, aspects of the present disclosure may enable a network to adjust parameters of wireless communications and application servers to improve the relative quality of application services (e.g., at an application server) and / or schedulers (e.g., at network entity 105-a or gNB) during idle and inactive states. In this regard, aspects of the present disclosure may facilitate improved coordination between UE 115-a and the network, and improve the efficiency and reliability of application services provided via wireless communications received by UE 115-a during inactive and idle states.

[0150] Figure 4 An example of a process flow 400 that supports techniques for QoE measurement and reporting in an idle state and an inactive state in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the process flow 400 may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, or any combination thereof. In particular, the process flow 400 illustrates QoE measurement and reporting configurations that enable a UE 115-b to perform QoE measurements when operating in an idle state or an inactive state, as described with reference to FIG. Figures 1 to 3 and other aspects described.

[0151] Process flow 400 may include UE 115-b and network entity 105-b, which may be as described in reference Figures 1 to 3 Examples of UE 115 and network entity 105 are described. For example, Figure 4 The UE 115-b and the network entity 105-b illustrated in the figure may be respectively as Figure 3 105 - a and a network entity 105 - a are shown in FIG. Figure 4 As shown, process flow 400 illustrates not only signaling between UE 115-b and network entity 105-b, but also signaling between various layers and components of UE 115-b and network entity 105-b. Figure 4 As shown, UE 115-b may include application 405 and AS 410. Similarly, network entity 105-b may include RAN component 415 and MCE / AMF 420.

[0152] In some examples, the operations illustrated by process flow 400 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. The following alternative examples may be implemented in which some of the steps are performed in an order different from the order described or not performed at all. In some cases, the steps may include additional features not mentioned below, or additional steps may be added.

[0153] At 425, the UE 115-b may receive a control message from the network entity 105-b. In some aspects, the control message may indicate one or more QoE measurement and reporting configurations that can be used by the UE 115-b. The QoE measurement and reporting configurations may include rules, conditions, and other parameters for performing QoE measurements, sending QoE reports, or both at the UE 115-b. The control message may include, but is not limited to, RRC signaling, synchronization signal block (SSB) signaling, system information signaling, and the like.

[0154] For example, in some cases, a control message may indicate a single QoE measurement and reporting configuration (e.g., for use when UE 115-b is in a connected state), but the single QoE measurement and reporting configuration may be updated so that a modified (and therefore different) QoE measurement and reporting configuration may be used in one or more other states (e.g., UE 115-b may use the modified configuration when in an idle state or an inactive state). In such cases, the QoE measurement and reporting configuration may be updated or modified when UE 115-b transitions between different states, so that UE 115-b effectively utilizes different “versions” of the QoE measurement and reporting configuration with different sets of parameters when operating in the respective states. As another example, in other cases, a control message may indicate a first QoE measurement and reporting configuration that may be used during a connected state, and a second QoE measurement and reporting configuration that may be used during an idle state and / or an inactive state.

[0155] In some aspects, the control message may indicate one or more additional parameters or characteristics associated with the corresponding QoE measurement and reporting configuration. For example, in some cases, the control message may indicate one or more trigger conditions for QoE reporting. The trigger conditions may include rules or conditions that, when met, cause the UE 115-b to send a QoE report. In particular, when the trigger conditions are met, these trigger conditions may cause the UE 115-b to transition from an idle / inactive state to a connected state in order to send a QoE report. As will be further described in detail herein, the trigger conditions for QoE reporting may be associated with the relative quality of the QoE measurements performed by the UE 115-b, the amount of QoE measurements stored / buffered in a memory, the type of service associated with the UE 115-b, or any combination thereof.

[0156] At 430, while operating in the connected state, the UE 115-b may perform a first set of QoE measurements in accordance with a first QoE measurement and reporting configuration associated with the connected state. In this regard, the UE 115-b may perform QoE measurements at 430 in accordance with the QoE measurement and reporting configuration indicated via the control message at 425. The QoE measurements may include, but are not limited to, BLER measurements, quality measurements, buffer delay measurements, or any combination thereof. The QoE measurements may be associated with a higher layer (e.g., an application layer measurement). The QoE measurements may include RAN-visible QoE measurements (e.g., QoE measurements that can be decoded by the network entity 105-b), RAN-invisible QoE measurements (e.g., QoE measurements that cannot be decoded by the network entity 105-b), or both.

[0157] In some implementations, the first QoE measurement set can be sent to the network entity 105-b at 430. Additionally or alternatively, as will be described in further detail herein, the first QoE measurement set can be stored in a memory and sent at a later time.

[0158] At 435, UE 115-b may receive an additional control message from network entity 105-b that commands UE 115-b to transition from a connected state to an idle state or an inactive state. For example, UE 115-b may receive an RRCRelease message that releases UE 115-b from a connected state to an idle state or an inactive state. UE 115-b may receive the additional control message at 435 based on receiving the control message at 425, performing the first QoE measurement set at 430, or both.

[0159] In some implementations, the additional control message at 435 may update or modify a QoE measurement and reporting configuration that can be used by the UE 115-b during the idle / inactive state, indicate a new QoE measurement and reporting configuration that can be used by the UE 115-b during the idle / inactive state, or both. That is, the additional control message may indicate or update a QoE measurement and reporting configuration associated with a RAN-visible QoE report, a RAN-invisible QoE report (e.g., for an MBS in an idle state or inactive state), or both.

[0160] For example, where UE 115-b is configured with a single QoE measurement and reporting configuration (e.g., a first QoE measurement and reporting configuration), the additional control message may update or modify one or more parameters associated with the first QoE measurement and reporting configuration. In particular, the additional control message may cause UE 115-b to update the one or more parameters in order to generate a modified version of the first QoE measurement and reporting configuration in order to reduce power consumption of the first QoE measurement and reporting configuration used during an inactive / idle state. The parameters of the QoE measurement and reporting configuration that may be modified or updated may include, but are not limited to, a periodicity / frequency of QoE measurements, a QoE measurement metric, a type of QoE measurement, a quality or accuracy of the QoE measurement, or any combination thereof. For example, the additional control message may reduce the periodicity or frequency of QoE measurements performed according to the first QoE measurement and reporting configuration in order to reduce power consumption at UE 115-b.

[0161] As another example, in some cases, the control message may indicate a new QoE measurement and reporting configuration to be used by UE 115-b in the idle / inactive state. For example, the control message at 425 may indicate a first QoE measurement and reporting configuration associated with the connected state, and the additional control message at 435 may indicate a second QoE measurement and reporting configuration associated with the idle / inactive state. In some implementations, the additional control message at 435 may additionally or alternatively indicate one or more parameters associated with the QoE measurement and reporting configuration, such as a trigger condition for a QoE report.

[0162] At 440, UE 115-b may transition from the connected state to an idle state or an inactive state. In particular, UE 115-b may transition to the idle / inactive state in response to receiving the additional control message at 435. Upon transitioning to the idle / inactive state, application 405 of UE 115-b may continue to perform QoE measurements, but may suspend or abort QoE reporting while UE 115-b is in the idle / inactive state.

[0163] At 445, when operating in an idle state or an inactive state, the UE 115-b may perform a second set of QoE measurements in accordance with a second QoE measurement and reporting configuration associated with the idle / inactive state. In this regard, the UE 115-b may perform QoE measurements at 445 in accordance with the QoE measurement and reporting configuration indicated via the control message at 425, via the additional control message at 435, or both. The QoE measurements may include, but are not limited to, BLER measurements, quality measurements, buffer delay measurements, or any combination thereof. The QoE measurements may be associated with a higher layer (e.g., an application layer measurement). The QoE measurements may include RAN-visible QoE measurements (e.g., QoE measurements that can be decoded by the network entity 105-b), RAN-invisible QoE measurements (e.g., QoE measurements that cannot be decoded by the network entity 105-b), or both.

[0164] The first QoE measurement and reporting configuration utilized at 430 and the second QoE measurement and reporting configuration utilized at 445 may be associated with different parameters for QoE reporting (e.g., different measurement periodicities for QoE measurements, different QoE reporting periodicities, different QoE measurement quantities, different QoE measurement qualities). Additionally, in some aspects, the second QoE measurement and reporting configuration may be associated with lower power consumption than the first QoE measurement and reporting configuration. For example, the first QoE measurement and reporting configuration may be associated with a first power consumption at UE 115-b, and the second QoE measurement and reporting configuration may be associated with a second power consumption at UE 115-b that is less than the first power consumption.

[0165] As previously described herein, UE 115-b may be configured with the same QoE measurement and reporting configuration that may be used for a connected state, an idle state, or an inactive state, or may be configured with separate QoE measurement and reporting configurations associated with the respective states. For example, where UE 115-b is configured with a single QoE measurement and reporting configuration, UE 115-b may update or modify the QoE measurement and reporting configuration when transitioning between states. For example, a control message may modify one or more parameters of a first QoE measurement and reporting configuration when releasing UE 115-b to an idle / inactive state. In such cases, the second QoE measurement and reporting configuration utilized at 445 may include a modified version of the first QoE measurement and reporting configuration. Additionally or alternatively, the second QoE measurement and reporting configuration may include a QoE measurement and reporting configuration separate from the first QoE measurement and reporting configuration, wherein the second QoE measurement and reporting configuration is associated with (e.g., designated for) an idle and / or inactive state.

[0166] As previously described herein, the second QoE measurement and reporting configuration may be associated with RAN-visible QoE information (e.g., RAN-aware QoE information), RAN-invisible QoE information (e.g., RAN-unaware QoE information), or both. That is, the second QoE measurement set may include RAN-visible QoE measurements (e.g., QoE measurements that are capable of being decoded by the network entity 105-b), RAN-invisible QoE measurements (e.g., QoE measurements that are not capable of being decoded by the network entity 105-b), or both.

[0167] At 450, the UE 115-b may store (e.g., buffer) at least a second amount of QoE measurements in a memory while operating in an idle / inactive state. In particular, at 450, the UE 115-b may store at least a second set of QoE measurements according to a second QoE measurement and reporting configuration. In the event that the first set of QoE measurements performed at 430 has not yet been sent to the network entity 105-b, the first set of QoE measurements may additionally be stored in the memory so that they may be sent in a next QoE report. In the event that the memory includes QoE measurements performed during a connected state and QoE measurements performed during an idle / inactive state, each respective QoE measurement may be stored together with an identifier indicating during which state the respective QoE measurement was performed.

[0168] At 455, UE 115-b may establish a wireless connection with a new cell when operating in an idle state or an inactive state. That is, UE 115-b may have previously communicated with a first cell and may establish a wireless connection with a second cell that is different from the first cell. In some cases, the first cell and the second cell may be associated with network entity 105-b or a different network entity 105 (e.g., supported by network entity 105-b or a different network entity 105). When establishing a connection with the second cell, AS 410 may send or indicate a cell identifier (ID) associated with the second cell to application 405. UE 115-b may store the cell ID of the second cell in a memory so that the cell ID may be included in the QoE report. That is, UE 115-b may be configured to send subsequent QoE reports to the first cell, the second cell, or both.

[0169] At 460, the UE 115-b may identify satisfaction of a trigger condition for a QoE report while operating in an idle / inactive state. That is, the UE 115-b may identify satisfaction of a trigger condition for sending a QoE report, for transitioning to a connected state, or both. In this regard, the UE 115-b may identify satisfaction of a trigger condition that is indicated or configured via the control message at 425, the additional control message at 435, or both.

[0170] The trigger condition for the QoE report may be associated with a relative quality of QoE measurements performed by the UE 115-b, an amount of QoE measurements stored / buffered in memory, a service type associated with the UE 115-b, or any combination thereof. For example, in the event that the UE 115-b is configured to perform MBS services (e.g., when RAN-visible QoE is configured for MBS at the UE 115-b), the UE 115-b may identify that the trigger condition is satisfied. As another example, in the event that the amount of buffered data (e.g., the amount of QoE measurements stored in memory, the QoE report size) is greater than or equal to a certain threshold, the UE 115-b may identify that the trigger condition is satisfied. As another example, in the event that at least one QoE measurement in the second set of QoE measurements performed at 445 is worse than a threshold (e.g., the QoE measurement is less than or equal to the QoE threshold), the UE 115-b may identify that the trigger condition is satisfied. In some aspects, the threshold for the trigger condition may be indicated via the control message at 425, the additional control message at 435, configured at UE 115-a (e.g., pre-configured), or any combination thereof.

[0171] As previously described herein, in some implementations, the UE 115-b may be able to send a QoE report while operating in an inactive state. In such cases, the UE 115-b may be configured to send a QoE report to the network entity 105-b while in an inactive state upon identifying satisfaction of a trigger condition at 460. For example, in some cases, the network entity 105-b may indicate or configure (e.g., via a control message at 425, via an additional control message at 435) an SRB for QoE reporting (SRB4), and the UE 115-b and the network entity 105-b may be configured to maintain the SRB in an activated state while the UE 115-b is operating in an inactive state. In such cases, the UE 115-b may be configured to send a QoE report via the configured and activated SRB while operating in an inactive state.

[0172] Conversely, in the event that UE 115-b operates in an idle state, UE 115-b may not be able to send a QoE report while in the idle state because DRBs and SRBs may not be able to remain in an activated state while in the idle state (e.g., UE 115-b may release DRBs and SRBs in the RRC_IDLE state). In such a case, process flow 400 may proceed to 465.

[0173] At 465, the UE 115-b and the network entity 105-b may establish (e.g., reestablish) or resume a connection. In other words, the UE 115-b and the network entity 105-b may perform an RRC connection establishment or an RRC connection resumption. In some aspects, the UE 115-b and the network entity 105-b may establish or resume a connection at 465 based on satisfaction of the triggering condition at 460.

[0174] In some cases, at 465, UE 115-b may send a request to establish or resume a wireless connection with network entity 105-b while operating in an idle / inactive state. In other words, UE 115-b may send an RRCResume request message (e.g., RRCResumeRequest, RRCResumeRequest1). Additionally, network entity 105-b may send an acknowledgment message (e.g., RRCResumeComplete message) in response to the request indicating that the RRC connection establishment or RRC connection resumption has been completed. In some cases, such as referring to FIG. Figures 5 and 6 In further detail, the network entity 105-b may indicate or configure an SRB (e.g., SRB4) for QoE reporting as part of the RRC connection establishment / recovery at 465. In such cases, the indicated / configured SRB may be used to send subsequent QoE reports.

[0175] In some aspects, the UE 115-b may perform QoE context retrieval and / or update QoE measurement and reporting configuration as part of establishing / restoring a wireless connection with the network entity 105-b at 465. For example, in some cases, the network entity 105-b may update the QoE measurement and reporting configuration to be used for a connected state, an idle / inactive state, or both.

[0176] At 470, the UE 115-b may transition from the idle / inactive state to the connected state. In particular, the UE 115-b may transition to the connected state at 470 based on establishing a connection with the new cell at 455, identifying satisfaction of a trigger condition at 460, establishing or resuming a connection with the network entity 105-b at 465, or any combination thereof. For example, the UE 115-b may send a request to establish or resume wireless communication with the network entity 105-b at 465, and may transition to the connected state at 470 based on sending the request (e.g., based on receiving a message in response to the request).

[0177] At 475, AS 410 may instruct application 405 to resume QoE reporting and / or update QoE measurement and reporting configuration (if applicable). AS 410 may instruct UE 115-b to resume QoE reporting based on establishing or resuming a connection with network entity 105-b at 465, transitioning to a connected state at 470, or both.

[0178] At 480, the UE 115-b may send a QoE report to the network entity 105-b, wherein the QoE report includes at least a second set of QoE measurements performed in an idle / inactive state at 445, and the second set of QoE measurements is stored in a memory at 450. In some cases, the QoE report may additionally include a first set of QoE measurements performed during a connected state at 430. The UE 115-b may send the QoE report according to the first QoE measurement and reporting configuration, the second QoE measurement and reporting configuration, or both. In the event that the UE 115-b establishes a connection with the second cell at 455, the QoE report may include or indicate a cell ID associated with the second cell. That is, the UE 115-b may send the QoE report to the first cell, the second cell, or both.

[0179] In addition, the UE 115-b may send the QoE report at 480 based on identifying satisfaction of the trigger condition at 460, establishing or resuming a connection with the network entity 105-b at 465, transitioning to a connected state at 470, resuming QoE reporting at 475, or any combination thereof. For example, in some cases, the network entity 105-b may (e.g., in response to a request from the UE 115-b) configure or indicate an SRB (e.g., SRB4) as part of establishing / resuming a wireless connection with the UE 115-b at 465. In such cases, the UE 115-b may send the QoE report to the network entity 105-b via the SRB indicated / configured at 465.

[0180] The techniques described herein may enable UE 115-b to perform QoE measurements when operating in an idle state, an inactive state, or both. Thus, the techniques described herein may enable UE 115-b to inform the network about the relative quality of wireless communications received at UE 115 during idle and inactive states, including the relative quality of emergency broadcast messages. Thus, aspects of the present disclosure may enable the network to adjust parameters of wireless communications to improve the relative quality of such wireless communications received by UE 115-b during idle and inactive states. In this regard, aspects of the present disclosure may facilitate improved coordination between UE 115-b and network entity 105-b, and improve the efficiency and reliability of application services provided by wireless communications received by UE 115-b during inactive and idle states.

[0181] Figure 5 An example of a process flow 500 that supports techniques for QoE measurement and reporting in an idle state and an inactive state in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the process flow 500 may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, the process flow 400, or any combination thereof. In particular, the process flow 500 illustrates QoE measurement and reporting configurations that enable a UE 115-c to perform QoE measurements when operating in an idle state or an inactive state, as described with reference to FIG. Figures 1 to 3 and other aspects described.

[0182] The process flow 500 may include a UE 115-c and a network entity 105-c, which may be as described in reference Figures 1 to 4 Examples of UE 115 and network entity 105 are described. For example, Figure 5 The UE 115-c and the network entity 105-c illustrated in FIG. 1 may be Figure 3 UE 115-a and network entity 105-a or Figure 4 105 - b and the network entity 105 - b are shown in FIG. Figure 5 As shown, process flow 500 illustrates not only signaling between UE 115-c and network entity 105-c, but also signaling between various layers and components of UE 115-c and network entity 105-c. Figure 5 As shown, UE 115 - c may include an application 505 and an RRC component 510 .

[0183] In some examples, the operations illustrated in process flow 500 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. The following alternative examples may be implemented in which some of the steps are performed in an order different from the order described or not performed at all. In some cases, the steps may include additional features not mentioned below, or additional steps may be added.

[0184] At 520, the UE 115-c may be configured to perform QoE measurements when operating in an inactive state. Figure 4 As described at 445 of the process flow 400 illustrated in , the UE 115 - c may be configured to perform QoE measurements according to the QoE measurement and reporting configuration associated with the inactive state.

[0185] At 525, UE 115-c (e.g., application 505 of UE 115-c) may trigger a QoE report. In particular, UE 115-c may trigger a QoE report based on the measurements performed at 520. For example, as described in reference Figure 4 As described at 460 of the process flow 400 illustrated in , the UE 115 - c may be configured to trigger a QoE report based on identifying satisfaction of a trigger condition for the QoE report.

[0186] At 530, the application 505 of the UE 115-c may send a QoE indication (e.g., a QoE reporting indication) to the RRC component 510. The application 505 may send the indication at 530 based on performing QoE measurements at 520, triggering QoE reporting at 530, or both.

[0187] At 535, the UE 115-c may send a request (e.g., RRCResumeRequest, RRCResumeRequest1) to establish or resume wireless communication with the network entity 105-c. The UE 115-c may send the request at 535 based on performing QoE measurements at 520, triggering a QoE report at 525, sending a QoE indication at 530, or any combination thereof.

[0188] In some aspects, a QoE measurement and reporting configuration capable of being used by a UE 115-c during an inactive state (e.g., RRC_INACTIVE) may include or define a UAC-based RRC establishment or resumption for reporting QoE measurements. For example, the RRC layer of the UE 115-c may set the access category value to "8" or another reserved value (e.g., values ​​3 to 10), and the UE 115-c may use an access identifier received from the NAS layer or the RRC layer to request connection resumption for reporting QoE measurements (e.g., connection resumption for sending QoE report 315). For example, in the resumption request at 535 (e.g., in Msg3 of the random access procedure), the UE 115-c may be configured to set a new cause value (e.g., QoE-data) as ResumeCause. The new ResumeCause value may be used by the network entity 105-c for access control in an overload scenario.

[0189] At 540, the UE 115-c may receive a resume message (e.g., RRCResume) from the network entity 105-c in response to the resume request at 535. In other words, the network entity 105-c may acknowledge the request at 535 and indicate that the wireless communication link may be resumed. In some aspects, the network entity 105-c may indicate or configure an SRB (e.g., SRB4) via the resume message at 540. For example, when the network entity 105-c receives a cause value of the resume request as "QoE-data", the network entity 105-c may be configured to set an SRB (e.g., SRB4) during the resume process, wherein the SRB is to be used by the UE 115-c to send QoE reports.

[0190] At 545, the UE 115-c may send a resume complete message (e.g., RRCResumeComplete) to the network entity 105-c. The UE 115-c may send the resume complete message at 545 based on sending the request at 535 and / or in response to receiving the resume message at 540.

[0191] Figure 5 The signal set 515-a illustrated in the example illustrates a first specific implementation in which the UE 115-c utilizes a reserved value for the access category to establish or resume a wireless connection for QoE reporting. In an additional or alternative specific implementation, the UE 115-a may be configured to utilize an existing cause value (e.g., MO-data) for RRC resumption in RRCResumeRequest or RRCResumeRequest1 as a resumption cause, as illustrated via signal set 515-b. Therefore, the corresponding signal sets 515-a, 515-b may be viewed as alternative signaling procedures for establishing or resuming wireless communication for QoE reporting.

[0192] At 550, the UE 115-c and the network entity 105-c may exchange recovery request messages and recovery response messages. The UE 115-c and the network entity 105-c may exchange messages at 550 based on performing QoE measurements at 520, triggering QoE reports at 525, sending QoE indications at 530, or any combination thereof.

[0193] At 555, the UE 115-c may send a recovery complete message (e.g., a RRCResumeComplete message) to the network entity 105-c based on the signaling at 550. In some cases, the recovery complete message may indicate the QoE data availability. In other words, the recovery complete message may indicate that the UE 115-c has QoE measurements to be reported via the QoE report. In this example, the UE 115-c may indicate the availability of the QoE data (e.g., the stored QoE measurements waiting to be reported via the QoE report) in Msg5 (e.g., RRCResumeComplete) of the random access procedure. In this regard, the recovery complete message may include an example of Msg5 of the random access procedure.

[0194] At 560, the UE 115-c may receive a reconfiguration message (e.g., RRCReconfiguration) from the network entity 105-c in response to the recovery complete message at 555. In some aspects, the network entity 105-c may indicate or configure an SRB (e.g., SRB4) via the reconfiguration message at 560. For example, upon receiving an indication of available QoE data via the recovery complete message (e.g., via Msg5), the network entity 105-c may be configured to set an SRB (e.g., SRB4) for sending / retrieving stored QoE measurements (e.g., setting SRB4 for QoE reporting). In some aspects, if RRC recovery is performed at a different network entity 105 other than the configuring network entity 105-a, the new network entity 105 may be configured to retrieve UE 115-a context information (including QoE configuration) from the network entity 105-a.

[0195] After performing the signaling illustrated in the first signal set 515 - a or the second signal set 515 - b , the process flow 500 may proceed to 565 .

[0196] At 565, the RRC component 510 may send a resume indication to the application 505 of the UE 115-c. In particular, the RRC component 510 may send the indication at 565 after setting or configuring an SRB (e.g., SRB4) via the first set of signals 515-a or the second set of signals 515-b.

[0197] At 570, the UE 115-c may send a QoE report to the network entity 105-c, wherein the QoE report includes the QoE measurements performed at 520. In particular, the UE 115-c may send the QoE report to the network entity 105-c via an SRB indicated / configured via the first signal set 515-a or the second signal set 515-b.

[0198] Figure 6 An example of a process flow 600 that supports techniques for QoE measurement and reporting in an idle state and an inactive state in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the process flow 600 may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, the process flow 400, the process flow 500, or any combination thereof. In particular, the process flow 600 illustrates QoE measurement and reporting configurations that enable a UE 115-d to perform QoE measurements when operating in an idle state or an inactive state, as described with reference to FIG. Figures 1 to 5 and other aspects described.

[0199] The process flow 600 may include a UE 115-d and a network entity 105-d, which may be as described in reference Figures 1 to 5 Examples of UE 115 and network entity 105 are described. For example, Figure 6 The UE 115-d and the network entity 105-d illustrated in FIG. 1 may be Figure 3 UE 115-a and network entity 105-a, Figure 4 UE 115-b and network entity 105-b and / or Figure 5 105 - c and the network entity 105 - c. Figure 6 As shown, process flow 600 illustrates not only signaling between UE 115-d and network entity 105-d, but also signaling between various layers and components of UE 115-d and network entity 105-d. Figure 6 As shown, UE 115-d may include application 605, NAS component 610, and RRC component 615. Similarly, network entity 105-d may include RAN component 620 and CN 625.

[0200] In some examples, the operations illustrated in process flow 600 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. The following alternative examples may be implemented in which some of the steps are performed in an order different from that described or not performed at all. In some cases, the steps may include additional features not mentioned below, or additional steps may be added.

[0201] At 630, the UE 115-d may be configured to perform QoE measurements when operating in an idle state. Figure 4 As described at 445 of the process flow 400 illustrated in , the UE 115 - d may be configured to perform QoE measurements according to the QoE measurement and reporting configuration associated with the idle state.

[0202] At 635, UE 115-d (e.g., application 605 of UE 115-d) may trigger a QoE report. In particular, UE 115-d may trigger a QoE report based on the measurements performed at 630. For example, as described in reference Figure 4 As described at 460 of the process flow 400 illustrated in , the UE 115 - d may be configured to trigger a QoE report based on identifying satisfaction of a trigger condition for the QoE report.

[0203] At 640, application 605 of UE 115-d may send a QoE indication (e.g., a QoE reporting indication) to RRC component 615. Application 605 may send the indication at 640 based on performing QoE measurements at 630, triggering QoE reporting at 635, or both.

[0204] At 645, the application 605 of the UE 115-d may send a QoE report (e.g., a QoE report including the QoE measurements performed at 630) to the RRC component 615 of the UE 115-d. In this regard, the application 605 may send the QoE report at 645 based on performing QoE measurements at 630, triggering the QoE report at 635, sending the QoE indication at 640, or any combination thereof.

[0205] At 650, the NAS component 610 and the RRC component 615 can exchange signaling of a NAS packet data unit (PDU) connection for QoE reporting. The NAS component 610 and the RRC component 615 can exchange signaling at 650 based on performing QoE measurements at 630, triggering QoE reporting at 635, receiving QoE indications at 640, receiving QoE reports at 645, or any combination thereof.

[0206] At 655, the RRC component of the UE 115-d and the RAN component of the network entity 105-d may reestablish the wireless connection (e.g., perform an RRC establishment). In some aspects, a QoE measurement and reporting configuration capable of being used by the UE 115-d during an idle state (e.g., RRC_IDLE) may include or define a UAC-based RRC establishment for reporting QoE measurements (e.g., for sending a QoE report). For example, during the RRC establishment at 655, the UE 115-d may set the access category value to "8" or another reserved value (e.g., values ​​3 to 10). In this example, in Msg3 of the random access procedure (e.g., RRCSetupRequest), the UE 115-d may be configured to set a new cause value (e.g., QoE-data) to EstablishmentCause, where the new EstablishmentCause value may be used by the network entity 105-d for access control in an overload scenario. In addition, when the network entity 105-d receives the cause value as "QoE-data", the network entity 105-d can be configured to set up an SRB (e.g., SRB4) during the RRCSetup procedure, where the SRB will be used by the UE 115-d to send QoE reports.

[0207] Additionally or alternatively, the UE 115-d may be configured to use an existing cause value (e.g., MO-data) for RRC establishment in the RRCSetupRequest as the establishment cause and indicate this. In such a case, the UE 115-d may indicate the availability of QoE data in Msg5 (e.g., RRCSetupComplete) of the random access procedure. Upon receiving the indication (e.g., via Msg5), the network entity 105-d may be configured to set an SRB (e.g., SRB4) for sending / retrieving stored QoE measurements (e.g., setting SRB4 for QoE reporting). During the RRC connection establishment, the QoE context information (including the corresponding QoE configuration that can be used by the UE 115-d) may be passed by the AMF to the NG-RAN in the Initial Context Setup Request message.

[0208] At 660, the UE 115-d and the network entity 105-d may exchange signaling for registration or service request. In particular, the UE 115-d and the network entity 105-d may exchange signaling at 660 based on establishing the RRC connection at 655. For example, in some cases, the UE 115-d and the network entity 105-d may exchange signaling for registration or CP service request without user plan resource establishment. Additionally or alternatively, the UE 115-d and the network entity 105-d may exchange signaling for service request to activate user plane resources for MBS service.

[0209] At 665, the RRC component 615 of the UE 115-d may send a setup complete message (e.g., RRCSetupComplete) to the application 605 of the UE 115-d. The RRC component 615 may send the setup complete message at 615 based on establishing the RRC connection at 655, exchanging signaling for registration or service requests at 660, or both.

[0210] At 670, application 605 of UE 115-d may send a QoE report (e.g., a QoE report including the QoE measurements performed at 630) to RRC component 615 of UE 115-d. Application 605 may send the QoE report at 670 based on receiving the setup complete message at 665.

[0211] At 675, the UE 115-d may send a QoE report to the network entity 105-d, wherein the QoE report includes the QoE measurements performed at 630. In particular, the UE 115-d may send the QoE report to the network entity 105-d via the SRB indicated / configured via the RRC setup at 655.

[0212] Figure 7 A block diagram 700 of a device 705 supporting techniques for QoE measurement and reporting in an idle state and an inactive state according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of a UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0213] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for QoE measurement and reporting in idle and inactive states). The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0214] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to techniques for QoE measurement and reporting in idle and inactive states), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0215] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the techniques for QoE measurement and reporting in idle and inactive states as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0216] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0217] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0218] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0219] According to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. For example, the communication manager 720 may be configured to or otherwise support a component for performing a first QoE measurement set according to a first QoE measurement and reporting configuration associated with the connected state when operating in a connected state. The communication manager 720 may be configured to or otherwise support a component for transitioning from a connected state to one of an idle state or an inactive state. The communication manager 720 may be configured to or otherwise support a component for performing a second QoE measurement set according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both when operating in an idle state or an inactive state, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration. The communication manager 720 may be configured to or otherwise support a component for sending a QoE report including at least a second QoE measurement set to a network entity.

[0220] By including or configuring a communication manager 720 according to an example as described herein, the device 705 (e.g., a processor that controls or is otherwise coupled to a receiver 710, a transmitter 715, a communication manager 720, or a combination thereof) may support techniques that enable the UE 115 to perform QoE measurements when operating in an idle state, an inactive state, or both. Thus, the techniques described herein may enable the UE 115 to inform the network about the relative quality of wireless communications received at the UE 115 during an idle state and an inactive state, including the relative quality of emergency broadcast messages. Thus, aspects of the present disclosure may enable the network to adjust parameters of wireless communications to improve the relative quality of such wireless communications received by the UE 115 during an idle state and an inactive state. In this regard, aspects of the present disclosure may facilitate improved coordination between the UE 115 and the network, and improve the efficiency and reliability of application services provided by wireless communications received by the UE 115 during an inactive state and an idle state.

[0221] Figure 8A block diagram 800 of a device 805 supporting techniques for QoE measurement and reporting in an idle state and an inactive state according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0222] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for QoE measurement and reporting in idle and inactive states). The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0223] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to techniques for QoE measurement and reporting in idle and inactive states), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0224] The device 805 or its various components may be examples of components for performing various aspects of the techniques for QoE measurement and reporting in idle and inactive states as described herein. For example, the communication manager 820 may include a QoE measurement manager 825, an operating state manager 830, a QoE report transmission manager 835, or any combination thereof. The communication manager 820 may be an example of various aspects of the communication manager 720 as described herein. In some examples, the communication manager 820 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0225] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. The QoE measurement manager 825 may be configured to or otherwise support a component for performing a first QoE measurement set according to a first QoE measurement and reporting configuration associated with the connected state when operating in a connected state. The operating state manager 830 may be configured to or otherwise support a component for transitioning from a connected state to one of an idle state or an inactive state. The QoE measurement manager 825 may be configured to or otherwise support a component for performing a second QoE measurement set according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both when operating in an idle state or an inactive state, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration. The QoE report sending manager 835 may be configured to or otherwise support a component for sending a QoE report including at least a second QoE measurement set to a network entity.

[0226] Fig. 9 A block diagram 900 of a communication manager 920 supporting techniques for QoE measurement and reporting in idle and inactive states according to one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of means for performing various aspects of the techniques for QoE measurement and reporting in idle and inactive states as described herein. For example, the communication manager 920 may include a QoE measurement manager 925, an operating state manager 930, a QoE report transmission manager 935, a control signaling reception manager 940, a measurement storage manager 945, a trigger condition manager 950, a wireless connection manager 955, a request transmission manager 960, an SRB manager 965, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0227] According to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. The QoE measurement manager 925 may be configured to or otherwise support a component for performing a first QoE measurement set according to a first QoE measurement and reporting configuration associated with the connected state when operating in a connected state. The operating state manager 930 may be configured to or otherwise support a component for transitioning from a connected state to one of an idle state or an inactive state. In some examples, the QoE measurement manager 925 may be configured to or otherwise support a component for performing a second QoE measurement set according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both when operating in an idle state or an inactive state, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration. The QoE report sending manager 935 may be configured to or otherwise support a component for sending a QoE report including at least a second QoE measurement set to a network entity.

[0228] In some examples, the control signaling reception manager 940 may be configured to or otherwise support means for receiving a control message from a network entity commanding the UE to transition from a connected state to an idle state or an inactive state, the control message modifying one or more parameters associated with a first QoE measurement and reporting configuration, wherein the transition to the idle state or the inactive state is based on the control message, and wherein the second QoE measurement and reporting configuration includes a modified version of the first QoE measurement and reporting configuration based on the control message.

[0229] In some examples, the control message includes an RRC release message.

[0230] In some examples, the control signaling reception manager 940 may be configured as or otherwise support a component for receiving a control message indicating a first QoE measurement and reporting configuration and a second QoE measurement and reporting configuration from a network entity, wherein performing the first QoE measurement set, performing the second QoE measurement set, or both is based on the control message.

[0231] In some examples, the control signaling reception manager 940 may be configured to or otherwise support means for receiving a control message from a network entity commanding the UE to transition from a connected state to an idle state or an inactive state, the control message indicating a second QoE measurement and reporting configuration, wherein the transition to the idle state or the inactive state and performing a second QoE measurement set are based on the control message.

[0232] In some examples, the measurement storage manager 945 may be configured to or otherwise support means for storing a second set of QoE measurements in memory according to a second QoE measurement and reporting configuration when operating in an idle state or an inactive state. In some examples, the operating state manager 930 may be configured to or otherwise support means for transitioning from an idle state or an inactive state to a connected state, wherein sending a QoE report occurs after transitioning to the connected state, and based on storing a second set of QoE measurements in memory when operating in an idle state or an inactive state.

[0233] In some examples, trigger condition manager 950 may be configured or otherwise support means for identifying satisfaction of a trigger condition for a QoE report when operating in an idle state or an inactive state. In some examples, operating state manager 930 may be configured or otherwise support means for transitioning from an idle state or an inactive state to a connected state based on satisfaction of the trigger condition, wherein sending the QoE report occurs after transitioning to the connected state.

[0234] In some examples, the control signaling reception manager 940 may be configured to or otherwise support components for receiving a control message from a network entity indicating a set of multiple trigger conditions for QoE reporting, the set of multiple trigger conditions including a trigger condition, wherein identifying satisfaction of the trigger condition is based on the control message.

[0235] In some examples, trigger condition manager 950 may be configured to or otherwise support means for determining that at least one QoE measurement in the second set of QoE measurements is less than or equal to a QoE threshold, wherein identifying satisfaction of the trigger condition is based on at least one QoE measurement being less than or equal to the QoE threshold.

[0236] In some examples, the wireless connection manager 955 may be configured to or otherwise support components for establishing a wireless connection with a second cell different from the first cell when operating in an idle state or an inactive state, wherein based on establishing the wireless connection with the second cell, a QoE report is sent to at least the second cell, and wherein the QoE report includes a cell ID associated with the second cell.

[0237] In some examples, request sending manager 960 may be configured or otherwise support means for sending a request to establish or resume a wireless connection with a network entity when operating in an idle state or an inactive state. In some examples, operating state manager 930 may be configured or otherwise support means for transitioning from an idle state or an inactive state to a connected state based on sending a request, wherein sending a QoE report occurs after transitioning to the connected state.

[0238] In some examples, request sending manager 960 may be configured to or otherwise support means for sending a request to a network entity to establish or resume a wireless connection with the network entity when operating in an idle state or an inactive state. In some examples, SRB manager 965 may be configured to or otherwise support means for receiving an indication of an SRB for QoE reporting from the network entity based on the request, wherein the QoE measurement and reporting configuration are sent via the indicated SRB.

[0239] In some examples, the SRB manager 965 may be configured or otherwise support means for receiving an indication of an SRB associated with wireless communication between the UE and the network entity from a network entity. In some examples, the QoE report transmission manager 935 may be configured or otherwise support means for transmitting a QoE report via the SRB when operating in an inactive state based on maintaining the SRB as active when operating in an inactive state.

[0240] In some examples, the second QoE measurement and reporting configuration is associated with at least RAN-visible QoE information decodable by the network entity. In some examples, the second QoE measurement set includes at least one RAN-visible QoE measurement decodable by the network entity.

[0241] In some examples, the first QoE measurement and reporting configuration is associated with a first parameter set. In some examples, the second QoE measurement and reporting configuration is associated with a second parameter set that is different from the first parameter set. In some examples, the first parameter set, the second parameter set, or both include measurement periodicity, reporting periodicity, measurement quantity, measurement quality, or any combination thereof.

[0242] In some examples, the first QoE measurement and reporting configuration is associated with a first power consumption at the UE. In some examples, the second QoE measurement and reporting configuration is associated with a second power consumption at the UE that is less than the first power consumption.

[0243] Fig.10A diagram of a system 1000 including a device 1005 supporting techniques for QoE measurement and reporting in an idle state and an inactive state according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein, or include components thereof. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

[0244] I / O controller 1010 can manage input and output signals for device 1005. I / O controller 1010 can also manage peripheral devices that are not integrated into device 1005. In some cases, I / O controller 1010 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1010 may be implemented as part of a processor (such as processor 1040). In some cases, a user may interact with device 1005 via I / O controller 1010 or via hardware components controlled by I / O controller 1010.

[0245] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, a wired link, or a wireless link as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1025 for transmission, and for demodulating packets received from one or more antennas 1025. The transceiver 1015 or the transceiver 1015 and the one or more antennas 1025 may be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or any components thereof as described herein.

[0246] Memory 1030 may include random access memory (RAM) and read-only memory (ROM). Memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed by processor 1040, cause device 1005 to perform various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1035 may not be directly executable by processor 1040, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1030 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0247] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks that support techniques for QoE measurement and reporting in idle and inactive states). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform various functions described herein.

[0248] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at the UE. For example, the communication manager 1020 may be configured to or otherwise support a component for performing a first QoE measurement set according to a first QoE measurement and reporting configuration associated with the connected state when operating in a connected state. The communication manager 1020 may be configured to or otherwise support a component for transitioning from the connected state to one of an idle state or an inactive state. The communication manager 1020 may be configured to or otherwise support a component for performing a second QoE measurement set according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both when operating in an idle state or an inactive state, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration. The communication manager 1020 may be configured to or otherwise support a component for sending a QoE report including at least a second QoE measurement set to a network entity.

[0249] By including or configuring a communication manager 1020 according to an example as described herein, the device 1005 may support techniques that enable the UE 115 to perform QoE measurements when operating in an idle state, an inactive state, or both. Thus, the techniques described herein may enable the UE 115 to inform the network about the relative quality of wireless communications received at the UE 115 during an idle state and an inactive state, including the relative quality of emergency broadcast messages. Thus, aspects of the present disclosure may enable the network to adjust parameters of wireless communications to improve the relative quality of such wireless communications received by the UE 115 during an idle state and an inactive state. In this regard, aspects of the present disclosure may facilitate improved coordination between the UE 115 and the network, and improve the efficiency and reliability of application services provided by wireless communications received by the UE 115 during an inactive state and an idle state.

[0250] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions that are executable by the processor 1040 to cause the device 1005 to perform various aspects of the techniques for QoE measurement and reporting in idle and inactive states as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0251] Fig.11 A block diagram 1100 of a device 1105 supporting techniques for QoE measurement and reporting in an idle state and an inactive state according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of a network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0252] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0253] The transmitter 1115 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0254] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the techniques for QoE measurement and reporting in idle and inactive states as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0255] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0256] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0257] In some examples, communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in conjunction with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0258] According to examples as disclosed herein, the communication manager 1120 may support wireless communication at a network entity. For example, the communication manager 1120 may be configured to or otherwise support a component for outputting a first control message to a UE, the first control message indicating a first QoE measurement and reporting configuration for the UE to perform QoE measurement when in a connected state. The communication manager 1120 may be configured to or otherwise support a component for outputting a second QoE measurement and reporting configuration for the UE to perform QoE measurement when in an idle state, an inactive state, or both via a first control message or a second control message. The communication manager 1120 may be configured to or otherwise support a component for obtaining a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in an idle state or an inactive state and according to a second QoE measurement and reporting configuration.

[0259] By including or configuring a communication manager 1120 according to an example as described herein, a device 1105 (e.g., a processor that controls or is otherwise coupled to a receiver 1110, a transmitter 1115, a communication manager 1120, or a combination thereof) may support techniques that enable a UE 115 to perform QoE measurements when operating in an idle state, an inactive state, or both. Thus, the techniques described herein may enable a UE 115 to inform a network about the relative quality of wireless communications received at the UE 115 during an idle state and an inactive state, including the relative quality of emergency broadcast messages. Thus, aspects of the present disclosure may enable a network to adjust parameters of wireless communications to improve the relative quality of such wireless communications received by the UE 115 during an idle state and an inactive state. In this regard, aspects of the present disclosure may facilitate improved coordination between the UE 115 and the network, and improve the efficiency and reliability of application services provided by wireless communications received by the UE 115 during an inactive state and an idle state.

[0260] Fig.12 A block diagram 1200 of a device 1205 supporting techniques for QoE measurement and reporting in an idle state and an inactive state according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or the network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0261] Receiver 1210 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1205. In some examples, receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0262] The transmitter 1215 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0263] The device 1205 or its various components may be examples of components for performing various aspects of the techniques for QoE measurement and reporting in idle and inactive states as described herein. For example, the communication manager 1220 may include a control signaling sending manager 1225, a QoE report receiving manager 1230, or any combination thereof. The communication manager 1220 may be an example of various aspects of the communication manager 1120 as described herein. In some examples, the communication manager 1220 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1210, the transmitter 1215, or both. For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0264] According to an example as disclosed herein, the communication manager 1220 may support wireless communication at a network entity. The control signaling sending manager 1225 may be configured to or otherwise support a component for outputting a first control message to a UE, the first control message indicating a first QoE measurement and reporting configuration for the UE to perform QoE measurement when in a connected state. The control signaling sending manager 1225 may be configured to or otherwise support a component for outputting a second QoE measurement and reporting configuration for the UE to perform QoE measurement when in an idle state, an inactive state, or both via a first control message or a second control message. The QoE report receiving manager 1230 may be configured to or otherwise support a component for obtaining a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in an idle state or an inactive state and according to a second QoE measurement and reporting configuration.

[0265] Fig.13 A block diagram 1300 of a communication manager 1320 supporting techniques for QoE measurement and reporting in an idle state and an inactive state is shown according to one or more aspects of the present disclosure. The communication manager 1320 can be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components can be examples of means for performing various aspects of the techniques for QoE measurement and reporting in an idle state and an inactive state as described herein. For example, the communication manager 1320 may include a control signaling sending manager 1325, a QoE report receiving manager 1330, a trigger condition manager 1335, a request receiving manager 1340, an SRB manager 1345, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0266] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. The control signaling sending manager 1325 may be configured to or otherwise support a component for outputting a first control message to a UE, the first control message indicating a first QoE measurement and reporting configuration for the UE to perform QoE measurements when in a connected state. In some examples, the control signaling sending manager 1325 may be configured to or otherwise support a component for outputting a second QoE measurement and reporting configuration for the UE to perform QoE measurements when in an idle state, an inactive state, or both via a first control message or a second control message. The QoE report receiving manager 1330 may be configured to or otherwise support a component for obtaining a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in an idle state or an inactive state and according to a second QoE measurement and reporting configuration.

[0267] In some examples, the second control message commands the UE to transition from a connected state to an idle state or an inactive state, and the second control message modifies one or more parameters associated with the first QoE measurement and reporting configuration. In some examples, the second QoE measurement and reporting configuration includes a modified version of the first QoE measurement and reporting configuration based on the second control message. In some examples, the second control message includes an RRC release message.

[0268] In some examples, the second control message commands the UE to transition from a connected state to an idle state or an inactive state, and the second control message indicates a second QoE measurement and reporting configuration. In some examples, obtaining the QoE report is based on the second control message.

[0269] In some examples, the trigger condition manager 1335 may be configured to or otherwise support a component for indicating a set of multiple trigger conditions for QoE reporting to the UE via a first control message, a second control message, an additional control message, or any combination thereof, wherein receiving the QoE report is based on the satisfaction of the trigger condition from the set of multiple trigger conditions.

[0270] In some examples, request reception manager 1340 may be configured as or otherwise support means for obtaining a request from a UE to establish or resume a wireless connection with a network entity, wherein obtaining the QoE report occurs after the wireless connection is established or resumed.

[0271] In some examples, request reception manager 1340 may be configured to or otherwise support means for obtaining a request from a UE to establish or resume a wireless connection with a network entity. In some examples, SRB manager 1345 may be configured to or otherwise support means for outputting to the UE an indication of an SRB for QoE reporting based on the request, wherein the QoE measurement and reporting configuration is obtained via the indicated SRB.

[0272] In some examples, SRB manager 1345 may be configured or otherwise support means for outputting to the UE an indication of an SRB associated with wireless communications between the UE and a network entity. In some examples, QoE report reception manager 1330 may be configured or otherwise support means for obtaining a QoE report from the UE via the SRB based on the SRB being maintained as active when the UE is in an inactive state.

[0273] In some examples, the second QoE measurement and reporting configuration is associated with at least RAN-visible QoE information decodable by the network entity. In some examples, the QoE measurement set includes at least one RAN-visible QoE measurement decodable by the network entity.

[0274] In some examples, the first QoE measurement and reporting configuration is associated with a first parameter set. In some examples, the second QoE measurement and reporting configuration is associated with a second parameter set that is different from the first parameter set. In some examples, the first parameter set, the second parameter set, or both include measurement periodicity, reporting periodicity, measurement quantity, measurement quality, or any combination thereof.

[0275] In some examples, the first QoE measurement and reporting configuration is associated with a first power consumption at the UE. In some examples, the second QoE measurement and reporting configuration is associated with a second power consumption at the UE that is less than the first power consumption.

[0276] Fig.14A diagram of a system 1400 including a device 1405 supporting techniques for QoE measurement and reporting in an idle state and an inactive state according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 as described herein, or include components thereof. The device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1405 may include components that support output and acquisition of communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1440).

[0277] The transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1410 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1415, from a wired receiver), and for demodulating a signal. Where applicable, transceiver 1410 or transceiver 1410 and one or more antennas 1415 or wired interfaces may be examples of transmitter 1115, transmitter 1215, receiver 1110, receiver 1210, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0278] Memory 1425 may include RAM and ROM. Memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by processor 1435, cause device 1405 to perform various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by processor 1435, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1425 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0279] Processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks that support techniques for QoE measurement and reporting in idle and inactive states). For example, device 1405 or a component of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435, and processor 1435 and memory 1425 are configured to perform various functions described herein. Processor 1435 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1430) to perform the functions of device 1405.

[0280] In some examples, bus 1440 may support communications of a protocol layer of a protocol stack (e.g., within the protocol layer). In some examples, bus 1440 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communications performed within a component of device 1405 or between different components of device 1405 that may be co-located or located in different locations (e.g., where device 1405 may refer to a system where one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one of the different components or divided between the different components).

[0281] In some examples, the communication manager 1420 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1420 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1420 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UE 115 in coordination with the other network entities 105. In some examples, the communication manager 1420 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0282] According to examples as disclosed herein, the communication manager 1420 may support wireless communications at a network entity. For example, the communication manager 1420 may be configured to or otherwise support a component for outputting a first control message to a UE, the first control message indicating a first QoE measurement and reporting configuration for the UE to perform QoE measurements when in a connected state. The communication manager 1420 may be configured to or otherwise support a component for outputting a second QoE measurement and reporting configuration for the UE to perform QoE measurements when in an idle state, an inactive state, or both via a first control message or a second control message. The communication manager 1420 may be configured to or otherwise support a component for obtaining a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in an idle state or an inactive state and according to a second QoE measurement and reporting configuration.

[0283] By including or configuring a communication manager 1420 according to an example as described herein, the device 1405 may support techniques that enable the UE 115 to perform QoE measurements when operating in an idle state, an inactive state, or both. Thus, the techniques described herein may enable the UE 115 to inform the network about the relative quality of wireless communications received at the UE 115 during an idle state and an inactive state, including the relative quality of emergency broadcast messages. Thus, aspects of the present disclosure may enable the network to adjust parameters of wireless communications to improve the relative quality of such wireless communications received by the UE 115 during an idle state and an inactive state. In this regard, aspects of the present disclosure may facilitate improved coordination between the UE 115 and the network, and improve the efficiency and reliability of application services provided by wireless communications received by the UE 115 during an inactive state and an idle state.

[0284] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1435, the memory 1425, the code 1430, the transceiver 1410, or any combination thereof. For example, the code 1430 may include instructions that are executable by the processor 1435 to cause the device 1405 to perform various aspects of the techniques for QoE measurement and reporting in idle and inactive states as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0285] Fig.15 A flow chart illustrating a method 1500 for supporting techniques for QoE measurement and reporting in idle and inactive states according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0286] At 1505, the method may include, while operating in a connected state, performing a first set of QoE measurements according to a first QoE measurement and reporting configuration associated with the connected state. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The described QoE measurement manager 925 is performed.

[0287] At 1510, the method may include transitioning from a connected state to one of an idle state or an inactive state. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The described operating state manager 930 is performed.

[0288] At 1515, the method may include, while operating in an idle state or an inactive state, performing a second set of QoE measurements according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Fig. 9 The described QoE measurement manager 925 is performed.

[0289] At 1520, the method may include sending a QoE report including at least a second set of QoE measurements to a network entity. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Fig. 9 The described QoE report is sent to the manager 935 to perform.

[0290] Fig.16 A flow chart illustrating a method 1600 of supporting techniques for QoE measurement and reporting in idle and inactive states according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0291] At 1605, the method may include, while operating in a connected state, performing a first set of QoE measurements according to a first QoE measurement and reporting configuration associated with the connected state. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig. 9 The described QoE measurement manager 925 is performed.

[0292] At 1610, the method may include receiving a control message from a network entity commanding the UE to transition from a connected state to an idle state or an inactive state, the control message modifying one or more parameters associated with the first QoE measurement and reporting configuration. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig. 9 The described control signaling reception manager 940 is executed.

[0293] At 1615, the method may include transitioning from the connected state to one of an idle state or an inactive state, wherein the transition to the idle state or the inactive state is based on a control message. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig. 9 The described operating state manager 930 is performed.

[0294] At 1620, the method may include, when operating in an idle state or an inactive state, performing a second set of QoE measurements according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both, and wherein the second QoE measurement and reporting configuration includes a modified version of the first QoE measurement and reporting configuration based on the control message. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig. 9 The described QoE measurement manager 925 is performed.

[0295] At 1625, the method may include sending a QoE report including at least a second set of QoE measurements to a network entity. The operations of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Fig. 9 The described QoE report is sent to the manager 935 to perform.

[0296] Fig.17 A flowchart illustrating a method 1700 of supporting techniques for QoE measurement and reporting in idle and inactive states according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0297] At 1705, the method may include, while operating in a connected state, performing a first set of QoE measurements according to a first QoE measurement and reporting configuration associated with the connected state. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig. 9 The described QoE measurement manager 925 is performed.

[0298] At 1710, the method may include transitioning from a connected state to one of an idle state or an inactive state. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig. 9 The described operating state manager 930 is performed.

[0299] At 1715, the method may include, while operating in an idle state or an inactive state, performing a second set of QoE measurements according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig. 9 The described QoE measurement manager 925 is performed.

[0300] At 1720, the method may include, when operating in an idle state or an inactive state, storing a second set of QoE measurements in a memory according to a second QoE measurement and reporting configuration. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig. 9 The described measurement storage manager 945 is executed.

[0301] At 1725, the method may include transitioning from an idle state or an inactive state to a connected state. The operations of 1725 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Fig. 9 The described operating state manager 930 is performed.

[0302] At 1730, the method may include sending a QoE report including at least a second QoE measurement set to a network entity, wherein sending the QoE report occurs after transitioning to a connected state, and is based on storing the second QoE measurement set in a memory when operating in an idle state or an inactive state. The operations of 1730 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1730 may be performed as described in reference to Fig. 9 The described QoE report is sent to the manager 935 to perform.

[0303] Fig.18 A flow chart illustrating a method 1800 of supporting techniques for QoE measurement and reporting in idle and inactive states according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 6 as well as Figures 11 to 14In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0304] At 1805, the method may include outputting a first control message to the UE indicating a first QoE measurement and reporting configuration for the UE to use to perform QoE measurements when in a connected state. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.13 The described control signaling is performed by sending manager 1325.

[0305] At 1810, the method may include outputting to the UE via the first control message or the second control message a second QoE measurement and reporting configuration for the UE to use to perform QoE measurements when in an idle state, an inactive state, or both. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.13 The described control signaling is performed by sending manager 1325.

[0306] At 1815, the method may include obtaining a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in an idle state or an inactive state and according to a second QoE measurement and reporting configuration. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.13 The described QoE report receiving manager 1330 is executed.

[0307] The following provides an overview of various aspects of the present disclosure:

[0308] Aspect 1: A method for wireless communication at a UE, comprising: when operating in a connected state, performing a first QoE measurement set according to a first QoE measurement and reporting configuration associated with the connected state; transitioning from the connected state to one of an idle state or an inactive state; when operating in the idle state or the inactive state, performing a second QoE measurement set according to a second QoE measurement and reporting configuration associated with the idle state, the inactive state, or both, the second QoE measurement and reporting configuration being different from the first QoE measurement and reporting configuration; and sending a QoE report including at least the second QoE measurement set to a network entity.

[0309] Aspect 2: The method according to Aspect 1 also includes: receiving a control message from the network entity commanding the UE to transition from the connected state to the idle state or the inactive state, the control message modifying one or more parameters associated with the first QoE measurement and reporting configuration, wherein the transition to the idle state or the inactive state is at least partially based on the control message, and wherein the second QoE measurement and reporting configuration includes a modified version of the first QoE measurement and reporting configuration based at least partially on the control message.

[0310] Aspect 3: The method according to Aspect 2, wherein the control message includes an RRC release message.

[0311] Aspect 4: The method according to any one of Aspects 1 to 3 further includes: receiving a control message indicating the first QoE measurement and reporting configuration and the second QoE measurement and reporting configuration from the network entity, wherein performing the first QoE measurement set, performing the second QoE measurement set, or performing both is at least partially based on the control message.

[0312] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: receiving a control message from the network entity commanding the UE to transition from the connected state to the idle state or the inactive state, the control message indicating the second QoE measurement and reporting configuration, wherein the transition to the idle state or the inactive state and the execution of the second QoE measurement set are at least partially based on the control message.

[0313] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: when operating in the idle state or the inactive state, storing the second QoE measurement set in a memory according to the second QoE measurement and reporting configuration; and transitioning from the idle state or the inactive state to the connected state, wherein sending the QoE report occurs after transitioning to the connected state and is at least partially based on storing the second QoE measurement set in the memory when operating in the idle state or the inactive state.

[0314] Aspect 7: The method according to any one of Aspects 1 to 6 further includes: when operating in the idle state or the inactive state, identifying the satisfaction of a trigger condition for QoE reporting; and transitioning from the idle state or the inactive state to the connected state based at least in part on the satisfaction of the trigger condition, wherein sending the QoE report occurs after transitioning to the connected state.

[0315] Aspect 8: The method according to Aspect 7 further includes: receiving a control message indicating multiple trigger conditions for QoE reporting from the network entity, the multiple trigger conditions including the trigger condition, wherein the identification of the satisfaction of the trigger condition is at least partially based on the control message.

[0316] Aspect 9: The method according to any one of Aspects 7 to 8 further includes: determining that at least one QoE measurement in the second QoE measurement set is less than or equal to a QoE threshold, wherein the identification of the satisfaction of the trigger condition is at least partially based on the at least one QoE measurement being less than or equal to the QoE threshold.

[0317] Aspect 10: A method according to any one of Aspects 1 to 9, wherein operating in the connected state includes communicating with a first cell, and the method further includes: when operating in the idle state or the inactive state, establishing a wireless connection with a second cell different from the first cell, wherein the QoE report is sent to at least the second cell at least partially based on establishing the wireless connection with the second cell, and wherein the QoE report includes a cell identifier associated with the second cell.

[0318] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: when operating in the idle state or the inactive state, sending a request to the network entity to establish or resume a wireless connection with the network entity; and transitioning from the idle state or the inactive state to the connected state based at least in part on sending the request, wherein sending the QoE report occurs after transitioning to the connected state.

[0319] Aspect 12: The method according to any one of Aspects 1 to 11 further includes: when operating in the idle state or the inactive state, sending a request to the network entity to establish or resume a wireless connection with the network entity; and receiving an indication of a signaling radio bearer for QoE reporting from the network entity based at least in part on the request, wherein the QoE measurement and reporting configuration is sent via the indicated signaling radio bearer.

[0320] Aspect 13: The method according to any one of Aspects 1 to 12 further includes: receiving an indication of a signaling radio bearer associated with wireless communication between the UE and the network entity from the network entity; and sending the QoE report via the signaling radio bearer when operating in the inactive state based at least in part on maintaining the signaling radio bearer active when operating in the inactive state.

[0321] Aspect 14: A method according to any one of Aspects 1 to 13, wherein the second QoE measurement and reporting configuration is associated with at least radio access network-aware QoE information that can be decoded by the network entity, and the second QoE measurement set includes at least one radio access network-visible QoE measurement that can be decoded by the network entity.

[0322] Aspect 15: A method according to any one of Aspects 1 to 14, wherein the first QoE measurement and reporting configuration is associated with a first parameter set, and the second QoE measurement and reporting configuration is associated with a second parameter set different from the first parameter set, and the first parameter set, the second parameter set, or both include measurement periodicity, reporting periodicity, measurement quantity, measurement quality, or any combination thereof.

[0323] Aspect 16: A method according to any one of Aspects 1 to 15, wherein the first QoE measurement and reporting configuration is associated with a first power consumption at the UE, and the second QoE measurement and reporting configuration is associated with a second power consumption at the UE that is less than the first power consumption.

[0324] Aspect 17: A method for performing wireless communications at a network entity, comprising: outputting a first control message to a UE, the first control message indicating a first QoE measurement and reporting configuration for the UE to perform QoE measurement when in a connected state; outputting a second QoE measurement and reporting configuration to the UE via the first control message or the second control message for the UE to perform QoE measurement when in an idle state, an inactive state, or both; and obtaining a QoE report from the UE, the QoE report including a set of QoE measurements performed when the UE is operating in the idle state or the inactive state and according to the second QoE measurement and reporting configuration.

[0325] Aspect 18: A method according to Aspect 17, wherein the second control message commands the UE to transition from the connected state to the idle state or the inactive state, and the second control message modifies one or more parameters associated with the first QoE measurement and reporting configuration, and the second QoE measurement and reporting configuration includes a modified version of the first QoE measurement and reporting configuration based at least in part on the second control message.

[0326] Aspect 19: The method according to Aspect 18, wherein the second control message comprises an RRC release message.

[0327] Aspect 20: A method according to any one of Aspects 17 to 19, wherein the second control message commands the UE to transition from the connected state to the idle state or the inactive state, and the second control message indicates the second QoE measurement and reporting configuration, and obtaining the QoE report is at least partially based on the second control message.

[0328] Aspect 21: The method according to any one of Aspects 17 to 20 further includes: indicating multiple trigger conditions for QoE reporting to the UE via the first control message, the second control message, an additional control message, or any combination thereof, wherein receiving the QoE report is at least partially based on the satisfaction of a trigger condition from the multiple trigger conditions.

[0329] Aspect 22: The method according to any one of Aspects 17 to 21 further includes: obtaining, from the UE, a request to establish or resume a radio connection with the network entity, wherein obtaining the QoE report occurs after the radio connection is established or resumed.

[0330] Aspect 23: The method according to any one of Aspects 17 to 22 further includes: obtaining a request from the UE to establish or resume a wireless connection with the network entity; and outputting an indication of a signaling radio bearer for QoE reporting to the UE based at least in part on the request, wherein the QoE measurement and reporting configuration is obtained via the indicated signaling radio bearer.

[0331] Aspect 24: The method according to any one of Aspects 17 to 23 further includes: outputting to the UE an indication of a signaling radio bearer associated with wireless communication between the UE and the network entity; and obtaining the QoE report from the UE via the signaling radio bearer based at least in part on the signaling radio bearer being maintained as active when the UE is in the inactive state.

[0332] Aspect 25: A method according to any one of Aspects 17 to 24, wherein the second QoE measurement and reporting configuration is associated with at least radio access network-aware QoE information that can be decoded by the network entity, and the QoE measurement set includes at least one radio access network-visible QoE measurement that can be decoded by the network entity.

[0333] Aspect 26: A method according to any one of Aspects 17 to 25, wherein the first QoE measurement and reporting configuration is associated with a first parameter set, and the second QoE measurement and reporting configuration is associated with a second parameter set different from the first parameter set, and the first parameter set, the second parameter set, or both include measurement periodicity, reporting periodicity, measurement quantity, measurement quality, or any combination thereof.

[0334] Aspect 27: A method according to any one of Aspects 17 to 26, wherein the first QoE measurement and reporting configuration is associated with a first power consumption at the UE, and the second QoE measurement and reporting configuration is associated with a second power consumption at the UE that is less than the first power consumption.

[0335] Aspect 28: An apparatus for performing wireless communications at a UE, 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 a method according to any one of Aspects 1 to 16.

[0336] Aspect 29: An apparatus for wireless communication at a UE, comprising at least one component for performing a method according to any one of aspects 1 to 16.

[0337] Aspect 30: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 16.

[0338] Aspect 31: An apparatus for wireless communication at a network entity, 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 a method according to any one of Aspects 17 to 27.

[0339] Aspect 32: An apparatus for wireless communication at a network entity, comprising at least one means for performing a method according to any one of aspects 17 to 27.

[0340] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 17 to 27.

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

[0342] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0343] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0344] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0345] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0346] Computer-readable media include both non-transient computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another.Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer.By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices or can be used to carry or store desired program code components and any other non-transient medium that can be accessed by a general or special-purpose computer or a general or special-purpose processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable media.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0347] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0348] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0349] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second or other subsequent reference labels.

[0350] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0351] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: while operating in a connected state, performing a first set of quality of experience measurements in accordance with a first quality of experience measurement and reporting configuration associated with the connected state; transitioning from the connected state to one of an idle state or an inactive state; while operating in the idle state or the inactive state, performing a second set of quality of experience measurements according to a second quality of experience measurement and reporting configuration associated with the idle state, the inactive state, or both, the second quality of experience measurement and reporting configuration being different from the first quality of experience measurement and reporting configuration; as well as Sending a quality of experience report including at least the second quality of experience measurement set to a network entity.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving a control message from the network entity commanding the UE to transition from the connected state to the idle state or the inactive state, the control message modifying one or more parameters associated with the first quality of experience measurement and reporting configuration, wherein transitioning to the idle state or the inactive state is based at least in part on the control message, and wherein the second quality of experience measurement and reporting configuration comprises a modified version of the first quality of experience measurement and reporting configuration based at least in part on the control message.

3. The apparatus of claim 2, wherein the control message comprises a radio resource control release message.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A control message is received from the network entity indicating the first quality of experience measurement and reporting configuration and the second quality of experience measurement and reporting configuration, wherein performing the first quality of experience measurement set, performing the second quality of experience measurement set, or both is based at least in part on the control message.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a control message from the network entity commanding the UE to transition from the connected state to the idle state or the inactive state, the control message indicating the second quality of experience measurement and reporting configuration, wherein transitioning to the idle state or the inactive state and performing the second set of quality of experience measurements are based at least in part on the control message.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: When operating in the idle state or the inactive state, storing the second quality of experience measurement set in a memory according to the second quality of experience measurement and reporting configuration; and and transitioning from the idle state or the inactive state to the connected state, wherein sending the quality of experience report occurs after transitioning to the connected state and is based at least in part on storing the second quality of experience measurement set in a memory while operating in the idle state or the inactive state.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: identifying satisfaction of a trigger condition for quality of experience reporting when operating in the idle state or the inactive state; and Based at least in part on the satisfaction of the trigger condition, transitioning from the idle state or the inactive state to the connected state, wherein sending the quality of experience report occurs after transitioning to the connected state.

8. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: A control message is received from the network entity indicating a plurality of trigger conditions for quality of experience reporting, the plurality of trigger conditions including the trigger condition, wherein identifying the satisfaction of the trigger condition is based at least in part on the control message.

9. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: Determining that at least one quality of experience measurement in the second quality of experience measurement set is less than or equal to a quality of experience threshold, wherein identifying the satisfaction of the trigger condition is based at least in part on the at least one quality of experience measurement being less than or equal to the quality of experience threshold.

10. The apparatus of claim 1, wherein operating in the connected state comprises communicating with a first cell, wherein the instructions are further executable by the processor to cause the apparatus to: While operating in the idle state or the inactive state, a radio connection is established with a second cell different from the first cell, wherein the quality of experience report is sent to at least the second cell based at least in part on establishing the radio connection with the second cell, and wherein the quality of experience report includes a cell identifier associated with the second cell.

11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: When operating in the idle state or the inactive state, sending to the network entity a request to establish or resume a wireless connection with the network entity; and Based at least in part on sending the request, transitioning from the idle state or the inactive state to the connected state, wherein sending the quality of experience report occurs after transitioning to the connected state.

12. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: When operating in the idle state or the inactive state, sending to the network entity a request to establish or resume a wireless connection with the network entity; and Based at least in part on the request, an indication of a signaling radio bearer for a quality of experience report is received from the network entity, wherein the quality of experience report is sent via the indicated signaling radio bearer.

13. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving, from the network entity, an indication of a signaling radio bearer associated with wireless communication between the UE and the network entity; and Based at least in part on maintaining the signaling radio bearer active while operating in the inactive state, the quality of experience report is sent via the signaling radio bearer while operating in the inactive state.

14. The apparatus of claim 1 , wherein the second quality of experience measurement and reporting configuration is associated with at least radio access network visible quality of experience information decodable by the network entity, and wherein the second quality of experience measurement set comprises at least one radio access network visible quality of experience measurement decodable by the network entity.

15. The apparatus of claim 1 , wherein the first quality of experience measurement and reporting configuration is associated with a first set of parameters, and the second quality of experience measurement and reporting configuration is associated with a second set of parameters different from the first set of parameters, wherein the first set of parameters, the second set of parameters, or both include measurement periodicity, reporting periodicity, measurement quantity, measurement quality, or any combination thereof.

16. The apparatus of claim 1, wherein the first quality of experience measurement and reporting configuration is associated with a first power consumption at the UE, and the second quality of experience measurement and reporting configuration is associated with a second power consumption at the UE that is less than the first power consumption.

17. An apparatus for wireless communication at a network entity, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: outputting a first control message to a user equipment (UE), the first control message indicating a first quality of experience measurement and reporting configuration for the UE to use to perform quality of experience measurement when in a connected state; outputting, to the UE via the first control message or the second control message, a second quality of experience measurement and reporting configuration for use by the UE to perform quality of experience measurement when the UE is in an idle state, an inactive state, or both; as well as A quality of experience report is obtained from the UE, the quality of experience report comprising a set of quality of experience measurements performed while the UE is operating in the idle state or the inactive state and in accordance with the second quality of experience measurement and reporting configuration.

18. The apparatus of claim 17, wherein the second control message commands the UE to transition from the connected state to the idle state or the inactive state, and the second control message modifies one or more parameters associated with the first quality of experience measurement and reporting configuration, and wherein the second quality of experience reporting measurement and reporting configuration comprises a modified version of the first quality of experience measurement and reporting configuration based at least in part on the second control message.

19. The apparatus of claim 18, wherein the second control message comprises a radio resource control release message.

20. The apparatus of claim 17, wherein the second control message commands the UE to transition from the connected state to the idle state or the inactive state, and the second control message indicates the second quality of experience measurement and reporting configuration, and wherein obtaining the quality of experience report is based at least in part on the second control message.

21. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: A plurality of trigger conditions for quality of experience reporting is indicated to the UE via the first control message, the second control message, an additional control message, or any combination thereof, wherein obtaining the quality of experience report is based at least in part on satisfying a trigger condition from the plurality of trigger conditions.

22. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: A request is obtained from the UE to establish or resume a radio connection with the network entity, wherein obtaining the quality of experience report occurs after the radio connection is established or resumed.

23. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: obtaining, from the UE, a request to establish or resume a radio connection with the network entity; and Based at least in part on the request, an indication of a signaling radio bearer for a quality of experience report is output to the UE, wherein the quality of experience report is obtained via the indicated signaling radio bearer.

24. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: outputting to the UE an indication of a signaling radio bearer associated with wireless communication between the UE and the network entity; and Based at least in part on the signaling radio bearer being maintained active while the UE is in the inactive state, obtaining the quality of experience report from the UE via the signaling radio bearer.

25. The apparatus of claim 17, wherein the second quality of experience measurement and reporting configuration is associated with at least radio access network visible quality of experience information decodable by the network entity, and wherein the quality of experience measurement set comprises at least one radio access network visible quality of experience measurement decodable by the network entity.

26. The apparatus of claim 17, wherein the first quality of experience measurement and reporting configuration is associated with a first set of parameters, and the second quality of experience measurement and reporting configuration is associated with a second set of parameters different from the first set of parameters, wherein the first set of parameters, the second set of parameters, or both include measurement periodicity, reporting periodicity, measurement quantity, measurement quality, or any combination thereof.

27. The apparatus of claim 17, wherein the first quality of experience measurement and reporting configuration is associated with a first power consumption at the UE, and the second quality of experience measurement and reporting configuration is associated with a second power consumption at the UE that is less than the first power consumption.

28. A method for wireless communication at a user equipment (UE), comprising: while operating in a connected state, performing a first set of quality of experience measurements in accordance with a first quality of experience measurement and reporting configuration associated with the connected state; transitioning from the connected state to one of an idle state or an inactive state; while operating in the idle state or the inactive state, performing a second set of quality of experience measurements according to a second quality of experience measurement and reporting configuration associated with the idle state, the inactive state, or both, the second quality of experience measurement and reporting configuration being different from the first quality of experience measurement and reporting configuration; as well as Sending a quality of experience report including at least the second quality of experience measurement set to a network entity.

29. The method according to claim 28, further comprising: receiving a control message from the network entity commanding the UE to transition from the connected state to the idle state or the inactive state, the control message modifying one or more parameters associated with the first quality of experience measurement and reporting configuration, wherein transitioning to the idle state or the inactive state is based at least in part on the control message, and wherein the second quality of experience measurement and reporting configuration comprises a modified version of the first quality of experience measurement and reporting configuration based at least in part on the control message.

30. A method for wireless communication at a network entity, comprising: outputting a first control message to a user equipment (UE), the first control message indicating a first quality of experience measurement and reporting configuration for the UE to use to perform quality of experience measurement when in a connected state; outputting, to the UE via the first control message or the second control message, a second quality of experience measurement and reporting configuration for use by the UE to perform quality of experience measurement when the UE is in an idle state, an inactive state, or both; as well as A quality of experience report is obtained from the UE, the quality of experience report comprising a set of quality of experience measurements performed while the UE is operating in the idle state or the inactive state and in accordance with the second quality of experience measurement and reporting configuration.

Images