Patent Description:
ZTE's document "Discussion on NR QoE Configuration", 3GPP Draft, R3-<NUM> discusses that, in order to support multiple simultaneous QOE measurement configuration for different services at the UE, the RAN can send multiple RRC reconfiguration messages, with each message carrying a QOE measurement configuration for one service type, or send one RRC reconfiguration message which carries a list of QOE measurement configuration for all services in the message. This document proposes to introduce signaling support of a list of QOE measurement configuration over Xn and NG interfaces. For each QoE measurement configuration, at least Service type, an application layer measurement container are included. Furthermore, due to multiple QoE measurement towards to a UE is supported in NR, it is more often that NG-RAN needs to trigger one or more QoE measurements for a certain UE when the services of this UE changed. In other words, the NG-RAN can not only configure multiple QOE measurements simultaneously for several services in a QOE-activated configuration, but can also configure QOE measurements for multiple times during the connection.

In some aspects, a user equipment (UE) for wireless communication includes a memory and one or more processors, coupled to the memory, configured to: receive, from a base station, a quality of experience (QoE) configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; obtain application layer QoE measurements; and transmit, to the base station, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations.

In some aspects, a base station for wireless communication includes a memory and one or more processors, coupled to the memory, configured to: transmit, to a UE, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; receive, from the UE, a QoE report that includes application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations; and forward the application layer QoE measurements to an operations, administration, and management (OAM) server based at least in part on the application-level identifier associated with the access stratum identifier included in the QoE report.

In some aspects, a method of wireless communication performed by a UE includes receiving, from a base station, a quality of experience (QoE) configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; obtaining application layer QoE measurements; and transmitting, to the base station, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations.

In some aspects, a method of wireless communication performed by a base station includes transmitting, to a UE, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; receiving, from the UE, a QoE report that includes application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations; and forwarding the application layer QoE measurements to an OAM server based at least in part on the application-level identifier associated with the access stratum identifier included in the QoE report.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive, from a base station, a quality of experience (QoE) configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; obtain application layer QoE measurements; and transmit, to the base station, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to: transmit, to a UE, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; receive, from the UE, a QoE report that includes application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations; and forward the application layer QoE measurements to an OAM server based at least in part on the application-level identifier associated with the access stratum identifier included in the QoE report.

In some aspects, an apparatus for wireless communication includes means for receiving, from a base station, a quality of experience (QoE) configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; means for obtaining application layer QoE measurements; and means for transmitting, to the base station, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations.

In some aspects, an apparatus for wireless communication includes means for transmitting, to a UE, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; means for receiving, from the UE, a QoE report that includes application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations; and means for forwarding the application layer QoE measurements to an OAM server based at least in part on the application-level identifier associated with the access stratum identifier included in the QoE report.

While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, or artificial intelligence-enabled devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders, or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, or end-user devices of varying size, shape, and constitution.

In some aspects, the UE <NUM> may include a communication manager <NUM>. As described in more detail elsewhere herein, the communication manager <NUM> may receive, from a base station <NUM>, a quality of experience (QoE) configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; obtain application layer QoE measurements; and transmit, to the base station <NUM>, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations. Additionally, or alternatively, the communication manager <NUM> may perform one or more other operations described herein.

In some aspects, the base station <NUM> may include a communication manager <NUM>. As described in more detail elsewhere herein, the communication manager <NUM> may transmit, to a UE <NUM>, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; receive, from the UE <NUM>, a QoE report that includes application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations; and forward the application layer QoE measurements to an operations, administration, and management (OAM) server based at least in part on the application-level identifier associated with the access stratum identifier included in the QoE report. Additionally, or alternatively, the communication manager <NUM> may perform one or more other operations described herein.

The transceiver may be used by a processor (e.g., controller/processor <NUM>) and memory <NUM> to perform aspects of any of the methods described herein (e.g., as described with reference to <FIG>).

The transceiver may be used by a processor (e.g., controller/processor <NUM>) and memory <NUM> to perform aspects of any of the methods described herein (e.g., as described with reference to <FIG>).

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with an identifier configuration to support quality of experience (QoE) measurements, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. In some aspects, memory <NUM> and/or memory <NUM> may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station <NUM> and/or the UE <NUM>, may cause the one or more processors, the UE <NUM>, and/or the base station <NUM> to perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, the UE <NUM> includes means for receiving, from the base station <NUM>, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; means for obtaining application layer QoE measurements; and/or means for transmitting, to the base station <NUM>, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations. The means for the UE <NUM> to perform operations described herein may include, for example, one or more of communication manager <NUM>, antenna <NUM>, demodulator <NUM>, MIMO detector <NUM>, receive processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, modulator <NUM>, controller/processor <NUM>, or memory <NUM>.

In some aspects, the base station includes means for transmitting, to the UE <NUM>, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations; means for receiving, from the UE <NUM>, a QoE report that includes application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations; and/or means for forwarding the application layer QoE measurements to an operations, administration, and management (OAM) server based at least in part on the application-level identifier associated with the access stratum identifier included in the QoE report. The means for the base station to perform operations described herein may include, for example, one or more of communication manager <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, modulator <NUM>, antenna <NUM>, demodulator <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, or scheduler <NUM>.

<FIG> is a diagram illustrating an example <NUM> of QoE measurement configuration and QoE reporting, in accordance with the present disclosure. "QoE" may refer to a level of satisfaction of a user with a service from a perspective of the user. Example <NUM> may include communication between a QoE server <NUM>, a base station <NUM>, and a UE <NUM>, which may operate with different layers that involve different functions. For example, the UE <NUM> may operate with an application layer configured to control operations for an application, such as a video streaming application, and the UE <NUM> may operate with an access stratum layer that handles commands and data flows between a physical layer and the application layer. The QoE server <NUM> may be associated with a network operator that uses the base station <NUM> (e.g., the QoE server <NUM> may be associated with an OAM system, a control node, or the like). The QoE server <NUM> may perform operations associated with QoE measurements, such as processing of the QoE information, analysis of the QoE information, determination of key performance indicators (KPIs) based on the QoE information, or the like. For example, in a video streaming application, KPIs may include a video start up time, a rebuffering ratio, a bitrate, a resolution, and/or a latency, among other examples. The UE <NUM> may be operating in a radio resource control (RRC) connected (e.g., RRC_CONNECTED) state. In addition, the UE <NUM> may be configured with a signaling radio bearer (SRB), for QoE reporting (e.g., SRB4), for the base station <NUM>.

As shown by reference number <NUM>, the base station <NUM> may receive, from the QoE server <NUM>, information that identifies a QoE configuration that is to be used by the base station <NUM> (e.g., for configuring UEs for QoE reporting). For example, the QoE server <NUM> may transmit to the base station <NUM> an application layer QoE measurement configuration, for a UE, that is encapsulated in a transparent container. As shown by reference number <NUM>, the base station <NUM> may transmit, and the UE <NUM> may receive (e.g., at the access stratum layer of the UE), a QoE measurement configuration (e.g., a QoE measurement configuration based at least in part on the QoE configuration received by the base station <NUM>). For example, the base station <NUM> may forward to the UE the application layer QoE measurement configuration received from the QoE server <NUM> (e.g., in a downlink RRC message). As an example, the base station <NUM> may transmit an RRC reconfiguration (e.g., RRCReconfiguration) message that indicates the QoE measurement configuration in a measConfigAppLayer information element.

The QoE measurement configuration may identify one or more QoE measurements (e.g., relating to a quality of streaming services used in the UE <NUM>) that are to be collected by the UE <NUM>. "QoE measurement" may refer to a measurement (e.g., relating to bitrate, drop rate, connection failure, jitter, playback time, or the like) that is for use in determining a QoE, a QoE metric, a QoE KPI, or the like. The QoE measurement configuration also may identify one or more service types (e.g., a multimedia telephony service for internet protocol multimedia subsystem (MTSI), a streaming service, and/or a multimedia broadcast multicast service (MBMS), among other examples) for which the UE <NUM> is to perform QoE measurements.

As shown by reference number <NUM>, the UE <NUM>, via the access stratum layer, may provide, to the application layer of the UE <NUM>, a command to initiate QoE measurement at the application layer. That is, the command may be a command to initiate QoE measurement collection (QMC). The command may be a mobile station modem (MSM) interface/attention (AT) command. As shown by reference number <NUM>, the UE <NUM>, via the application layer, may provide application layer QoE measurements to the access stratum layer. The application layer QoE measurements may be per service type indicated by the QoE measurement configuration.

As shown by reference number <NUM>, the UE <NUM> may transmit (e.g., using the access stratum layer), and the base station <NUM> may receive, a QoE report. For example, the UE <NUM> may encapsulate the application layer QoE measurements from the higher layer of the UE in a transparent container that is transmitted to the base station <NUM> (e.g., in an uplink RRC message). As an example, the UE <NUM> may transmit a measReportAppLayer message that includes the QoE report. The QoE report may be based at least in part on the application layer QoE measurements collected by the UE <NUM>. For example, the QoE report may identify the application layer QoE measurements collected by the UE <NUM> (e.g., per service type). The UE <NUM> may transmit the QoE report via the SRB for QoE reporting (e.g., SRB4), which is a separate SRB (e.g., separate from current NR SRBs) for the lower-priority (e.g., relative to other SRB transmissions) QoE reporting. In some examples, the base station <NUM> may transmit to the UE <NUM> (e.g., via RRC signaling) an indication to pause or resume QoE reporting. As shown by reference number <NUM>, the base station <NUM> may transmit the QoE report, or information associated with the QoE report, to the QoE server <NUM>.

As described herein, the QoE server <NUM> and the base station <NUM> may configure the UE <NUM> with one or more QoE measurement configurations, and each QoE measurement configuration may be associated with one application-level reference identifier, which may be referred to herein as an application-level identifier. For example, when the base station <NUM> transmits the downlink RRC message with the measConfigAppLayer information element to the UE <NUM> to provide a QoE measurement configuration to the UE <NUM>, the QoE measurement configuration may be associated with one application-level identifier that the UE <NUM> configures to the application layer. In general, the application-level identifier may specify a network request session, and is therefore a globally unique identifier that is configured at the UE <NUM>, the base station <NUM>, and the QoE server <NUM> to manage a QoE measurement configuration. For example, in some cases, the application-level identifier may include a mobile country code (MCC), a mobile network code (MNC), and a QMC identifier, where the QoE server <NUM> provides the MCC and the MNC to the base station <NUM> in a trace activation request to identify one public land mobile network (PLMN) that contains the management system for the QoE measurement configuration, and where the QMC identifier is a <NUM>-byte octet string generated by the QoE server <NUM> or an operator associated with the QoE server <NUM> to identify a QoE measurement collection job in one or more traffic nodes (e.g., the base station <NUM>) and a QoE measurement collection center (e.g., the QoE server <NUM>).

Furthermore, when the base station <NUM> provides a QoE measurement configuration to the UE <NUM>, the base station <NUM> may provide the UE <NUM> with an access stratum identifier (e.g., an identifier that is configured at the access stratum layer) to identify the QoE measurement configuration at a radio access network (RAN)-level. Additionally, in cases where the QoE server <NUM> and/or base station <NUM> configure the UE <NUM> with multiple QoE measurement configurations, the base station <NUM> may need to allocate one access stratum identifier to identify each QoE measurement configuration. In general, the base station <NUM> may include the access stratum identifier associated with a particular QoE measurement configuration in the downlink RRC message that the base station <NUM> transmits to the UE <NUM> to provide the QoE measurement configuration to the UE <NUM>, and the UE <NUM> may include the access stratum identifier associated with the QoE measurement configuration in the uplink RRC message that the UE <NUM> transmits to the base station <NUM> to provide the QoE report that includes the application layer QoE measurements. In order to enable the base station <NUM> to forward the application layer QoE measurements to the correct QoE server <NUM>, the access stratum identifier may have a relationship with the application-level identifier. For example, in some cases, the application-level identifier may be used as the access stratum identifier. However, the application-level identifier is typically a <NUM>-byte octet string that includes an MCC, an MNC, and a QMC identifier. Accordingly, reusing the application-level identifier as the access stratum identifier may significantly increase the RRC signaling overhead.

Some aspects described herein relate to techniques and apparatuses for providing an identifier configuration to support QoE measurements. For example, in some aspects, a QoE measurement configuration may be associated with an access stratum identifier (e.g., an identifier used at an RRC or access stratum level) that is derived from a globally unique application-level identifier associated with the QoE measurement configuration. For example, in some aspects, the access stratum identifier may be a shortened (e.g., truncated) version of the application-level identifier, and the access stratum identifier may be included in RRC messages that are transmitted from a base station to a UE, and in RRC messages that are transmitted from the UE to the base station, to identify messages that relate to a particular QoE measurement configuration. In this way, when the base station receives an RRC message that includes application layer QoE measurements, the base station may determine the application-level identifier mapped to the access stratum identifier included in the received RRC message in order to determine the correct OAM entity (e.g., QoE server) to which to forward the application layer QoE measurements. For example, as described herein, an OAM server that provides a QoE measurement configuration to the base station may indicate an application-level identifier to the base station, and the base station may allocate an access stratum identifier that is derived from the application-level identifier to the QoE measurement configuration. Accordingly, the base station may provide the access stratum identifier to the UE when providing the QoE measurement configuration, such that the base station may map application layer QoE measurements associated with the access stratum identifier to the application-level identifier and thereby determine the correct OAM entity to receive the application layer QoE measurements.

<FIG> is a diagram illustrating an example <NUM> associated with an identifier configuration to support QoE measurements, in accordance with the present disclosure. As shown in <FIG>, example <NUM> includes communication between a base station <NUM>, a UE <NUM>, and an OAM server (e.g., a QoE server associated with an OAM entity). In some aspects, the base station <NUM>, the UE <NUM>, and the OAM server may be included in a wireless network, such as wireless network <NUM>. The base station <NUM> and the UE <NUM> may communicate via a wireless access link, which may include an uplink and a downlink. The base station <NUM> and the OAM server may communicate via a backhaul interface (e.g., an F1 interface, an NG interface, and/or an X2 interface).

In some aspects, as shown in <FIG> and described herein, the UE <NUM> may operate with different layers that involve different functions related to QoE measurements. For example, the UE <NUM> may operate with an application layer configured to control operations for an application, such as a video streaming application, and the UE <NUM> may operate with an access stratum layer that handles commands and data flows between a physical layer and the application layer. The OAM server may be associated with a network operator that uses the base station <NUM> to manage QoE measurement collection and QoE measurement reporting by the UE <NUM>. The OAM server may perform operations associated with QoE measurements, such as processing application layer QoE measurements reported by the UE, analyzing the application layer QoE measurements, and/or determining KPIs based on the application layer QoE measurements, among other examples.

As shown in <FIG>, and by reference number <NUM>, the OAM server may transmit a QoE measurement configuration to the base station <NUM>. For example, as described herein, the QoE measurement configuration provided from the OAM server to the base station <NUM> may include information that identifies a QoE measurement configuration that the base station <NUM> is to use to configure the UE <NUM> for reporting application layer QoE measurements. For example, the OAM server may transmit, to the base station <NUM>, an application layer QoE measurement configuration that is encapsulated in a transparent container for the UE <NUM>. Accordingly, in some aspects, the application layer QoE measurement configuration that the OAM server provides to the base station <NUM> may include at least an application-level identifier associated with the application layer QoE measurements to be collected and reported by the UE <NUM>. For example, in some aspects, the application-level identifier may be a globally unique identifier, such as a <NUM>-byte octet string that includes a combination of an MCC and an MNC to identify a PLMN that contains the OAM server and a QMC identifier that is generated by the OAM server to identify a QoE measurement collection job to be carried out at the UE <NUM> (e.g., at the application layer).

As further shown in <FIG>, and by reference number <NUM>, the base station <NUM> may allocate an access stratum identifier to identify the QoE measurement configuration at an access stratum layer (e.g., an RRC layer). For example, in some aspects, the access stratum identifier allocated to the QoE measurement configuration may be derived from the application-level identifier associated with the QoE measurement configuration such that the base station <NUM> may store information related to a mapping between the application-level identifier and the access stratum identifier. In some aspects, the access stratum identifier may be derived from the application-level identifier based on one or more derivation rules, whereby the access stratum identifier may be a shortened (e.g., truncated) version of the application-level identifier. For example, as shown in <FIG> and described herein, the application-level identifier may be a globally unique identifier that includes a combination of an MCC, an MNC, and a QMC identifier, and the access stratum identifier derived from the application-level identifier may include only the QMC identifier (e.g., omitting the MCC and the MNC) or only the QMC identifier and the MNC (e.g., omitting the MCC). In another example, the derivation rules may specify that the access stratum identifier corresponds to a set of leftmost bits or a set of rightmost bits in the application-level identifier. In some aspects, the OAM server may provide the QoE measurement configuration and the application-level identifier to the base station <NUM>, and the base station <NUM> may derive the access stratum identifier (e.g., the shortened or truncated version of the application-level identifier) based on the appropriate derivation rule(s). Alternatively, the OAM server may derive the access stratum identifier based on the appropriate derivation rule(s) and provide the access stratum identifier to the base station <NUM> together with the QoE measurement configuration and the application-level identifier.

In some aspects, the access stratum identifier that is derived from the application-level identifier may be defined to be unique within the scope of a RAN that includes the base station <NUM> (e.g., to enable management-based QoE measurement), unique within the scope of a cell provided by the base station <NUM>, or unique within the scope of the UE <NUM> (e.g., to enable signaling-based QoE measurement). In some aspects, the base station <NUM> may allocate the access stratum identifier based on a service type associated with the QoE measurement configuration and/or a network slice associated with the QoE measurement configuration. Furthermore, in some aspects, there may be a one-to-one (<NUM>:<NUM>) mapping between an application-level identifier and the access stratum identifier or an N-to-one (N:<NUM>) mapping between multiple application-level identifiers and the same access stratum identifier. In the latter case, where there is an N:<NUM> mapping between multiple application-level identifiers and the same access stratum identifier, the N application-level identifiers may generally belong to the same OAM server such that the base station <NUM> may know the correct OAM server to which to forward application layer QoE measurements based on an access stratum identifier. For example, when the OAM server provides a QoE measurement configuration associated with an application-level identifier and the base station <NUM> allocates an access stratum identifier that is derived from the application-level identifier, the base station <NUM> may store a mapping or other relationship between the access stratum and the application-level identifier. In this way, when the base station <NUM> receives a QoE report from the UE <NUM> that includes the access stratum identifier, the base station <NUM> may determine the OAM server that provided the QoE measurement configuration associated with the application-level identifier mapped to the access stratum identifier.

As further shown in <FIG>, and by reference number <NUM>, the base station <NUM> may transmit an RRC message that encapsulates the QoE measurement configuration to the UE <NUM>, and the RRC message may include the access stratum identifier derived from the application-level identifier. As shown in <FIG>, the QoE measurement configuration may be received at the access stratum layer of the UE <NUM>. As an example, the base station <NUM> may transmit an RRC reconfiguration (e.g., RRCReconfiguration) message that indicates the QoE measurement configuration and/or the access stratum identifier in a measConfigAppLayer information element. As described above, the QoE measurement configuration may identify one or more QoE measurements (e.g., relating to a quality of streaming services used in the UE <NUM>) that are to be collected by the UE <NUM>. The QoE measurement configuration also may identify one or more service types for which the UE <NUM> is to perform QoE measurements (e.g., MTSI, a streaming service, and/or MBMS).

In some aspects, when the UE <NUM> receives the RRC message that encapsulates the QoE measurement configuration from the base station <NUM>, the UE <NUM> may process the access stratum identifier included in the RRC message to determine a mapping or other relationship between the application-level identifier associated with the QoE measurement configuration and the access stratum identifier used to identify the QoE measurement configuration at the access stratum layer. For example, in some aspects, the access stratum layer may forward the application-level QoE measurement configuration to the application layer, and the application layer may decode the application-level identifier associated with the application-level QoE measurement configuration. The application layer may then provide the application-level identifier to the access stratum layer, and the access stratum layer may store a mapping between the access stratum identifier and the application-level identifier. In this way, when the application layer provides application layer QoE measurements to be reported to the access stratum layer, the application layer may provide the application-level identifier to the access stratum layer, and the access stratum layer may derive the access stratum identifier from the application-level identifier based on the mapping.

Alternatively, in some aspects, the access stratum layer may forward the application-level QoE measurement configuration and the access stratum identifier to the application layer, and the application layer may decode the application-level identifier associated with the application-level QoE measurement configuration. In this case, the application layer may store the mapping between the access stratum identifier and the application-level identifier. In this way, when the application layer provides application layer QoE measurements to be reported to the access stratum layer, the application layer may provide the access stratum identifier to the access stratum layer together with the application layer QoE measurements. Alternatively, in some aspects, the access stratum layer may store a mapping between the access stratum identifier received in the RRC message encapsulating the QoE measurement configuration and the corresponding application. In this way, when an application provides application layer QoE measurements to the access stratum layer, the access stratum layer may determine the appropriate access stratum identifier to associate with the application layer QoE measurements based on an identity of the application that provided the application layer QoE measurements to the access stratum layer.

As further shown in <FIG>, and by reference number <NUM>, the access stratum layer of the UE <NUM> may provide, to the application layer of the UE <NUM>, a command to initiate an application layer QoE measurement based on the access stratum identifier (e.g., an AT command to initiate QoE measurement collection at the application layer). As further shown in <FIG>, and by reference number <NUM>, the application layer may provide application layer QoE measurements to the access stratum layer. The application layer QoE measurements may be per service type indicated by the QoE measurement configuration. Furthermore, as described herein, the application layer QoE measurements may be associated with the application-level identifier associated with the QoE measurement configuration. For example, when providing the command to initiate the QoE measurement collection, the access stratum may forward the QoE measurement configuration to the application layer, and the application layer may decode the application-level identifier included in the QoE measurement configuration. In some aspects, the application layer may provide the decoded application-level identifier to the access stratum layer, which may store information related to a mapping between the access stratum identifier and the application-level identifier. Accordingly, when the application layer returns application layer QoE measurements to the access stratum layer, the application layer may further provide the application-level identifier associated with the application layer QoE measurements. In this way, the access stratum layer may derive the access stratum identifier (e.g., the shortened or truncated version of the application-level identifier) based on the mapping.

Alternatively, when providing the command to initiate the QoE measurement collection, the access stratum may forward the QoE measurement configuration and the access stratum identifier to the application layer, and the application layer may decode the application-level identifier included in the QoE measurement configuration (e.g., based on the QoE measurement configuration and/or one or more derivation rules). In some aspects, the application layer may store information related to the mapping between the access stratum identifier and the application-level identifier. Accordingly, when the application layer returns application layer QoE measurements to the access stratum layer, the application layer may further provide the access stratum identifier associated with the application layer QoE measurements based on the mapping. Alternatively, the access stratum layer may store information associating the access stratum identifier included in the RRC message providing the QoE measurement configuration and the corresponding application at the application layer, in which case the access stratum layer may determine the access stratum identifier associated with application layer QoE measurements returned from the application layer based on the application that provided or obtained the application layer QoE measurements.

As further shown in <FIG>, and by reference number <NUM>, the UE <NUM> may transmit (e.g., using the access stratum layer), and the base station <NUM> may receive, a QoE report message that includes the application layer QoE measurements and the access stratum identifier derived from the application-level identifier associated with the application layer QoE measurements. For example, the UE <NUM> may encapsulate the application layer QoE measurements in a transparent container that is transmitted to the base station <NUM> (e.g., in an uplink RRC message). As an example, the UE <NUM> may transmit a measReportAppLayer message that includes the QoE report with the application layer QoE measurements collected by the UE <NUM>. For example, the QoE report may identify the application layer QoE measurements collected by the UE <NUM> (e.g., per service type). The UE <NUM> may transmit the QoE report via the SRB for QoE reporting (e.g., SRB4), which is a separate SRB (e.g., separate from current NR SRBs) for the lower-priority (e.g., relative to other SRB transmissions) QoE reporting.

In some aspects, as described herein, the access stratum layer of the UE <NUM> may include the access stratum identifier derived from the application-level identifier in the RRC message that is transmitted to provide the QoE report with the application layer QoE measurements. Accordingly, when the base station <NUM> receives the QoE report from the access stratum layer of the UE <NUM>, the base station may determine the application-level identifier associated with the access stratum identifier (e.g., the base station <NUM> may determine the full application-level identifier based on the access stratum identifier, which is a shortened, truncated, or otherwise derived version of the application-level identifier). In this way, the base station <NUM> may determine the OAM server associated with the application-level identifier. Alternatively, in some aspects, the base station <NUM> may store information associating the OAM server with the access stratum identifier such that the base station <NUM> may determine the OAM server associated with the QoE report based on the access stratum identifier included in the RRC message that provides the QoE report. As further shown in <FIG>, and by reference number <NUM>, the base station <NUM> may then forward the QoE report to the OAM entity associated with the application-level identifier or access stratum identifier.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE <NUM>, in accordance with the present disclosure. Example process <NUM> is an example where the UE (e.g., UE <NUM>) performs operations associated with an identifier configuration to support QoE measurements.

As shown in <FIG>, in some aspects, process <NUM> may include receiving, from a base station, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations (block <NUM>). For example, the UE (e.g., using communication manager <NUM> and/or reception component <NUM>, depicted in <FIG>) may receive, from a base station, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include obtaining application layer QoE measurements (block <NUM>). For example, the UE (e.g., using communication manager <NUM> and/or measurement component <NUM>, depicted in <FIG>) may obtain application layer QoE measurements, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting, to the base station, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations (block <NUM>). For example, the UE (e.g., using communication manager <NUM> and/or transmission component <NUM>, depicted in <FIG>) may transmit, to the base station, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations, as described above.

In a first aspect, process <NUM> includes receiving, at an access stratum layer, the application layer QoE measurements and information that indicates the application-level identifier, and determining the shortened version of the application-level identifier used as the access stratum identifier based at least in part on one or more derivation rules.

In a second aspect, alone or in combination with the first aspect, process <NUM> includes receiving, at an access stratum layer, the application layer QoE measurements and information indicating the shortened version of the application-level identifier.

In a third aspect, alone or in combination with one or more of the first and second aspects, process <NUM> includes storing, at an access stratum layer, information associating an application with the access stratum identifier included in the QoE measurement configuration, and receiving the application layer QoE measurements from the application, wherein the QoE report includes the access stratum identifier based at least in part on the information associating the application with the access stratum identifier.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the access stratum identifier identifies the one or more QoE configurations in an access stratum layer.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the access stratum identifier includes a set of leftmost bits or a set of rightmost bits in the application-level identifier.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the application-level identifier includes an MCC, an MNC, and a QMC identifier, and the access stratum identifier includes only the QMC identifier or only the MNC and the QMC identifier.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process <NUM> includes decoding the application-level identifier based at least in part on the access stratum identifier included in the QoE configuration message, storing a mapping between the access stratum identifier and one or more of the application-level identifier or the one or more QoE configurations based at least in part on the decoding, and including the access stratum identifier in the QoE report according to the mapping based at least in part on an application layer indicating that the application layer QoE measurements are associated with the application-level identifier, the shortened version of the application-level identifier, or the one or more QoE configurations.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the access stratum identifier is unique within a scope of one or more of a RAN, a cell of the RAN, or the UE.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the application-level identifier and the access stratum identifier have a one-to-one mapping or an N-to-one mapping.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a base station, in accordance with the present disclosure. Example process <NUM> is an example where the base station (e.g., base station <NUM>) performs operations associated with an identifier configuration to support QoE measurements.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting, to a UE, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations (block <NUM>). For example, the base station (e.g., using communication manager <NUM> and/or transmission component <NUM>, depicted in <FIG>) may transmit, to a UE, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving, from the UE, a QoE report that includes application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations (block <NUM>). For example, the base station (e.g., using communication manager <NUM> and/or reception component <NUM>, depicted in <FIG>) may receive, from the UE, a QoE report that includes application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include forwarding the application layer QoE measurements to an OAM server based at least in part on the application-level identifier associated with the access stratum identifier included in the QoE report (block <NUM>). For example, the base station (e.g., using communication manager <NUM> and/or transmission component <NUM>, depicted in <FIG>) may forward the application layer QoE measurements to an OAM server based at least in part on the application-level identifier associated with the access stratum identifier included in the QoE report, as described above.

In a first aspect, process <NUM> includes receiving, from the OAM server, the application-level identifier, and determining the shortened version of the application-level identifier used as the access stratum identifier based at least in part on one or more derivation rules.

In a second aspect, alone or in combination with the first aspect, process <NUM> includes receiving, from the OAM server, the application-level identifier and information indicating the shortened version of the application-level identifier.

In a third aspect, alone or in combination with one or more of the first and second aspects, the access stratum identifier identifies the one or more QoE configurations in an access stratum layer.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the access stratum identifier includes a set of leftmost bits or a set of rightmost bits in the application-level identifier.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the application-level identifier includes an MCC, an MNC, and a QMC identifier, and the access stratum identifier includes only the QMC identifier or only the MNC and the QMC identifier.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process <NUM> includes determining the application-level identifier associated with the QoE report based at least in part on the access stratum identifier included in the QoE report, and determining the OAM server to which to forward the application layer QoE measurements based at least in part on the application-level identifier associated with the QoE report.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process <NUM> includes storing information associating the access stratum identifier with the OAM server, and determining the OAM server to which to forward the application layer QoE measurements based at least in part on the QoE report including the access stratum identifier associated with the OAM server.

<FIG> is a block diagram of an example apparatus <NUM> for wireless communication. The apparatus <NUM> may be a UE, or a UE may include the apparatus <NUM>. In some aspects, the apparatus <NUM> includes a reception component <NUM> and a transmission component <NUM>, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus <NUM> may communicate with another apparatus <NUM> (such as a UE, a base station, or another wireless communication device) using the reception component <NUM> and the transmission component <NUM>. As further shown, the apparatus <NUM> may include the communication manager <NUM>. The communication manager <NUM> may include one or more of a measurement component <NUM>, a determination component <NUM>, a storage component <NUM>, or a reporting component <NUM>, among other examples.

In some aspects, the apparatus <NUM> may be configured to perform one or more operations described herein in connection with <FIG>. Additionally, or alternatively, the apparatus <NUM> may be configured to perform one or more processes described herein, such as process <NUM> of <FIG>. In some aspects, the apparatus <NUM> and/or one or more components shown in <FIG> may include one or more components of the UE described above in connection with <FIG>. Additionally, or alternatively, one or more components shown in <FIG> may be implemented within one or more components described above in connection with <FIG>. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The reception component <NUM> may receive, from a base station, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations. The measurement component <NUM> may obtain application layer QoE measurements. The transmission component <NUM> may transmit, to the base station, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations.

The reception component <NUM> may receive, at an access stratum layer, the application layer QoE measurements and information that indicates the application-level identifier. The determination component <NUM> may determine the shortened version of the application-level identifier used as the access stratum identifier based at least in part on one or more derivation rules.

The reception component <NUM> may receive, at an access stratum layer, the application layer QoE measurements and information indicating the shortened version of the application-level identifier.

The storage component <NUM> may store, at an access stratum layer, information associating an application with the access stratum identifier included in the QoE measurement configuration. The reception component <NUM> may receive the application layer QoE measurements from the application, wherein the QoE report includes the access stratum identifier based at least in part on the information associating the application with the access stratum identifier.

The determination component <NUM> may decode the application-level identifier based at least in part on the access stratum identifier included in the QoE configuration message. The storage component <NUM> may store a mapping between the access stratum identifier and one or more of the application-level identifier or the one or more QoE configurations based at least in part on the decoding. The reporting component <NUM> may include the access stratum identifier in the QoE report according to the mapping based at least in part on an application layer indicating that the application layer QoE measurements are associated with the application-level identifier, the shortened version of the application-level identifier, or the one or more QoE configurations.

<FIG> is a block diagram of an example apparatus <NUM> for wireless communication. The apparatus <NUM> may be a base station, or a base station may include the apparatus <NUM>. In some aspects, the apparatus <NUM> includes a reception component <NUM> and a transmission component <NUM>, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus <NUM> may communicate with another apparatus <NUM> (such as a UE, a base station, or another wireless communication device) using the reception component <NUM> and the transmission component <NUM>. As further shown, the apparatus <NUM> may include the communication manager <NUM>. The communication manager <NUM> may include one or more of a determination component <NUM> or a storage component <NUM>, among other examples.

In some aspects, the apparatus <NUM> may be configured to perform one or more operations described herein in connection with <FIG>. Additionally, or alternatively, the apparatus <NUM> may be configured to perform one or more processes described herein, such as process <NUM> of <FIG>. In some aspects, the apparatus <NUM> and/or one or more components shown in <FIG> may include one or more components of the base station described above in connection with <FIG>. Additionally, or alternatively, one or more components shown in <FIG> may be implemented within one or more components described above in connection with <FIG>. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

In some aspects, the reception component <NUM> may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with <FIG>.

In some aspects, the transmission component <NUM> may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with <FIG>.

The transmission component <NUM> may transmit, to a UE, a QoE configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations. The reception component <NUM> may receive, from the UE, a QoE report that includes application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that the QoE report is associated with the application-level identifier or the one or more QoE configurations. The transmission component <NUM> may forward the application layer QoE measurements to an OAM server based at least in part on the application-level identifier associated with the access stratum identifier included in the QoE report.

The reception component <NUM> may receive, from the OAM server, the application-level identifier. The determination component <NUM> may determine the shortened version of the application-level identifier used as the access stratum identifier based at least in part on one or more derivation rules.

The reception component <NUM> may receive, from the OAM server, the application-level identifier and information indicating the shortened version of the application-level identifier.

The determination component <NUM> may determine the application-level identifier associated with the QoE report based at least in part on the access stratum identifier included in the QoE report. The determination component <NUM> may determine the OAM server to which to forward the application layer QoE measurements based at least in part on the application-level identifier associated with the QoE report.

The storage component <NUM> may store information associating the access stratum identifier with the OAM server. The determination component <NUM> may determine the OAM server to which to forward the application layer QoE measurements based at least in part on the QoE report including the access stratum identifier associated with the OAM server.

Claim 1:
A user equipment, UE, (<NUM>) for wireless communication, comprising:
a memory; and
one or more processors, coupled to the memory, configured to:
receive, from a base station, (<NUM>) a quality of experience, QoE, configuration message that includes an access stratum identifier, wherein the access stratum identifier is a shortened version of an application-level identifier associated with one or more QoE configurations;
obtain application layer QoE measurements; and
transmit, to the base station, a QoE report that includes the application layer QoE measurements, wherein the QoE report includes the access stratum identifier to indicate that QoE report is associated with the application-level identifier or the one or more QoE configurations.