PLMN checking for QoE measurements during UE mobility in different RRC states

Abstract

Systems and methods are disclosed for enabling a Public Land Mobile Network (PLMN) to check Quality of Experience (QoE) measurement reports during User Equipment (UE) mobility. In one embodiment, a method performed by a UE comprises receiving a QoE measurement configuration from a first network node, the QoE measurement configuration comprising one or more PLMN lists indicating one or more allowed PLMNs. The method further includes initiating an application session compliant with the QoE measurement configuration, initiating a QoE measurement according to the QoE measurement configuration, and transitioning from a connected state to an idle state. The method further comprises obtaining a PLMN identifier (ID) of a second network node during transition from an idle state to a connected state with respect to the second network node and determining whether the PLMN is an allowed PLMN. The method also includes operating according to a result of the determination.

Description

[0001] Related Applications This application claims the benefit of provisional patent application serial number 63 / 494,673, filed April 6, 2023, the disclosure of which is hereby incorporated by reference in its entirety. TECHNICAL FIELD

[0002] The present disclosure relates to quality of experience (QoE) measurement configuration and reporting in a wireless communication system, such as, for example, a Third Generation Partnership Project (3GPP) system. BACKGROUND

[0003] QoE framework overview Quality of experience (QoE) measurements (also referred to as “application layer measurements”) have been specified for Third Generation Partnership (3GPP) Long Term Evolution (LTE) and Universal Mobile Telecommunication System (UMTS), and recently for Fifth Generation (5G) New Radio (NR) in 3GPP Release 17. The purpose of QoE measurements is to measure the end-user experience of using certain applications. Currently, QoE measurements are specified and supported for Dynamic Adaptive Streaming over Hypertext Transfer Protocol (HTTP) (DASH), Mobile Telephone Service (MTSI) service of Internet Protocol (IP) Multimedia Subsystem (IMS), and Virtual Reality (VR).

[0004] The solution in LTE and UMTS is similar in the following general principles. QoE measurement collection (QMC) enables configuration of application layer measurements in a user equipment (UE) and transfer of a QoE measurement results file (often referred to as a “QoE report”) to the network by means of radio resource control (RRC) signaling. An application layer measurement configuration (also referred to as a QoE measurement configuration or QoE configuration) received by the radio access network (RAN) from an operation, administration, and maintenance (OAM) system or core network (CN) is encapsulated in a transparent container that is forwarded to the UE in a downlink RRCReconfiguration message. An application layer measurement report (also referred to as a QoE report) received by the UE access stratum (UE AS) or UE RRC layer from a higher layer (application layer) of the UE is encapsulated in a transparent container and sent to the network in an uplink RRC message MeasurementAppLayerReport . The RAN then forwards the QoE report to a measurement collector entity (MCE).

[0005] In 3GPP Release 17, the study “Study on NR QoE management and optimisation for different services” targeting solutions for QoE measurements in NR has been completed and finalized. According to this study project, QoE management in NR will not only collect QoE parameters for streaming services, but also consider typical performance requirements of different services (e.g. Augmented Reality (AR) / VR and Ultra-Reliable Low-Latency Communication (URLLC), where at least VR is covered in 3GPP Release 17). Based on the requirements of the services, the NR study also includes a more adaptive QoE management scheme that enables network optimization to meet the user experience of different services.

[0006] The configuration data related to QoE measurements (commonly referred to as application layer measurements in the standard specifications) consists of the following: an indication of the service type, an indication of the area in which the measurements are to be performed (denoted as Area Scope ), an IP address of the entity to which the collected measurement results (i.e. QoE reports) should be sent (commonly referred to as MCE, detailed as Measurement Collector Entity or Measurement Collection Entity), and a set of instructions of which type of measurements should be performed and how these measurements should be performed. These instructions are intended for the application layer in the UE and are placed in a “container” that cannot be read and interpreted by the network entities handling it, e.g. forwarding it to the UE and the UE access stratum level. The service types currently specified are MTSI and streaming traffic (DASH), and VR was added in 3GPP Rel-17. The area scope is defined according to cell or network related areas. In UMTS, the area scope is defined as a list of cells, a list of routing areas or a list of tracking areas. In LTE, the area scope is defined as a list of cells or a list of tracking areas or a list of Public Land Mobile Networks (PLMNs). In NR, the area scope is defined as a list of cells (list of NR Cell Global Identifiers (NCGIs)) or a list of tracking areas (list of Tracking Area Codes (TACs)) or a list of PLMNs in which measurements can be made.

[0007] QoE, and especially QoE configuration, comes in two flavors: management-based (m-based) QoE configuration and signaling-based (s-based) QoE configuration. In both cases, the QoE configuration originates from an OAM system or some other management entity, e.g. an entity handling customer satisfaction. All these entities are referred to as OAM systems in this document (where the OAM system also encompasses other entities).

[0008] For m-based QoE, the OAM system is typically interested in general QoE statistics from a certain area configured as an area scope. The m-based QoE configuration is sent directly from the OAM system to the RAN nodes controlling the cells within the area scope. Each RAN node then selects UEs within the area scope (and also fulfilling any other relevant conditions, such as support for the relevant application / service type), and sends the m-based QoE configuration to these UEs.

[0009] For s-based QoE, the OAM system is interested in collecting QoE measurements from a specific UE, e.g. because the user of the UE has submitted a complaint. The OAM system sends the s-based QoE configuration to the Home Subscriber Server (HSS) (in Evolved Packet System (EPS) / LTE) or Unified Data Management (UDM) (in 5G System (5GS) / NR), which forwards the QoE configuration to the current core network node (CN) of the UE, e.g. the Mobility Management Entity (MME) in EPS / LTE or the Access and Mobility Management Function (AMF) in 5G / NR. The CN then forwards the s-based QoE configuration to the RAN node serving the relevant UE, and the RAN forwards it to the UE.

[0010] What is forwarded to the UE is a service type indication and a container with measurement instructions. The UE does not know whether the received QoE configuration is m-based or s-based. In legacy systems, the QoE framework is integrated with the trace functionality, and a trace identifier (ID) is associated with each QoE configuration. In NR, the QoE functionality is logically separated from the trace functionality, but it will still partly reuse the trace signaling mechanism. In NR, and possibly in LTE, a globally unique QoE reference (formed by Mobile Country Code (MCC) + Mobile Network Code (MNC) + QoE Measurement Collection (QMC) ID, where the QMC ID is a 24-bit string) will be associated with each QoE configuration. The QoE reference is included in the container with measurement instructions, and is also sent to the RAN (i.e. the gNodeB (gNB) in NR). For the communication between the gNodeB (gNB) and the UE, the QoE reference is replaced by a shorter identifier denoted measConfigAppLayerId , which is locally unique within the UE (i.e. for each QoE configuration provided to the UE, there is a one-to-one mapping between measConfigAppLayerId and the QoE reference). measConfigAppLayerId is stored in the UE access layer, and is also forwarded in AT commands (which is a type of instruction used in the communication between the modem part of the UE and the application layer of the UE) together with the service type indication and the container with measurement instructions.

[0011] The reports with collected QoE reports are sent from the UE application layer to the UE access stratum level, which forwards them to the RAN, which in turn forwards them to the MCE. These QoE reports are placed in a "container" which is not interpretable for both the UE access stratum level and the RAN. The QoE reports can be configured to be periodic or only sent at the end of the application session. In addition, the RAN can instruct the UE to suspend QoE reporting, e.g. in case the cell / gNB is in an overload situation.

[0012] The RAN does not automatically become aware when an application session associated with a QoE measurement session is ongoing, and the UE access stratum level does not automatically become aware of this either. To mitigate this, session "start" / "stop" indications are introduced, sent from the application layer in the UE to the UE AS and from the UE AS to the RAN. When the application session and associated QoE measurement session ends, a session "stop" indication can be sent explicitly or implicitly in the form of a QoE report.

[0013] As an implementation based decision, the RAN can decide to release the QoE configuration in the UE at any time. Typically, this is done when the UE has moved outside the configured Area Scope area at any time.

[0014] One opportunity provided by the conventional solution is to be able to keep QoE measurements for the entire session even in case of handover. It is also discussed to let the UE continue QoE measurements for an ongoing application session even if the UE moves outside the configured area range at the same time, until the application session ends.

[0015] RRC states in 5G / NR In 5G / NR, a UE can be in any of three different RRC states: RRC CONNECTED state, RRC INACTIVE state and RRC IDLE state. The RRC CONNECTED state is the state typically used when the UE is actively communicating. The RRC INACTIVE state and the RRC IDLE state are designed to allow the UE to save energy compared to when the UE is in the RRC CONNECTED state.

[0016] The RRC IDLE state is the state where the UE consumes the least energy, when the UE moves to RRC IDLE, both the UE and the gNB delete information related to the UE, also called UE context, and the gNB thereby saves resources, but at the cost of a relatively long network access time, e.g. to move to RRC CONNECTED state.

[0017] The RRC_INACTIVE state has the property of placing it between the RRC_CONNECTED state and the RRC_IDLE state. The purpose of the RRC_INACTIVE state is to reduce the signaling overhead on the radio and network interfaces and to improve UE access latency (compared to the RRC_IDLE state) and UE energy consumption. In this state, the core network (CN) still considers the UE as connected, so the CN-RAN connection for the UE remains active although the RRC connection between the gNB and the UE is suspended. The gNB that maintains the connection to the CN when the UE is in the RRC_INACTIVE state is called the anchor gNB. To reduce the radio interface signaling at connection setup, UE context information is saved in the UE and in the anchor gNB, which enables the UE to resume its RRC connection when it is paged or has uplink (UL) data or signaling to send. When the CN has user data or control data to send to the UE, the data is sent to the anchor gNB, which then initiates the paging of the UE (also called RAN-initiated paging).

[0018] QoE measurement is supported when the UE is in RRC_IDLE state In 3GPP Release 18, the following agreements have been made so far regarding QoE measurements when the UE is in the RRC_IDLE state: • Both signaling-based and management-based QoE measurements in RRC INACTIVE / IDLE mode will be supported in Rel-18. • The UE handles area scope check for QoE measurements in RRC INACTIVE / IDLE mode. • Whether the UE AS layer or the UE APP layer handles area scope will be discussed based on RAN2 progress. • Multicast / broadcast service (MBS) broadcast service INACTIVE / IDLE QoE is supported first. • The UE shall save the QoE configuration for MBS broadcast service configured in RRC_CONNECTED even when the UE switches to RRC_IDLE and RRC_INACTIVE. • If the UE receives the configuration in RRC connected state, common QoE configuration mechanism is used to support QoE measurement configuration for MBS broadcast service for all RRC states, with Rel-17 QoE configuration mechanism as the baseline. • Whether the UE can only report INACTIVE / IDLE QoE report to gNB when the UE has entered RRC_CONNECTED due to other reasons is to be discussed in RAN2. • RAN3 discussed the alignment between logged minimization of drive tests (MDT) and MBS QoE when the basic solution for MBS QoE has been defined first. • RAN3 continued to discuss how to handle QoE reporting sent by a new gNB when the UE is in RRC_IDLE. • There is no enhancement for paging for the purpose of configuring the UE with legacy QoE measurement for RRC_IDLE / INACTIVE UEs. • Legacy paging for legacy QoE purpose is up to implementation. • The same set of parameters is used in QMC configuration for all RRC states. • RAN3 assumes that QoE measurement is not required per UE RRC state. • WA: MBS service area can be expressed by QoE area scope information element (IE), whether any enhancement is needed for this IE is FFS. • RRC state information when UE collects the uploaded QoE data should not be reported in the QoE report for MBS BC. MBS MC can discuss later. • MBS BC QoE measurement can be done after the UE switches from RRC_IDLE / RRC_INACTIVE to RRC_CONNECTED. • RAN3 will discuss which configuration information related to QoE measurement needs to be available in the new gNB. • In the new gNB, at least the following QoE configuration related information for MBS broadcast service should be available: o QoE reference o Measurement collection entity information, details can be further discussed • RAN3 will discuss which of the other QoE configuration information for MBS BC QoE should be available in the new gNB. o Measurement configuration application layer ID (RRC level ID) o Service type o Container for application layer measurement configuration (configuration container) o MDT alignment information o Area scope of QMC (area scope) o Single network slice assistance information (S-NSSAI) information (slice information) o RAN visible QoE (RVQoE) information o QoE measurement type (signaling based, management based) • Whether RV QoE measurement in RRC_IDLE and RRC_INACTIVE is supported is to be studied • Whether a new gNB can reconfigure MBS BC QoE is to be studied. SUMMARY

[0019] Systems and methods for enabling a public land mobile network (PLMN) to check quality of experience (QoE) measurement reports during user equipment (UE) mobility are disclosed. In one embodiment, a method performed by a UE includes receiving a QoE measurement configuration from a first network node, the QoE measurement configuration including one or more PLMN lists indicating one or more allowed PLMNs. The method also includes starting an application session subject to the QoE measurement configuration and starting QoE measurements according to the QoE measurement configuration. The method also includes transitioning from a connected state to an idle state. The method also includes, in transitioning from the idle state to the connected state with respect to a second network node, obtaining a PLMN identifier (ID) of the second network node and determining, based on a comparison of the PLMN ID of the second network node and PLMN IDs included in the one or more PLMN lists, whether the UE is to send any one or more of the following to the second network node: a QoE report; a QoE report availability indication; a network instance of the QoE measurement configuration stored by the UE; or an indication of availability of the network instance of the QoE measurement configuration stored by the UE. The method also includes operating according to a result of the determination. In this way, if the second network node is supposed to receive QoE reports and / or a network instance of a QoE configuration, the UE only sends that information to the second network node. This prevents the information from being sent to network nodes that are not supposed to receive it, which increases security.

[0020] In one embodiment, the one or more PLMN lists consists of a list of PLMNs in a regional scope of the QoE measurement configuration. In one embodiment, the PLMN ID of the second network node is not in the list of PLMNs, and the determining comprises determining that the UE will not send a QoE report availability indication to the second network node based on the PLMN ID of the second network node not being in the list of PLMNs. In another embodiment, the PLMN ID of the second network node is in the list of PLMNs, such that the UE, and the determining comprises determining that the UE will send a QoE report availability indication to the second network node based on the PLMN ID of the second network node being in the list of PLMNs. In another embodiment, the PLMN ID of the second network node is in the list of PLMNs, such that the UE, and the determining comprises determining that the UE will send a QoE report to the second network node based on the PLMN ID of the second network node being in the list of PLMNs.

[0021] In one embodiment, the first network node is in a first PLMN, and the second network node is in a second PLMN different from the first PLMN. In one embodiment, the PLMN ID of the second network node is not in the list of PLMNs, such that the UE, and the determining comprises determining that the UE will not send a QoE report to the second network node. In another embodiment, the PLMN ID of the second network node is in the list of PLMNs, and the determining comprises determining that the UE will send a QoE report availability indication to the second network node based on the PLMN ID of the second network node being in the list of PLMNs. In another embodiment, the PLMN ID of the second network node is in the list of PLMNs, and the determining comprises determining that the UE will send a QoE report to the second network node based on the PLMN ID of the second network node not being in the list of PLMNs.

[0022] In one embodiment, the determining comprises determining, based on the comparison of the PLMN ID of the second network node and the PLMN IDs included in the one or more PLMN lists, that the PLMN of the second network node is a PLMN in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration; and operating in accordance with the result of the determining comprises sending, to the second network node, any one or more of: a QoE report of QoE measurements performed according to the QoE measurement configuration; a QoE report availability indication of a QoE report of QoE measurements performed according to the QoE measurement configuration; the network instance of the QoE measurement configuration stored by the UE; an indication of availability of the network instance of the QoE measurement configuration stored by the UE.

[0023] In one embodiment, the determining comprises determining, based on the comparison of the PLMN ID of the second network node and the PLMN IDs included in the one or more PLMN lists, that the PLMN of the second network node is a PLMN in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration; and operating in accordance with the result of the determining comprises sending, to the second network node, the network instance of the QoE measurement configuration stored by the UE or an indication of availability of the network instance of the QoE measurement stored by the UE.

[0024] In one embodiment, the determining comprises determining, based on the comparison of the PLMN ID of the second network node and the PLMN IDs included in the one or more PLMN lists, that the PLMN of the second network node is a PLMN in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, but not a PLMN to which the UE is allowed to send QoE reports of QoE measurements performed according to the QoE measurement configuration; and operating in accordance with the result of the determining comprises performing QoE measurements according to the QoE measurement configuration while in the connected state with respect to the second network node, but refraining from sending a QoE report availability indication to the second network node.

[0025] In one embodiment, the determining comprises determining, based on the comparison of the PLMN ID of the second network node and the PLMN IDs included in the one or more PLMN lists, that the PLMN of the second network node is a PLMN in which the UE is not allowed to perform QoE measurements according to the QoE measurement configuration; and operating in accordance with the result of the determining comprises stopping performing QoE measurements according to the QoE measurement configuration.

[0026] In one embodiment, the one or more allowed PLMNs are: one or more PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration; and / or one or more PLMNs to which the UE is allowed to send QoE reports and / or stored network instances of the QoE measurement configuration.

[0027] In one embodiment, the one or more PLMN lists include a single list of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration and to which the UE is allowed to send associated QoE reports.

[0028] In one embodiment, the one or more PLMN lists include a first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration and a second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports.

[0029] In one embodiment, the one or more PLMN lists include a first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration and a second PLMN list containing PLMN IDs of stored network instances of the QoE measurement configuration to which the UE is allowed to send the QoE measurement configuration.

[0030] In one embodiment, the one or more PLMN lists include a first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, a second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports, and a third PLMN list containing PLMN IDs of stored network instances of the QoE measurement configuration to which the UE is allowed to send the QoE measurement configuration.

[0031] In one embodiment, the one or more PLMN lists include a first PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports and a second PLMN list containing PLMN IDs of stored network instances of the QoE measurement configuration to which the UE is allowed to send the QoE measurement configuration.

[0032] In one embodiment, the one or more PLMN lists include a PLMN list that includes PLMN IDs of PLMNs in which the UE is allowed to send associated QoE reports.

[0033] In one embodiment, the one or more PLMN lists include a PLMN list that includes PLMN IDs of PLMNs in which the UE is allowed to send only associated QoE reports.

[0034] In one embodiment, the one or more PLMN lists include a PLMN list that includes PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration but the UE is not allowed to send associated QoE reports.

[0035] In one embodiment, the one or more PLMN lists include a PLMN list that includes PLMN IDs of PLMNs in which the UE is allowed to send stored network instances of the QoE measurement configuration.

[0036] In one embodiment, the one or more PLMN lists include a PLMN list that includes PLMN IDs of PLMNs in which the UE is allowed to send only stored network instances of the QoE measurement configuration.

[0037] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE is adapted to receive, from a first network node, a QoE measurement configuration, the QoE measurement configuration including one or more PLMN lists indicating one or more allowed PLMNs. The UE is also adapted to start an application session subject to the QoE measurement configuration; start QoE measurements according to the QoE measurement configuration; and transition from a connected state to an idle state. The UE is further adapted, in a transition from the idle state to the connected state with respect to a second network node, to obtain a PLMN identifier (ID) of the second network node; determine, based on a comparison of the PLMN ID of the second network node and PLMN IDs included in the one or more PLMN lists, whether the UE is to send to the second network node any one or more of: a QoE report; a QoE report availability indication; a network instance of the QoE measurement configuration stored by the UE; or an indication of availability of the network instance of the QoE measurement configuration stored by the UE. The UE is also adapted to operate according to a result of the determination.

[0038] Embodiments of a method performed by a first network node are also disclosed. In one embodiment, a method performed by a first network node comprises sending, to a UE, a QoE measurement configuration comprising one or more PLMN lists indicating one or more allowed PLMNs, and causing the UE to transition from a connected state to an idle state.

[0039] In one embodiment, the one or more allowed PLMNs are one or more PLMNs in which the UE is to perform QoE measurements according to the QoE measurement configuration, and / or one or more PLMNs to which the UE is allowed to send QoE reports and / or stored network instances of QoE measurement configurations.

[0040] Corresponding embodiments of a first network node are also disclosed. In one embodiment, a first network node is adapted to send, to a UE, a QoE measurement configuration comprising one or more PLMN lists indicating one or more allowed PLMNs, and to cause the UE to transition from a connected state to an idle state. BRIEF DESCRIPTION OF DRAWINGS

[0041] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0042] Figure 1 Operation of a user equipment (UE), an old gNodeB (gNB), and a new gNB according to embodiments of the present disclosure is shown; Figure 2 An example of a communication system according to some embodiments is shown; Figure 3 A UE according to some embodiments is shown; Figure 4 A network node according to some embodiments is shown; Figure 5 is a block diagram of a host according to various aspects described herein, which can be Figure 2 Embodiments of a host; Figure 6 is a block diagram illustrating a virtual environment in which functions implemented by some embodiments can be virtualized; and Figure 7 A communication diagram showing a host communicating with a UE via a network node over a partial wireless connection according to some embodiments is shown. DETAILED DESCRIPTION

[0043] The examples set forth herein represent the information available to those skilled in the art as of the filing date of this patent application. Those skilled in the art will appreciate that the concepts set forth herein can apply to any number of embodiments beyond those explicitly described. Unless otherwise indicated, the description set forth herein is that for the best currently contemplated mode of carrying out the described embodiments. Those skilled in the art will appreciate that the concepts set forth herein can apply to any number of embodiments beyond those explicitly described. Unless otherwise indicated, the description set forth herein is that for the best currently contemplated mode of carrying out the described embodiments.

[0044] There are certain challenge(s) with Quality of Experience (QoE) measurements currently in Third Generation Partnership Project (3GPP) systems (e.g., Fifth Generation (5G) systems). The RAN3 working group in 3GPP is currently discussing support of QoE measurements for Multicast / Broadcast Services (MBS) when a User Equipment (UE) is in Radio Resource Control (RRC) IDLE or INACTIVE state. If a UE is configured to perform QoE measurements in IDLE state, 3GPP agrees that the UE will keep the QoE measurement configuration during the measurement performance. On the other hand, one issue that 3GPP is addressing is that, according to current specifications, the gNodeB (gNB) serving the UE should delete the UE context (i.e., information associated with the UE) before transitioning to IDLE state when the UE transitions to RRC IDLE. This means that the gNB deletes all information it has about the QoE measurement configuration for the UE. Then, when the UE returns to CONNECTED state from IDLE state, the UE can connect to another gNB, which will have no information about the QoE measurement configuration for the UE.

[0045] To overcome this issue, 3GPP agrees that the network instance of the QoE measurement configuration for the UE will not be deleted when the UE transitions to IDLE, but stored somewhere outside the gNB. Discussions are ongoing about where to store the network instance of the QoE measurement configuration for the UE. The basic principle in the discussions is that the stored information provided to the new gNB will ensure continuity of ongoing QoE measurements for MBS services even if the UE transitions between RRC states during an application session (i.e., during the measurement). Restoration of the network instance of the QoE measurement configuration for the UE will also be used to enable the gNB to forward QoE measurement results received from the UE to the correct Measurement Collector Entity (MCE).

[0046] In some scenarios, the UE can return to CONNECTED state from IDLE by connecting to a gNB in a different Public Land Mobile Network (PLMN) than the one the UE was in when the UE entered IDLE state and / or when the UE received the QoE configuration (these PLMNs are referred to herein as the “new PLMN” and the “old PLMN”, respectively). The basic property of this scenario is that: • The new PLMN can be a non-equivalent PLMN. • When connecting to a new gNB, if the UE has stored QoE reports collected while in IDLE, the UE can send a "QoE report availability" indication to the new gNB. • If the PLMN of the new gNB (i.e. the new PLMN) is a non-equivalent PLMN, the UE should not send a "QoE report availability" indication to the new gNB, one reason being that the MCE to which the gNB should forward the QoE reports can not be part of the new PLMN, or can not be reachable from that new PLMN. • When the UE is not configured for QoE measurements, it does not receive information about area scope, which means that it does not know in which PLMNs it is allowed to perform QoE measurements and send reports. • In case 3GPP decides to store network instances of QoE configuration at the UE while the UE is in IDLE, the UE should send the stored information to the new gNB to ensure QoE measurement and reporting continuity, but provided that the gNB is within an equivalent PLMN. • If the new PLMN is an illegal recipient of the stored network instances of QoE configuration as well as any stored QoE reports (containing measurement results collected in the old PLMN) (e.g. depending on business relationships between the operators of the new and old PLMN), then if the UE sends this information to the new PLMN, the result would be an undesired leakage of information between PLMNs, where the leaked information can sometimes be considered sensitive. Whether a certain PLMN is a legal recipient of the information is determined by the operator of the old PLMN. One possibility is that equivalent PLMNs constitute the legal recipients of the information.

[0047] It is not clear how to ensure that the stored QoE reports and the stored network instances of QoE configuration for the UE are provided by the UE only to gNBs in equivalent PLMNs, up to today.

[0048] Certain aspects of the present disclosure and embodiments thereof can provide solutions to these or other challenges. Systems and methods are disclosed herein to enable a UE to return from an IDLE state to a CONNECTED state to determine whether the UE should deliver stored QoE reports and stored network instances of QoE configuration information to a gNB serving the UE when it returns to the CONNECTED state.

[0049] According to one embodiment, the radio access network (RAN) node can also provide instructions to the UE in RRC CONNECTED or when releasing the UE from RRC CONNECTED to a non-connected RRC state. The instructions relate to whether the UE is allowed or not to deliver stored QoE / RAN visible QoE (RVQoE) reports to the new gNB (e.g., when the UE transitions back to CONNECTED state) based on the PLMN to which mobility is performed. Note that, as understood by one of ordinary skill in the art, conventional QoE measurement reports are provided in encapsulated format, while RVQoE measurement reports are visible to the RAN (e.g., encoded in RRC format).

[0050] Certain embodiments can provide one or more of the following technical advantages. Embodiments of the solution described herein have the advantage that the UE only sends the network instance of the QoE report or QoE configuration to the gNB that intends to receive it. This prevents information from being sent to gNBs that should not receive it, which increases security.

[0051] As used herein, a “network node” can be a RAN node, a gNodeB (gNB), an eNodeB (eNB), an en-gNB, a next generation eNodeB (ng-eNB), a gNB-central unit (CU), a gNB-distributed unit (DU), a gNB-CU-control plane (CP), a gNB-CU-user plane (UP), an eNB-CU, an eNB-CU-CP, an eNB-CU-UP, an integrated access and backhaul (IAB)-node, an IAB-donor DU, an IAB-donor-CU, an IAB-DU, an IAB-mobile termination (MT), an open RAN (O)-CU, an O-CU-CP, an O-CU-UP, an O-DU, an O-radio unit (RU), an O-eNB, a non-real-time RAN intelligent controller (non-RT RIC), a real-time RAN intelligent controller (RT-RIC), etc. As used herein, a “network node” can be a RAN node, a gNodeB (gNB), an eNodeB (eNB), an en-gNB, a next generation eNodeB (ng-eNB), a gNB-central unit (CU), a gNB-distributed unit (DU), a gNB-CU-control plane (CP), a gNB-CU-user plane (UP), an eNB-CU, an eNB-CU-CP, an eNB-CU-UP, an integrated access and backhaul (IAB)-node, an IAB-donor DU, an IAB-donor-CU, an IAB-DU, an IAB-mobile termination (MT), an open RAN (O)-CU, an O-CU-CP, an O-CU-UP, an O-DU, an O-radio unit (RU), an O-eNB, a non-real-time RAN intelligent controller (non-RT RIC), a real-time RAN intelligent controller (RT-RIC), etc.

[0052] The terms “application layer measurement configuration,” “application measurement configuration,” “QoE measurement configuration,” “QoE configuration,” “QoE measurement and reporting configuration,” and “QMC configuration” can be used interchangeably. Note, however, that “QMC configuration file” is not an equivalent term, but rather refers to the part of the QoE configuration that consists of an XML file containing instructions for the QoE metrics to be collected, etc.

[0053] The terms “QoE report” and “QoE measurement report” can be used interchangeably.

[0054] The terms “QoE configuration” and “QoE measurement configuration” can be used interchangeably.

[0055] The term "QoE configured network instance" refers to information that the gNB has when serving a UE in RRC CONNECTED, which refers to those QoE measurement configurations that are eligible to be performed in RRC IDLE mode. According to 3GPP agreements, the QoE configured network instance will be stored when the UE is in RRC IDLE mode.

[0056] When referring to a UE, the terms "access stratum", "UE AS" and "radio layer" can be used interchangeably.

[0057] The solution presented in this disclosure applies to New Radio (NR) and future radio access technologies (RATs) such as the sixth generation (6G), the IAB-MT has a parent backhaul link termination function and the IAB-DU has an access service provision function of a relay node.

[0058] "Sending a report to a node" can or can not imply that the node is the consumer, i.e. the final destination of the report.

[0059] The terms "node", "network node", "gNB" and "RAN node" can be used interchangeably herein.

[0060] The terms "session" and "application session" can be used interchangeably.

[0061] The solution is described herein using examples of QoE measurements for MBS, but the solution is equally applicable to QoE measurements of any service type that can be collected in IDLE state.

[0062] The solution is described herein using examples in which a session is ongoing when the UE transitions from RRC CONNECTED to RRC IDLE and back to RRC CONNECTED, but the examples are applicable even if the measurements have started while the UE was in RRC IDLE.

[0063] In the solution description, it is sometimes mentioned that the UE is not allowed to send QoE reports in a certain PLMN (e.g. a new PLMN). This also means that the UE is not allowed to indicate the availability of stored QoE report(s) in that PLMN. Conversely, if the UE is allowed to send QoE reports in a certain PLMN, this means that the UE is also allowed to indicate the availability of QoE reports in that PLMN.

[0064] In the solution description, it is often described to send a PLMN or a list of PLMNs to the UE, or to indicate a PLMN. In such expressions, "PLMN" refers to a PLMN ID consisting of MCC and MNC.

[0065] “Sending a report / configuration to a PLMN” means sending this information to a gNB whose cell serving the UE is located in this PLMN.

[0066] The network instance from which the UE sends the QoE configuration (which the UE has stored on behalf of the network when the UE was in RRC_IDLE state) can include a prior indication (from the UE to the network) of the availability of this network instance of QoE configuration at the UE. Upon receiving such an indication, the network can or can not choose to request the UE to send the network instance of QoE configuration. If this is how the sending of the network instance of QoE configuration is performed, then if the UE is not allowed to send a network instance of QoE configuration in a certain PLMN (e.g. a new PLMN), this also means that the UE is not allowed to indicate the availability of a stored such network instance of QoE configuration in that PLMN. Conversely, if the UE is allowed to send a network instance of QoE configuration in a certain PLMN, this means that the UE is also allowed to indicate the availability of a network instance of QoE configuration to the network in that PLMN. Note also that sending a network instance of QoE configuration to the network can only involve sending the network instance of QoE configuration without a prior indication of the availability of this network instance of QoE configuration.

[0067] In this specification, the following terms are considered equivalent: RRC_IDLE, IDLE, RRC_IDLE state, IDLE state, RRC_IDLE mode, IDLE mode, idle state, idle mode. Furthermore, the following terms are considered equivalent: RRC_INACTIVE, INACTIVE, RRC_INACTIVE state, INACTIVE state, RRC_INACTIVE mode, INACTIVE mode, inactive state, inactive mode. Likewise, the following terms are considered equivalent: RRC_CONNECTED, CONNECTED, RRC_CONNECTED state, CONNECTED state, RRC_CONNECTED mode, CONNECTED mode, connected state, connected mode.

[0068] The general scenario involves a UE transitioning to RRC_CONNECTED state after spending a period of time in IDLE state during which the UE has performed QoE measurements and stored the reports. More details of this scenario are: • The application session and QoE measurements are ongoing when the UE transitions from RRC_CONNECTED to RRC_IDLE and back to RRC_CONNECTED. Alternatively, the application session and QoE measurements start when the UE is in RRC_IDLE state. • The gNB to which the UE connects upon returning to RRC CONNECTED state is different from the node that was serving the UE when the UE previously transitioned from RRC CONNECTED state to RRC IDLE state. The former is referred to as the new gNB and the latter as the old gNB. • According to the current agreement, if the UE has stored QoE reports collected in IDLE state, the UE will send a "QoE report availability" indication to the new gNB. • In case 3GPP decides to store the network instance of the QoE configuration at the UE when the UE is in RRC IDLE, the UE shall send the stored information to the new gNB to ensure QoE measurement and reporting continuity, but provided that the gNB is within the equivalent PLMN or the gNB is identified by a specific network identifier.

[0069] The solution is described using an example of one QoE measurement configuration, but it is equally applicable to any number of QoE measurement configurations at the UE.

[0070] Another scenario involves a UE that is handed over (i.e., in RRC CONNECTED state) to a PLMN that is an equivalent PLMN but not included in the area scope for QoE / RVQoE measurements. For example, as part of the QoE / RVQoE configuration sent to the UE, the source RAN node includes a first "mobility to equivalent PLMN" parameter, which will make the UE understand that, in case of mobility towards an equivalent PLMN that is not included in the area scope, the UE should handle QoE / RVQoE measurements and / or QoE / RVQoE reports in the same way as described in the solution for the UE transition from RRC CONNECTED to RRC IDLE. In a variant of this case, the "mobility to equivalent PLMN" parameter will make the UE know that, in case of mobility towards any equivalent PLMN, the UE should handle QoE / RVQoE measurements and / or QoE / RVQoE reports in the same way as described in the solution for the UE transition from RRC CONNECTED to RRC IDLE.

[0071] In one variant, as part of the handover execution, the source RAN node sends to the UE a second "mobility to equivalent PLMN" parameter (in one variant, this parameter is the same as the first "mobility to equivalent PLMN" parameter described above), e.g. in the RRCReconfiguration message containing the handover command prepared by the target RAN node. The second "mobility to equivalent PLMN" parameter will make the UE understand that, once it will be served / connected by the target RAN node, it will have to handle the QoE / RVQoE measurements and / or QoE / RVQoE reporting in the same way as described in the solution for the transition of the UE from RRC_CONNECTED to RRC_IDLE.

[0072] In another variant, in case of transition from RRC_CONNECTED to RRC_IDLE or RRC_INACTIVE, the RAN node instructs the UE (e.g. in the RRCRelease message) that, when reconnecting or resuming towards a cell belonging to an equivalent PLMN not included in the area scope, the UE should apply the methods described in the present disclosure. The instruction can be sent using a third "mobility to equivalent PLMN" parameter, which can be the same as the first and / or second "mobility to equivalent PLMN" parameters described above, or a different parameter.

[0073] The terms "new PLMN" and "old PLMN" are used herein. As long as only two PLMNs are involved, these terms are clear enough. However, in some scenarios / embodiments, a UE can receive a QoE configuration in a first PLMN (PLMN1), then move to a second PLMN (PLMN2), and then move to a third PLMN (PLMN3). In such scenarios / embodiments, the first PLMN (PLMN1) is considered as the "old PLMN", even when the UE has entered / connected to the third PLMN (PLMN3), i.e. it is the PLMN from which the UE received the QoE configuration that is the "old PLMN". It is also noted that the term "old gNB" refers to a gNB in the old PLMN. Likewise, the term "new gNB" refers to a gNB in the new PLMN.

[0074] Figure 1 The operation of the UE 100, the old gNB 102 and the new gNB 104 according to one embodiment of the present disclosure is illustrated. Optional steps are represented by dashed lines / dashed boxes. Furthermore, although the steps are illustrated in a particular order in Figure 1 the procedure, the steps can be performed in any suitable order. The steps of the procedure are as follows: Step 106: When in RRC_CONNECTED state, the UE 100 receives a QoE measurement configuration (e.g. for a MBS service) from the old gNB 102, according to which the UE 100 will perform QoE measurements in RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE states. As part of the measurement configuration, the UE 100 receives a list of PLMNs of stored network instances in which it should perform measurements and / or to which it can send QoE reports and / or QoE configurations. These PLMNs are referred to herein as “equivalent PLMNs” or “allowed PLMNs” (Note: in TS 28.405, v18.2.0, the list of PLMNs in which the UE should perform measurements is referred to as PLMN targets) • In one variant, the UE receives one list of equivalent PLMNs in which the UE is allowed to perform QoE measurements and to which it is allowed to send reports. • In another variant, the UE receives two lists of PLMNs. The first list contains the PLMNs in which the UE is allowed to perform measurements, and the second list contains the PLMNs to which the UE is allowed to send reports. • In another variant, the UE receives two lists of PLMNs. The first list contains the PLMNs in which the UE is allowed to perform measurements, and the second list contains the PLMNs to which the UE is allowed to send reports and QoE configurations of stored network instances. • In another variant, the UE receives three lists of PLMNs. The first list contains the PLMNs in which the UE is allowed to perform measurements, the second list contains the PLMNs to which the UE is allowed to send reports, and the third list contains the PLMNs to which the UE is allowed to send QoE configurations of stored network instances. • In another variant, the UE receives two lists of PLMNs. The first list contains the PLMNs to which the UE is allowed to send reports, and the second list contains the PLMNs to which the UE is allowed to send QoE configurations of stored network instances. • In one variant, the UE receives one list of PLMNs, which contains the PLMNs in which the UE is allowed to send reports only. • In one variant, the UE receives one list of PLMNs, which contains the PLMNs in which the UE is allowed to measure only but not to send reports (i.e. it needs to store the reports). • In one variant, the UE receives one list of PLMNs, which contains the PLMNs in which the UE is allowed to send QoE configurations of stored network instances only. • In one variant, (one or more) lists are associated with the area ranges received by the RAN nodes from the OAM (e.g., in TS38.413 v17.4.0). Area Scope for QMC The PLMN list in IE is the same. In another variant, the "report list" is a subset of the PLMN list within the region. • In one variant, the UE receives a list of equivalent PLMNs not included in the Area Scope for QMC IE in TS 38.413 v17.4.0, in which the UE is allowed to continue performing measurements but is not allowed to send reports. • In one variant, the UE receives a list of equivalent PLMNs not included in the Area Scope for QMC IE in TS 38.413 v17.4.0, in which the UE is not allowed to continue performing measurements and is not allowed to send reports. • In one variant, when the UE moves to any equivalent PLMN, the UE receives an instruction to continue performing the measurement. • In one variant, when moving to any non-equivalent PLMN, the UE receives an indication that no QoE / RVQoE measurements are reported. • In one variant, the UE is instructed not to report any QoE configuration information received by the RAN at any time to any equivalent PLMN (or, alternatively, any QoE configuration information received by the RAN when the UE is released to RRC_IDLE). • In one variant, the UE is instructed not to report any QoE configuration information received by the RAN at any time to any non-equivalent PLMN (or, alternatively, any QoE configuration information received by the RAN when the UE is released to RRC_IDLE). • In one variant, the UE is instructed not to report any QoE configuration information received by the RAN at any time to any equivalent PLMN that is not included in the area scope (or, alternatively, any QoE configuration information received by the RAN when the UE is released to RRC_IDLE). • In one variant, when the UE is in RRC_IDLE mode, the UE receives a network instance of the QoE measurement configuration from the network for storage. Alternatively, this can be done in step 2 or 3. • In one variant, the UE receives a list of PLMNs containing multiple PLMNs, among which, after the UE returns to RRC_CONNECTED, the UE is allowed to send an instance of the QoE measurement configuration. This list can be the same as any of the lists mentioned above, or it can be a separate list. • In one variant, for each entry in the list of PLMNs to which the report can be sent, the network also indicates a separate identifier of the MCE to which the gNB should forward the report, e.g. MCE ID or MCE Uniform Resource Indicator (URI) or MCE IP address. • In one variant, the list of PLMN(s) is received as part of or together with the network instance of the QoE measurement configuration. • In one variant, instead of receiving a list of PLMNs, the UE receives a network or gNB identifier which identifies the network instance and / or the network or gNB to which the UE is allowed to send the QoE configuration and / or the QoE report. The network identifier can for example be used to identify a certain operator or a certain network vendor.

[0075] Step 108: The UE starts an application session subject to the above measurement configuration and starts the QoE measurement. This can happen while the UE is in RRC_CONNECTED, RRC_INACTIVE or RRC_IDLE state. Furthermore, this can happen before or after the UE has moved to a new PLMN. It is also possible that the UE moves to and transitions to RRC_CONNECTED state in the new PLMN and then transitions back to RRC_INACTIVE or RRC_IDLE state in the new PLMN and then starts an application session subject to the above measurement configuration and starts the QoE measurement and then returns again to RRC_CONNECTED state in the new PLMN.

[0076] This step is optional. However, if this step is not performed, it means that there will be no stored QoE measurement reports to send (or not to send) in the new PLMN.

[0077] Step 110: The network sends the UE to RRC_IDLE state (in some cases, this step can be performed before step 2). When the UE is released to RRC_IDLE state, the application session and the QoE measurement can be ongoing, but the application session and the QoE measurement session can also start after the transition to RRC_IDLE state (see also step 2). The UE stores the assembled QoE report. • In one variant, just before being sent to RRC_IDLE state by the network, the UE receives from the network a network instance of the QoE measurement configuration which is to be stored while the UE is in RRC_IDLE mode. Alternatively, this can be done in step 1 or 2.

[0078] Step 112: In the course of transitioning from RRC_IDLE to RRC_CONNECTED state, the UE receives an RRCSetup message from the new gNB (step 112A). The UE checks the PLMN(s) list it previously received from the old gNB and based on the list content and the PLMN of the new gNB, the UE decides (step 112B) whether it should send to the network one or both of the following, or none: • an indication of "QoE report availability". • the network instance of the QoE measurement configuration. • alternatively, an indication of the availability of the network instance of the QoE measurement configuration.

[0079] The UE operates according to the result of the decision in step 112C.

[0080] More specifically, in one embodiment, if the PLMN of the new gNB is in the list of PLMNs where the UE is allowed to send QoE reports (including the case of one complete list for both QoE reporting and QoE configuration delivery), the UE sends an indication of "QoE report availability", e.g. as part of the RRCSetupComplete message (step 112C1). Subsequently, the UE can send the stored reports to the network upon request from the network (e.g. after SRB4 has been established). • If the UE receives a dedicated ID (or URI or URL or IP address) of the MCE in that PLMN to which the reports should be sent, the UE indicates the MCE ID to the gNB and the gNB forwards the reports to that MCE. • In one variant, the UE will only send to the new gNB the reports collected in IDLE state when the UE was in the same PLMN. In another variant, all stored reports will be sent. • In one variant, the UE is instructed in which order to send the reports, e.g. first the newest reports or first the oldest reports.

[0081] If the PLMN of the new gNB is in the list of PLMNs where the UE is allowed to perform QoE measurements (including the case of one complete list for both QoE reporting and QoE configuration delivery), or if the gNB is a gNB to which the UE is allowed to send QoE reports or the network instance of the QoE measurement configuration according to a network or gNB identifier, the UE sends the stored network instance of the QoE measurement configuration as part of the RRCSetupComplete message or another RRC message.

[0082] If the PLMN of the new gNB is in the list of PLMN(s) in which the UE can perform QoE measurements, but not in the list of PLMNs to which the UE is allowed to send QoE reports, the UE will continue to perform the measurements and store the reports, without sending them to the network, nor indicating their availability to the network.

[0083] If the PLMN of the new gNB is in the list of PLMNs in which the network instance of the QoE measurement configuration is allowed for the UE, the UE sends the network instance of the QoE measurement configuration, or an indication of the availability of the network instance of the QoE measurement configuration.

[0084] If the PLMN of the new gNB is not in the list of PLMNs in which the UE is allowed to perform QoE measurements, the UE will stop performing the QoE measurements. If the UE is not allowed to send QoE reports or network instances of QoE configuration, the UE will not indicate the presence of any QoE reports or QoE configuration in the network in RRC messages.

[0085] Additional embodiments and variations For any of the above lists of PLMNs, the list of PLMNs can be a list stored in a Universal Subscriber Identity Module (USIM) (e.g., entered into the USIM before or at the time of provisioning a subscription (e.g., a subscription associated with the UE or a user of the UE)), rather than a list of PLMNs sent to the UE in the old PLMN. An example of such a list stored in the USIM is a list of equivalent home PLMNs.

[0086] In some embodiments, the UE performs QoE measurements (either continued or newly started) in the new PLMN according to the QoE configuration received in the old PLMN (where the QoE measurements can be performed in any RRC state, in particular in RRC_IDLE state). In some embodiments, the UE is allowed to send QoE reports in the new PLMN if the QoE reports contain at least in part information collected in the new PLMN. In other embodiments, the UE is allowed to send QoE reports in the new PLMN only if the QoE reports contain only information collected in the new PLMN. As an option, the UE can prune the compiled QoE reports (i.e., remove such information from the QoE reports) from information not collected in the new PLMN, so that the QoE reports meet the requirement of containing only information collected in the new PLMN, thereby allowing the UE to send the QoE reports in the new PLMN. In all these embodiments, the rules and / or behavior followed by the UE can be configured by the old PLMN, or can be specified in standards.

[0087] Capability signaling For the proposed solution to be executed, in one embodiment, the UE indicates to the network that it is capable of reporting according to a variant of that solution. • The UE can indicate its capabilities in the form of ENUMERATED indication type, e.g. “Support two PLMN list”. • Alternatively, the capabilities to support different variants of the solution can be indicated in the form of a bitmap, where each bit corresponds to a variant. Bit value “1” can mean that the variant is supported, while value “0” can mean that the variant is not supported, or vice versa.

[0088] An implementation example in TS 38.331 v17.4.0 is shown below: >>>>>>>>>>>>>>>>> Start of example implementation <<<<<<<<<<<<<<<<<< 5.3.3.4 Reception of RRCSetup by the UE The UE shall, upon receipt of RRCSetup perform the following actions: 1> set the contents of RRCSetupComplete message as follows: […] 2> if the UE has logged measurements available for NR and if RPLMN is included in VarLogMeasReport : plmn-IdentityList 3> include in logMeasAvailable message; RRCSetupComplete 3> if Bluetooth measurement results are included in the logged measurements, the UE is available for NR: 4> include in logMeasAvailableBT message; RRCSetupComplete 3> if WLAN measurement results are included in the logged measurements, the UE is available for NR: 4> include in logMeasAvailableWLAN message RRCSetupComplete 2> if is included in VarLogMeasReport : sigLoggedMeasType 3> if T330 timer is running and the logged measurements are configured for NR: 4> set to RRCSetupComplete in sigLogMeasConfigAvailable message true 3> else: 4> if the UE has logged measurements available for NR: 5> include RRCSetupCompleteThe message will include sigLogMeasConfigAvailable be set to false 2> if the UE has stored QoE measurement configuration available for NR and if the RPLMN is included in the plmn-IdentityList including in the storage of VarLogMeasReportApplayer or VarLogMeasConfigAppLayer plmn- ​ IdentityList In some embodiments, the method further comprises administering 2> if the UE has stored QoE measurement configuration available for NR and if the RPLMN is included in the plmn-IdentityList includes, as part of the corresponding QoE configuration, stored in the plmn-IdentityList repository 120: 3> set measReportAppLayerAvailable and appLayerMeasNetworkConfigStored including in RRCSetupComplete the message; 2> if the UE has available connection setup failure or connection resume failure information in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to the plmn stored in at least one entry of VarConnEstFailReport or VarConnEstFailReportList - Identity : 3> include the connEstFailInfoAvailable in the RRCSetupComplete message; […] 1> submit the RRCSetupComplete message to lower layers for transmission, whereupon the procedure ends. >>>>>>>>>>>>>>>>> End of example implementation <<<<<<<<<<<<<<<<<<< Figure 2 An example of a communication system 200 according to some embodiments is shown. It should be noted that the UE and network node described in Figure 2 and in the following figures can operate according to the above description of functionality of the UE and network node / RAN node / gNB, as will be appreciated by a person skilled in the art.

[0089] ​In this example, the communication system 200 includes a telecommunication network 202 that includes an access network 204 (e.g., a radio access network (RAN)) and a core network 206 that includes one or more core network nodes 208. The access network 204 includes one or more access network nodes (e.g., network nodes 210A and 210B (one or more of which are generally referred to as network nodes 210)) or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP access point (AP). Further, as those skilled in the art will appreciate, network nodes are not necessarily limited to implementations in which the radio and baseband parts are supplied and integrated by a single supplier. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 202 includes one or more Open RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 202 that supports ORAN specifications (e.g., specifications published by the O-RAN Alliance or any similar organization) and can operate individually or with other nodes to implement one or more functionalities of any node in the telecommunication network 202, including one or more network nodes 210 and / or core network nodes 208.

[0090] Examples of ORAN network nodes include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU) (including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP)), a RAN intelligent controller (near real-time or non-real-time) hosting software or software plug-ins (e.g., near real-time control applications (e.g., xApps) or non-real-time control applications (e.g., rApps)), or any combination thereof (the adjective “open” denotes support for ORAN specifications). The network nodes can support the specifications by, for example, supporting interfaces defined by the ORAN specifications, such as Al, Fl, Wl, El, E2, X2, Xn interfaces, an open fronthaul user plane interface, or an open fronthaul management plane interface. Further, an ORAN access node can be a logical node in a physical node. Further, the ORAN network nodes can be implemented in a virtualized environment (further described below) in which one or more network functions are virtualized. For example, the virtualized environment can include an O-Cloud computing platform that is orchestrated by a service management and orchestration framework via an O-2 interface defined by the O-RAN Alliance or similar technology. The network nodes 210 facilitate direct or indirect connectivity of user equipment (UE) such as the UEs 212A, 212B, 212C, and 212D (one or more of which can be referred to collectively as UEs 212) to the core network 206, such as through one or more wireless connections.

[0091] Example wireless communications over wireless connections include the use of electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable to convey information over distances without the use of wiring, cables, or other physical conduits. Moreover, in different embodiments, communication system 200 can include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (whether via wired or wireless means). Communication system 200 can include any type of communication, telecommunications, data, cellular, radio, and / or other similar type of system, and / or connect with such systems through an interface.

[0092] UE 212 can be any of a variety of communication devices, including a wireless device arranged, configured and / or operable to communicate wirelessly with network node 210 and other communication devices. Similarly, network node 210 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 212 and / or with other network nodes or devices in the telecommunication network 202 to enable and / or provide network access (such as wireless network access) and / or to perform other functions (such as management in the telecommunication network 202).

[0093] In the depicted example, core network 206 connects network node 210 to one or more hosts, such as host 216. These connections can be direct or indirect (e.g., via one or more intermediate networks or devices). In other examples, network nodes can be coupled to hosts directly. Core network 206 includes one or more core network nodes (e.g., core network node 208), which are comprised of hardware and software components. Features of these components can be substantially similar to those described with respect to UEs, network nodes, and / or hosts, such that their description can generally apply to corresponding components of core network node 208. Example core network nodes include functionality of one or more of a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-concealing function (SIDF), a unified data management (UDM), a security edge protection proxy (SEPP), a network exposure function (NEF), and / or a user plane function (UPF).

[0094] The host 216 can be under the ownership or control of a service provider other than the operator or provider of the access network 204 and / or the telecommunication network 202, and can be operated by or for the service provider. The host 216 can host various applications to provide one or more services. Examples of such applications include live and on-demand audio / video content, data collection services (such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs), analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for alarm and monitoring centers, or any other such functionality performed by servers.

[0095] Overall, Figure 2 The communication system 200 enables connectivity between the UEs, the network nodes, and the host computer. In that sense, the communication system 200 can be considered to comprise at least the following three parts:

[0096] In some examples, the telecommunication network 202 is a cellular network implementing 3GPP standardized features. Thus, the telecommunication network 202 can support network slicing to provide different logical networks for different devices connected to the telecommunication network 202. For example, the telecommunication network 202 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, while providing enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine type communications (mMTC) / Internet of Things (IoT) services to yet other UEs.

[0097] In some examples, the UEs 212 are configured to transmit and / or receive information without direct human interaction. For example, a UE can be designed to transfer information to the access network 204 according to a predetermined schedule, when triggered to do so by an internal or external event, or in response to requests from the access network 204. In addition, UEs can be configured for operation in a single radio access technology (RAT) or multiple radio access technologies or multi-standard mode. For example, UEs can be configured for operation using any one or a combination of WiFi, New Radio (NR), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC) such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR- Dual Connectivity (EN-DC).

[0098] In this example, the hub 214 communicates with the access network 204 to facilitate indirect communication between one or more UEs (e.g., UEs 212C and / or 212D) and a network node (e.g., network node 210B). In some examples, the hub 214 can be, for example, a controller, a router, a content source and analytics, or any other communication apparatus described herein with respect to a UE. For example, the hub 214 can be a broadband router that enables access by the UEs to the core network 206. As another example, the hub 214 can be a controller that sends commands or instructions to one or more actuators in the UEs. The commands or instructions can be received from the UEs, from the network nodes 210, or by executable code, scripts, processes, or other instructions in the hub 214. As another example, the hub 214 can be a data collector that acts as a temporary storage for UE data, and in some embodiments, can perform analysis or other processing of the data. As another example, the hub 214 can be a content source. For example, for a UE that is a virtual reality (VR) headset, display, speaker, or other media delivery apparatus, the hub 214 can retrieve VR assets, video, audio, or other media or data related to sensory information via the network nodes, which the hub 214 then provides directly to the UE after performing local processing, and / or after adding additional local content. In still another example, the hub 214 acts as a proxy server or orchestrator for the UEs, especially in the case that one or more of the UEs are low-energy loT devices.

[0099] The hub 214 can have a constant / persistent or intermittent connection to the network node 210B. The hub 214 can also allow for different communication schemes and / or scheduling between the hub 214 and UEs (e.g., UEs 212C and / or 212D) and between the hub 214 and the core network 206. In other examples, the hub 214 is connected to the core network 206 and / or one or more UEs via a wired connection. Further, the hub 214 can be configured to connect to a machine-to-machine (M2M) service provider over the access network 204 and / or to another UE over a direct connection. In some scenarios, a UE can establish a wireless connection with the network node 210 while still being connected via the hub 214 via a wired or wireless connection. In some embodiments, the hub 214 can be a dedicated hub - i.e., a hub whose primary function is to route communications to / from UEs from / to the network node 210B. In other embodiments, the hub 214 can be a non-dedicated hub - i.e., a device that is capable of operating to route communications between UEs and the network node 210B, but is additionally capable of operating as a communication start and / or end point for certain data channels.

[0100] Figure 3 A UE 300 according to some embodiments is shown. As used herein, a UE refers to a device that is capable, configured, arranged and / or operable to communicate wirelessly with a network node and / or other UEs. Examples include, but are not limited to, smart phones, mobile phones, cellular phones, Voice Over Internet Protocol (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless web tablets, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop-mounted devices, smartbooks, smart devices, wireless customer premises equipment (CPE) devices, vehicles, vehicle-mounted or vehicle-embedded devices, etc. Other examples include any UE identified by 3GPP, including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0101] A UE can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, dedicated short range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-anything (V2X). In other examples, a UE can not necessarily have a user in the sense of a human user that owns and / or operates the relevant device. Instead, a UE can represent a device that is intended for sale to, or operation by, a human user but can not, or can not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended for sale to, or operation by, an end user but can be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0102] The UE 300 includes processing circuitry 302 operably coupled to an input / output interface 306, a power source 308, a memory 310, a communication interface 312, and / or any other component(s) or any combination thereof. Certain UEs can utilize all of the components shown in FIG. 3, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Furthermore, a particular UE can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. Figure 3 The components of the UE 300, or alternatively the components of the base station 350, can include hardware components, software components, or a combination of both hardware and software components.

[0103] The processing circuitry 302 is configured to process instructions and data, and can be configured to implement any sequential state machine operative to

[0104] In this example, the input / output interface 306 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include 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. The input devices can allow a user to capture information into the UE 300. Examples of input devices include a touch-sensitive or presence-sensitive 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 direction pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, and the like, or any combination thereof. The output devices can use the same types of interfaces as the input devices. For example, a universal serial bus (USB) port can be used to provide input to the UE 300, as well as output from the UE 300.

[0105] In some embodiments, the power source 308 can be configured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), an photovoltaic device, or a power cell can be used. The power source 308 can also include a power circuit that can deliver power from the power source 308 and / or an external power source to portions of the UE 300 via an input circuit or interface, such as a power cable. For example, the power circuit can deliver power to charge the power source 308. The power circuit can perform any formatting, converting, or other modification to the power from the power source 308 to make the power suitable for the respective components of the UE 300 to which power is supplied.

[0106] The memory 310 can be configured to include a memory, such as a volatile memory (e.g., random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM)), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable disk, a flash drive, and the like. In one example, the memory 310 includes one or more applications 314, such as an operating system, a web browser application, a widget or gadget engine, or other applications, and corresponding data 316. The memory 310 can store any of a variety of operating systems, or combinations of operating systems, for use by the UE 300.

[0107] Memory 310 can be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drives, external hard drives, thumb drives, pen drives, key drives, High-Density Digital Versatile Disc (HD-DVD) optical disc drives, internal hard disk drives, Blu-Ray optical disc drives, Holographic Digital Data Storage (HDDS) optical disc drives, external mini-dual in-line memory modules (DIMMs), synchronous dynamic RAM (SDRAM), external micro-DIMMs, intelligent card memory such as a Universal Integrated Circuit Card (UICC) -form factor, tamper-resistant module containing one or more Subscriber Identity Modules (SIM), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card." Memory 310 can allow UE 300 to access instructions, application programs and the like stored on transitory or non-transitory storage media for downloading or uploading data. An article of manufacture, such as one utilizing a communication system, can have information stored thereon that can be tangibly embodied in a machine-readable storage medium or that can be transmitted by a signal that can be tangibly embodied in a machine-readable storage medium.

[0108] Processing circuitry 302 can be configured to communicate with an access network or other networks using communication interface 312. Communication interface 312 can include one or more communication subsystems and can include or be communicably coupled to antenna 322. Communication interface 312 can include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node of an access network), for example. Each transceiver can include transmitter 318 and / or receiver 320 adapted to provide network communications (e.g., optical, electrical, frequency allocations, etc.). Additionally, transmitter 318 and receiver 320 can be coupled to one or more antennas (e.g., antenna 322) and can share circuit components, software, or firmware, or alternatively be separately implemented.

[0109] In the illustrated embodiment, the communication functionality of the communication interface 312 can include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, NFC, location-based communication such as determining a location using the Global Positioning System (GPS), another similar communication functionality, or any combination thereof. The communication can be implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connections (QUIC), Hypertext Transfer Protocol (HTTP), and so on.

[0110] Regardless of the type of sensor, the UE can provide an output of data captured by its sensors via its communication interface 312 through a wireless connection to a network node. The data captured by the sensors of the UE can be passed to the network node through the wireless connection via another UE. The output can be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to even the load of the reports from several sensors), in response to a triggering event (e.g., sending an alarm when moisture is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0111] As another example, the UE includes an actuator, motor, or switch related to a communication interface that is configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight according to the received input, or a robotic arm performing a medical procedure according to the received input.

[0112] A UE in the form of an IoT device can be a device intended for use in one or more application domains such as, but not limited to, smart cities, extended industrial applications, and health care. Non-limiting examples of such IoT devices are devices that are or are embedded into: a connected refrigerator or freezer, a television, a connected lighting fixture, an electric meter, a robotic vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / water level sensor, an electric door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, an augmented reality (AR) or VR head-mounted display, a wearable device for tactile augmentation or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device like a heart rate monitor or a teleoperated surgical robot. In addition to the other components described with respect to the UE 300 as shown in FIG. 3, a UE in the form of an IoT device also includes circuitry and / or software depending on the intended application of the IoT device. Figure 3

[0113] As still another specific example, in an IoT scenario, a UE can represent a machine or other device that performs monitoring and / or measurements and passes the results to another UE and / or a network node. In this case, the UE can be a M2M device, which in a 3GPP context can be referred to as an MTC device. As one particular example, a UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent a vehicle (such as a car, bus, truck, boat, airplane) or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0114] In practice, any number of UEs can be used together in relation to a single use case. For example, a first UE can be or be integrated in a drone, and provide speed information (obtained by a speed sensor) of the drone to a second UE that is a remote controller operating the drone. When the user makes a change from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the speed of the drone. The first and / or second UE can also contain more than one of the functionalities described above. For example, a UE can include both a sensor and an actuator, and handle data communication for both the speed sensor and the actuator.

[0115] Figure 4 ​A network node 400 according to some embodiments is shown. As used herein, network node refers to devices, equipment, and / or facilities capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with UEs and / or with other network nodes or equipment in a telecommunications network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), base stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of O-RAN nodes (e.g., O-RUs, O-DUs, O-CUs).

[0116] Base stations can be categorized based on the amount of their provided coverage (or, in other words, their transmission power level) and thus, depending on the provided coverage, can be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Base stations can be relay nodes or relay donor nodes controlling relays. Network nodes can also include one or more (or all) parts of a distributed radio base station such as centralized, distributed, and / or remote radio units (RRUs), sometimes called remote radio heads (RRHs). Such RRUs can be integrated with antennas or be integrated as radio equipment without antennas. Parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS).

[0117] Other examples of network nodes include multi-transmit and receive point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices such as MSR BSs, network controllers such as radio network controllers (RNCs) or BS controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Center (E-SMLC)), and / or

[0118] The network node 400 includes processing circuitry 402, a memory 404, a communication interface 406, and a power source 408. The network node 400 can be composed of multiple physical

[0119] The processing circuitry 402 can comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other processing integrated circuit, as well as a combination of hardware and / or software that provide the functionality described herein. The processing circuitry 402 can be implemented with

[0120] In some embodiments, the processing circuitry 402 comprises a system on a chip (SOC). In some embodiments, the processing circuitry 402 comprises one or more of radio frequency (RF) transceiver circuitry 412 and baseband processing circuitry 414. In some embodiments, the RF transceiver circuitry 412 and the baseband processing circuitry 414 can be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuitry 412 and the baseband processing circuitry 414 can be on the same chip or set of chips, board, or unit.

[0121] Memory 404 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, optical discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuitry 402. Memory 404 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.) and / or other instructions (capable of being executed by processing circuitry 402 and utilized by network node 400). Memory 404 may be used to store any calculations performed by processing circuitry 402 and / or any data received via communication interface 406. In some embodiments, processing circuitry 402 and memory 404 are integrated.

[0122] Communication interface 406 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface 406 includes one or more ports / terminals 416 for sending and receiving data to and from a network, for example, via a wired connection. Communication interface 406 also includes radio front-end circuitry 418, which may be coupled to antenna 410 or, in some embodiments, is part of antenna 410. Radio front-end circuitry 418 includes filter 420 and amplifier 422. Radio front-end circuitry 418 may be connected to antenna 410 and processing circuitry 402. Radio front-end circuitry 418 may be configured to modulate the signal transmitted between antenna 410 and processing circuitry 402. Radio front-end circuitry 418 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 418 may use a combination of filter 420 and / or amplifier 422 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 410. Similarly, when receiving data, antenna 410 can collect radio signals, which are then converted into digital data by radio front-end circuitry 418. The digital data can then be passed to processing circuitry 402. In other embodiments, communication interface 406 may include different components and / or different combinations of components.

[0123] In certain alternative embodiments, network node 400 does not include separate radio front-end circuitry 418, instead, processing circuitry 402 includes radio front-end circuitry and is connected to antenna 410. Similarly, in some embodiments all or some of RF transceiver circuitry 412 is part of communication interface 406. In still yet other embodiments, communication interface 406 includes one or more ports or terminals 416, radio front-end circuitry 418, and RF transceiver circuitry 412 as part of a radio unit (not shown) and communication interface 406 communicates with baseband processing circuitry 414, which is part of a digital unit (not shown).

[0124] Antenna 410 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 410 can be coupled to radio front-end circuitry 418 and can be any type of antenna and / or antenna array capable of inducting and / or radiating wireless communications (e.g., radio frequency, microwave, etc.). In certain embodiments, antenna 410 can be separate from network node 400 and can be connectable to network node 400 by an interface or port.

[0125] Antenna 410, communication interface 406, and / or processing circuitry 402 can be configured to perform any of the receiving operations and / or certain obtaining operations described herein as being performed by a network node 400. Any information, data and / or signals can be received from a UE, another network node and / or any other network equipment. Similarly, antenna 410, communication interface 406, and / or processing circuitry 402 can be configured to perform any of the transmitting operations described herein as being performed by a network node 400. Any information, data and / or signals can be transmitted to a UE, another network node and / or any other network equipment.

[0126] Power source 408 provides power to various components of network node 400 in a form suitable for the respective components, e.g., at a voltage and current level needed for each respective component. Power source 408 can also include, or be coupled to, power management circuitry to regulate power supplied to the components of network node 400 for performing the functions described herein. For example, network node 400 can be connectable to an external power source (e.g., an electricity outlet) via an interface or input circuitry such as an electrical cable, whereby the external power source supplies power to the power circuitry of power source 408. As a further example, power source 408 can comprise one or more power sources, such as batteries or battery packs. The batteries can supply backup power to power source 408 when the external power source fails.

[0127] Embodiments of network node 400 can include Figure 4Additional components beyond those shown in FIG. 5 can be included in the network node 400 as is readily appreciated by one of ordinary skill in the art. Such components are not shown in FIG. 5 as art-recognized components such as power supplies, cooling fans, and the like are not described in further detail herein so as to not unnecessarily obscure the principles of the various aspects described herein. For example, the network node 400 can include user interface equipment to allow input of information into the network node 400 and to allow output of information from the network node 400. This can allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 400.

[0128] Figure 5 is a block diagram of a host 500 that can be an embodiment of the host 216 in accordance with various aspects described herein. As used herein, the host 500 can be or include various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a processing resource in a server farm. The host 500 can provide one or more services to one or more UEs. Figure 2

[0129] The host 500 includes a processing circuit 502 that is operatively coupled, via a bus 504, to an input / output interface 506, a network interface 508, a power source 510, and a memory 512. Other components can be included in other embodiments. Features of these components can be substantially similar to those described with respect to the devices of the previous figures, such as the UE 102 and the base station 104, so that their description generally applies to the corresponding components of the host 500. Figure 3 and Figure 4

[0130] ​​Memory 512 can include one or more computer programs, including one or more host applications 514 and data 516, which can include user data, such as data generated by a UE for host 500 or data generated by host 500 for a UE. Embodiments of host 500 can utilize only a subset of the illustrated components or all of them. Host applications 514 can be implemented in a container-based architecture and can provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Motion Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, and g.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., cellphones, desktop computers, wearable display systems, and heads-up display systems). Host applications 514 can also provide user authentication and permission checks, and can periodically report health, routing, and content availability to a central node, such as a device in a core network or on an edge. Thus, host 500 can select and / or indicate different hosts for over-the-top (OTT) services for UEs. Host applications 514 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real Time Messaging Protocol (RTMP), Real Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), and the like.

[0131] Figure 6 FIG. 6 is a block diagram illustrating a virtualization environment 600 in which functions implemented by some embodiments can be virtualized. In this context, virtualization means the creation of virtual versions of devices or appliances, which can include virtualization of hardware platforms, storage devices, and networking resources. As used herein, virtualization can apply to any device or component thereof described herein and involves an implementation in which at least a portion of the functionality is implemented as a virtual component executed by one or more virtual machines (VMs). Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtualization environments 600 hosted by one or more hardware nodes, which are hardware computing devices such as hardware computing devices that operate as network nodes, UEs, core network nodes, or hosts. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., core network nodes or hosts), then the node can be entirely virtualized. In some embodiments, virtualization environment 600 includes components defined by the O-RAN Alliance, such as an O-CLOUD environment orchestrated by a service management and orchestration framework via an O-2 interface.

[0132] The application 602, which can alternatively be referred to as a software instance, virtual appliance, network function, virtual node, virtual network function, etc., is run in the virtualization environment 600 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0133] The hardware 604 comprises processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware apparatus, such as a network interface, input / output interface, etc., as described herein. The software can be executable by the processing circuitry to instantiate one or more virtualization layers 606 (also referred to as a hypervisor or VM monitor (VMM)), provide VMs 608A and 608B (one or more of which can be referred to collectively as VMs 608), and / or perform any of the functions, features, and / or benefits described with regard to some of the embodiments described herein. The virtualization layer 606 can present a virtual operating platform that appears like networking hardware to the VMs 608.

[0134] The VMs 608 comprise virtual processing, memory, networking or interface, and storage, and can be run by a corresponding virtualization layer 606. Different embodiments of the instance of the virtual appliance 602 can be implemented in one or more of the VMs 608, and the implementation can be made in different ways. Virtualization of the hardware is sometimes referred to as Network Function Virtualization (NFV). NFV can 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.

[0135] In the context of NFV, the VMs 608 can be software implementations of physical machines that run programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 608, and that portion of the hardware 604 that executes that VM, whether it be hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs 608, forms a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that are run in one or more of the VMs 608 on top of hardware 604 and corresponds to an application 602.

[0136] Hardware 604 can be implemented in a standalone network node with general-purpose or special-purpose components. Hardware 604 can implement some functions via virtualization. Alternatively, hardware 604 can be part of a larger hardware cluster (e.g., in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration 610, which oversees the lifecycle management of application 602 among other operations. In some embodiments, hardware 604 is coupled to one or more radio units, each containing one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more suitable network interfaces and can be used in conjunction with virtual components to provide a radio-capable virtual node, such as a RAN or base station. In some embodiments, some signaling can be provided using control system 612, which can alternatively be used for communication between hardware nodes and radio units.

[0137] Figure 7 A communication diagram is shown illustrating communication between host 702 and UE 706 via network node 704 through a partial wireless connection, according to some embodiments. Reference will now be made to... Figure 7 Describe the UEs discussed in the preceding paragraphs (such as...) Figure 2 UE 212A and / or Figure 3 UE 300), network nodes (such as Figure 2 Network node 210A and / or Figure 4 Network node 400) and host (such as Figure 2 Host 216 and / or Figure 5 Example implementations of the host 500 according to various embodiments.

[0138] Similar to host 500, embodiments of host 702 include hardware such as a communication interface, processing circuitry, and memory. Host 702 also includes software stored in or accessible by host 702 and executable by the processing circuitry. This software includes a host application operable to provide services to remote users, such as UE 706 connected via an OTT connection 750 extended between UE 706 and host 702. When providing services to remote users, the host application can provide user data transmitted using the OTT connection 750.

[0139] Network node 704 contains hardware that enables it to communicate with host 702 and UE 706. Connection 760 can be direct or via a core network (like...). Figure 2 The core network (206) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a backbone network or the Internet.

[0140] The UE 706 includes hardware and software, which are stored in or accessible to the UE 706 and executable by UE processing circuitry. The software includes a client application, such as a web browser or a proprietary "app" that can be operative to provide a service to a human or non-human user via the UE 706 with support from the host computer 702. In the host computer 702, an executing host application can communicate with the executing client application via the OTT connection 750 terminating at the UE 706 and the host computer 702. In providing the service to the user, the client application of the UE can receive request data from the host application of the host computer, and provide user data in response to the request data. The OTT connection 750 can transfer the request data and the user data. The client application of the UE can generate the user data by interacting with the user, e.g., by presenting user interface screens to the user via the display of the UE, and receiving user inputs via the input device of the UE.

[0141] The OTT connection 750 can be extended over connections 760 between the host computer 702 and the network node 704, and wireless connections 770 between the network node 704 and the UE 706, to provide the connection between the host computer 702 and the UE 706. The connections 760 and the wireless connections 770 over which the OTT connection 750 can be extended can be implemented as electrical, optical, RF, and / or other connections. Moreover, these connections can be established via a variety of different

[0142] As an example of transferring data via the OTT connection 750, in step 708, the host computer 702 provides user data, which can be performed by executing the host application. In some embodiments, the user data is associated with a specific human user interacting with the UE 706. In other embodiments, the user data is associated with the UE 706, such as when the UE 706 is sharing data with the host computer 702 without explicit human interaction. In step 710, the host computer 702 initiates a transmission carrying the user data towards the UE 706. The host computer 702 can initiate the transmission in response to a request transmitted by the UE 706. The request can be caused by a human interaction with the UE 706, or by the operation of client application software stored on the UE 706. In accordance with the teachings of embodiments described throughout this disclosure, the transmission can be relayed via the network node 704. Accordingly, in step 712, the network node 704 transmits to the UE 706 the user data which was carried in the transmission initiated by the host computer 702, in accordance with the teachings of embodiments described throughout this disclosure. In step 714, the UE 706 receives the user data carried in the transmission, which can be performed by the client application executing on the UE 706 in association with the host application executing on the host computer 702.

[0143] In some examples, the UE 706 executes a client application providing user data to the host 702. The user data can be provided as a reaction to or response from data received from the host 702. Thus, in step 716, the UE 706 can provide user data, which can be performed by executing the client application. In providing the user data, the client application can also take into account user input received from a user via an input / output interface of the UE 706. Regardless of the specific manner in which the user data is provided, in step 718, the UE 706 initiates a transfer of the user data towards the host 702 via the network node 704. In step 720, the network node 704 receives the user data from the UE 706 and initiates a transfer of the received user data towards the host 702, in accordance with the teachings of the embodiments described throughout this disclosure. In step 722, the host 702 receives the user data carried in the transfer initiated by the UE 706.

[0144] One or more of the various embodiments use the OTT connection 750 to improve the performance of OTT services provided to the UE 706, in which the wireless connection 770 forms the last segment.

[0145] In an example scenario, factory condition information can be collected and analyzed by the host 702. As another example, the host 702 can process audio and video data that has been acquired from UEs for creating a map. As another example, the host 702 can collect and analyze real-time data to help control traffic congestion (e.g., control traffic lights). As another example, the host 702 can store surveillance videos uploaded by UEs. As another example, the host 702 can store or control access to media content, such as videos, audio, VR, or AR, that it can broadcast, multicast, or unicast to UEs. As other examples, the host 702 can be used for energy pricing, remote control of non-time critical electric loads to balance power generation needs, location services, presence services (such as compiled maps according to data collected from remote devices, etc.), or any other functionality that collects, retrieves, stores, analyzes, and / or transfers data.

[0146] In some embodiments, a measurement procedure can be provided for the purpose of monitoring data rate, latency, and other factors for which the one or more embodiments improve. There can also be an optional network functionality to reconfigure OTT connection 750 between host 702 and UE 706, in response to measurements results. The measurement procedure and / or the network functionality to reconfigure OTT connection 750 can be implemented in software and hardware of host 702 and / or in software and hardware of UE 706. In some embodiments, sensors (not shown) can be deployed in or in association with other devices through which OTT connection 750 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software can compute or estimate the monitored quantities. The reconfiguring of OTT connection 750 can include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly change the settings of network nodes 704, but can e.g. involve setting parameters of UE 706 in a way that it will adjust its settings in turn. Such procedures and functionalities can be known and practiced in the art. In certain embodiments, measurements can involve dedicated UE signaling facilitating host 702 to measure throughput, propagation times, latency, and the like. The measurements can be implemented e.g. because software causes messages (specifically empty or "dummy" messages) to be transmitted while monitoring propagation times, errors, etc.

[0147] Although the computing devices described herein (e.g., UEs, network nodes, hosts) can include combinations of the hardware components shown, other examples can include computing devices with different combinations of components. It will be appreciated that these computing devices can include any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods disclosed herein. Determinations, calculations, obtaining, or similar operations described herein can be performed by processing circuitry, which can process information by, for example, transforming the obtained information, comparing the obtained information or transformed information to information stored in the network node, and / or performing one or more operations based on the obtained information or transformed information, and as a result of said processing make a determination. Moreover, while components are depicted as individual blocks or within individual blocks, in practice, the computing devices can include multiple different physical components constituting a single illustrated component, and functionality can be partitioned between components in a manner not exactly as depicted. For example, communication interfaces can be configured to include any of the components described herein, and / or functionality of components can be partitioned between the processing circuitry and the communication interfaces. In another example, non-computationally intensive functionality of any of the components can be implemented in software or firmware and computationally intensive functionality can be implemented in hardware.

[0148] In certain embodiments, some or all of the functionality described herein can be provided by a processing circuit executing instructions stored in a memory, which in certain embodiments can be a computer program product in the form of a non-transitory computer readable storage medium. In alternative embodiments, some or all of the functionality can be provided by a processing circuit without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In either of those particular embodiments, whether executing instructions stored on a non-transitory computer readable storage medium or not, the processing circuit can be configured to perform the described functionality. The benefits provided by such functionality are not limited to a processing circuit or to other components of a computing device alone, but are enjoyed by computing devices as a whole and / or by end users and wireless networks generally.

[0149] Some example embodiments of the present disclosure are as follows: Group A embodiments Embodiment 1 : A method performed by a user equipment, UE (100), the method comprising one or more of: • receiving (106) a quality of experience, QoE, measurement configuration from a first network node (102), the QoE measurement configuration comprising one or more Public Land Mobile Network, PLMN, lists indicating one or more equivalent PLMNs; • starting (108) an application session subject to the QoE measurement configuration; • starting (108) QoE measurements according to the QoE measurement configuration; • transitioning (110) from a connected state to an idle state; • in a process of transitioning (112) from the idle state to the connected state with respect to a second network node (104), o obtaining (112A) a PLMN identifier, ID, of the second network node (104); o determining (112B), based on a comparison of the PLMN ID of the second network node (104) and PLMN IDs included in the one or more PLMN lists, whether the UE is to send any one or more of: ■ a QoE report; ■ a QoE report availability indication; ■ a network instance of the QoE measurement configuration stored by the UE; ■ an indication of availability of the network instance of the QoE measurement configuration stored by the UE; and • operating (112C) according to a result of the determination (112B).

[0150] Embodiment 2: The method according to embodiment 1, wherein the one or more equivalent PLMNs are one or more PLMNs in which the UE is to perform QoE measurements according to the QoE measurement configuration and / or one or more PLMNs of a stored network instance of the QoE measurement configuration to which the UE is allowed to send QoE reports.

[0151] Embodiment 3: The method according to embodiment 1 or 2, wherein: • determining (112B) comprises determining, based on the comparison of the PLMN ID of the second network node (104) and the PLMN ID included in the one or more PLMN lists, that the PLMN of the second network node (104) is an equivalent PLMN; and • operating (112C) according to the result of the determination comprises sending (112C) to the second network node (104) any one or more of: o a QoE report of QoE measurements performed according to the QoE measurement configuration; o a QoE report availability indication of a QoE report of QoE measurements performed according to the QoE measurement configuration; o the network instance of the QoE measurement configuration stored by the UE; o an indication of availability of the network instance of the QoE measurement configuration stored by the UE.

[0152] Embodiment 4: The method according to embodiment 1 or 2, wherein determining (112B) comprises determining, based on the comparison of the PLMN ID of the second network node (104) and the PLMN ID included in the one or more PLMN lists, that the PLMN of the second network node (104) is a PLMN in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration; and operating (112C) according to the result of the determination comprises sending (112C) to the second network node (104) the network instance of the QoE measurement configuration stored by the UE or an indication of availability of the network instance of the QoE measurement stored by the UE.

[0153] Embodiment 5: The method of embodiment 1 or 2, wherein: determining (112B) comprises determining, based on the comparison of the PLMN ID of the second network node (104) and the PLMN IDs included in the one or more PLMN lists, that the PLMN of the second network node (104) is a PLMN in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration but not a PLMN to which the UE is allowed to send QoE reports of QoE measurements performed according to the QoE measurement configuration; and operating (112C) in accordance with the result of the determination comprises performing QoE measurements according to the QoE measurement configuration while in the connected state with respect to the second network node (104) but refraining from sending a QoE report availability indication to the second network node (104).

[0154] Embodiment 6: The method of embodiment 1 or 2, wherein: determining (112B) comprises determining, based on the comparison of the PLMN ID of the second network node (104) and the PLMN IDs included in the one or more PLMN lists, that the PLMN of the second network node (104) is a PLMN in which the UE is not allowed to perform QoE measurements according to the QoE measurement configuration; and operating (112C) in accordance with the result of the determination comprises ceasing to perform QoE measurements according to the QoE measurement configuration.

[0155] Embodiment 7: The method of embodiments 1-6, wherein the one or more PLMN lists comprise a single list of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration and to send associated QoE reports.

[0156] Embodiment 8: The method of embodiments 1-6, wherein the one or more PLMN lists comprise a first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration and a second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports.

[0157] Embodiment 9: The method of embodiments 1-6, wherein the one or more PLMN lists comprise a first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration and a second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports and stored network instances of the QoE measurement configuration.

[0158] Embodiment 10: The method as in embodiments 1-6, wherein the one or more PLMN lists comprises a first PLMN list, a second PLMN list, and a third PLMN list, the first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports, and the third PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send stored network instances of the QoE measurement configuration.

[0159] Embodiment 11: The method as in embodiments 1-6, wherein the one or more PLMN lists comprises a first PLMN list and a second PLMN list, the first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to send associated QoE reports, and the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send stored network instances of the QoE measurement configuration.

[0160] Embodiment 12: The method as in embodiments 1-6, wherein the one or more PLMN lists comprises a PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to send associated QoE reports.

[0161] Embodiment 13: The method as in embodiments 1-6, wherein the one or more PLMN lists comprises a PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to send only associated QoE reports.

[0162] Embodiment 14: The method as in embodiments 1-6, wherein the one or more PLMN lists comprises a PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration but is not allowed to send associated QoE reports.

[0163] Embodiment 15: The method as in embodiments 1-6, wherein the one or more PLMN lists comprises a PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send stored network instances of the QoE measurement configuration.

[0164] Embodiment 16: The method as in embodiments 1-6, wherein the one or more PLMN lists comprises a PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send only stored network instances of the QoE measurement configuration.

[0165] Embodiment 17: The method of any of the preceding embodiments, further comprising: providing user data; and forwarding the user data to a host via a transfer to a network node.

[0166] Group B embodiments Embodiment 18: A method performed by a first network node (102), the method comprising any one or more of: sending (106) a quality of experience, QoE, measurement configuration to a user equipment, UE (100), the QoE measurement configuration comprising one or more Public Land Mobile Network, PLMN, lists indicating one or more equivalent PLMNs; causing (110) the UE to transition from a connected state to an idle state.

[0167] Embodiment 19: The method of embodiment 18, wherein the one or more equivalent PLMNs are one or more PLMNs in which the UE is to perform QoE measurements according to the QoE measurement configuration; and / or one or more PLMNs to which the UE is allowed to send QoE reports and / or stored network instances of the QoE measurement configuration.

[0168] Embodiment 20: The method of any of the preceding embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0169] Group C embodiments Embodiment 21: A user equipment 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 processing circuitry.

[0170] Embodiment 22: A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0171] Embodiment 23: A user equipment (UE) comprising: an antenna configured to transmit and receive wireless signals; a radio front-end circuit connected to the antenna and to processing circuitry and configured to condition signals passed between the antenna and the processing circuitry; the processing circuitry 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 that is 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.

[0172] Embodiment 24: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0173] Embodiment 25: The host of any preceding embodiment, wherein the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0174] Embodiment 26: A method implemented in a host configured to operate in a communication system that also includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating transmission of the user data to the UE via a cellular network that includes the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0175] Embodiment 27: The method of any preceding embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0176] Embodiment 28: The method of any of the preceding 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executed on the UE, the client application being associated with the host application.

[0177] Embodiment 29: A communication system configured to provide an over-the-top (OTT) service, the communication system comprising a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0178] Embodiment 30: The communication system of any preceding embodiment, further comprising: the network node; and / or the UE.

[0179] Embodiment 31 : A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate reception of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.

[0180] Embodiment 32: The host of the preceding 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executed on the UE, the client application associated with the host application.

[0181] Embodiment 33: The host of any of the preceding 2 embodiments, wherein the initiated reception of the user data comprises requesting the user data.

[0182] Embodiment 34: A method implemented by a host configured to operate in a communication system that also includes a network node and a user equipment (UE), the method comprising: at the host, initiating reception of user data from the UE, the user data originating from a transmission, the network node having received the transmission from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.

[0183] Embodiment 35: The method of the preceding embodiment, further comprising, at the network node, transmitting the received user data to the host.

[0184] Embodiment 36: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host.

[0185] Embodiment 37: The host of the preceding embodiment, wherein the cellular network also includes a network node configured to communicate with the UE to transmit the user data from the host to the UE.

[0186] Embodiment 38: The host of any of the preceding 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, whereby the user data is provided; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0187] Embodiment 39: A method implemented by a host operating in a communication system that also includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network that includes the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

[0188] Embodiment 40: The method of any of the preceding embodiments, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.

[0189] Embodiment 41 : The method of any of the preceding embodiments, further comprising: at the host, transmitting input data to the client executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0190] Embodiment 42: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate a transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0191] Embodiment 43: The host of any of the preceding embodiments, wherein the cellular network also includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0192] Embodiment 44: The host of any of the preceding 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, whereby the user data is provided; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0193] Example 45: A method implemented by a host configured to operate in a communication system that also includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted by the UE to the host via the network node, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0194] Example 46: The method of the preceding 1 embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0195] Example 47: The method of the preceding 2 embodiments, further comprising: at the host, transmitting input data to the client executing on the UE, the input data provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0196] Those skilled in the art will recognize modifications and improvements to the embodiments of the present disclosure. All such modifications and improvements are considered within the scope of the concepts disclosed herein.

Claims

1. A method performed by a user equipment, UE (100), the method comprising: receiving (106), from a first network node (102), a quality of experience, QoE, measurement configuration, the QoE measurement configuration comprising one or more public land mobile network, PLMN, lists indicating one or more allowed PLMNs; starting (108) an application session subject to the QoE measurement configuration; starting (108) QoE measurements according to the QoE measurement configuration; transitioning (110) from a connected state to an idle state; in a process of transitioning (112) from the idle state to the connected state with respect to a second network node (104), obtaining (112A) a PLMN identifier, ID, of the second network node (104); based on a comparison of the PLMN ID of the second network node (104) and PLMN IDs included in the one or more PLMN lists, determining (112B) whether the UE is to send any one or more of the following to the second network node (104): a QoE report; a QoE report availability indication; a network instance of the QoE measurement configuration stored by the UE; an indication of availability of the network instance of the QoE measurement configuration stored by the UE; and operating (112C) in accordance with a result of the determining (112B). the one or more PLMN lists consist of PLMN lists in a regional scope of the QoE measurement configuration.

2. The method of claim 1, wherein, the PLMN ID of the second network node (104) is not in the PLMN lists, and the determining (112B) comprises determining (112B), based on the PLMN ID of the second network node (104) not being in the PLMN lists, that the UE (100) is not to send a QoE report availability indication to the second network node (104).

3. The method of claim 2, wherein, the PLMN ID of the second network node (104) is in the PLMN lists, such that the UE (100), and the determining (112B) comprises determining (112B), based on the PLMN ID of the second network node (104) being in the PLMN lists, that the UE (100) is to send a QoE report availability indication to the second network node (104).

4. The method of claim 2, wherein, the PLMN ID of the second network node (104) is in the PLMN lists, such that the UE (100), and the determining (112B) comprises determining (112B), based on the PLMN ID of the second network node (104) being in the PLMN lists, that the UE (100) is to send a QoE report to the second network node (104).

5. The method of claim 2, wherein, the first network node (102) is in a first PLMN, and the second network node (104) is in a second PLMN different from the first PLMN.

6. The method of claim 2, wherein, ​ 7. The method of claim 6, wherein, the PLMN ID of the second network node (104) is not in the PLMN list, such that the UE (100) and the determining (112B) comprises determining (112B) that the UE (100) will not send QoE reports to the second network node (104).

8. The method of claim 6, wherein, the PLMN ID of the second network node (104) is in the PLMN list, and the determining (112B) comprises determining (112B) that the UE (100) will send a QoE report availability indication to the second network node (104) based on the PLMN ID of the second network node (104) being in the PLMN list.

9. The method of claim 6, wherein, the PLMN ID of the second network node (104) is in the PLMN list, and the determining (112B) comprises determining (112B) that the UE (100) will send a QoE report availability indication to the second network node (104) based on the PLMN ID of the second network node (104) not being in the PLMN list.

10. The method of claim 1, wherein: the determining (112B) comprises determining that the PLMN of the second network node (104) is an allowed PLMN based on the comparison of the PLMN ID of the second network node (104) and the PLMN IDs included in the one or more PLMN lists; and the operating (112C) in accordance with the result of the determining comprises sending (112C) to the second network node (104) any one or more of: a QoE report of QoE measurements performed in accordance with the QoE measurement configuration; a QoE report availability indication of a QoE report of QoE measurements performed in accordance with the QoE measurement configuration; the network instance of the QoE measurement configuration stored by the UE; an indication of availability of the network instance of the QoE measurement configuration stored by the UE.

11. The method of claim 1, wherein: the determining (112B) comprises determining that the PLMN of the second network node (104) is a PLMN in which the UE is allowed to perform QoE measurements in accordance with the QoE measurement configuration based on the comparison of the PLMN ID of the second network node (104) and the PLMN IDs included in the one or more PLMN lists; and the operating (112C) in accordance with the result of the determining comprises sending (112C) to the second network node (104) the network instance of the QoE measurement configuration stored by the UE or an indication of availability of the network instance of the QoE measurement stored by the UE.

12. The method of claim 1, wherein: determining (112B) comprises determining, based on the comparison of the PLMN ID of the second network node (104) and the PLMN IDs included in the one or more PLMN lists, that the PLMN of the second network node (104) is a PLMN in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, but not a PLMN to which the UE is allowed to send QoE reports of QoE measurements performed according to the QoE measurement configuration; and operating (112C) in dependence on the result of the determining comprises performing QoE measurements according to the QoE measurement configuration while in the connected state with respect to the second network node (104), but refraining from sending a QoE report availability indication to the second network node (104).

13. The method of claim 1, wherein: determining (112B) comprises determining, based on the comparison of the PLMN ID of the second network node (104) and the PLMN IDs included in the one or more PLMN lists, that the PLMN of the second network node (104) is a PLMN in which the UE is not allowed to perform QoE measurements according to the QoE measurement configuration; and operating (112C) in dependence on the result of the determining comprises stopping performing QoE measurements according to the QoE measurement configuration.

14. The method of any one of claims 10 to 13, wherein, The one or more allowed PLMNs are: one or more PLMNs in which the UE is to perform QoE measurements according to the QoE measurement configuration; and / or one or more PLMNs to which the UE is allowed to send QoE reports and / or stored network instances of the QoE measurement configuration.

15. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a single list of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration and to which the UE is allowed to send associated QoE reports.

16. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a first PLMN list and a second PLMN list, the first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports.

17. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a first PLMN list and a second PLMN list, the first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports and stored network instances of the QoE measurement configuration.

18. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a first PLMN list, a second PLMN list and a third PLMN list, the first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports, the third PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send stored network instances of the QoE measurement configuration.

19. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a first PLMN list and a second PLMN list, the first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to send associated QoE reports, the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send stored network instances of the QoE measurement configuration.

20. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to send associated QoE reports.

21. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to send only associated QoE reports.

22. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration but not allowed to send associated QoE reports.

23. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send stored network instances of the QoE measurement configuration.

24. The method of any one of claims 1 and 10-13, wherein, The one or more PLMN lists comprise a PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send only stored network instances of the QoE measurement configuration.

25. The method of any one of claims 1 to 24, wherein, The QoE measurement configuration is a configuration to collect and report QoE measurements in a encapsulated format or a Radio Access Network, RAN, visible QoE, RVQoE, measurement configuration.

26. A user equipment, UE (100), adapted to: receive (106) a quality of experience, QoE, measurement configuration from a first network node (102), the QoE measurement configuration comprising one or more Public Land Mobile Network, PLMN, lists indicating one or more allowed PLMNs; start (108) an application session subject to the QoE measurement configuration; start (108) QoE measurements according to the QoE measurement configuration; transition (110) from a connected state to an idle state; in a transition (112) from the idle state to the connected state with respect to a second network node (104), obtain (112A) a PLMN identifier, ID, of the second network node (104); based on a comparison of the PLMN ID of the second network node (104) and the PLMN IDs included in the one or more PLMN lists, determine (112B) whether the UE will send any one or more of the following to the second network node (104): a QoE report; a QoE report availability indication; a network instance of the QoE measurement configuration stored by the UE; an indication of availability of the network instance of the QoE measurement configuration stored by the UE; and operate (112C) in accordance with a result of the determining (112B).

27. The UE (100) of claim 26, further adapted to perform the method of any one of claims 2 to 25.

28. A user equipment, UE (100; 300), comprising: a communication interface (312) comprising a transmitter (318) and a receiver (320); and a processing circuitry (302) associated with the communication interface (312), the processing circuitry (302) being configured to cause the UE (100; 300) to: receive (106), from a first network node (102), a quality of experience, QoE, measurement configuration, the QoE measurement configuration comprising one or more PLMN lists indicating one or more allowed public land mobile networks, PLMNs; start (108) an application session subject to the QoE measurement configuration; start (108) QoE measurements in accordance with the QoE measurement configuration; transition (110) from a connected state to an idle state; in a process of transitioning (112) from the idle state to the connected state with respect to a second network node (104), obtain (112A) a PLMN identifier, ID, of the second network node (104); based on a comparison of the PLMN ID of the second network node (104) and the PLMN IDs included in the one or more PLMN lists, determine (112B) whether the UE will send any one or more of the following to the second network node (104): a QoE report; a QoE report availability indication; a network instance of the QoE measurement configuration stored by the UE; an indication of availability of the network instance of the QoE measurement configuration stored by the UE; and operate (112C) in accordance with a result of the determining (112B). the one or more PLMN lists consist of PLMN lists in a regional scope of the QoE measurement configuration. the PLMN ID of the second network node (104) is not in the PLMN lists, and the determining (112B) comprises determining (112B), based on the PLMN ID of the second network node (104) not being in the PLMN lists, that the UE (100) will not send a QoE report availability indication to the second network node (104).

29. The UE of claim 28, wherein, ​ 30. The UE of claim 29, wherein, ​ 31. The UE of claim 29, wherein, The PLMN ID of the second network node (104) is in the PLMN list, causing the UE (100), and the determining (112B) comprises determining (112B) that the UE (100) will send a QoE report availability indication to the second network node (104) based on the PLMN ID of the second network node (104) being in the PLMN list.

32. The UE of claim 29, wherein, The PLMN ID of the second network node (104) is in the PLMN list, causing the UE (100), and the determining (112B) comprises determining (112B) that the UE (100) will send a QoE report to the second network node (104) based on the PLMN ID of the second network node (104) being in the PLMN list.

33. The UE of claim 29, wherein, The first network node (102) is in a first PLMN, and the second network node (104) is in a second PLMN different from the first PLMN.

34. The UE of claim 33, wherein, The PLMN ID of the second network node (104) is not in the PLMN list, causing the UE (100), and the determining (112B) comprises determining (112B) that the UE (100) will not send a QoE report to the second network node (104).

35. The UE of claim 33, wherein, The PLMN ID of the second network node (104) is in the PLMN list, and the determining (112B) comprises determining (112B) that the UE (100) will send a QoE report availability indication to the second network node (104) based on the PLMN ID of the second network node (104) being in the PLMN list.

36. The UE of claim 33, wherein, The PLMN ID of the second network node (104) is in the PLMN list, and the determining (112B) comprises determining (112B) that the UE (100) will send a QoE report to the second network node (104) based on the PLMN ID of the second network node (104) not being in the PLMN list.

37. The UE of any one of claims 28-36, wherein, The QoE measurement configuration is a configuration to collect and report QoE measurements in a packed format, or a Radio Access Network, RAN, visible QoE, RVQoE, measurement configuration.

38. A method performed by a first network node (102), the method comprising: sending (106) a Quality of Experience, QoE, measurement configuration to a User Equipment, UE, (100), the QoE measurement configuration comprising one or more Public Land Mobile Network, PLMN, lists indicating one or more allowed PLMNs; and causing (110) the UE (100) to transition from a connected state to an idle state.

39. The method of claim 38, wherein, The one or more allowed PLMNs are: one or more PLMNs in which the UE is to perform QoE measurements according to the QoE measurement configuration; and / or one or more PLMNs to which the UE is allowed to send QoE reports and / or stored network instances of the QoE measurement configuration.

40. The method of claim 38, wherein, The one or more PLMN lists consist of a list of PLMNs in a region scope of the QoE measurement configuration.

41. The method of claim 38, wherein, The one or more PLMN lists comprise a single list of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration and is allowed to send associated QoE reports.

42. The method of claim 38, wherein, The one or more PLMN lists comprise a first PLMN list and a second PLMN list, the first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports.

43. The method of claim 38, wherein, The one or more PLMN lists comprise a first PLMN list and a second PLMN list, the first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports and stored network instances of the QoE measurement configuration.

44. The method of claim 38, wherein, The one or more PLMN lists comprise a first PLMN list, a second PLMN list and a third PLMN list, the first PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration, the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports, the third PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send stored network instances of the QoE measurement configuration.

45. The method of claim 38, wherein, The one or more PLMN lists comprise a first PLMN list and a second PLMN list, the first PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports, the second PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send stored network instances of the QoE measurement configuration.

46. The method of claim 38, wherein, The one or more PLMN lists comprise a PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send associated QoE reports.

47. The method of claim 38, wherein, The one or more PLMN lists comprise a PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send only associated QoE reports.

48. The method of claim 38, wherein, The one or more PLMN lists comprise a PLMN list containing PLMN IDs of PLMNs in which the UE is allowed to perform QoE measurements according to the QoE measurement configuration but the UE is not allowed to send associated QoE reports.

49. The method of claim 38, wherein, The one or more PLMN lists comprise a PLMN list containing PLMN IDs of PLMNs to which the UE is allowed to send stored network instances of the QoE measurement configuration.

50. The method of claim 38, wherein, The one or more PLMN lists comprise a PLMN list comprising PLMN IDs of PLMNs in which a stored network instance is allowed in which the UE is allowed to send only the QoE measurement configuration.

51. The method of any one of claims 38 to 50, wherein, The QoE measurement configuration is a configuration to collect and report QoE measurements in a packed format or a Radio Access Network, RAN Visible QoE, RVQoE measurement configuration.

52. A first network node (102), adapted to: send (106) a Quality of Experience, QoE, measurement configuration to a User Equipment, UE (100), the QoE measurement configuration comprising one or more Public Land Mobile Network, PLMN, lists indicating one or more allowed PLMNs; and cause (110) the UE (100) to transition from a connected state to an idle state.

53. The first network node (102) of claim 52, further adapted to perform the method of any one of claims 39 to 51.

54. A first network node (102; 400), comprising: processing circuitry (402) configured to cause the first network node (102; 400) to: send (106) a Quality of Experience, QoE, measurement configuration to a User Equipment, UE (100), the QoE measurement configuration comprising one or more Public Land Mobile Network, PLMN, lists indicating one or more allowed PLMNs; and cause (110) the UE (100) to transition from a connected state to an idle state.

Images