Patent Description:
"Quality of Experience (QoE) Measurement Collection" is a technique introduced into Third Generation Partnership Project (3GPP) release <NUM> for use in Long Term Evolution (LTE) and potentially for use in future wireless communication standards (e.g., New Radio (NR)). QoE Measurement Collection includes features intended to be applied to streaming services and Multimedia Telephony Service for Internet Protocol (IP) Multimedia Subsystem (IMS) (MTSI) services.

Traditionally, QoE Measurement Collection involves a wireless device (e.g., a User Equipment (UE)) performing measurements to collect information about the quality of streaming services used in the UE. The streaming service is typically a third-party streaming application on top of a Packet Switched (PS) Interactive Radio Access Bearer (RAB) defined in the Radio Access Network (RAN). The general purpose of these measurements is to collect information that may be used to enable improvements to the quality of the streaming service. Thus, it would be advantageous to ensure that network conditions do not interfere with the ability to collect or exploit this information for purposes of improving service.

Document <CIT> discloses a technique pertaining to Quality of Experience (QoE) Measurement collection that is continued from a source network node servicing a terminal to a target network node following a relocation or handover of the terminal. When the source network node is preparing for the relocation, e.g., SRNS Relocation, Intra-RAT handover (e.g., X2 handover), or Inter-RAT handover, for a terminal which has QoE Measurement configured, the trace session information, which has been received by the source network node from a Measurement Initiating node, is sent from the source network node to the target network node. The target network node provides information about the handling of the ongoing QoE measurement to the source network node, e.g., whether the QoE measurement is to be continued or terminated. The source network node updates to the Measurement Initiating node that the trace session is transferred to the target network node. The Measurement Initiating node may then continue the trace session management towards the target network node. The trace session information transferred to the target network node may be the same as that in the source network node), or it may be modified by the Measurement Initiating node.

Document "<NPL>, discloses an evaluation of a necessity of deactivating Immediate MDT configuration and possible solutions to perform the deactivation was discussed. The relation between Serving PLMN and Trace PLMN in Immediate MDT configuration was also discussed. The following proposals were made. Proposal <NUM>: It is proposed to clarify that in MDT configuration, whether the Serving PLMN ID is always the same or can be different with PLMN ID in the Trace Activation IE. Proposal <NUM>: It is proposed for RAN2 to agree that the evaluation to deactivate (or continue) Immediate MDT measurement is performed based on Serving PLMN (i.e., RPLMN) change during Inter-PLMN handover. Proposal <NUM>: If proposal <NUM> is confirmed, it is proposed that that RAN <NUM> agrees that PLMN check and deactivation evaluation is controlled and decided by the network. (i.e., not evaluated by the UE). Proposal <NUM>: It is proposed for RAN2 to agree that behaviour <NUM> (the reporting of Immediate MDT in the target cell is always deactivated) and behaviour <NUM> (depending on roaming agreement between operators, immediate MDT may be continued) (due to roaming agreement Immediate MDT measurement report is continued even if serving PLMN is changed) is not supported. In other words, it is purposed that if serving PLMN change occurs during inter-PLMN handover, then the Immediate MDT measurement shall be deactivated. Proposal <NUM>: for case <NUM> (Serving PLMN == Trace PLMN), the deactivation of Immediate MDT configuration follows the current transferring and reconfiguration principle, i.e., deactivation in the target eNB. However, implementation specific deactivation in the Source eNB is also feasible. Proposal <NUM>: for case <NUM> (Serving PLMN =! Trace PLMN), the necessity to support target eNB solution should be discussed after the necessity and existence of case <NUM> is identified.

Document <CIT> discloses a communications system comprising a managing entity responsible for handling measurement reports and a network node. The managing entity is capable of sending condition-related parameters to the network node and the network node being capable of controlling measurement reporting in a communications system by: receiving a measurement report from a mobile terminal, determining from the measurement report whether it is a type of measurement report for which condition-related parameters need to be applied, wherein if the measurement report is of the type requiring the condition-related parameters to be applied, applying a load-related condition and a security related condition and if both are satisfied, providing the measurement report to the managing entity.

Document "<NPL>, discloses an evolution of QoE Measurement Collection for streaming services in UTRAN. In this regard, using MDT mechanism is not only way to fulfil SA4 requirement and operator expectation. It is hoped that RAN2 can discuss these proposal and adopt one generic solution that just has little impact to RAN system and specification, especially it is easy to be extended in future for other similar requirement if have. The following proposals were made. Proposal <NUM>: One generic solution no binding with specific service is preferred. Proposal <NUM>: It is worth to do study if existed messages, such as DOWNLINK DIRTECT TRANSFER and UPLINK DIRECT TRANSFER, can be reused if RAN2 agree RNC to assist collection data of NAS layer or application layer by "container" manner. Proposal <NUM>: One generic container defined in MDT measurement is preferred if RAN2 agree MDT mechanism is used in the document. Proposal <NUM>: Identify commonalities and possible impacts with the existing MDT Trace configuration and reporting.

According to the present disclosure, methods, a radio access network node, a management system and a computer program according to the independent claims are provided. Developments are set forth in the dependent claims.

According to a first aspect of the present disclosure, there is provided a method, implemented by a radio access network, RAN, node in a RAN of a wireless communication network. The method comprises signaling, responsive to detecting an overload condition of the RAN, a wireless device to stop reporting Quality of Experience, QoE, measurements to the RAN; and notifying a management system in the core network outside of the RAN that the reporting of QoE measurements to the RAN has stopped.

According to a second aspect of the present disclosure, there is provided a method, implemented by a management system in a core network outside of a radio access network, RAN. The method comprises receiving a notification, from a RAN node in the RAN of the wireless communication network, indicating that reporting of Quality of Experience, QoE, measurements from a wireless device to the RAN has stopped.

According to a third aspect, there is provided a radio access network, RAN, node in a RAN of a wireless communication network. The RAN node is configured to perform the method of the first aspect.

According to a fourth aspect, there is provided a management system in a core network outside of a radio access network, RAN. The management system is configured to perform the method of the second aspect.

According to a fifth aspect, there is provided a computer program, comprising instructions which, when executed on at least one processor of a radio access network, RAN, node, cause the at least one processor to carry out the method according to the first aspect. Alternatively, said instructions, when executed on at least one processor of a management system, cause the at least one processor to carry out the method according to the second aspect.

Whenever in the following disclosure any of the above-stated aspects (corresponding to the independent claims) is disclosed as "optional" (e.g., due to usage of conjunctive terms, such as "can", "may", "should", etc.), it is nevertheless to be read as "mandatory".

Hereinabove and in the following, "examples" pertain to principles underlying the claimed subject-matter and/or being useful for understanding the claimed subject-matter, while "embodiments" pertain to the claimed subject-matter within the claim scope.

Whenever in this description an "embodiment" is described, reference is to be made to the above figure list to determine whether this is to be read as "embodiment" or "example".

<FIG> illustrates an example wireless communication network <NUM> comprising a wireless device <NUM>, a RAN <NUM>, a Core Network (CN) <NUM>, and a Packet Data Network (PDN) <NUM>. The RAN <NUM> is responsible for radio-related functions of the wireless communication network <NUM>. Such radio-related functions may include, for example, transmission scheduling, radio resource management, and/or coding, among other things. The CN <NUM> is responsible for non-radio-related functions of the wireless communication network <NUM>. Such non-radio-related functions may include, for example, authentication and/or charging, among other things.

The RAN <NUM> comprises a RAN node <NUM>. The wireless device <NUM> and RAN node <NUM> are configured to exchange signals with each other over a wireless interface. In particular, the RAN node <NUM> is configured to receive signals transmitted from the wireless device <NUM> on an uplink <NUM>, and transmit signals to the wireless device <NUM> on a downlink <NUM>. Correspondingly, the wireless device <NUM> is configured to receive signals transmitted from the RAN node <NUM> on the downlink <NUM>, and transmit signals to the RAN node <NUM> on the uplink <NUM>. Examples of the wireless device <NUM> include a mobile terminal and/or user equipment (UE). Examples of the RAN node <NUM> include a base station and/or access node.

The CN <NUM> comprises a management system <NUM>. The management system <NUM> configures QoE measurements taken by the wireless device <NUM>. Examples of the management system <NUM> include a network manager (NM), element manager (EM), domain manager (DM), and/or Operations and Maintenance node (O&M node). In some embodiments, the management system <NUM> is also a Measurement Collection Entity (MCE) configured to collect measurement reports from the wireless device <NUM>. An example of the CN <NUM> includes an Evolved Packet Core (EPC). In some embodiments, the CN <NUM> further comprises an Access and Mobility Management Function (AMF) <NUM>, a Serving General Packet Radio Services (GPRS) Support Node (SGSN) <NUM> and/or a Mobility Management Entity (MME) <NUM>.

The RAN <NUM> provides the wireless device <NUM> with access to the PDN <NUM> via the CN <NUM>. The PDN <NUM> comprises a content server <NUM>. The content server <NUM> is configured to provide data (e.g., streaming data, MTSI service data) to the wireless device <NUM> via the CN <NUM> and RAN <NUM>. An example of the PDN <NUM> is the Internet, or a portion thereof. Although the content server <NUM> in this example is illustrated in the PDN <NUM>, in some embodiments, the content server <NUM> is located elsewhere in the wireless communication network <NUM>.

According to embodiments of the present disclosure, the management system <NUM> may configure or trigger the wireless device <NUM> to perform measurements and report those measurements towards the RAN <NUM>. In some embodiments, this is initiated by the management system <NUM> in generic way for a plurality of wireless devices <NUM>. Additionally or alternatively, this may be initiated by signaling from the management system <NUM> via the CN <NUM> and the RAN <NUM> that is directed to one or more particular wireless devices <NUM>.

<FIG> illustrates an example of measurement activation and reporting, performed on a management basis. According to this example, the management system <NUM> is an O&M node that comprises an MCE, NM, and DM/EM. Also according to this example, the wireless device <NUM> comprises a UE Access Stratum and a UE Application Level.

The O&M node sends an activateAreaQoEJob message to the RAN node <NUM> to activate QoE measurements for an area served by the RAN node <NUM>. In the activation message, the O&M node specifies one or more parameters, e.g., service type, area, MCE address, and/or QoE target. The configuration of the measurement includes measurement details, which are encapsulated in a container that is transparent to RAN <NUM>. Thus, in some embodiments, some parameters are inside the container (and are not visible to the RAN <NUM>), while other parameters are outside the container, e.g., so that intermediate nodes and/or layers may make use of the parameters outside of the container.

Accordingly, <FIG> illustrates an example of which parameters and attributes may be included in the activateAreaQoEJob sent from the NM to the RAN node <NUM>. Although <FIG> illustrates QoE measurement activation as may be appropriate for LTE, similar signaling may be applied to UTRAN, e.g., by changing the names of the messages sent from the RAN node <NUM> to the wireless device <NUM>, and vice versa, as appropriate.

The trigger to perform QoE measurement collection is forwarded to the wireless device <NUM> using RRC signaling. The configuration to perform QoE measurements is provided to the wireless device <NUM> in a container, e.g., the measConfigAppLayerContainer field. The container is then forwarded to the application layer of the wireless device <NUM> using relevant Attention (AT) commands.

As the size of the report can be fairly large, embodiments of the present disclosure include mechanisms to stop and/or start reporting, e.g., in response to an overload situation in the RAN <NUM> so as not to further increase network load and/or interference. For example, in some embodiments, when the UE application layer receives an AT command with the <start-stop_reporting> Information Element set to <NUM>, measurement reporting is stopped. In some embodiments, the measurement configuration parameters may also be deleted.

For example, in Universal Mobile Telecommunications System (UMTS) and LTE, measurement recording may be stopped and the configuration parameters deleted, whereas <NUM> may stop reporting without deleting the configuration parameters (i.e., the configuration parameters are retained). By retaining the configuration parameters, reporting may be readily restarted once the overload situation stops.

In some particular embodiments, if the wireless device <NUM> receives an otherConfig parameter that does not include a measConfigAppLayer parameter, the wireless device <NUM> may clear the stored application layer measurement configuration and discard any stored measurement reports. Thus, according to some embodiments, when overload occurs, no reports are sent to the management system <NUM> and the wireless devices <NUM> previously activated and configured to perform QoE measurement reporting will not do any reporting unless reactivated.

Note that while the examples herein specifically describe scenarios involving QoE measurements for streaming services and MTSI services, similar principles may be applied to other types of application layer measurements throughout this disclosure. That is, the concepts discussed herein may be valid for any type of application layer measurements. While QoE measurements for streaming services and MTSI services in particular are currently only introduced for UMTS and LTE, one or more embodiments of the present disclosure include the described concepts and solutions herein as applied to NR/<NUM> as well.

In scenarios such as the one illustrated in <FIG>, the management layer (NM and DM, in this example) is not aware that the RAN <NUM>, due to overload, may have stopped one or more wireless devices <NUM> from sending reports, which may result in insufficient number of collected reports at the MCE. Additionally or alternatively, the management layer may also not be aware when the overload situation has stopped, and that QoE measurement reporting has been restarted. Moreover, if overload occurs over a long period, there may be inadequate reports available to the management system <NUM>.

Accordingly, embodiments of the present disclosure introduce signaling to prolong or expand QoE measurement collection in order to ensure that sufficient number reports are received at the Measurement Collection Entity (e.g., to avoid inadequate reports being available to the management system <NUM>). Embodiments additionally or alternatively include introduction of signaling between the RAN <NUM> and the management system <NUM> in which the RAN <NUM> is able to indicate that QoE measurement reporting has been stopped or started. In this way, the management system <NUM> will know that QoE measurement reporting has been stopped and/or started, which in turn may enable the management system <NUM> to determine whether or not to take actions to modify the initial QoE measurement collection. For example, in response to determining that QoE measurement reporting has been stopped and/or started, the management system <NUM> may trigger additional QoE measurements (e.g., by increasing the targeted number of cells to be measured, or the duration of QoE measurement collection).

In some embodiments, to ensure that the network management layer (e.g., the management system <NUM>) is aware that QoE measurement reporting has been stopped and/or started in the RAN <NUM> due to an overload and/or return to normal conditions (respectively), the RAN <NUM> sends a notification to the network management layer with an indication that QoE measurement reporting has been stopped and/or started, as shown in <FIG>. According to the example illustrated in <FIG>, a notification is sent from the RAN <NUM> to the network management layer at steps 3b and <NUM>, respectively. The notification may also include an indication of service type such as streaming, MTSI, or similar.

Note that the management system <NUM> (e.g., a Network Manager) may, after receiving the notification in step <NUM>, modify the original job by increasing the area (e.g., the QoE target) or prolonging the duration of the QoE measurement collection. The reason for modifying the original job may, e.g., be due to the RAN overload occurring for an extended period of time. The modification of the original job may require that the NM first deactivate the current job and send a new modified activateAreaQoEJob to the RAN <NUM>. The RAN <NUM> would then (as shown in step <NUM>) look for wireless devices <NUM> that match the criteria specified in the new job. In some embodiments, the indication is sent to the management system <NUM> via a CN node, such as an AMF <NUM>, SGSN <NUM> and/or MME <NUM>.

Other embodiments include signaling other than that shown in <FIG> in which the RAN <NUM> indicates to the management system <NUM> that QoE measurement collection has been stopped and/or started.

In view of the above, signaling between the RAN <NUM> and the management system <NUM> enables the RAN <NUM> to indicate that QoE measurement reporting has been stopped and/or started, e.g., in order to enable the management server <NUM> to decide whether or not to modify the current QoE measurement collection job, e.g., by increasing the area or prolonging the duration of the QoE measurement collection.

As such, as shown in <FIG>, embodiments of the present disclosure include a method <NUM> implemented by a RAN node <NUM> in a RAN <NUM> of a wireless communication system <NUM>. The method <NUM> comprises signaling a wireless device <NUM> to stop reporting Quality of Experience (QoE) measurements to the RAN <NUM> (block <NUM>). The method <NUM> further comprises notifying a management system <NUM> in a core network <NUM> of the wireless communication system <NUM> that the reporting of QoE measurements to the RAN <NUM> has stopped (block <NUM>). Some embodiments additionally or alternative comprise one or more other features discussed herein.

Note that a network node as discussed herein is any type of node in the RAN <NUM> (e.g., a base station) or CN <NUM> (e.g., management system <NUM>, AMF <NUM>, SGSN <NUM>, MME <NUM>). Where the network node is a radio network node in the RAN <NUM>, the node may be capable of communicating with another node over radio signals. A wireless device <NUM> is any type device capable of communicating with a RAN node <NUM> over radio signals. A wireless device <NUM> may therefore refer to a machine-to-machine (M2M) device, a machine-type communications (MTC) device, a narrowband Internet of Things (NB-IoT) device, etc. The wireless device <NUM> may also be a user equipment (UE), however it should be noted that the UE does not necessarily have a "user" in the sense of an individual person owning and/or operating the device. A wireless device <NUM> may also be referred to as a radio device, a radio communication device, a wireless terminal, or simply a terminal - unless the context indicates otherwise, the use of any of these terms is intended to include device-to-device UEs or devices, machine-type devices or devices capable of machine-to-machine communication, sensors equipped with a wireless device, wireless-enabled table computers, mobile terminals, smart phones, laptop-embedded equipped (LEE), laptop-mounted equipment (LME), USB dongles, wireless customer-premises equipment (CPE), etc. In the discussion herein, the terms machine-to-machine (M2M) device, machine-type communication (MTC) device, wireless sensor, and sensor may also be used. It should be understood that these devices may be UEs, but are generally configured to transmit and/or receive data without direct human interaction.

In an IOT scenario, a wireless device <NUM> as described herein may be, or may be comprised in, a machine or device that performs monitoring or measurements, and transmits the results of such monitoring measurements to another device or a network. Particular examples of such machines are power meters, industrial machinery, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a wireless device <NUM> as described herein may be comprised in a vehicle and may perform monitoring and/or reporting of the vehicle's operational status or other functions associated with the vehicle.

Note that the RAN node <NUM> described above may perform the processing herein by implementing any functional means or units. In one embodiment, for example, the RAN node <NUM> comprises respective circuits configured to perform the steps shown in <FIG>. The circuits in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. In embodiments that employ memory, which may comprise one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc., the memory stores program code that, when executed by the one or more microprocessors, carries out the techniques described herein. That is, in some embodiments memory of the RAN node <NUM> contains instructions executable by the processing circuitry whereby the RAN node <NUM> is configured to carry out the processing herein.

<FIG> illustrates additional details of a RAN node <NUM> in accordance with one or more embodiments. As shown, the RAN node <NUM> comprises processing circuitry <NUM> and communication circuitry <NUM>. The communication circuitry <NUM> is configured to communicate with one or more other nodes, e.g., the wireless device <NUM>. In particular, the communication circuitry <NUM> may be configured to transmit and/or receive via one or more antennas. The processing circuitry <NUM> is configured to perform processing described above, e.g., in <FIG>, such as by executing instructions stored in memory <NUM>. The processing circuitry <NUM> in this regard may implement certain functional means or units.

<FIG> in this regard illustrates a RAN node <NUM> in accordance with one or more other embodiments. As shown, the RAN node <NUM> comprises a signaling unit or module <NUM> configured to signal a wireless device <NUM> to stop reporting Quality of Experience (QoE) measurements to the RAN <NUM>. The RAN node <NUM> further comprises a notifiying unit or module <NUM> configured to notify a management system <NUM> in a core network <NUM> of the wireless communication system <NUM> that the reporting of QoE measurements to the RAN <NUM> has stopped. These modules and/or units may be implemented by the processing circuitry <NUM> of <FIG>. In some embodiments, the RAN node <NUM> additionally or alternatively comprises one or more other units or modules configured to perform one or more other features described herein.

Other embodiments of the present disclosure, as described in <FIG>, include a method <NUM> implemented by a management system <NUM> in a core network <NUM> of a wireless communication network <NUM>. The method <NUM> of <FIG> comprises receiving a notification, from a RAN node <NUM> in a RAN <NUM> of the wireless communication system <NUM>, indicating that reporting of Quality of Experience (QoE) measurements from a wireless device <NUM> to the RAN <NUM> has stopped or restarted (block <NUM>). In some embodiments, the notification indicates that the reporting of QoE measurements has stopped, and the method <NUM> of <FIG> further comprises receiving a further notification from the RAN node <NUM> indicating that the reporting of QoE measurements has restarted (block <NUM>). In some embodiments, the method <NUM> of <FIG> further comprises, responsive to receiving the further notification, sending a request to the RAN node <NUM> requesting a modification to how the wireless device <NUM> performs the QoE measurements (block <NUM>). Some embodiments additionally or alternative comprise one or more other features discussed herein.

Note that the management system <NUM> described above may perform the processing herein by implementing any functional means or units. In one embodiment, for example, the management system <NUM> comprises respective circuits configured to perform the steps shown in <FIG>. The circuits in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. In embodiments that employ memory, which may comprise one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc., the memory stores program code that, when executed by the one or more microprocessors, carries out the techniques described herein. That is, in some embodiments, memory of the management system <NUM> contains instructions executable by the processing circuitry whereby the management system <NUM> is configured to carry out the processing herein.

<FIG> illustrates additional details of a management system <NUM> in accordance with one or more embodiments. As shown, the management system <NUM> comprises processing circuitry <NUM> and communication circuitry <NUM>. The communication circuitry <NUM> is configured to communicate with one or more other nodes, e.g., the RAN node <NUM>. The processing circuitry <NUM> is configured to perform processing described above, e.g., in <FIG>, such as by executing instructions stored in memory <NUM>. The processing circuitry <NUM> in this regard may implement certain functional means or units.

<FIG> in this regard illustrates a management system <NUM> in accordance with one or more other embodiments. As shown, the management system <NUM> comprises a first receiving unit or module <NUM> configured to receive a notification, from a RAN node <NUM> in a RAN <NUM> of the wireless communication system <NUM>, indicating that reporting of Quality of Experience (QoE) measurements from a wireless device <NUM> to the RAN <NUM> has stopped or restarted. In some embodiments, the notification indicates that the reporting of QoE measurements has stopped, and the management system <NUM> further comprises a second receiving unit or module <NUM> configured to receive a further notification from the RAN node <NUM> indicating that the reporting of QoE measurements has restarted. In some embodiments, the management system <NUM> further comprises a sending unit or module <NUM> configured to send a request to the RAN node <NUM> requesting a modification to how the wireless device <NUM> performs the QoE measurements. These modules and/or units may be implemented by the processing circuitry <NUM> of <FIG>. In some embodiments, the measurement system <NUM> additionally or alternatively comprises one or more other units or modules configured to perform one or more other features described herein.

A computer program comprises instructions which, when executed on at least one processor of a node, cause the node to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Other embodiments will now be described with respect to certain contexts. These embodiments are combinable with and expound upon embodiments above.

Those skilled in the art will appreciate that the various methods and processes described herein may be implemented using various hardware configurations that generally, but not necessarily, include the use of one or more microprocessors, microcontrollers, digital signal processors, or the like, coupled to memory storing software instructions or data for carrying out the techniques described herein. In particular, those skilled in the art will appreciate that the circuitry of various embodiments may be configured in ways that vary in certain details from the broad descriptions given above. For instance, one or more of the processing functionalities discussed above may be implemented using dedicated hardware, rather than a microprocessor configured with program instructions. Such variations, and the engineering tradeoffs associated with each, will be readily appreciated by the skilled practitioner. Since the design and cost tradeoffs for the various hardware approaches, which may depend on system-level requirements that are outside the scope of the present disclosure, are well known to those of ordinary skill in the art, further details of specific hardware implementations are not provided herein.

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 <FIG>. For simplicity, the wireless network of <FIG> only depicts network <NUM>, network nodes <NUM> and 1160b, and wireless devices (WDs) <NUM>, 1110b, and 1110c. 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 <NUM> and wireless device (WD) <NUM> 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.

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), Narrowband Internet of Things (NB-IoT), and/or other suitable <NUM>, <NUM>, <NUM>, or <NUM> standards; wireless local area network (WLAN) standards, such as the IEEE <NUM> 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.

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 (IoT) 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-IoT) 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.

WD <NUM> may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD <NUM>, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-loT, or Bluetooth wireless technologies, just to mention a few.

UE <NUM> may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE <NUM>, as illustrated in <FIG>, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or <NUM> standards.

Network connection interface <NUM> may be configured to provide a communication interface to network 1243a. Network 1243a 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 1243a may comprise a Wi-Fi network.

In <FIG>, processing circuitry <NUM> may be configured to communicate with network 1243b using communication subsystem <NUM>. Network 1243a and network 1243b may be the same network or networks or different network or networks. Communication subsystem <NUM> may be configured to include one or more transceivers used to communicate with network 1243b.

Network 1243b 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 1243b may be a cellular network, a Wi-Fi network, and/or a near-field network.

<FIG> illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference to <FIG>, in accordance with an embodiment, a communication system includes telecommunication network <NUM>, such as a 3GPP-type cellular network, which comprises access network <NUM>, such as a radio access network, and core network <NUM>. Access network <NUM> comprises a plurality of base stations 1412a, 1412b, 1412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1413a, 1413b, 1413c. Each base station 1412a, 1412b, 1412c is connectable to core network <NUM> over a wired or wireless connection <NUM>. A first UE <NUM> located in coverage area 1413c is configured to wirelessly connect to, or be paged by, the corresponding base station 1412c. A second UE <NUM> in coverage area 1413a is wirelessly connectable to the corresponding base station 1412a.

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 <FIG> illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system <NUM>, host computer <NUM> comprises hardware <NUM> including communication interface <NUM> configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system <NUM>.

It is noted that host computer <NUM>, base station <NUM> and UE <NUM> illustrated in <FIG> may be similar or identical to host computer <NUM>, one of base stations 1412a, 1412b, 1412c and one of UEs <NUM>, <NUM> of <FIG>, respectively.

Wireless connection <NUM> between UE <NUM> and base station <NUM> 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 <NUM> using OTT connection <NUM>, in which wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may improve service continuity and thereby provide benefits such as the ability to handover between access nodes without a perceptible interruption in service.

Other objectives, features and advantages of the enclosed embodiments will be apparent from the description.

Claim 1:
A method (<NUM>), implemented by a radio access network, RAN, node (<NUM>) in a RAN (<NUM>) of a wireless communication network (<NUM>), the method comprising:
signaling (<NUM>), responsive to detecting an overload condition of the RAN (<NUM>), a wireless device (<NUM>) to stop reporting Quality of Experience, QoE, measurements to the RAN (<NUM>); and
notifying (<NUM>) a management system (<NUM>) in a core network (<NUM>) outside of the RAN (<NUM>) that the reporting of QoE measurements to the RAN (<NUM>) has stopped.