Quality of experience (QoE)

Abstract

A user equipment comprising means for performing a Quality of Experience (QoE) measurement; transmitting a QoE measurement report indicating the QoE measurement to the network; receiving, from the network, a QoE configuration message indicating at least the event-based trigger; at least an event-based trigger is monitored to trigger at least one or more of performing a QoE measurement and sending a QoE measurement report indicating the QoE measurement and dependent on the QoE configuration message.

Description

Technical Field

[0001] Examples of the present disclosure relate to Quality of Experience (QoE). Background Art

[0002] Quality of Experience (QoE) is a subjective multi-dimensional representation of an end user's satisfaction or annoyance with a service based on explicit and / or implicit input from the user.

[0003] Currently, in the 3rd Generation Partnership Project (3GPP) "Overall description; Stage-2" [TS38.300], Quality of Experience (QoE) measurement and reporting are described in Chapter 21 (Application layer measurement collection). QoE measurement collection is only supported in the RRC_CONNECTED state. It should be noted that QoE measurement is also referred to as "application layer measurement".

[0004] A base station (e.g., gNB) requests an immediate measurement of service-specific parameters and provides an instruction regarding the reporting period. The user equipment receives the request and immediately measures the service parameters. The user equipment reports the measurement of a single service according to the instructed time period. If the UE enters the RRC_IDLE state, the UE releases the QoE measurement configuration. RAN-visible QoE measurements include information readable by the gNB.

[0005] There is a desire to improve Quality of Experience (QoE) monitoring. Summary of the Invention

[0006] According to various but not necessarily all examples, a user equipment is provided that includes components for:

[0007] Performing Quality of Experience (QoE) measurement;

[0008] Sending a QoE measurement report indicating the QoE measurement to the network;

[0009] Receiving from the network at least a QoE configuration message indicating an event-based trigger;

[0010] Monitoring at least the event-based trigger to trigger at least one or more of the following: performing a QoE measurement, and sending a QoE measurement report indicating the QoE measurement and depending on the QoE configuration message.

[0011] In some but not necessarily all examples, the QoE configuration message indicates: an event-based trigger for triggering a QoE measurement.

[0012] In some but not necessarily all examples, the QoE configuration message indicates: the periodicity for QoE measurement.

[0013] In some but not necessarily all examples, the QoE configuration message indicates an event-based trigger for triggering the sending of a QoE measurement report.

[0014] In some but not necessarily all examples, the QoE configuration message indicates the content measured by the QoE measurement.

[0015] In some but not necessarily all examples, the QoE measurement is a measurement related to a standardized telecommunication protocol stack and is independent of the measurement of one or more services using the standardized telecommunication protocol stack. The standardized telecommunication protocol stack includes a set of layered protocols that work together to provide a set of standardized telecommunication functions.

[0016] In some but not necessarily all examples, the QoE measurement is a measurement related to parameters that affect QoE when decreased and may be decreased due to network energy-saving features. In some but not necessarily all examples, the QoE measurement is a measurement related to parameters changed by network energy-saving features.

[0017] In some but not necessarily all examples, the QoE measurement includes a measurement of parameters related to the current and / or future processing capabilities of the user equipment.

[0018] In some but not necessarily all examples, the QoE measurement includes a measurement of the changed operating parameters of the device.

[0019] In some but not necessarily all examples, the QoE measurement includes a measurement of one or more of the following: energy usage, overheating, cache overflow, latency / delay.

[0020] In some but not necessarily all examples, the received QoE configuration message includes an identification reference, and the QoE measurement report includes an identification reference.

[0021] In some but not necessarily all examples, when an event defined by the event-based trigger is determined to occur, the event-based trigger triggers one or more of the following: performing a QoE measurement and sending a QoE measurement report indicating the QoE measurement and the QoE configuration message, where the event is

[0022] a non-temporal event, and / or

[0023] related to a standardized telecommunication protocol stack and independent of one or more services using the standardized telecommunication protocol stack. The standardized telecommunication protocol stack includes a set of layered protocols that work together to provide a set of standardized telecommunication features.

[0024] In some but not necessarily all examples, the event-based trigger is based on a change in the energy-saving feature.

[0025] In some but not necessarily all examples, the energy saving features include one or more of: network energy saving features and / or UE energy saving features.

[0026] In some but not necessarily all examples, the QoE configuration message is a configuration message including additional attributes related to QoE.

[0027] In some but not necessarily all examples, the QoE configuration message extends the QoE framework visible to the 3GPP RAN.

[0028] In some but not necessarily all examples, the event-based trigger is indicated by the network based on L1 / L2 signaling.

[0029] In some but not necessarily all examples, the QoE configuration message is a 3GPP RRCReconfiguration message including the AppLayerMeasConfig information element.

[0030] In some but not necessarily all examples, the QoE report identifier is included in an RRC message that includes a MeasurementReportAppLayer message.

[0031] In some but not necessarily all examples, performing QoE measurements is configured to: perform QoE measurements during the IDLE state and / or during the INACTIVE state.

[0032] In some but not necessarily all examples, the user equipment is configured to provide a capability report to the network indicating the capability for event-based QoE measurement, and / or is configured to provide a capability report to the network indicating the capability for event-based QoE measurement reporting, and / or is configured to provide a capability report to the network indicating the capability for event-based QoE measurement and / or event-based QoE measurement reporting.

[0033] In some but not necessarily all examples, a system includes a user equipment and at least one network unit, wherein the network unit is configured to: use the QoE measurement report received from the user equipment to select a network configuration option from multiple network configuration options with or enabling different network energy savings.

[0034] According to various but not necessarily all examples, a method is provided, including:

[0035] Performing QoE measurements;

[0036] Sending a QoE measurement report indicating the QoE measurement to the network;

[0037] Receive at least a QoE configuration message indicating an event-based trigger from a network;

[0038] Monitor at least the event-based trigger to trigger at least one or more of the following: perform a QoE measurement, and send a QoE measurement report indicating the QoE measurement and depending on the QoE configuration message.

[0039] According to various but not necessarily all examples, a computer program is provided, the computer program comprising instructions that, when executed by one or more processors, cause:

[0040] Perform a QoE measurement;

[0041] Send a QoE measurement report indicating the QoE measurement to the network;

[0042] Process at least a QoE configuration message received from the network indicating an event-based trigger;

[0043] Monitor at least the event-based trigger to trigger at least one or more of the following: perform a QoE measurement, and send a QoE measurement report indicating the QoE measurement and depending on the QoE configuration message.

[0044] According to various but not necessarily all examples, a network device is provided, comprising components for:

[0045] Send at least a Quality of Experience (QoE) configuration message indicating an event-based trigger to a user equipment;

[0046] Depending on the event-based trigger, receive a QoE measurement report including a Quality of Experience (QoE) measurement performed at the user equipment from the user equipment.

[0047] In some but not necessarily all examples, the network device comprises: components for selecting a network configuration option from a plurality of network configuration options having or enabling different network energy saving features using the QoE measurement report received from the user equipment.

[0048] In some but not necessarily all examples, the network device comprises: components for including an identification reference in the QoE configuration message sent to the user equipment, components for storing a mapping between the identification reference and the user equipment, and components for associating the received QoE measurement report with the user equipment based on the stored mapping.

[0049] According to various but not necessarily all examples, a method is provided, comprising:

[0050] Send at least a Quality of Experience (QoE) configuration message indicating an event-based trigger to a user equipment; and

[0051] Receive a QoE measurement report from a user equipment, depending on an event-based trigger, the report including QoE measurements performed at the user equipment.

[0052] According to various but not necessarily all examples, there is provided a computer program comprising instructions which, when executed by one or more processors, cause: sending to a user equipment a quality of experience (QoE) configuration message indicating at least an event-based trigger; and

[0053] Receive a QoE measurement report from a user equipment, depending on an event-based trigger, the report including QoE measurements performed at the user equipment.

[0054] According to various but not necessarily all examples, there is provided a user equipment comprising components for:

[0055] Receiving a measurement command from a network;

[0056] Monitoring an event-based trigger to trigger measurements to be performed after a delay following receipt of the measurement command from the network;

[0057] Depending on the measurements, sending a report to the network.

[0058] In some but not necessarily all examples, the measurement command is a QoE configuration message, the measurements are QoE measurements, and the report is a QoE measurement report.

[0059] According to various but not necessarily all examples, there is provided a user equipment comprising components for:

[0060] Receiving a QoE configuration message from a network;

[0061] Monitoring an event-based trigger to trigger measurements to be performed after a delay following receipt of the QoE configuration message from the network;

[0062] Depending on the measurements, sending a QoE report to the network.

[0063] In some but not necessarily all examples, the measurements are QoE measurements

[0064] In some but not necessarily all examples, the QoE configuration message indicates an event-based trigger to trigger QoE measurements and / or an event-based trigger to trigger a QoE measurement report. In some but not necessarily all examples, the report also depends on the QoE configuration message.

[0065] According to various but not necessarily all examples, there is provided a user equipment comprising components for:

[0066] Receive from a network at least a QoE configuration message indicating an event-based trigger to trigger QoE measurement and optionally trigger a QoE measurement report;

[0067] At least monitor an event-based trigger to trigger performance of a QoE measurement;

[0068] Depending on the measurement and based on the QoE configuration message, send a QoE measurement report to the network.

[0069] According to various but not necessarily all examples, examples as claimed in the appended claims are provided.

[0070] Although the above examples and optional features of the present disclosure are described separately, it should be understood that their provision in all possible combinations and permutations is included within the present disclosure. It should be understood that each example of the present disclosure may include any or all of the features described for other examples of the present disclosure, and vice versa. Additionally, it should be understood that any one or more or all of the features, in any combination, may be implemented as / included in / executed by an apparatus, method, and / or computer program instructions as needed and appropriately. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] Some examples will now be described with reference to the drawings, in which:

[0072] Figure 1 Examples of the subject matter described herein are shown;

[0073] Figure 2A Another example of the subject matter described herein is shown;

[0074] Figure 2B Another example of the subject matter described herein is shown;

[0075] Figure 2C Another example of the subject matter described herein is shown;

[0076] Figure 2D Another example of the subject matter described herein is shown;

[0077] Figure 3 Another example of the subject matter described herein is shown;

[0078] Figure 4 Another example of the subject matter described herein is shown;

[0079] Figure 5 Another example of the subject matter described herein is shown;

[0080] Figure 6 Another example of the subject matter described herein is shown;

[0081] Figure 7 Shows another example of the subject matter described herein;

[0082] FIG. 8 shows another example of the subject matter described herein;

[0083] FIG. 9 shows another example of the subject matter described herein.

[0084] FIG. 10 shows another example of the subject matter described herein;

[0085] Figure 11 Shows another example of the subject matter described herein.

[0086] Figure 12 Shows another example of the subject matter described herein

[0087] These figures are not necessarily drawn to scale. For clarity and conciseness, some features and views in the figures may be shown schematically or enlarged in scale. For example, the dimensions of some elements in the figures may be enlarged relative to other elements to aid in the explanation. Similar reference numerals are used in the figures to denote similar features. For the sake of clarity, not all reference numerals are necessarily shown in all figures.

[0088] Definition

[0089] 3GPP: Third Generation Partnership Project.

[0090] RAN: Radio Access Network, such as a base station, such as an eNodeB (eNB) or a gNodeB (gNB).

[0091] Control Plane: The part of the network that carries the information required to establish and control the network. When illustrating the control of the network, it is typically used to describe the flow of information packets between network interfaces.

[0092] NR: New Radio, also known as 5G.

[0093] UTRA is Universal Terrestrial Radio Access, and UTRAN is Universal Terrestrial Radio Access Network. UTRA is related to the air interface of 3GPP. E-UTRA is the evolved UTRA and describes the air interface used by eNodeB and gNodeB.

[0094] Protocol Stack: A collection of layered protocols that work together to provide a set of functions.

[0095] Telecommunication Protocol Stack: A collection of layered protocols that work together to provide a set of telecommunication functions.

[0096] Standardized Telecommunication Protocol Stack: A telecommunication protocol stack defined by telecommunication standards.

[0097] 3GPP Telecommunication Protocol Stack: A standardized telecommunication protocol stack defined by 3GPP telecommunication standards. The radio protocols between a UE and a RAN node (eNodeB or gNodeB) and the protocol stack including the protocol stack for the control plane are specified in "Overall description; Stage 2" (TS 36.300) for E-UTRA and E-UTRAN and in "Overall description; Stage 2" (TS 38.300) for NR in 3GPP.

[0098] Service: The use of the functions of the protocol stack.

[0099] Quality of Service (QoS): A set of performance parameters that can be directly observed and measured and are related to the delivery of one of multiple services. It can include parameters for, e.g., latency, bit rate, packet error rate, etc.

[0100] Quality of Experience (QoE): A subjective multi-dimensional representation of the end-user's satisfaction or annoyance with a service based on explicit and / or implicit input from the user.

[0101] Radio Resource Measurement (RRM) is an objective measurement related to the radio environment, such as RSRP, RSRQ, SINR, RSSI based on RS or other signals.

[0102] Network Energy Saving (NES) is a set of features executed at the network to reduce energy consumption. For example, it can involve selecting one option from multiple options based on greater network energy saving.

[0103] RRC: Radio Resource Control is a radio resource control plane protocol for radio resource management.

[0104] RRC_CONNECTED state: The UE has established an RRC connection.

[0105] RRC_IDLE state: The UE has not established an RRC connection.

[0106] RRC_INACTIVE state: The UE has a suspended, established RRC connection. Detailed implementation

[0107] Figure 1 An example of a radio telecommunication system including a network 200 and a terminal device 100 is shown. The network 200 and the terminal device 100 communicate by exchanging radio signals. In this example, but not necessarily in all examples, the terminal device is a user equipment 100.

[0108] The network 200 is configured to send a measurement command 201 to a user equipment (UE) 100.

[0109] The UE 100 is configured to receive a measurement command 201 from the network 200; monitor 140 event-based triggers 202 to trigger 140 to perform 130 measurements that are delayed after receiving the measurement command 201 from the network 200; and send a report 203 to the network 200 depending on the measurement.

[0110] The report 203 to the network 200 may indicate a measurement, for example. For example, the report 203 may include a measurement. This may be a measurement such as a measurement or a value determined from an actual measurement or based on an actual measurement.

[0111] In at least some examples, the measurement command 201 is a QoE configuration message, the measurement is a QoE measurement, and the report 203 is a QoE measurement report.

[0112] In at least some examples, the measurement command 201 indicates an event-based trigger 202 to trigger 140 QoE measurements and / or an event-based trigger to trigger a QoE measurement report 203.

[0113] In at least some examples, the report 203 also depends on the measurement command 201 (QoE configuration message). For example, in at least some examples, the report 203 includes an indicator provided by the measurement command 201 (QoE configuration message).

[0114] Using event-based measurements such that the measurements are delayed rather than immediate decouples the measurements from the receipt of the measurement command 201.

[0115] Using event-based reporting decouples the reporting from the receipt of the measurement command 201 and / or the measurement itself.

[0116] It will be understood that in some examples, the user equipment 100 includes components for: receiving a QoE configuration message 201 from the network 200; monitoring 140 event-based triggers 202 to trigger the execution of 130 measurements that are delayed after receiving the QoE configuration message 201 from the network 200; sending a QoE measurement report 203 to the network 200 depending on the measurement. The measurement may be a QoE measurement. The QoE configuration message indicates an event-based trigger to trigger a QoE measurement and / or an event-based trigger to trigger a QoE measurement report. The report also depends on the QoE configuration message 201.

[0117] Figure 2A 、 2B 、2C and 2D illustrate examples of the user equipment 100, including components for:

[0118] Performing 130 quality of experience (QoE) measurements;

[0119] Send a QoE measurement report 203 that depends on QoE measurements to network 200;

[0120] Receive from the network a QoE configuration message 201 that at least indicates an event-based trigger 202;

[0121] At least monitor 130 event-based triggers 202 to trigger one or more of the following:

[0122] (i) Perform 130 QoE measurements, and

[0123] (ii) Send a QoE measurement report 203 that depends on QoE measurements and QoE configuration message 201.

[0124] The QoE measurement report 203 may include, for example, QoE measurements.

[0125] Figure 2A A user equipment 100 is shown, including components for:

[0126] Perform 130 quality of experience (QoE) measurements;

[0127] Send a QoE measurement report 203 that depends on QoE measurements to the network;

[0128] Receive from network 200 a QoE configuration message 201 that at least indicates an event-based trigger 202;

[0129] At least monitor 140 event-based triggers 202 to trigger the performance of QoE measurements.

[0130] The event-based trigger 202 determines when QoE measurements occur. The QoE configuration message 201 indicates the event-based trigger 202 for triggering QoE measurements.

[0131] Figure 2B A user equipment 100 is shown, including components for:

[0132] Perform 130 quality of experience (QoE) measurements;

[0133] Send a QoE measurement report 203 that depends on QoE measurements to network 200;

[0134] Receive from network 200 a QoE configuration message 201 that at least indicates an event-based trigger 202;

[0135] At least monitor 140 event-based triggers 202 to trigger the sending of a QoE measurement report that depends on QoE measurements and the QoE configuration message.

[0136] The QoE measurement report 203 may include, for example, QoE measurements.

[0137] The event-based trigger 202 does not necessarily determine when the QoE measurement occurs. The QoE configuration message 201 can indicate, for example, the periodicity 131 for the QoE measurement.

[0138] The event-based trigger 202 determines when the QoE measurement report 203 occurs. The QoE configuration message 201 indicates the event-based trigger 202 for triggering the transmission of the QoE measurement report 203.

[0139] Figure 2C and 2D illustrates a user equipment, including components for:

[0140] performing 130 a quality of experience (QoE) measurement;

[0141] sending a QoE measurement report 203 depending on the QoE measurement to the network 200;

[0142] receiving from the network 100 a QoE configuration message 201 indicating at least a first event-based trigger 202A and a second event-based trigger 202B;

[0143] monitoring 140A the first event-based trigger 202A to trigger the performance of the QoE measurement.

[0144] monitoring 140B the second event-based trigger 202B to trigger the sending of a QoE measurement report 203 depending on the QoE measurement and the QoE configuration message 201.

[0145] The QoE measurement report 203 can include, for example, the QoE measurement.

[0146] The event-based trigger 202 determines when the QoE measurement occurs. The QoE configuration message 201 indicates the event-based trigger 202A for triggering the QoE measurement.

[0147] The event-based trigger 202 determines when the QoE measurement report 203 occurs. The QoE configuration message 201 indicates the event-based trigger 202B for triggering the transmission of the QoE measurement report 203.

[0148] Thus, in at least some examples, the user equipment 100 includes components for:

[0149] receiving from the network 200 a QoE configuration message 201 indicating at least an event-based trigger 202 for triggering the QoE measurement and optionally triggering the QoE measurement report;

[0150] monitoring at least 140 the event-based trigger 202 to trigger the performance of the QoE measurement;

[0151] Depending on the measurement and based on the QoE configuration message 201, a QoE measurement report 203 is sent to the network.

[0152] In some but not necessarily all examples, the QoE configuration message 201 includes an identification reference, and the QoE measurement report 203 includes an identification reference. For example, each QoE measurement configuration can be uniquely identified by a QoE reference.

[0153] In some but not necessarily all examples, the QoE configuration message 201 indicates the content measured by the QoE measurement.

[0154] QoE measurement is generally a subjective multi-dimensional representation of the end-user's satisfaction or annoyance with the service, where multiple dimensions (such as device, content / service, environment, user expectation, personality) are weighted by the end-user (the user of the user equipment 100). One of the dimensions affecting QoE may be the radio environment (and radio resource management (RRM) measurements). A new class of additional QoE attributes related to the user equipment (rather than the service) and its hardware performance is used. RRM measurements are limited to representing the radio environment through its objective metrics (RSRP, RSRQ, SINR, RSSI based on reference signals or other signals).

[0155] In some but not necessarily all examples, the QoE measurement includes the measurement of parameters related to the current and / or future processing capabilities of the user equipment. For example, the battery level of the user equipment, UE operating temperature, setup time, cache level, QoS (delay, data rate, packet loss). Therefore, the QoE measurement includes the measurement of the changed operating parameters of the user equipment 100.

[0156] In some but not necessarily all examples, the QoE measurement is a measurement related to parameters that affect QoE when reduced and can be reduced through the network energy saving (NES) process.

[0157] In some but not necessarily all examples, the user equipment 100 includes a UE modem layer 102 and an application layer 104, as Figures 2A to 2D shown.

[0158] The UE modem layer 102 performs external communication with the network 200 and internal communication with the application layer 104. The application layer 104 does not communicate directly with the network 200.

[0159] For example, the UE modem layer 102 sends an attention (AT) message 101 to the application layer 104 and receives an attention (AT) message 193 from the application layer 104 as a reply. The attention (AT) message 101 causes the execution of 130 QoE measurements. The attention (AT) message 103 includes this QoE measurement.

[0160] For example, the UE modem layer 102 receives a QoE configuration message 201 via a radio interface between the modem layer 102 and the network 200, and the UE modem layer 102 sends a QoE measurement report 203 via the radio interface between the modem layer 102 and the network 200. The QoE measurement report 203 may include QoE measurements received in an attention (AT) message 103.

[0161] The UE modem layer 102 represents a standardized telecommunication protocol stack. As Figure 3 shown, the protocol stack 300 includes a plurality of protocol layers 302 that are arranged as a hierarchical set and work together to provide a set of functions. The standardized telecommunication protocol stack 300 includes a hierarchical set of protocols 302 that work together to provide a set of standardized telecommunication functions. In at least some examples, the standardized telecommunication protocol stack 300 is a 3GPP telecommunication protocol stack.

[0162] The service layer 304 is separate from the protocol stack 300. Services may use the standardized telecommunication protocol stack 300.

[0163] In at least some examples, the QoE measurement is a measurement related to the standardized telecommunication protocol stack 300 and not a measurement related to one or more services 304. The QoE measurement is a measurement independent of the service 304.

[0164] The event-based trigger 202 triggers one or more of the following:

[0165] i) Performing 130 QoE measurements and

[0166] ii) Sending a QoE measurement report 203 that depends on the QoE measurement and the QoE configuration message,

[0167] when a trigger event defined by the event-based trigger is determined by the user equipment 100 to have occurred.

[0168] The trigger event may for example be a non-time event. A non-time event is an event that is not determined solely by the passage of time. For example, triggering at a specific time or multiple specific times or each time period is a time event.

[0169] The trigger event may for example be related to the standardized telecommunication protocol stack (and not related to one or more services that use the standardized telecommunication protocol stack).

[0170] The trigger event may for example be a change in an energy saving feature. In this case, the user equipment 100 notifies the network 200 of the impact on the QoE at the user equipment 100 caused by the energy saving. The energy saving feature may include one or more of a network energy saving (NES) feature and / or a UE energy saving feature.

[0171] The triggering event can be, for example, a change to a different network energy saving (NES) state. The triggering event can be, for example, a change to a different RRC state, such as a change between RRC_CONNECTED, RRC_IDLE, and RRC_INACTIVE.

[0172] The triggering event can be, for example, a change in the configuration of the air interface (UTRA).

[0173] In at least some examples, the QoE configuration message is a configuration message that includes additional attributes related to QoE. For example, new attributes can be added to an existing message. The new attributes can control one or more of the following: the content being measured, when it is measured (event-based triggering), and when it is reported (event-based triggering).

[0174] In at least some examples, the QoE configuration message 201 extends the 3GPP RAN visible QoE framework.

[0175] In at least some examples, the event-based triggering 202 is indicated by the network 200 based on L1 / L2 signaling.

[0176] In at least some examples, the QoE configuration message 202 is a 3GPP RRCReconfiguration message that includes the AppLayerMeasConfig information element, and the QoE measurement report is an RRC message that includes the MeasurementReportAppLayer message.

[0177] Figure 4 A state machine 310 for a terminal node 100 (such as a user equipment) is shown. The state machine 310 includes three different states: a connected state 312, an inactive state 314, and an idle state 316.

[0178] In the example shown, the terminal node 110 is a user equipment, and the states are the RRC connected state 312, the RRC inactive state 314, and the RRC idle state 316. In the specific example shown, the terminal node 110 is a new radio (NR) user equipment, and the states are the NR RRC connected state 312, the NR RRC inactive state 314, and the NR RRC idle state 316.

[0179] The states and the transitions between the states are defined in the appropriate specifications.

[0180] In this example, the inactive state 314 can only be entered from the connected state 312, for example, via a radio resource control (RRC) release with a suspend message. In this example, the inactive state can be exited to the connected state via an RRC resume, or exited to the idle state via an RRC release.

[0181] The RRC release message with suspension is an RRC release message that includes suspension configuration information. It is a downlink message.

[0182] The inactive state 314 is a state that has a first set of characteristics common with the idle state 316 but not common with the connected state 312, and a second set of characteristics common with the connected state 312 but not common with the idle state 316.

[0183] In at least some examples, the first set of characteristics includes mobility management via cell reselection, and the second set of characteristics includes a security context for encryption.

[0184] Data transmission is possible in the connected state 312 and the inactive state 314. The inactive state 314 can support, for example, small data transmission.

[0185] The above event-triggered QoE measurement can occur in the connected state 312, the inactive state 314, and the idle state 316, or as a result of a transition between states.

[0186] The above event-triggered QoE measurement report can occur in the connected state 312 and the inactive state 314 but not in the idle state 316, or as a result of a transition to the connected state 312 or the inactive state 314.

[0187] Figure 5 UE capability reporting in the previously described system is shown.

[0188] The user equipment 100 is configured to provide a capability report 213 to the network 200. The capability report 213 can indicate, for example, the capability for event-based QoE measurement or the capability for event-based QoE measurement report or the capability for event-based QoE measurement and / or event-based QoE measurement report.

[0189] In this example, the user equipment 100 is configured to provide the capability report 213 to the network 200 in response to receiving a capability request message 211 sent by the network 200.

[0190] Figure 6 The previously described system is shown. It shows the operation at the network 200 after the network 200 receives the QoE measurement report 203.

[0191] The network element 200 is configured to select a network configuration option from multiple available network configuration options having or enabling different network energy savings using the QoE measurement report 203 received from the user equipment 100.

[0192] For example, network 200 may be configured to optimize energy savings while complying with the constraints imposed by QoE measurement report 203. In some examples, for instance, network 200 may be configured to select options that provide a QoE above a minimum threshold and exceed minimum power savings at UE 100. In some examples, network 200 may be configured, for example, to select options that provide a QoE above a minimum threshold and also provide maximum network power savings at UE 100.

[0193] Figure 7 An example of method 500 is shown.

[0194] The method includes receiving, at block 502, a QoE configuration message from a network that indicates at least an event-based trigger.

[0195] The method includes, at block 504, monitoring at least an event-based trigger to trigger one or more of: performing a QoE measurement, and sending a QoE measurement report that depends on the QoE measurement and the QoE configuration message.

[0196] The method includes performing a QoE measurement and sending a QoE measurement report at block 506.

[0197] A number of use cases will now be described with reference to the previous figures. These use cases relate to enhancements for network energy savings (NES) in NR. NES reduces the energy consumption of a mobile network, and in particular of the RAN, which consumes the largest portion of the network's total energy consumption.

[0198] As previously mentioned, quality of experience (QoE) represents the overall quality or performance of a provided service as subjectively perceived by a user.

[0199] Within the 3GPP specifications, QoE measurement collection (QMC) has been part of the 5G standard since Rel-17. The overall framework enables the collection of QoE measurements generated at the application layer of the UE.

[0200] In RAN visible QoE, network 200 is the gNB. The QoE measurement is configured by the gNB. A subset of QoE metrics is reported from UE 100 as explicit information elements (IEs) readable by gNB 200. The set of available RAN visible QoE metrics is a subset of the metrics that have been configured as part of the QoE measurement configuration to be encapsulated in a transparent container.

[0201] In the following use cases, the 3GPP radio protocol stack is referred to as the "UE" or "UE layer" according to typical 3GPP naming and the QoE measurement set in chapter 21 of TS 38.300.

[0202] These examples combine Network Energy Saving (NES) and QoE measurement. To enable this, QoE measurements currently only associated with user plane services (such as DASH, VR) are extended to control plane configurations that affect QoE.

[0203] Most power saving techniques (device or network side techniques) can degrade the experience of UE 100 users with network 200 and can thus result in a lower QoE. This is because activating power saving techniques can lead to a degraded Quality of Service (QoS) (in terms of data rate, latency, etc.) that network 200 can offer to users, which in turn can affect QoE. For example, if UE 100 or network 200 is in or starts from a sleep mode (such as an inactive state), latency, reliability, or bandwidth can be reduced.

[0204] gNB 200 is the entity that controls the application of energy saving techniques, and the QoE measurement report 203 allows gNB 200 to understand how NES affects QoE.

[0205] The use case allows gNB 200 to understand the impact of (network) energy saving on the QoE of the UE.

[0206] gNB 200 obtains NES (Network Energy Saving) - related QoE metrics from UE 100 via the QoE measurement report 203 to evaluate how one or more NES techniques affect the QoE of the user. The NES - specific QoE measurement report allows network 200 to optimize the decision on whether, when, and where (in which cells) to activate a given NES technique, aiming to minimize / avoid the impact on the QoE of the end - user.

[0207] For example, the new RAN - visible QoE report trigger can be associated with the NES state of the UE monitoring / from its serving cell / beam. That is, measurements and / or reports from the UE side can be triggered based on a given NES state, e.g., if the gNB is in / moves to / exits a given NES state.

[0208] gNB 200 is responsible for configuring, de - activating, and releasing NES - related QoE measurements, including configuring NES - specific triggers and / or NES - specific report triggers for NES - dedicated QoE measurement / logging at UE 100.

[0209] In one example, NES - specific QoE measurements (if configured) are only performed when network 200 is in the corresponding NES state.

[0210] The trigger can be event - based (e.g., the event can be defined due to network 200 changing to a different NES state and / or UE 100 changing to a different RRC state, and / or re - configuration of the air interface).

[0211] Different triggers can be configured for different NES states. For example, a trigger for reporting may be required only when the NES state is expected to fail to meet the UE's QoS requirements.

[0212] The RAN visible QoE framework is also extended for UEs in RRC_INACTIVE and RRC_IDLE states. That is, a UE 100 in RRC idle / inactive state shall perform and store certain QoE measurements and shall report these measurements based on gNB configuration. The UE 100 may perform QoE measurements in the idle / inactive state. The QoS measurement report 203 may be sent via small data transfer (SDT) during the RRC_INACTIVE state. Specific QoE attributes may be defined for UEs in the idle / inactive state.

[0213] New QoE attributes related to NES can be used. These attributes can be classified into new metrics required for QoE measurement and / or metrics associated with NES events that trigger the collection of RAN visible QoE reports.

[0214] For example:

[0215] UE battery status (at the start and stop of the QoE log): An indication of battery consumption over a period of time, e.g., when the UE 100 has to camp on a cell for paging monitoring and at the same time monitor another sleeping cell for UL transmission. Such an indication may be provided together with the screen duration.

[0216] Device heating / overheating information.

[0217] Initial setup time: How long it takes for the UE to access the service when the NES technology is activated (e.g., cell shutdown, on-demand activation of a sleeping cell).

[0218] UE cache level associated with the NES mode state: An indication of the UE cache level when the NES technology is activated (sleeping cell / beam).

[0219] The experienced QoS (in terms of latency, data rate, packet loss) derived by the UE: When the NES state is activated, the UE may report information about the experienced QoS together with the corresponding NES state associated therewith. For example, network discontinuous transmission (DTX) can affect the latency seen by the UE 100. Using the QoS measurement report 203, the network 200 can determine the extent of the impact on QoS due to NES. This may be particularly useful for UEs in the RRC idle / inactive state as QoS monitoring cannot be performed by the network on them.

[0220] The measurement may be common to all PDU sessions of the UE.

[0221] The use cases are based on (and extend) the RAN visible QoE configuration framework. The existing signaling framework is reused and new QoE attributes are added. For example, according to the existing signaling, the RAN visible QoE is configured together with the container-based QoE, and an RRC identifier can be assigned to each measurement configuration in the measurement configuration.

[0222] In the use cases, the following terms are used to distinguish between two types of QoE measurements, referred to as "traditional QoE" and "NES QoE":

[0223] "Traditional QoE" measurements include traditional attributes / parameters: These include service-specific QoE parameters / attributes that are already available in the specification. After operation in Release 17, the reporting of these QoE parameters is periodic.

[0224] "NES QoE" measurements include new NES-based attributes / parameters and / or new NES-specific triggers: The NES-specific QoE attributes / parameters proposed in this solution. In addition to periodic reporting, NES QoE parameters should be event-based enabled (e.g., measured / reported when the NES mode is activated or deactivated).

[0225] Note that there may be deployments where traditional QoE and NES QoE parameters may be configured in a way that the gNB can evaluate how the services (e.g., flows, VR) the UE is running are affected by the NES configuration, or there may be deployments where the gNB is only interested in NES QoE parameters.

[0226] The gNB 200 can use the NES triggers / NES-based QoE reports 203 collected by the gNB 200 based on the local gNB implementation to

[0227] evaluate whether the NES affects the QoE, and

[0228] determine how to maintain the QoE of the UE that is using the NES for its services.

[0229] For example, the gNB 200 may prioritize one service over another to avoid a QoE degradation of the prioritized service while still being able to use the NES state. Additionally or alternatively, the gNB may change the UE configuration or allocated resources to avoid QoE degradation while still being able to use the NES state. As an example, it may allocate more physical resource blocks (PRBs) in the frequency domain to compensate for the reduced time allocation due to the NES state (e.g., in the time domain). Additionally or alternatively, whenever the UE is active, the gNB may deactivate the NES feature or avoid activating the NES feature if it is deemed that this would cause a QoE degradation for a given UE.

[0230] Service or UE preemption can also be used by starving another low - priority service or releasing a low - priority UE.

[0231] Additionally or alternatively, the gNB may change the UE configuration (e.g., the C - DRX configuration for optimizing time - domain resources, and / or the BWP configuration for optimizing frequency - domain resources) or may allocate a larger amount of resources when serving the UE (e.g., by allocating more PRBs in the frequency domain to compensate for the reduced time allocation due to the NES state) to avoid QoE degradation while still being able to use the NES state in the time domain.

[0232] The first use case relates to RAN - visible QoE for NES: configuration and reporting. QoE measurements are controlled by event - based triggers.

[0233] The first use case is shown in FIG. 8, which includes features from Figure 5 , 2A and 6.

[0234] As Figure 5 and 8 show, the network 200 sends a UE capability query 211 to the UE 100 (step 1 in FIG. 8). The UE 100 responds with UE capability information that includes an indication of RAN - visible NES QoE support (step 2 in FIG. 8).

[0235] As Figure 2A and 8 show, the network 200 sends an RRC re - configuration message to the UE 100, which includes RAN - visible parameters: NES QoE parameters and RAN - visible events: NES event conditions (step 3 in FIG. 8). It may also include an associated reporting period. The RRC re - configuration message is a QoE measurement command 202 because it includes NES QoE parameters (for measurement) and / or NES event conditions (for event - based triggers).

[0236] UE 100 monitors the event-based trigger 140 to trigger the execution 130 of NES QoE measurement with a delay after receiving the measurement command 201 from the network 200 (step 4 in Figure 8). In response to detecting the event-based trigger, the UE sends an AT command 101 including the QoE measurement configuration (step 6 in Figure 8). UE 100 performs QoE measurement collection 130 (step 7 in Figure 8). The UE sends an AT command 103 including the QoE measurement (step 8 in Figure 8).

[0237] UE 100 sends a QoE measurement report 203 to the network (gNB 200) (step 9 in Figure 8). For example, a signaling radio bearer (SRB) (e.g., SRB4) can provide measurement report application layer and RAN-visible parameters: NES QoE parameters.

[0238] As Figure 6 shown in and 8, gNB 200 evaluates 220 the resulting service QoE affected by the NES state (step 10 in Figure 8). gNB 200 determines whether and how to adjust the NES state configuration based on the collected QoE measurement report 203 (step 11 in Figure 8).

[0239] The second use case relates to an alternative implementation for RAN-visible QoE for NES: configuration and reporting. The sending of the QoE measurement report is controlled by an event-based trigger.

[0240] The second use case is shown in Figure 9, which includes features from Figure 5 , 2B and 6.

[0241] In this example, QoE metrics before and after the detection of NES events continue to be reported.

[0242] gNB 200 configures UE 100 using NES mode-specific QoE measurement report triggers, while UE 100 has no NES event detection in the initial stage of data collection. The configuration provided by the gNB is activated via an AT command to trigger data reporting regardless of the NES event conditions. The configuration for NES event condition detection is stored and monitored in UE 100. After detecting an NES event, UE 100 continues data collection 130 but additionally appends information about the NES event detection to the reported data in the QoE measurement report 203.

[0243] As Figure 5 shown in and 9, the network 200 sends a UE capability query 211 to UE 100 (step 1 in Figure 9). UE 100 replies with UE capability information, which includes an indication of RAN-visible NES QoE support (step 2 in Figure 9).

[0244] AsFigure 2B As shown in FIGS. 9, network 200 sends an RRC reconfiguration message to UE 100, including RAN-visible parameters: NES QoE parameters and RAN-visible events: NES event conditions (step 3 in FIG. 9). It may also include an associated reporting period. The RRC reconfiguration message is a QoE measurement command 202 as it includes NES QoE parameters (for measurement) and / or NES event conditions (for event-based triggering).

[0245] UE 100 stores the RAN-visible NES configuration (step 4 in FIG. 9). UE immediately measures 130 and reports 205 NES RAN-visible QoE (not based on NES status events), and then periodically measures 130 and reports 205 NES RAN-visible QoE (not based on NES status events) (steps 5 and 6 in FIG. 9).

[0246] UE sends an AT command 101 including QoE measurement configuration (step 7 in FIG. 9). UE 100 performs QoE measurement collection 130 (step 8 in FIG. 9). UE sends an AT command 103 including QoE measurement (step 9 in FIG. 9).

[0247] UE 100 sends a QoE measurement report 203 to the network (gNB 200) (step 10 in FIG. 9). For example, a signaling radio bearer (SRB) (e.g., SRB4) can provide the measurement report application layer and RAN-visible parameters: NES QoE parameters (without NES event impact).

[0248] UE 100 periodically performs QoE measurement collection 130 and sends an AT command 103 including QoE measurement (steps 12 and 13 in FIG. 9).

[0249] UE 100 monitors 140 event-based triggers 202 to trigger the execution of NES QoE measurements that are delayed after receiving a measurement command 201 from network 200 (step 11 in FIG. 9). The event-based trigger is an NES event condition.

[0250] In response to detecting an event-based trigger, UE 100 attaches an NES event condition detection flag to the received QoE measurement (step 14 in FIG. 9).

[0251] UE 100 sends a QoE measurement report 203 to the network (gNB 200) (step 15 in FIG. 9). For example, a signaling radio bearer (SRB) (e.g., SRB4) can provide the measurement report application layer and RAN-visible parameters: NES QoE parameters (without NES event impact) and RAN-visible flag bit: NES event detected.

[0252] AsFigure 6 As shown in FIGS. 8 and 9, the gNB 200 evaluates the resulting serving QoE affected by the NES state (step 16 in FIG. 9). The gNB 200 determines whether and how to adjust the NES state configuration based on the collected QoE measurement reports 203 (step 17 in FIG. 9).

[0253] The third use case relates to an alternative implementation for RAN visible QoE for NES: configuration and reporting. The QoE measurements are controlled by event-based triggers, and the sending of the QoE measurement reports is controlled by event-based triggers.

[0254] The third use case is shown in FIG. 10, which includes features from Figure 5 、 2D and 6.

[0255] This use case relates to network discontinuous transmission / reception DTX / DRX, where the network 200 can pause / discard any transmission / reception for a given (short) period (such as a few tens of milliseconds). In this example, while the UE 100 is running two user plane services (i.e., service 1 and service 2), the gNB 200 configures NES mode (DTX / DRX)-specific QoE measurements and / or NES mode-specific QoE reporting triggers for the UE 100. The purpose of collecting QoE measurements from the UE 100 at the gNB 200 is to determine how the activation / use of a given NES mode (DTX / DRX) affects the QoE of the services that the UE 100 is running in the RRC_CONNECTED state. Thus, the conventional QoE measurements at the PDU session level (reported by the UE 100 as 205) can be analyzed at the gNB together with the proposed NES-related QoE measurements (reported by the UE 100 as 203). To enable this, NES-related (different) triggers for reporting are needed. First, based on the detected NES-related event 202B of 140B (such as the activation or deactivation of DTX), and second, periodic reporting while the NES mode is active (to be able to understand the evolution of service satisfaction while the NES mode is active).

[0256] The QoE measurement report 203 can be used at the network 200 to determine, for example, whether network DTX / DRX can be applied when any service is running. The decision on whether to apply network DTX / DRX based on the received QoE measurement report can be applied during subsequent parts of the UE session, after the QoE report 203 is received, or during future connections of the same UE (e.g., QoE-impacting information from the NES can be stored in the UE context) or in connections of different UEs requesting the same service. For example, if a (significant) QoE drop is noticed based on the QoE report for service 1 rather than for service 2, the network can activate network DTX / DRX only when service 2 rather than service 1 is running.

[0257] Reference Figure 5 and Figure 10:

[0258] Step 1: UE 100 is in RRC_CONNECTED mode and runs two user plane services (streaming and VR in this example) in 2 PDU sessions.

[0259] Steps 2 and 3: gNB 200 learns about the UE capabilities for RAN-visible QoE measurement configurations. For this, the UE indicates 213 its support for traditional QoE measurements (as already available in the specification, e.g., for streaming or VR services) and also for NES QoE measurements.

[0260] Reference Figure 2D and Figure 10:

[0261] Step 4: gNB 200 configures 201 UE 100 with RAN-visible QoE measurements (parameters and triggers for reporting). Two subsets of parameters can be requested:

[0262] Traditional RAN-visible QoE parameters (service-specific): e.g., the number of cache level entries or the playout delay for media startup.

[0263] NES QoE parameters: e.g., trigger events 202A, 202B.

[0264] Step 5: UE 100 stores the QoE measurement configuration requested by gNB 200.

[0265] Steps 6 to 9: UE initiates 101 QoE measurement 130 for the traditional RAN-visible QoE parameters requested by gNB 200 in step 4. This QoE measurement is reported 205 and can be used at gNB 200 as a reference QoE that UE 100 has when the NES mode is not used.

[0266] Step 10: gNB 200 activates 207 network DTX.

[0267] Step 11: UE 100 identifies the trigger 202B for NES QoE measurement due to NES-related events (i.e., DTX activation) according to the configuration provided by gNB in Step 4.

[0268] Steps 12 - 15: UE 100 initiates 101 QoE measurement 130 and reports traditional RAN visible QoE parameters and / or the NES QoE parameters requested by gNB in Step 4. Along with the QoE measurement, the UE indicates the NES status in the QoE measurement report 203.

[0269] Step 16: If the QoE measurement configuration provided by gNB in Step 4 includes a reporting period, the UE will initiate and report QoE measurement periodically.

[0270] Reference Figure 6 and Figure 10:

[0271] Steps 17 - 18: Based on the NES-related QoE measurement obtained from UE 100, gNB 200 can determine whether the trade-off between user experience and energy saving is good enough to further utilize / adopt one or more NES technologies, or prioritize the QoS configuration to improve the service performance of the UE.

[0272] Step 19: gNB deactivates DTX.

[0273] Step 20: If the QoE measurement configuration provided by gNB in Step 4 includes a DTX deactivation event trigger, the UE will initiate QoE measurement and reporting due to NES-related events (i.e., DTX deactivation).

[0274] Steps 21 and 22: gNB deactivates the QoE measurement configuration.

[0275] If gNB reports NES-related QoE and associated NES configuration to the core / OAM, the above solution can be used to provide further analysis and QoS fine-tuning at the 5G core network.

[0276] Figure 11 An example of the use in the controller 400 applicable to the device 100 or 200 is shown. The implementation of the controller 400 can be controller circuitry. The controller 400 can be implemented solely in hardware, or can have certain aspects in software (including firmware), or can be a combination of hardware and software (including firmware).

[0277] As Figure 11As shown, the controller 400 can be implemented using instructions that enable hardware functions. For example, by using executable instructions of a computer program 406 in a general-purpose or special-purpose processor 402, the executable instructions can be stored on a computer-readable storage medium (such as a disk, memory, etc.) for execution by such a processor 402.

[0278] The processor 402 is configured to read from and write to the memory 404. The processor 402 may also include an output interface and an input interface. The processor 402 outputs data and / or commands via the output interface, and the data and / or commands are input into the processor 402 via the input interface.

[0279] The memory 404 stores a computer program 406, which includes computer program instructions (computer program code). When the computer program instructions are loaded into the processor 402, they control the operation of the device 100. The computer program instructions of the computer program 406 provide the logic and routines that enable the device to execute the methods shown in the figures. The processor 402 can load and execute the computer program 406 by reading the memory 404.

[0280] The device 100 includes:

[0281] At least one processor 402; and

[0282] At least one memory 404, including computer program code

[0283] The at least one memory 404 and the computer program code are configured to, together with the at least one processor 402, cause the device 100 to at least perform:

[0284] Perform QoE measurement;

[0285] Send a QoE measurement report depending on the QoE measurement to the network;

[0286] Process a QoE configuration message received from the network that at least indicates an event-based trigger;

[0287] Monitor the event-based trigger to trigger one or more of the following: perform a QoE measurement, and send a QoE measurement report depending on the QoE measurement and the QoE configuration message.

[0288] The device 100 includes:

[0289] At least one processor 402; and

[0290] At least one memory 404, including computer program code,

[0291] The at least one memory stores instructions that, when executed by the at least one processor 402, cause the device to at least perform:

[0292] Perform QoE measurement;

[0293] Send a QoE measurement report to the network that depends on the QoE measurement;

[0294] Process a QoE configuration message received from the network that at least indicates an event-based trigger;

[0295] Monitor event-based triggers to trigger one or more of the following: performing a QoE measurement, and sending a QoE measurement report that depends on the QoE measurement and the QoE configuration message.

[0296] As Figure 12 shown, the computer program 406 can reach the device 100 via any suitable delivery mechanism 408. The delivery mechanism 408 can be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a recording medium (such as a compact disc read-only memory (CD-ROM) or a digital versatile disc (DVD) or a solid-state memory), an article of manufacture that includes or tangibly embodies the computer program 406. The delivery mechanism can be a signal configured to reliably deliver the computer program 406. The device 100 can propagate or transmit the computer program 406 as a computer data signal.

[0297] Computer program instructions for causing a device to at least perform the following or for at least performing the following:

[0298] Perform QoE measurement;

[0299] Send a QoE measurement report to the network that depends on the QoE measurement;

[0300] Process a QoE configuration message received from the network that at least indicates an event-based trigger;

[0301] Monitor event-based triggers to trigger one or more of the following: performing a QoE measurement, and sending a QoE measurement report that depends on the QoE measurement and the QoE configuration message.

[0302] The computer program instructions can be included in a computer program, a non-transitory computer-readable medium, a computer program product, a machine-readable medium. In some but not necessarily all examples, the computer program instructions can be distributed over more than one computer program.

[0303] Although the memory 404 is shown as a single component / circuit system, it can be implemented as one or more separate component / circuit systems, some or all of which can be integrated / removable and / or can provide permanent / semi-permanent / dynamic / cache storage.

[0304] Although the processor 402 is shown as a single component / circuit system, it may be implemented as one or more separate component / circuit systems, some or all of which may be integrated / movable. The processor 402 may be a single-core or multi-core processor.

[0305] References to "computer-readable storage media", "computer program products", "tangibly embodied computer programs", etc. or "controllers", "computers", "processors", etc. should be understood to include not only computers having different architectures (such as single / multi-processor architectures and sequential (von Neumann) / parallel architectures), but also dedicated circuits (such as field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs)), signal processing devices, and other processing circuit systems. References to computer programs, instructions, code, etc. should be understood to cover software for programmable processors or firmware, such as, for example, programmable content for hardware devices, whether instructions for a processor or configuration settings for fixed function devices, gate arrays, or programmable logic devices, etc.

[0306] As used in this application, the term "circuit system" may refer to one or more or all of the following:

[0307] (a) Only hardware circuit system implementations (such as, only implementations in analog and / or digital circuit systems) and

[0308] (b) Combinations of hardware circuits and software, such as (where applicable):

[0309] (i) Combinations of (multiple) analog and / or digital hardware circuits and software / firmware and

[0310] (ii) Any part of (multiple) hardware processors (including (multiple) digital signal processors) with software, software, and one or more memories that work together to cause a device (such as a mobile phone or a server) to perform various functions and

[0311] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a part of (multiple) microprocessors, that require software (e.g., firmware) to operate, but the software may be absent when operation does not require it.

[0312] This definition of circuit system applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuit system also encompasses implementations of only hardware circuits or processors and their (or their) attendant software and / or firmware. The term circuit system also encompasses, for example, if applicable to a particular claim element, baseband integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0313] The blocks shown in the figures may represent steps in a method and / or portions of code in a computer program 406. The recitation of a particular order of the blocks does not necessarily imply that the blocks have a required or preferred order, and the order and arrangement of the blocks may be changed. Additionally, some blocks may be omitted.

[0314] Where a structural feature has been described, it may be replaced by a component or components that perform one or more of the functions of the structural feature, whether the function or functions are explicitly or implicitly described.

[0315] As used herein, a "module" refers to a unit or device that does not include certain components added by a final manufacturer or user. The UE 100 may be a module. The UE modem 102 may be a module.

[0316] The above examples find use as enabling components in: automotive systems; telecommunications systems; electronic systems (including consumer electronics); distributed computing systems; media systems for generating or presenting media content (including audio, video, and audiovisual content as well as mixed, mediated, virtual, and / or augmented reality); personal systems (including personal health systems or personal fitness systems); navigation systems; user interfaces (also known as human-machine interfaces); networks (including cellular, non-cellular, and fiber-optic networks); ad-hoc networks; the Internet; the Internet of Things; virtualized networks; and associated software and services.

[0317] According to an example of the present disclosure, the apparatus may be provided in an electronic device, such as a mobile terminal. However, it should be understood that the mobile terminal is merely an example of an electronic device that would benefit from the implementations of the present disclosure and should not be considered as limiting the scope of the present disclosure thereto. Although in some implementation examples, the apparatus may be provided in a mobile terminal, other types of electronic devices, such as but not limited to: mobile communication devices, handheld portable electronic devices, wearable computing devices, personal digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices, and other types of electronic systems, may readily adopt the examples of the present disclosure. Additionally, whether the device is intended to provide mobility or not, the device may readily adopt the examples of the present disclosure.

[0318] The term "comprising" is used in this document in an inclusive rather than an exclusive sense. That is, any reference to X comprising Y indicates that X may include only one Y or may include more than one Y. If an exclusive sense of "comprising" is intended, it will be made explicit in the context by reference to "comprising only one..." or by using "consisting of".

[0319] In this specification, the terms "connected", "coupled", and "communicate" and their derivatives mean operationally connected / coupled / communicating. It should be understood that any number or combination of intermediate components (including no intermediate components) may exist, i.e., so as to provide a direct or indirect connection / coupling / communication. Any such intermediate components may include hardware and / or software components.

[0320] As used herein, the term "determine / determining" (and its grammatical variants) may include, but is not limited to: calculating, computing, processing, deriving, measuring, investigating, identifying, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, etc. Additionally, "determine" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), obtaining, etc. Additionally, "determine / determining" may include parsing, selecting, picking, establishing, etc.

[0321] In this specification, various examples have been referred to. A description of a feature or function associated with an example indicates that those features or functions exist in that example. The use of the terms "example" or "for example" or "may" or "might" in the text indicates that, whether explicitly stated or not, these features or functions exist at least in the stated example, whether described as an example or not, and they may but need not exist in some or all other examples. Thus, "example", "for example", "may", or "might" are indicative of a particular instance within a class of examples. The attributes of an instance may be attributes of only that instance, or attributes of the class, or attributes of a subclass of the class that includes some but not all instances of the class. Thus, features described with reference to one example rather than another are implicitly disclosed and, where possible, may be used as part of a working combination in that other example, but need not necessarily be used in that other example.

[0322] Although examples have been described in the preceding paragraphs with reference to various examples, it should be understood that modifications to the given examples may be made without departing from the scope of the claims.

[0323] The features described in the foregoing description may be used in combinations other than those explicitly described above.

[0324] Although functions have been described with reference to certain features, those functions may be executable by other features, whether or not described.

[0325] Although features have been described with reference to certain examples, those features may also exist in other examples, whether or not described.

[0326] As used herein, the terms "a", "an", or "the" have an inclusive rather than an exclusive meaning. That is, any reference to X that includes a / an / the Y indicates that X may include only one Y, or may include more than one Y, unless the context clearly dictates otherwise. If an exclusive meaning of "a", "an", or "the" is intended, it will be made clear in the context. In some cases, the use of "at least one" or "one or more" may be used to emphasize the inclusive meaning, but the absence of these terms should not be taken as inferring any exclusive meaning.

[0327] The presence of a feature (or combination of features) in a claim refers to the feature or (combination of features) itself, as well as features that achieve substantially the same technical effect (equivalent features). Equivalent features include, for example, features of variants that achieve substantially the same result in substantially the same way. Equivalent features include, for example, features that perform substantially the same function in substantially the same way to achieve substantially the same result.

[0328] In this specification, various examples have been referred to in which adjectives or adjective phrases are used to describe the characteristics of the examples. Such a description of a characteristic related to an example indicates that the characteristic is present exactly as described in some examples, and is present substantially as described in other examples.

[0329] The foregoing description describes some examples of the present disclosure. However, those of ordinary skill in the art will recognize possible alternative structural and method features that provide functions equivalent to the specific examples of these structures and features described above herein, and have been omitted from the foregoing description for the sake of brevity and clarity. Nevertheless, the foregoing description should be understood to implicitly include references to these alternative structural and method features that provide equivalent functions, unless these alternative structures or method features are explicitly excluded in the foregoing description of the examples of the present disclosure.

[0330] Although efforts have been made in the foregoing specification to draw attention to those features regarded as important, it should be understood that the applicant may seek protection via the claims for any patentable feature or combination of features mentioned above and / or shown in the drawings, whether or not emphasis has been placed thereon.

Claims

1. A user equipment, comprising components for: Performing quality of experience (QoE) measurements; Sending a QoE measurement report indicating the QoE measurements to a network; Receiving from the network at least a QoE configuration message indicating an event-based trigger; Monitoring at least the event-based trigger to trigger at least one or more of the following: performing QoE measurements, and sending a QoE measurement report indicating the QoE measurements and depending on the QoE configuration message.

2. The user equipment according to claim 1, wherein the QoE configuration message indicates: an event-based trigger for triggering QoE measurements.

3. The user equipment according to claim 1 or 2, wherein the QoE configuration message indicates: a periodicity for the QoE measurements.

4. The user equipment according to any one of the preceding claims, wherein the QoE configuration message indicates: an event-based trigger for triggering the sending of a QoE measurement report.

5. The user equipment according to any one of the preceding claims, wherein the QoE configuration message indicates: the content measured by the QoE measurements.

6. The user equipment according to any one of the preceding claims, wherein the QoE measurements are measurements related to a standardized telecommunication protocol stack and are independent of measurements of one or more services using the standardized telecommunication protocol stack, the standardized telecommunication protocol stack comprising a set of hierarchical protocols that work together to provide a set of standardized telecommunication functions.

7. The user equipment according to any one of the preceding claims, wherein the QoE measurements are measurements related to parameters changed by network energy-saving features.

8. The user equipment according to any one of the preceding claims, wherein the QoE measurements comprise: Measurements of parameters related to the current and / or future processing capabilities of the user equipment.

9. The user equipment according to any one of the preceding claims, wherein the QoE measurements comprise: Measurements of changed operating parameters of the device.

10. The user equipment according to any one of the preceding claims, wherein the QoE measurements include measurements of one or more of the following: Energy usage, overheating, buffer overflow, latency / delay.

11. The user equipment according to any one of the preceding claims, wherein the received QoE configuration message includes an identification reference, and the QoE measurement report includes the identification reference.

12. The user equipment according to any one of the preceding claims, wherein when an event defined by the event-based trigger is determined to have occurred, the event-based trigger triggers one or more of the following: performing QoE measurements, and sending a QoE measurement report indicating the QoE measurements and the QoE configuration message, wherein the event is a non-time event, and / or is related to a standardized telecommunication protocol stack and is independent of one or more services using the standardized telecommunication protocol stack, the standardized telecommunication protocol stack comprising a set of hierarchical protocols that work together to provide a set of standardized telecommunication features.

13. The user equipment according to any one of the preceding claims, wherein the event-based trigger is based on a change in an energy saving feature.

14. The user equipment according to any one of the preceding claims, wherein the energy saving feature comprises: one or more of a network energy saving feature and / or a UE energy saving feature.

15. The user equipment according to any one of the preceding claims, wherein the QoE configuration message is a configuration message comprising additional attributes related to QoE.

16. The user equipment according to any one of the preceding claims, wherein the QoE configuration message extends the QoE framework visible to the 3GPP RAN.

17. The user equipment according to any one of the preceding claims, wherein the event-based trigger is indicated by the network based on L1 / L2 signaling.

18. The user equipment according to any one of the preceding claims, wherein the QoE configuration message is a 3GPP RRCReconfiguration message comprising an AppLayerMeasConfig information element.

19. The user equipment according to any one of the preceding claims, wherein a QoE report identifier is included in an RRC message, the RRC message comprising a MeasurementReportAppLayer message.

20. The user equipment according to any one of the preceding claims, wherein the performing of the QoE measurement is configured to: perform the QoE measurement during an IDLE state and / or during an INACTIVE state.

21. The user equipment according to any one of the preceding claims, wherein the user equipment is configured to provide the network with a capability report indicating a capability for event-based QoE measurement, and / or is configured to provide the network with a capability report indicating a capability for event-based QoE measurement reporting, and / or is configured to provide the network with a capability report indicating a capability for event-based QoE measurement and / or event-based QoE measurement reporting.

22. A system comprising a user equipment and at least one network element, wherein the network element is configured to: use the QoE measurement report received from the user equipment to select a network configuration option from a plurality of network configuration options enabling different network energy savings.

23. A method, comprising: performing a QoE measurement; sending a QoE measurement report indicating the QoE measurement to a network; receiving from the network a QoE configuration message indicating at least an event-based trigger; at least monitoring the event-based trigger to trigger at least one or more of the following: performing a QoE measurement, and sending a QoE measurement report indicating the QoE measurement and depending on the QoE configuration message.

24. A computer program comprising instructions which, when executed by one or more processors, cause: performing a QoE measurement; sending a QoE measurement report indicating the QoE measurement to a network; receiving from the network a QoE configuration message indicating at least an event-based trigger; Monitor at least the event-based trigger to trigger at least one or more of the following: perform QoE measurements, and send a QoE measurement report indicating the QoE measurements and depending on the QoE configuration message.

25. A network device, comprising components for: Sending a quality of experience (QoE) configuration message to a user equipment indicating at least an event-based trigger; Receiving, depending on the event-based trigger, a QoE measurement report from the user equipment indicating QoE measurements performed at the user equipment.

26. The network device according to claim 25, Comprising: Components for selecting a network configuration option from a plurality of network configuration options enabling different network energy saving features using the QoE measurement report received from the user equipment.

27. The network device according to claim 25 or 26, Comprising: Components for including an identification reference in the QoE configuration message sent to the user equipment, for storing a mapping between the identification reference and the user equipment, and for associating the received QoE measurement report with the user equipment based on the stored mapping.

28. A method, Comprising: Sending a quality of experience (QoE) configuration message to a user equipment indicating at least an event-based trigger; and And Receiving, depending on the event-based trigger, a QoE measurement report from the user equipment indicating QoE measurements performed at the user equipment.

29. A computer program, comprising instructions which, when executed by one or more processors, cause: Sending a QoE configuration message to a user equipment indicating at least an event-based trigger; and Receiving, depending on the event-based trigger, a QoE measurement report from the user equipment indicating QoE measurements performed at the user equipment.

Images