WO2022081064A1

WO2022081064A1 - Method for configuring a wireless device for quality of experience (qoe) measurements of an internet of things (lot) application associated with the wireless device

Info

Publication number: WO2022081064A1
Application number: PCT/SE2021/050982
Authority: WO
Inventors: Luca LUNARDI; Cecilia EKLÖF; Angelo Centonza; Johan Rune; Filip BARAC; Ali PARICHEHREHTEROUJENI
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2020-10-15
Filing date: 2021-10-07
Publication date: 2022-04-21
Anticipated expiration: 2023-04-15

Abstract

Methods and apparatus are disclosed. In an example, a method performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurements is disclosed. The method comprises receiving a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (IoT) application associated with the wireless device, and applying the QoE measurement configuration.

Description

Method for configuring a wireless device for Quality of Experience (QoE) measurements of an Internet of Things (loT) application associated with the wireless device

Technical Field

Examples of the present disclosure relate to conditional reconfiguration.

Background

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

QoE measurements in legacy solution

Quality of Experience (QoE) measurements have been specified for Long Term Evolution (LTE) and Universal Mobile Telecommunications System (UMTS). The purpose of the QoE measurements is to measure the end user experience when using certain applications. Currently QoE measurements for streaming services and for MTSI (Mobility Telephony Service for IP Multimedia Subsystem, IMS) services are supported. The solutions in LTE and UMTS are similar with the overall principles as follows. Quality of Experience Measurement Collection enables configuration of application layer measurements in the User Equipment (UE) and transmission of QoE measurement result files by means of Radio Resource Control (RRC) signalling. Application layer measurement configuration received from Operations, Administration and Maintenance (QAM) or Core Network (CN) is encapsulated in a transparent container, which is forwarded to UE in a downlink RRC message. Application layer measurements received from UE's higher layer are encapsulated in a transparent container and sent to network in an uplink RRC message. The result container at forwarded to a Trace Collector Entity (TCE).

In 3GPP release 17 a new study item for “Study on NR QoE management and optimizations for diverse services” for NR has been approved. The purpose of the study item is to study solutions for QoE measurements in NR. QoE management in NR will not just collect the experience parameters of streaming services but also consider the typical performance requirements of diverse services (e.g. Augmented Reality/Virtual Reality, AR/VR, and Ultra Reliable Low Latency Communications, URLLC). Based on requirements of services, the NR study will also include more adaptive QoE management schemes that enable network intelligent optimization to satisfy user experience for diverse services. The measurements may be initiated towards RAN in management-based manner, i.e. from an O&M node in a generic way e.g. for a group of UEs, or they may also be initiated in a signaling-based manner, i.e. initiated from CN to RAN e.g. for a single UE. The configuration of the measurement includes the measurement details, which is encapsulated in a container that is transparent to RAN.

When initiated via the core network, the measurement is started towards a specific UE. For the LTE case, the "TRACE START" S1AP message is used, which carries, among others, the details about the measurement configuration the application should collect (in the “Container for application layer measurement configuration” IE, transparent to the RAN) and the details to reach the trace collection entity to which the measurements should be sent. The Radio Access Network (RAN) is not aware of when the streaming session is ongoing in the UE Access Stratum is also not aware of when the measurements are ongoing. It is an implementation decision when RAN stops the measurements. Typically, it is done when the UE has moved outside the measured area. One opportunity provided by legacy solution is also to be able to keep the QoE measurement for the whole session, even during handover situation.

QoE measurement in E-UTRAN

E-UTRAN - Application layer measurement capabilities For Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN), the UE capability transfer is used to transfer UE radio access capability information from the UE to E-UTRAN. Figure 1 shows an example of E-UTRAN UE capability transfer. As shown in Figure 1, the E- UTRAN transmits a “UECapabilityEnquiry” message to the UE. In the response message “UECapabilitylnformation” from the UE to the E-UTRAN, the UE can include the “UE- EUTRA-Capability” Information Element (IE). The UE-EUTRA-Capability IE is used to convey the E-UTRA UE Radio Access Capability Parameters and the Feature Group Indicators for mandatory features to the network. The “UE-EUTRA-Capability” IE may include the UE-EUTRA-Capability-v1530-IE which can be used by the UE to indicate whether the UE supports or not QoE Measurement Collection for streaming services and/or MTSI services, as detailed in the “MeasParameters-v1530” enconding below.

The contribution CR 4297 (R2-2004624) for 3GPP TS 36.331 v16.0.0, which is incorporated herein by reference, at the 3GPP TSG RAN2 Meeting #110 proposed an extension of the “UE-EUTRA-Capability” IE that, within the “UE-EUTRA-Capability-v16xy-IE” may include a “measParameters-v16xy” comprising the qoe-Extensions-r16 IE. The qoe-Extensions-r16 IE may be used to indicate whether the UE supports the release 16 extensions for QoE Measurement Collection, i.e. if the UE supports more than one QoE measurement type at a time and if the UE supports the signaling of withinArea, sessionRecordinglndication, qoe- Reference, temporaryStopQoE and restartQoE. The QoE-Reference contains the parameter QoE Reference as defined in 3GPP TS 28.405 V16.1.0, which is incorporated herein by reference.

E-UTRAN - Application layer measurement reporting

The purpose of the “Application layer measurement reporting” procedure described in 3GPP TS 36.331 V16.2.1 , which is incorporated herein by reference, is to inform E-UTRAN about application layer measurement report. A UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when configured with application layer measurement, i.e. when measConfigAppLayer has been configured by E-UTRAN.

E-UTRAN - QoE measurement configuration setup and release - RRC signaling The RRCConnectionReconfiguration message is used to reconfigure the UE to setup or release the UE for Application Layer measurements. This is signaled in the measConfigAppLayer-15 IE within the “OtherConfig” IE. The setup includes the transparent container measConfigAppLayerContainer which specifies the QoE measurement configuration for the Application of interest and the serviceType IE to indicates the Application (or service) for which the QoE measurements are being configured. Supported services are streaming and MTSI.

The contribution CR 4297 (R2-2004624) for 3GPP TS 36.331 v16.0.0, which is incorporated herein by reference, at the 3GPP TSG RAN2 Meeting #110 proposed to extend the QoE measurement configuration. The measConfigAppLayerToAddModList-r16 may be used to add or modify multiple QoE measurement configurations (up to maxQoE-Measurement-r16). The measConfigAppLayerToReleaseList-r16 IE may be used to remove multiple QoE measurement configuration (up to maxQoE-Measurement-r16).

E-UTRAN - QoE measurement reporting - RRC signaling

As specified in 3GPP TS 36.331 V16.2.1 , which is incorporated herein by reference, the MeasReportAppLayer RRC message is used by the UE to send to the E-UTRAN node the QoE measurement results of an Application (or service). The service for which the report is being sent is indicated in the “serviceType” IE. The contribution CR 4297 (R2-2004624) for 3GPP TS 36.331 v16.0.0 at the 3GPP TSG RAN2 Meeting #110 proposed to extend the MeasReportAppLayer lEs introducing a QoE reference comprising the Public Land Mobile Network (PLMN) identity and the identifier of the QoE Measurement Collection

Vertical applications characteristics

A vertical domain is a particular industry or group of enterprises in which similar products or services are developed, produced, and provided. Many examples of vertical applications are provided in TS 22.104 v17.2.0, which is incorporated herein by reference, such as factories of the future, electric-power distribution, central power generation, connected hospital or medical facilities. Automation refers to the control of processes, devices, or systems in vertical domains by automatic means. The main control functions of automated control systems include taking measurements, comparing results, computing any detected or anticipated errors, and correcting the process to avoid future errors. These functions are performed by sensors, transmitters, controllers, and actuators.

Cyber-physical systems are referred to as systems that include engineered, interacting networks of physical and computational components. Cyber-physical control applications are to be understood as applications that control physical processes. Cyber-physical control applications in automation follow certain activity patterns, which are open-loop control, closed-loop control, sequence control, and batch control.

Communication services supporting cyber-physical control applications need to be ultrareliable, dependable with a high communication service availability, and often require low or (in some cases) very low end-to-end latency.

Communication in automation in vertical domains follows certain communication patterns. The most well-known is periodic deterministic communication, others are aperiodic deterministic communication and non-deterministic communication.

Activity patterns in automation

Open-loop control: The salient aspect of open-loop control is the lack of feedback from the output to the control; when providing commands to an actuator, it is assumed that the output of the influenced process is predetermined and within an acceptable range. This kind of control loop works if the influences of the environment on process and actuator are negligible. Also, this kind of control is applied in case unwanted output can be tolerated.

Closed-loop control: Closed-loop control enables the manipulation of processes even if the environment influences the process or the performance of the actuator changes over time. This type of control is realized by sensing the process output and by feeding these measurements back into a controller.

Sequence control: Sequence control may either step through a fixed sequence or employ logic that performs different actions based on various system states and system input. Sequence control can be seen as an extension of both open-loop and closed-loop control, but instead of achieving only one output instance, an entire sequence of output instances can be produced.

Batch control: Batch processes lead to the production of finite quantities of material (batches) by subjecting input materials to a defined order of processing actions by use of one or more pieces of equipment.

Communication attributes

Communication in automation can be characterized by two main attributes: periodicity and determinism. Periodicity means that a transmission interval is repeated. For example, a transmission occurs every 15 ms. Reasons for a periodical transmission can be the periodic update of a position or the repeated monitoring of a characteristic parameter. Most periodic intervals in communication for automation are rather short. The repeated transmissions are started once and then continues unless a stop command is provided. An aperiodic transmission is, for example, a transmission which is triggered instantaneously by an event, i.e., events are the trigger of the transmission. Events are defined by the control system or by the user. Example events are:

Process events: events that come from the process when thresholds are exceeded or fallen below, e.g., temperature, pressure, level, etc.

Diagnostic events: events that indicate malfunctions of an automation device or module, e.g., power supply defective; short circuit; too high temperature; etc. Maintenance events: events based on information that indicates necessity of maintenance work to prevent the failure of an automation device.

Most events, and especially alarms, are confirmed. In this context, alarms are messages that inform a controller or operator that an event has occurred, e.g., an equipment malfunction, process deviation, or other abnormal condition requiring a response. The receipt of the alarm is acknowledged usually within a short time period by the application that received the alarm. If no acknowledgment is received from the target application after a preset time, the so-called monitoring time, the alarm is sent again after a preset time or some failure response action is started. Determinism refers to whether the delay between transmission of a message and receipt of the message at the destination address is stable (within bounds). Usually, communication is called deterministic if it is bounded by a given threshold for the latency/transmission time. In case of a periodic transmission, the variation of the interval is bounded.

Communication patterns

In practice, vertical communication networks serve a large number of applications exhibiting a wide range of communication requirements. In order to facilitate efficient modelling of the communication network during engineering and for reducing the complexity of network optimization, traffic classes or communication patterns have been identified [6], There are three typical traffic classes or communication patterns in industrial environments [6], i.e. , deterministic periodic communication: periodic communication with stringent requirements on timeliness of the transmission. deterministic aperiodic communication: communication without a preset sending time. Typical activity patterns for which this kind of communication is suitable are event-driven actions. non-deterministic communication: subsumes all other types of traffic, including periodic non-real time and aperiodic non-real time traffic. Periodicity is irrelevant in case the communication is not time-critical.

Some communication services exhibit traffic patterns that cannot be assigned to one of the above communication patterns exclusively (mixed traffic).

Summary

One aspect of the present disclosure provides a method performed by a wireless devicefor configuring the wireless device for Quality of Experience (QoE) measurements. The method comprises receiving a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device, and applying the QoE measurement configuration.

Another aspect of the present disclosure provides a method performed by a network node for configuring a wireless device for Quality of Experience (QoE) measurements. The method comprises sending a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device.

A further aspect of the present disclosure provides a wireless device comprising a processor and a memory. The memory contains instructions executable by the processor such that the wireless device is operable to receive a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device, and apply the QoE measurement configuration.

A still further aspect of the present disclosure provides a network node for configuring a wireless device for Quality of Experience (QoE) measurement reporting. The network node comprises a processor and a memory. The memory contains instructions executable by the processor such that the wireless device is operable to send a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device.

Another aspect of the present disclosure provides a wireless device configured to receive a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device, and apply the QoE measurement configuration.

An additional aspect of the present disclosure provides a network node for configuring a wireless device for Quality of Experience (QoE) measurement reporting. The network node is configured to send a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device. Brief Description of the Drawings

For a better understanding of examples of the present disclosure, and to show more clearly how the examples may be carried into effect, reference will now be made, by way of example only, to the following drawings in which:

Figure 1 shows an example of E-UTRAN UE capability transfer;

Figure 2 depicts an example of a method performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurements;

Figure 3 depicts an example of a method performed by a wireless device for Quality of Experience (QoE) measurement reporting;

Figure 4 depicts an example of a method performed by a network node for configuring a wireless device for Quality of Experience (QoE) measurements;

Figure 5 illustrates a schematic block diagram of an apparatus in a wireless network;

Figure 6 illustrates another schematic block diagram of an apparatus in a wireless network;

Figure 7 illustrates another schematic block diagram of an apparatus in a wireless network;

Figure 8 shows an example of a wireless network in accordance with some embodiments;

Figure 9 shows an example of a User Equipment (UE) in accordance with some embodiments;

Figure 10 is a schematic block diagram illustrating a virtualization environment in accordance with some embodiments;

Figure 11 shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;

Figure 12 shows a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;

Figure 13 shows methods implemented in a communication system in accordance with some embodiments;

Figure 14 shows methods implemented in a communication system in accordance with some embodiments;

Figure 15 shows methods implemented in a communication system in accordance with some embodiments; and Figure 16 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

Detailed Description

The following sets forth specific details, such as particular embodiments or examples for purposes of explanation and not limitation. It will be appreciated by one skilled in the art that other examples may be employed apart from these specific details. In some instances, detailed descriptions of well-known methods, nodes, interfaces, circuits, and devices are omitted so as not obscure the description with unnecessary detail. Those skilled in the art will appreciate that the functions described may be implemented in one or more nodes using hardware circuitry (e.g., analog and/or discrete logic gates interconnected to perform a specialized function, ASICs, PLAs, etc.) and/or using software programs and data in conjunction with one or more digital microprocessors or general purpose computers. Nodes that communicate using the air interface also have suitable radio communications circuitry. Moreover, where appropriate the technology can additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analogue) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.

There currently exist certain challenge(s). For example, currently, QoE metrics in 3GPP are defined for the services where the end consumer of the service is a human (herein referred to as the legacy case). However, with the appearance of Internet of Things (loT), it becomes clear that the end user may also be a machine, which incurs significant differences, compared to the legacy case. For example, the asymmetry between the amount of uplink and downlink traffic is not as prevalent in machine-to-machine communication, compared to the legacy case. QoE metrics well adapted to the previously described use cases and communication patterns of Industrial Internet of Things (HoT) and Massive Internet of Things (MIoT) are currently not available.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, embodiments of this disclosure may introduce new QoE metrics for Industrial loT (I loT) and/or new QoE metrics for Massive loT (MIoT). There are, proposed herein, various embodiments which address one or more of the issues disclosed herein. For example, one aspect of this disclosure provides a method performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurement reporting. The method comprises receiving a Quality of Experience (QoE) measurement reporting configuration, wherein the QoE measurement reporting configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device, and applying the QoE measurement reporting configuration.

In another example, an aspect of this disclosure provides a method performed by a wireless device for Quality of Experience (QoE) measurement reporting. The wireless device is configured with a Quality of Experience (QoE) measurement reporting configuration, wherein the QoE measurement reporting configuration identifies one or more metrics for measurement reporting. The method comprises reporting the one or more metrics to a network node. The one or more metrics comprise one or more of:

(i) a property of a measured parameter identified by the QoE measurement reporting configuration;

(ii) an energy consumption and/or or energy efficiency of a task performed by the wireless device or another device;

(iii) an execution time of a task performed by the wireless device or another device;

(iv) a metric relating to a survival mode or downtime of the wireless device or another device;

(v) a metric identifying to uptime of the wireless device or another device;

(vi) a metric relating to timing of communications by the wireless device or another device;

(vii) a metric identifying a number or type of fault conditions experienced by the wireless device or another device; (viii) a metric identifying requirements for recovering from a survival mode or downtime of the wireless device or another device;

(ix) a metric identifying utilization of the wireless device or another device;

(x) a metric identifying a level of resources required by the wireless device or another device; and

(xi) a metric identifying a power status or variation in power status of the wireless device or another device.

In another example, an aspect of the present disclosure provides a method performed by a network node for configuring a wireless device for Quality of Experience (QoE) measurement reporting. The method comprises sending a Quality of Experience (QoE) measurement reporting configuration to the wireless device, wherein the QoE measurement reporting configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device.

Certain embodiments may provide one or more of the following technical advantage(s). For example, examples of this disclosure may provide new QoE metrics for Industrial loT and Massive loT, which may allow QoE measurements and reported QoE metrics to be more relevant and useful in related use cases.

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

In an example, a method is provided performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurement reporting. The method comprises receiving a Quality of Experience (QoE) measurement reporting configuration, wherein the QoE measurement reporting configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device, and applying the QoE measurement reporting configuration. Figure 2 depicts a method 200 in accordance with particular embodiments, for example a method performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurements. The method begins at step 202 with receiving a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device, and continues to step 204, with applying the QoE measurement configuration.

An loT application may be, for example, a software and/or hardware application or process that is implemented in or executing on the wireless device (and thus the application is associated with the wireless device), or for example the wireless device may perform communication including reporting QoE measurements for the application (which may in some examples be implemented or executing on another device), and thus the application is associated with the wireless device in this way. Examples of loT applications may include, for example, industrial control applications or applications that implement the examples of vertical applications that are provided in TS 22.104 v17.2.0 (which is incorporated herein by reference), such as factories of the future, electric-power distribution, central power generation, connected hospital or medical facilities.

The one or more metrics may comprise for example one or more of the following:

(i) a property of a measured parameter identified by the QoE measurement configuration;

(ii) an energy consumption and/or energy efficiency of a task performed by the wireless device or another device;

(v) a metric identifying to uptime of the wireless device or another device;

(vii) a metric identifying a number or type of fault conditions experienced by the wireless device or another device;

(viii) a metric identifying requirements for recovering from a survival mode or downtime of the wireless device or another device; (ix) a metric identifying utilization of the wireless device or another device;

In some examples, the one or more metrics comprise or include a property of a measured parameter identified by the QoE measurement configuration. The property of the measured parameter may comprise for example one or more of:

(i) an accuracy or precision of the measured parameter;

(ii) whether the measured parameter has exceeded a predetermined threshold; and

(iii) an amount by which the measured parameter has exceeded a predetermined threshold.

In some examples, the one or more metrics comprise a metric relating to a survival mode or downtime of the wireless device or another device. The metric relating to a survival mode or downtime may comprise for example one or more of:

(i) a length of time spent in downtime for the wireless device or another device;

(ii) an amount of information not received by the wireless device or another device;

(iii) a status of the wireless device or another device after the survival mode or downtime; and

(iv) an identification of an event that caused the survival mode or downtime.

In some examples, the one or more metrics comprise a metric relating to timing of communications by the wireless device or another device. The metric relating to timing of communications may comprise for example one or more of:

(i) a mean or range of latency for communications by the wireless device or another device;

(ii) a number or fraction of communications delivered or acknowledged for the wireless device or another device within a predetermined interval; and

(iii) a time between commands received by the wireless device or another device.

The QoE measurement configuration may be received in some examples, from a network node, such as for example a gNB, eNB, en-gNB, ng-eNB, gNB-Cll, gNB-CU-CP, eNB-Cll, eNB-CU-CP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU, IAB MT, or other network node (including a core network node).

In some examples, the QoE measurement configuration is received in a RRC message, such as for example a RRCConnectionReconfiguration message.

In some examples, the one or more metrics are based on a determination that the QoE measurement configuration relates to measurements of at least one Internet of Things (loT) application associated with the wireless device.

In another example, a method performed by a wireless device for Quality of Experience (QoE) measurement reporting is provided, wherein the wireless device is configured with a Quality of Experience (QoE) measurement reporting configuration, and the QoE measurement reporting configuration identifies one or more metrics for measurement reporting. The method comprises reporting the one or more metrics to a network node.

Figure 3 depicts a method 300 in accordance with particular embodiments, such as for example a method performed by a wireless device for Quality of Experience (QoE) measurement reporting, wherein the wireless device is configured with a Quality of Experience (QoE) measurement configuration or measurement reporting configuration, wherein the QoE measurement (reporting) configuration identifies one or more metrics for measurement reporting. The method begins at step 302 with reporting one or more metrics to a network node. In examples of this disclosure, the terms measurement configuration and measurement reporting configuration may be used interchangeably.

The one or more metrics comprise one or more of:

(v) a metric identifying to uptime of the wireless device or another device; (vi) a metric relating to timing of communications by the wireless device or another device;

(viii) a metric identifying requirements for recovering from a survival mode or downtime of the wireless device or another device;

(ix) a metric identifying utilization of the wireless device or another device;

In some examples, the one or more metrics comprise a property of a measured parameter identified by the QoE measurement reporting configuration. The property of the measured parameter may comprise for example one or more of:

(i) an accuracy or precision of the measured parameter;

(ii) whether the measured parameter has exceeded a predetermined threshold; and

(i) In some examples, the one or more metrics comprise a metric relating to a survival mode or downtime of the wireless device or another device. The metric relating to a survival mode or downtime may comprise for example one or more of:

(iv) an identification of an event that caused the survival mode or downtime.

(i) a mean or range of latency for communications by the wireless device or another device; (ii) a number or fraction of communications delivered or acknowledged for the wireless device or another device within a predetermined interval; and

In some examples, the network node comprises a gNB, eNB, en-gNB, ng-eNB, gNB-Cll, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU, IAB MT or other network node (including a core network node).

In any of the methods disclosed herein, in some examples, the wireless device is associated with at least one Internet of Things (loT) application, and the metrics for measurement reporting comprise metrics for the loT application.

Figure 4 depicts a method in accordance with particular embodiments, for example a method performed by a network node for configuring a wireless device for Quality of Experience (QoE) measurements. The method begins at step 402 with sending a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device.

The one or more metrics may comprise for example one or more of:

(v) a metric identifying to uptime of the wireless device or another device;

In some examples, the one or more metrics comprise a property of a measured parameter identified by the QoE measurement configuration. The property of the measured parameter may comprise for example one or more of:

(i) an accuracy or precision of the measured parameter;

(ii) whether the measured parameter has exceeded a predetermined threshold; and

(iv) an identification of an event that caused the survival mode or downtime.

(iii) a time between commands received by the wireless device or another device. In some examples, the network node comprises a gNB, eNB, en-gNB, ng-eNB, gNB-Cll, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, lAB-donor DU, lAB-donor-CU, IAB-DU, IAB MT or other network node (including a core network node).

In some examples, the QoE measurement configuration is sent to the wireless device in a RRC message, such as for example a RRCConnectionReconfiguration message.

The wireless device in some examples of any method disclosed herein may be associated with an industrial control device or application, and the metrics for measurement comprise metrics for the industrial control device or application.

In some examples, the method further comprises, before sending the QoE measurement configuration to the wireless device, determining that the QoE measurement configuration relates to measurements of at least one Internet of Things (loT) application associated with the wireless device, and wherein the one or more metrics are based on the determination that the QoE measurement configuration relates to measurements of at least one Internet of Things (loT) application associated with the wireless device.

Figure 5 illustrates a schematic block diagram of an apparatus 500 in a wireless network (for example, the wireless network shown in Figure 8). The apparatus may be implemented in a wireless device (e.g., wireless device QQ110 shown in Figure 8). Apparatus 500 is operable to carry out the example method described with reference to Figure 2 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 2 is not necessarily carried out solely by apparatus 500. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving unit 502, applying unit 504 and any other suitable units of apparatus VWV00 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in Figure 5, apparatus 500 includes receiving unit 502 configured to receive a Quality of Experience (QoE) measurement configuration, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device, and applying unit 504 configured to apply the QoE measurement configuration.

Figure 6 illustrates a schematic block diagram of an apparatus 600 in a wireless network (for example, the wireless network shown in Figure 8). The apparatus may be implemented in a network node (e.g., network node QQ160 shown in Figure 8). Apparatus 600 is operable to carry out the example method described with reference to Figure 3 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 3 is not necessarily carried out solely by apparatus 600. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 600 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause reporting unit 602 and any other suitable units of apparatus 600 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in Figure 6, apparatus 600 includes reporting unit 602 configured to report one or more metrics to a network node. The one or more metrics comprise one or more of: (i) a property of a measured parameter identified by the QoE measurement reporting configuration;

(v) a metric identifying to uptime of the wireless device or another device;

(ix) a metric identifying utilization of the wireless device or another device;

Figure 7 illustrates a schematic block diagram of an apparatus 700 in a wireless network (for example, the wireless network shown in Figure 8). The apparatus may be implemented in a network node (e.g., network node QQ160 shown in Figure 8). Apparatus 700 is operable to carry out the example method described with reference to Figure 4 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 4 is not necessarily carried out solely by apparatus 700. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause sending unit 702 and any other suitable units of apparatus 700 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in Figure 7, apparatus 700 includes sending unit 702 configured to send a Quality of Experience (QoE) measurement configuration to the wireless device, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device.

Particular examples will now be described. Examples of this disclosure may extend the existing QoE metrics to loT use cases, such as for example Industrial loT and Massive loT use cases. The involved entities, such as the entity creating the QoE measurement configuration, the Radio Access Network forwarding the QoE Measurement Configuration to UEs and, when applicable, may selects the wireless devices (referred to herein in some examples as User Equipments, UEs) to be subject to the QoE Measurement Configuration, the UEs interpreting the extended (novel) QoE metrics and performing the QoE measurements and reporting the result, and the entity being the end receiver of the reported results, e.g. a TCE/MCE or an entity obtaining information from a TCE/MCE, are enabled to use such new QoE metrics (to the extent required for the respective entity).

QoE metrics for I loT and MIoT

The following QoE metrics can be defined for QoE monitoring purposes for Industrial loT applications and/or Massive loT applications:

Accuracy per task (e.g. an example of property of a measured parameter) o An example of application that could benefit from such QoE metrics is the following: in motion control systems where sensors are connected to a workpiece and report the status of the production to the controller, the controller can compare this information to a configured target and produce a QoE report towards a monitoring system to check the production accuracy. One way to represent this could be in terms of the standard deviation in relation the expected outcome of the task. For instance, in conjunction with shaping of a workpiece, e.g. using lathing, the deviation from the target diameter could be measured and reported in a QoE report, e.g. in terms of the standard deviation.

Timing accuracy (e.g. an example of property of a measured parameter) o This represents the timeliness of the application, i.e. the range between the minimum and maximum end-to-end latency. In applications with periodic deterministic communication, a message (command) has to be correctly delivered not too early and not too late, i.e. within the timeliness interval. A message correctly delivered within the timeliness interval will make the application consider the communication service as “ok”. A message correctly delivered outside the timeliness interval or not correctly delivered within the timeliness interval will make the application consider the communication service as “not ok”. o This QoE metrics may be represented e.g. as the fraction of the messages that were delivered within the timeliness interval (i.e. the service was considered “OK”) or the fraction of the messages that were delivered outside the timeliness interval (i.e. the service was considered “not OK”. Alternatively, the metrics can comprise the number of messages delivered within the timeliness interval and the number messages delivered outside the timeliness interval. As an alternative, or as a complement, the metrics may be represented as a mean value and a standard deviation. The mean value could be the mean value of the difference between the time of delivery of a message and the middle of the message’s timeliness interval. Alternatively, the mean value could be the mean value of the difference between the time of delivery of a message and the start of the message’s timeliness interval.

Precision per task (e.g. an example of property of a measured parameter) o As an example, in a production environment, sensors can measure the dimensions of a workpiece and report this information to a controller. The controller can assess how close the measurements reported during a configured time interval or for at least one actuator are close to each other and further report this metric to a monitoring system to check the production precision. The measure can e.g. be a standard deviation of the difference from the mean value for the actuator and/or within the configured time interval.

Safety margin abidance (e.g. an example of property of a measured parameter, whether the measured parameter has exceeded a predetermined threshold, or an amount by which the measured parameter has exceeded a predetermined threshold) o A quantification of how “far” from the “safety limit” a measurable has been. For example, in scenarios involving remotely steered vehicles (drones, platooning vehicles, tools in mines etc.), the metric indicates often the vehicle’s distance from other vehicles/objects was less than a distance considered safe.

Energy efficiency per task o An example of an application that could benefit from such QoE metrics is the following: in a production chain, a robot performs repetitive tasks and consumes a certain amount of energy (e.g. per hour or per day). The consumed energy is reported to a controller which produces QoE reports to monitor the production efficiency.

Execution time per received command o An example of application that could benefit from such QoE metrics is the following: in case of productions environments where deterministic and periodic communication is used, such metric can be used to indicate deviations in the production quality or the number of produced units.

Time between consecutive reception of commands o This metric can be seen as somewhat similar to the previous and focuses more on the ability of an application to receive consecutive commands expected with a certain time interval in between them, before they are executed.

Time between reception of command and completion of task o This metric somehow comprises the ability of an application to receive commands as well as the capability to complete a required task on time.

Operation in survival time (or survival mode) o This measurement could consist of the number of packets, or in general of a quantification of information, that were missed by the application (e.g. information that were supposed to be received from an external system, but that were not received) but that did not imply halting of normal working processes at the application, namely the application was able to continue working as normal. o Alternatively, the measurement could be an indication of the time during which the application performed as normal, but in absence of information that were supposed to be received, e.g. packets from a different application, protocol, network node etc. o The reported metric could include, or be complemented by, an indication of how close the application/process/device was to being stopped, e.g. how much longer the application/process/device is able to operate in survival time. o The reported metric could include an indication of how long the application/process/device has been operating in survival time or how long an ended period of operation in survival time was or, in case multiple separate periods of operation in survival time are reported, indications of the length of each of the survival time operation periods (optionally including timestamps of starts and ends of the periods). o The reported metric could include, or be complemented by, an indication of whether the period of operation in survival time ended by resumption of normal operation or halt of the operation. o An example that could benefit from such QoE metrics is the following: in an industrial environment, a distributed automation function running on a first (source) device sends commands (messages) to and a second (target) device. The target device expects to receive consecutive commands within a configured period. When the target device does not receive a command at the expected time, it can wait an extra time (survival time) before transitioning from the current state (e.g. in-production) to a different state (e.g. the production paused). o Other QoE metrics could be specifically associated with the periods during which the device/process operates in survival time or may have dedicated configurations associated with operation in survival time:

■ A QoE Measurement Configuration could include that a certain QoE metric should be measured only while the device/process/application operates in survival time.

■ A QoE Measurement Configuration could include that a certain QoE metric should be measured more frequently while the device/process/application operates in survival time than when the device/process/application does not operate in survival time (e.g. when the device/process/application operates normally).

■ A QoE Measurement Configuration could include that a certain QoE metric should not be measured while the device/process/application operates in survival time (for instance, the QoE metric may only be applicable when the device/process/application operates normally).

■ QoE metrics which are anyway configured to be measured, irrespective of normal operation or operation in survival time, may have an associated indication indicating whether the QoE metric was collected while the device/process/application was operating in survival time. For instance, every sample, or every set (or partial set) of samples processed into a QoE metric value, may have such an indication. As one option, the indication may be an explicit indication. As another option, the indication may be a timestamp which can be correlated with the reported time period(s) during which the device/process/application was operating in survival time.

■ Any QoE metric could be of interest in the above (i.e. could have specific QoE Measurement Configuration properties associated with operation in survival time), but specifically of interest may be e.g. Accuracy of task, Precision of task Number and type of reported faults. More generic QoE metrics, e.g. related to the data traffic characteristics, such as data rate, jitter and/or latency, may also be subject to special QoE Measurement Configuration properties associated with operation in survival time.

Occurrence of downtime (or halt-time) o This is an indication of the downtime event, namely the event according to which the application stopped working in normal conditions. Together with this event, the application can indicate the overall time for which the application was net working as per normal conditions. o As an example, the application might have experienced a certain period of operation in survival time but the condition triggering survival time operation could not be resolved, hence the application experienced downtime.

Recovery time (e.g. requirements for recovering from a survival mode or downtime) o This is a metric that indicates the time or the amount or number of packets, or a quantification of information needed, to allow the application to recover from a down time and return to normal operation o An example is that of an application that experienced down time due to e.g. loss of a certain number of packets expected to be received from lower layers. The application then starts receiving packets correctly again. However, before the application can operate normally a certain number of packets need to be received, which might be reported in this metric.

Availability o The availability metric is a measure of the application uptime over the (uptime + downtime). This metric gives the percentage of time the application was performing as normal and it might be used to check if the overall system performance is sufficient to maintain an availability level in line with the Service Level Agreements set for the service associated to the application. As a variation, the metric may give the percentage/fraction of time the application is available for operation (e.g. there is no malfunctioning), irrespective of whether it is actually utilized or is in an idle state (due to lack of tasks to perform).

Utilization o This metric captures the degree to which an application or process utilizes its full capacity. This may for instance be measured in terms of the fraction of the full speed of a process (i.e. the process’s operating speed in relation to its maximum speed). It may also be measured in terms of how many of a set of parallel instances of a type of equipment (or the fraction of the full number of equipment instances) that are utilized/operating, e.g. involving manufacturing equipment. The utilization may be reported in percent of full utilization, i.e. in the range 0% - 100%. Alternatively, the utilization may be reported as a number in the range 0 - 1. Yet other alternatives include reporting the number of operating equipment instances or the operation speed (accompanied by indications of the full number of equipment instances or the maximum operation speed, unless these values are assumed to be known by the receiver of the report).

Number and type of reported faults o This metric reports the number of faults an application has detected. The number of faults could be of different types, e.g. it could consist of an information that was supposed to be received and it is missing, or it could be the lack of communication with other parts of the system. Faults could be reported as aggregated faults, irrespective of type of fault, i.e. without distinguishing fault types in the report. As another option, the faults may be categorized (e.g. a set of default types per category) and reported per category. As yet another option, each individual fault type may be reported separately o The application might have a certain robustness and therefore it might be able to still work as normal or with a certain performance degradation, in occurrence of faults. In this case the metric may report also whether the application is working under normal conditions while reporting the faults detected, or whether the application is net working under normal conditions, but it is working under degraded performance. A quantification of the performance degradation may also be provided as part of the metric. An additional indication could be how close the application was to be stopped because of the reported faults. o The reported fault information may comprise more details and information than purely occurrence and number. For instance, a single reported fault may be associated with any combination of:

■ an indication of fault type,

■ a timestamp,

■ an indication of severity,

■ an indication of whether the fault caused a process/device/application to halt.

If the faults are reported in an aggregated manner, e.g. per fault type, complementing information could be any combination of:

• an indication of fault type,

• an indication of the time period during which the reported faults occurred (e.g. start and end times),

• an indication of the maximum severity of the reported faults,

• an indication of whether the fault caused a process/device/application to halt.

Cooperation status o In a system with multiple applications distributed among different devices that cooperate to perform one task, the application residing in the device (or function) coordinating the task can collect measurements from the participants and produce an aggregated QoE metric indicating the performance of the overall system. An example can be represented by a cooperative carrying system where multiple mobile robots work together to carry work pieces.

Battery status (e.g. an example of power status) o For devices not connected to a power grid, an indication of the battery status that is sent, e.g. periodically can be useful to detect when such devices require to replaced or maintained. Depending on the type of device, the periodicity can vary quite a lot, e.g. in a range from hours to weeks. As an example, an equipment running on battery and meant to replace an equipment normally connected to power grid can communicate its battery status every hour or so. As another example, an loT device which is expected to function for years in the same place, can be asked to report its battery status once per week. Variation of battery status over time (e.g. an example of variation in power status over time) o this metric can be used for similar purposes as the previous metric and focuses on the variation of the battery charge over a configured period. This may be particularly useful, when the battery is charged by an off-grid energy/power source, such as a solar panel.

Scalability (e.g. an example of a level of resources required) o Certain tasks may be possible to perform one at a time, but not multiple at the same time. A scalability factor could show the potential scalability of the task. o For example, an index can be associated to each task, such index (e.g. a numerical 0 to 100) may represent whether the process can be performed in parallel with other processes, or on the contrary, that the process should be allocated full processing power and not be performed in parallel with other tasks.

Reliability of the measurement (e.g. an example of a property of a measured parameter) o In I loT scenarios the reliability of the measurement could be of interest. The UE may e.g. have measured a certain accuracy, but also the measured result has a certain accuracy which could be reported, e.g. in terms of a relative or absolute range within which the fault is bounded/contained with a certain probability.

For any or all of the above, timestamps or time interval indications may be associated with the reported QoE metrics, to facilitate correlation of e.g. Timing accuracy with Accuracy per task or Precision per task.

The new QoE metrics can be reported in some examples according to one or more of various criteria: minimum, maximum, median, variance, standard deviation, average (over time, over a number of samples), percentage, and according to various patterns, such as: periodically, semi-periodically (with different periodicities), on-demand, in batches.

The influence of uplink communication on I loT QoE metrics

In the above considerations, the focus was on the downlink (DL) communication, in the sense that the reported metrics reflect the influence of DL communication on the KPIs of the production process. For example, a delayed (or lost in transit over the air) command may activate the failsafe mechanism and stop the production. Nevertheless, it is important to note that:

• For many time- and safety-critical applications, the communication with the control system is closed-loop. In particular, the control system issues commands to the actuators (e.g. collocated with the UEs) based on sensor readings, whereas these sensor readings are delivered via uplink (UL) communication. In other words, a delayed delivery of a sensor reading will lead to a delayed issuance of a command from the control system, or an issuance of a sub-optimal command, which will affect the industrial process. Herein, the term “sensor reading” denotes any kind of application level information, sent from the UE to the network (i.e. on UL), that has influence on the content for DL application level information (e.g. commands to actuators).

• There exist UL-centric lloT applications, such as e.g. video surveillance.

Therefore, a use case of interest for 11 oT QoE is the one where the UL transmission resources for a UE are adjusted based on the analysis of the QoE report (in addition to the “traditional” adjustment of DL resources). With respect to the above, the following metrics can be defined:

• The number of times the process was halted or entered survival time due to a delayed command (sent on DL), where the delay of the command was preceded (i.e. caused) by the delayed delivery of one or more sensor reading (sent on UL), based on which this command is assembled.

• The survival time-related metrics from chapter 5.1 , with the difference that the “survival time” in the UL context refers to the ability of the control system (in the DL context it was the ability of the UE) to operate ’’normally” in the absence of UL connection. “Operating normally” means the ability to issue the commands (sent on DL) that do not lead to process halt.

Different interpretations of the newly proposed metrics

Several of the above described QoE metrics can have different interpretations. For instance, the Efficiency per task metrics may be measured in terms of consumed energy or amount of wasted material, depending on the nature of the task and/or process being monitored and what efficiency measure you are interested in. As another example, if the Accuracy per task metrics is applied to a task of shaping a workpiece, the accuracy may be measured in terms of deviation from a target length, deviation from a target width or deviation from a target height.

However, when standardizing a QoE metric, it is very impractical to standardize a separate metric for each possible application or interpretation. Therefore, the metric should be more generic and only its representation format (e.g. mean value and standard deviation) should be standardized. Then it is up to the application or entity making use of the reported metrics to ensure at the application level that a certain real-world entity (e.g. workpiece length accuracy or energy efficiency) is mapped to a QoE metric with a suitable representation format.

Furthermore, an organization, application or entity may be interested in multiple interpretations or aspects (real-world entities) mapping to the same QoE metric format (e.g. both energy efficiency and material efficiency of a task or all three of length, width and height accuracy of a shaped workpiece). To cover such scenarios, the configuration and reporting of QoE measurements/data should allow multiple instances of the same QoE metric, e.g., in terms of ASN.1 code:

QoE-Metricl-List : : = SEQUENCE ( SI ZE ( 1 . . maxNoOfQoE-Metricl ) ) OF QoE- Metricl QoE-Metricl : : = SEQUENCE { meanValue INTEGER (minMean . . maxMean ) OPTIONAL, standardDeviation INTEGER (minStdDev . . maxStdDev) }

Note that the INTEGER type parameters may easily be converted to non-integer numbers, e.g. floating-point numbers. For instance, if non-integer/floating-point numbers with two decimals are desired, the INTEGER parameters may represent the floating-point numbers multiplied by 100 (rounded to the closest integer value if applicable).

Even more generic could be to not specify the actual format of the QoE metric parameters, but instead let them be generic bit strings and leave the interpretation of them be determined in conjunction with each use case. For instance, when a monitoring configuration is set up, e.g. when an enterprise puts monitoring of an industrial process in place, the entity/organization/enterprise responsible for the setup decides what data to fill the bit strings with, as well as how many of the available bit strings to use.

QoE-Metricl-List : := SEQUENCE (SIZE ( 1.. maxNoOfQoE-Metricl ) ) OF QoE- Metricl

QoE-Metricl : := SEQUENCE (SIZE ( 1. . maxNoOfValuesInQoE-Metricl ) ) OF BIT STRING (SIZE (bitStringSizeMetricl) )

The above two ASN.l examples may also be combined in a CHOICE structure, e.g. :

QoE-Metricl : := CHOICE { distribution SEQUENCE { meanValue INTEGER (minMean. .maxMean) OPTIONAL, standardDeviationINTEGER (minStdDev. .maxStdDev) }, genericValues SEQUENCE (SIZE ( 1. .maxNoOfValuesInQoE-

Metricl) ) OF BIT STRING (SIZE (bitStringSizeMetricl) ) }

Another example where the QoE metric may have different interpretations is the Occurrence of downtime metric. This QoE metric could represent a multitude of use case specific events. In the UE and the 3GPP system, this can be captured as illustrated by the three following ASN.1 examples, where the event is represented as a BIT STRING or ENUMERATED type of parameter. With the bit string representation, the use case specific interpretation would be defined by the entity/organization/enterprise setting up the QoE monitoring, and this definition may be transparent/invisible to the 3GPP system.

ASN.1 code example with BIT STRING representation of occurrence of downtime:

OccurrenceOf DowntimeList : := SEQUENCE (SIZE (1. . maxNoOfOccurrenceOf Downtimeinfo ) ) of OccurrenceOf Downtimeinfo

OccurrenceOf Downtimeinfo ; ;= BIT STRING (SIZE (bitStringSizeOccurrenceOf Downtimeinfo ) )

ASN.l code example with ENUMERATED representation of occurrence of downtime : OccurrenceOf DowntimeList : := SEQUENCE (SIZE (1. . maxNoOfOccurrenceOf Downtimeinfo ) ) of OccurrenceOf Downtimeinfo

OccurrenceOf Downtimeinfo ; ;= ENUMERATED {eventTypel, eventType2, eventType3 , eventType4 , eventType5 , eventType6 , eventType7 , eventType8 , eventType9 , eventTypel O , eventTypel l , eventType!2 , sparel , spare2 , spare3 , spare4 }

ASN.1 code example with choice of BIT STRING or ENUMERATED representation of occurrence of downtime:

OccurrenceOf DowntimeList : : = SEQUENCE ( SI ZE ( 1 . . maxNoOfOccurrenceOf Downtimeinfo ) ) of

OccurrenceOf Downtimeinfo

OccurrenceOf Downtimeinfo ; ; = CHOICE { genericEventType BIT STRING ( SI ZE

(bitStringSi zeOccurrenceOfDowntimelnfo ) ) , explicitEventType ENUMERATED { eventTypel , eventType2 , eventType3 , eventType4 , eventType5 , eventType6 , eventType7 , eventType8 , eventType9 , eventTypel O , eventTypel l , eventTypel2 , sparel , spare2 , spare3 , spare4 }

}

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 8. For simplicity, the wireless network of Figure 8 only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ110, QQ110b, and QQ110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide- area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node QQ160 and WD QQ110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E- SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In Figure 8, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of Figure 8 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.

Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry QQ170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hardwired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.

Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170. Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components. In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omnidirectional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as Ml MO. In certain embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node QQ160 may include additional components beyond those shown in Figure 8 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc.. A WD may support device-to- device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to- everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111 , interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111 , interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120. Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ114. Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120. In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated. User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

Figure 9 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE QQ200 may be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in Figure 9, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 9 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 9, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211 , memory QQ215 including random access memory (RAM) QQ217, readonly memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231 , power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 9, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In Figure 9, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200. The input device may include a touch-sensitive or presencesensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor. In Figure 9, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a. Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243a may comprise a Wi-Fi network. Network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to offload data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221, which may comprise a device readable medium.

In Figure 9, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks. Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11 , CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200.

Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231. In another example, the non- computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

Figure 10 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized. The functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways. During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

As shown in Figure 10, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in Figure 10.

In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.

With reference to FIGURE 11 , in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414. Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491, QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.

Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420. Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown). The communication system of Figure 11 as a whole enables connectivity between the connected UEs QQ491, QQ492 and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications. For example, base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 12. In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.

Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 12) served by base station QQ520. Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may pass through a core network (not shown in Figure 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531, which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides. It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 12 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491, QQ492 of Figure 11 , respectively. This is to say, the inner workings of these entities may be as shown in Figure 12 and independently, the surrounding network topology may be that of Figure 11.

In Figure 12, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the usefulness of QoE measurement reporting and thereby provide benefits such as improved network performance.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection QQ550 between host computer QQ510 and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ511, QQ531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.

Figure 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figure 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section. In step QQ610, the host computer provides user data. In substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figure 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section. In step QQ710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step QQ720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission. Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figure 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figure 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In step QQ910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

The following enumerated embodiments form part of this description. Group A Embodiments

1. A method performed by a wireless device for configuring the wireless device for Quality of Experience (QoE) measurement reporting, the method comprising: receiving a Quality of Experience (QoE) measurement reporting configuration, wherein the QoE measurement reporting configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device; and applying the QoE measurement reporting configuration.

2. The method of embodiment 1 , wherein the one or more metrics comprise one or more of:

(v) a metric identifying to uptime of the wireless device or another device;

(ix) a metric identifying utilization of the wireless device or another device;

3. The method of embodiment 2, wherein the one or more metrics comprise a property of a measured parameter identified by the QoE measurement reporting configuration, and the property of the measured parameter comprises one or more of:

(i) an accuracy or precision of the measured parameter; (ii) whether the measured parameter has exceeded a predetermined threshold; and

4. The method of embodiment 2 or 3, wherein the one or more metrics comprise a metric relating to a survival mode or downtime of the wireless device or another device, and the metric comprises one or more of:

(iv) an identification of an event that caused the survival mode or downtime.

5. The method of any of embodiments 2 to 4, wherein the one or more metrics comprise a metric relating to timing of communications by the wireless device or another device, and the metric comprises one or more of:

6. The method of any of embodiments 1 to 5, wherein the QoE measurement reporting configuration is received from a network node.

7. The method of embodiment 6, wherein the network node comprises a gNB, eNB, en- gNB, ng-eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, lAB-donor DU, IAB- donor-CU, IAB-DU or IAB-MT.

8. The method of any of embodiments 1 to 7, wherein the QoE measurement reporting configuration is received in a RRC message.

9. The method of embodiment 8, wherein the RRC message comprises a RRCConnectionReconfiguration message. 6o

10. The method of any of embodiments 1 to 9, wherein the one or more metrics are based on a determination that the QoE measurement reporting configuration relates to measurements of at least one Internet of Things (loT) application associated with the wireless device.

11. A method performed by a wireless device for Quality of Experience (QoE) measurement reporting, wherein the wireless device is configured with a Quality of Experience (QoE) measurement reporting configuration, wherein the QoE measurement reporting configuration identifies one or more metrics for measurement reporting, the method comprising: reporting the one or more metrics to a network node; wherein the one or more metrics comprise one or more of:

(v) a metric identifying to uptime of the wireless device or another device;

(ix) a metric identifying utilization of the wireless device or another device;

12. The method of embodiment 11, wherein the one or more metrics comprise a property of a measured parameter identified by the QoE measurement reporting configuration, and property of the measured parameter comprises one or more of:

13. The method of embodiment 11 or 12, wherein the one or more metrics comprise a metric relating to a survival mode or downtime of the wireless device or another device, and the metric comprises one or more of:

(iv) an identification of an event that caused the survival mode or downtime.

14. The method of any of embodiments 11 to 13, wherein the one or more metrics comprise a metric relating to timing of communications by the wireless device or another device, and the metric comprises one or more of:

15. The method of any of embodiments 11 to 14, wherein the network node comprises a gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, IAB- donor DU, lAB-donor-CU, IAB-DU or IAB-MT.

16. The method of any of embodiments 1 to 15, wherein the wireless device is associated with at least one Internet of Things (loT) application, and the metrics for measurement reporting comprise metrics for the loT application.

17. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

Group B Embodiments 18. A method performed by a network node for configuring a wireless device for Quality of Experience (QoE) measurement reporting, the method comprising: sending a Quality of Experience (QoE) measurement reporting configuration to the wireless device, wherein the QoE measurement reporting configuration identifies one or more metrics for measurements of at least one Internet of Things (loT) application associated with the wireless device.

19. The method of embodiment 18, wherein the one or more metrics comprise one or more of:

(v) a metric identifying to uptime of the wireless device or another device;

(ix) a metric identifying utilization of the wireless device or another device;

20. The method of embodiment 19, wherein the one or more metrics comprise a property of a measured parameter identified by the QoE measurement reporting configuration, and the property of the measured parameter comprises one or more of:

(i) an accuracy or precision of the measured parameter;

(ii) whether the measured parameter has exceeded a predetermined threshold; and

(iii) an amount by which the measured parameter has exceeded a predetermined threshold. 21. The method of embodiment 19 or 20, wherein the one or more metrics comprise a metric relating to a survival mode or downtime of the wireless device or another device, and the metric comprises one or more of:

(iv) an identification of an event that caused the survival mode or downtime.

22. The method of any of embodiments 19 to 21, wherein the one or more metrics comprise a metric relating to timing of communications by the wireless device or another device, and the metric comprises one or more of:

23. The method of any of embodiments 18 to 22, wherein the network node comprises a gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, eNB-CU, eNB-CU-CP, lAB-node, IAB- donor DU, lAB-donor-CU, IAB-DU or IAB-MT.

24. The method of any of embodiments 18 to 23, wherein the QoE measurement reporting configuration is sent to the wireless device in a RRC message.

25. The method of embodiment 24, wherein the RRC message comprises a RRCConnectionReconfiguration message.

26. The method of any of embodiments 18 to 25, wherein the wireless device is associated with an industrial control device or application, and the metrics for measurement reporting comprise metrics for the industrial control device or application.

27. The method of any of embodiments 18 to 26, further comprising, before sending the QoE measurement reporting configuration to the wireless device, determining that the QoE measurement reporting configuration relates to measurements of at least one Internet of Things (loT) application associated with the wireless device, and wherein the one or more metrics are based on the determination that the QoE measurement reporting configuration relates to measurements of at least one Internet of Things (loT) application associated with the wireless device.

28. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.

Group C Embodiments

29. A wireless device for configuring the wireless device for Quality of Experience (QoE) measurement reporting, the wireless device comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless device.

30. A base station for configuring a wireless device for Quality of Experience (QoE) measurement reporting, the base station comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the base station.

31. A user equipment (UE) for configuring the UE for Quality of Experience (QoE) measurement reporting, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

32. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

33. The communication system of the previous embodiment further including the base station.

34. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

35. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

36. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

37. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. 38. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

39. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

40. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.

41. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

42. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

43. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

44. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. 45. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.

46. The communication system of the previous embodiment, further including the UE.

47. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

48. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

49. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

50. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

51. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. 52. The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

53. The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

54. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

55. The communication system of the previous embodiment further including the base station.

56. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

57. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

58. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

59. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

60. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Claims

1. A method (200) performed by a wireless device for configuring the wireless device for Quality of Experience, QoE, measurements, the method comprising: receiving (202) a Quality of Experience, QoE, measurement configuration, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things, loT, application associated with the wireless device; and applying (204) the QoE measurement configuration.

2. The method of claim 1 , wherein the one or more metrics comprise one or more of:

(ii) an execution time of a task performed by the wireless device or another device;

(iii) a metric relating to a survival mode or downtime of the wireless device or another device;

(iv) a metric identifying to uptime of the wireless device or another device;

(v) a metric relating to timing of communications by the wireless device or another device;

(vi) a metric identifying a number or type of fault conditions experienced by the wireless device or another device;

(vii) a metric identifying requirements for recovering from a survival mode or downtime of the wireless device or another device;

(viii) a metric identifying utilization of the wireless device or another device;

(ix) a metric identifying a level of resources required by the wireless device or another device;

(x) an energy consumption and/or energy efficiency of a task performed by the wireless device or another device; and

3. The method of claim 2, wherein the one or more metrics comprise a property of a measured parameter identified by the QoE measurement configuration, and the property of the measured parameter comprises one or more of:

(i) an accuracy or precision of the measured parameter;

(ii) whether the measured parameter has exceeded a predetermined threshold; and (iii) an amount by which the measured parameter has exceeded a predetermined threshold.

4. The method of claim 2 or 3, wherein the one or more metrics comprise a metric relating to a survival mode or downtime of the wireless device or another device, and the metric comprises one or more of:

(iv) an identification of an event that caused the survival mode or downtime.

5. The method of any of claims 2 to 4, wherein the one or more metrics comprise a metric relating to timing of communications by the wireless device or another device, and the metric comprises one or more of:

6. The method of any of claims 1 to 5, wherein the QoE measurement configuration is received from a network node.

7. The method of any of claims 1 to 6, wherein the QoE measurement configuration is received in a RRC message.

8. The method of claim 7, wherein the RRC message comprises a RRCConnectionReconfiguration message.

9. The method of any of claims 1 to 8, wherein the one or more metrics are based on a determination that the QoE measurement configuration relates to measurements of at least one Internet of Things (loT) application associated with the wireless device.

10. The method of any of claims 1 to 9, wherein: the at least one loT application associated with the wireless device comprises an Industrial Internet of Things, HoT, application or Massive Internet of Things, MIoT, application; the at least one loT application is associated with an Ultra Reliable Low Latency Communication, URLLC, service type; and/or the wireless device comprises an loT, HoT or MIoT device.

11. The method of any of claims 1 to 10, comprising reporting the one or more metrics to a network node.

12. The method of claim 6 or 11, wherein the network node comprises a gNB, an eNB, an en-gNB, a ng-eNB, a gNB-CU, a gNB-CU-CP, an eNB-CU, an eNB-CU-CP, an lAB-node, an lAB-donor DU, an lAB-donor-CU, an IAB-DU or an IAB-MT.

13. A method (400) performed by a network node for configuring a wireless device for Quality of Experience, QoE, measurements, the method comprising: sending (402) a Quality of Experience, QoE, measurement configuration to the wireless device, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things, loT, application associated with the wireless device.

14. The method of claim 13, wherein the one or more metrics comprise one or more of:

(iv) a metric identifying to uptime of the wireless device or another device;

(viii) a metric identifying utilization of the wireless device or another device; (ix) a metric identifying a level of resources required by the wireless device or another device;

15. The method of claim 14, wherein the one or more metrics comprise a property of a measured parameter identified by the QoE measurement configuration, and the property of the measured parameter comprises one or more of:

(i) an accuracy or precision of the measured parameter;

(ii) whether the measured parameter has exceeded a predetermined threshold; and

16. The method of claim 14 or 15, wherein the one or more metrics comprise a metric relating to a survival mode or downtime of the wireless device or another device, and the metric comprises one or more of:

(iv) an identification of an event that caused the survival mode or downtime.

17. The method of any of claims 14 to 16, wherein the one or more metrics comprise a metric relating to timing of communications by the wireless device or another device, and the metric comprises one or more of:

18. The method of any of claims 13 to 17, wherein the network node comprises a gNB, an eNB, an en-gNB, a ng-eNB, a gNB-Cll, a gNB-CU-CP, an eNB-Cll, an eNB-CU-CP, an IAB- node, an lAB-donor DU, an lAB-donor-CU, an IAB-DU or an IAB-MT.

19. The method of any of claims 13 to 18, wherein the QoE measurement configuration is sent to the wireless device in a RRC message.

20. The method of claim 19, wherein the RRC message comprises a RRCConnectionReconfiguration message.

21. The method of any of claims 13 to 20, wherein the wireless device is associated with an industrial control device or application, and the metrics comprise metrics for the industrial control device or application.

22. The method of any of claims 13 to 21 , further comprising, before sending the QoE measurement configuration to the wireless device, determining that the QoE measurement configuration relates to measurements of at least one Internet of Things, loT, application associated with the wireless device, and wherein the one or more metrics are based on the determination that the QoE measurement configuration relates to measurements of at least one Internet of Things, loT, application associated with the wireless device.

23. The method of any of claims 13 to 22, wherein: the at least one loT application associated with the wireless device comprises an Industrial Internet of Things, HoT, application or a Massive Internet of Things, MIoT, application; the at least one loT application is associated with an Ultra Reliable Low Latency Communication, URLLC, service type; and/or the wireless device comprises an loT, an I loT or a MIoT device.

24. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method (200, 400) according to any of claims 1 to 23.

25. A carrier containing a computer program according to claim 24, wherein the carrier comprises one of an electronic signal, optical signal, radio signal or computer readable storage medium.

26. A computer program product comprising non transitory computer readable media having stored thereon a computer program according to claim 24.

27. A wireless device comprising a processor and a memory, the memory containing instructions executable by the processor such that the wireless device is operable to: receive (202) a Quality of Experience, QoE, measurement configuration, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things, loT, application associated with the wireless device; and apply (204) the QoE measurement configuration.

28. The wireless device of claim 27, wherein the memory contains instructions executable by the processor such that the wireless device is operable to perform the method (200) of any of claims 2 to 12.

29. A network node for configuring a wireless device for Quality of Experience, QoE, measurements, the network node comprising a processor and a memory, the memory containing instructions executable by the processor such that the wireless device is operable to: send (402) a Quality of Experience, QoE, measurement configuration to the wireless device, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things, loT, application associated with the wireless device.

30. The network node of claim 29, wherein the memory contains instructions executable by the processor such that the network node is operable to perform the method (400) of any of claims 14 to 23.

31. A wireless device configured to: receive (202) a Quality of Experience, QoE, measurement configuration, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things, loT, application associated with the wireless device; and apply (204) the QoE measurement configuration.

32. The wireless device of claim 31 , wherein the wireless device is configured to perform the method (200) of any of claims 2 to 12.

33. A network node for configuring a wireless device for Quality of Experience, QoE, measurements, the network node configured to: send (402) a Quality of Experience, QoE, measurement configuration to the wireless device, wherein the QoE measurement configuration identifies one or more metrics for measurements of at least one Internet of Things, loT, application associated with the wireless device.

34. The network node of claim 33, wherein the network node is configured to perform the method (400) of any of claims 14 to 23.