Improved procedure for quality of experience measurement reporting and quality of experience configurations retrieval

Abstract

A communication device can generate (2250) a message The message can include an indication of all configuration information that was known by a network node that was serving the communication device when the communication device transitioned to an idle state. The communication device can further transmit (2260) the message to the network node.

Description

IMPROVED PROCEDURE FOR QUALITY OF EXPERIENCE MEASUREMENT REPORTING AND QUALITY OF EXPERIENCE CONFIGURATIONS RETRIEVALTECHNICAL FIELD

[0001] The present disclosure is related to communication systems, entities, network node, and host for an improved procedure for quality of experience measurement reporting and quality of experience configurations retrieval.BACKGROUND

[0002] The present disclosure is related to communication systems, entities, network node, and host for an improved procedure for quality of experience measurement reporting and quality of experience configurations retrieval.

[0003] FIG. 1 illustrates an example of a new radio (“NR”) network (e.g., a 5th Generation (“5G”) network) including a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base station (“gNB”)), multiple communication devices 110 (also referred to as user equipment (“UE”)).

[0004] Multicast and Broadcast Services (“MBS”) are point-to-multipoint service in which services and data are transmitted from a single source entity to multiple recipients, either to all UEs in a Broadcast service area, or to users in a multicast group.

[0005] A 5G NR system enables delivery of MBS in a resource-efficient way. Via the MBS, the same service and the same specific content data from a single source can be provided simultaneously to all UEs in a geographical area (in the broadcast communication service) or to a dedicated set of UEs (in the multicast communication service). That is, all UEs in a broadcast area can receive the data, while not all UEs are authorized to receive the data in a multicast area.

[0006] A UE can receive a broadcast MBS communication service independently of its radio resource control (“RRC”) state, while a multicast MBS service can be received only by the UEs in the RRC CONNECTED state. Multicast communication data can be delivered to a UE via Point-to-Point (“PTP”) and / or Point-To-Multipoint (“PTM”) mechanisms, and hybrid automatic repeat request (“HARQ”) retransmission / feedback can be applied to both of these mechanisms.SUMMARY

[0007] Various embodiments herein describe ensuring that a radio access network (“RAN”) can always be aware of whether all the user equipment (“UE”) stored “network instance of quality of experience (“QoE”) configurations” and / or session start / stop indication and / or QoEmeasurement reports are received when a UE transitions to RRC CONNECTED from RRC IDLE and to decrease or eliminate the risk of UE discarding the QoE measurement reports due to RRC message size restriction.

[0008] According to some embodiments, a method of operating a communication device is provided. The method includes generating a message to include an indication of all configuration information that was known by a network node that was serving the communication device when the communication device transitioned to an idle state. The method further including transmitting the message to the network node.

[0009] According to other embodiments, a method of operating a network node is provided. The method includes, responsive to determining that a communication device has transitioned from a connected state to an idle state, releasing configuration information associated with the communication device. The method further including subsequent to releasing the configuration information, receiving a message from the communication device including an indication of the configuration information.

[0010] According to other embodiments, a communication device, a network node, a computer program, a computer program product, a host, a system, or a non-transitory computer- readable medium is provided to perform one of the above methods.

[0011] Certain aspects of these embodiments may provide technical advantages. In some embodiments, aligned understanding of UE stored QoE configurations are reached between gNB and UE. In other words, the gNB that serves the UE upon transition from RRC IDLE to RRC CONNECTED is aware of all the QoE configurations that the UE stored while in RRC IDLE mode. Consequently, uncertainties of the UE behavior and potentially varying behavior between UEs from different vendors are eliminated. The risk of collision between identities used for QoE / RVQoE configuration already sent / applied by a UE, and identities the network determines for QoE / RVQoE configuration to be sent to the UE (e.g., collisions in the measConfigAppLayerld) can be eliminated. Moreover, the probability of the UE discarding the QoE measurement reports due to RRC message size restriction can be decreased.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0013] FIG. 1 is a schematic diagram illustrating an example of a 5thgeneration (“5G”) network;

[0014] FIG. 2 is a block diagram illustrating an example of a MBS delivery procedure;

[0015] FIG. 3 is a signal flow diagram illustrating an example of signaling involved in configuration and reporting of QoE measurements;

[0016] FIG. 4 is a diagram illustrating an example of an ASN. 1 definition of an AppLayerMeasConfig IE;

[0017] FIG. 5 is a table illustrating an example of field descriptions of the AppLayerMeasConfig IE;

[0018] FIG. 6 is a table illustrating an example of field descriptions of a RAN- VisibleParameter field of the AppLayerMeasConfig IE;

[0019] FIG. 7 is a diagram illustrating an example of an ASN. 1 definition of an MeasurementReportAppLayer IE;

[0020] FIG. 8 is a table illustrating an example of MeasurementReportAppLayer field descriptions;

[0021] FIG. 9 is a table illustrating an example of field descriptions of the MeasurementReportAppLayer IE;

[0022] FIG. 10 is a table illustrating an example of field descriptions of a RAN- VisibleMeasurements field of the MeasurementReportAppLayer IE;

[0023] FIG. 11 illustrates a first example of a MeasurementReportAppLayer message in accordance with some embodiments;

[0024] FIGS. 12-14 illustrate a second example of a MeasurementReportAppLayer message in accordance with some embodiments;

[0025] FIGS. 15-17 illustrate a third example of a MeasurementReportAppLayer message in accordance with some embodiments;

[0026] FIGS. 18-19 illustrate a fourth example of a MeasurementReportAppLayer message in accordance with some embodiments;

[0027] FIGS. 20-21 illustrate a fifth example of a MeasurementReportAppLayer message in accordance with some embodiments;

[0028] FIG. 22 is a flow chart illustrating an example of operations performed by a communication device in accordance with some embodiments;

[0029] FIG. 23 is a flow chart illustrating an example of operations performed by a network node in accordance with some embodiments;

[0030] FIG. 24 is a block diagram of a communication system in accordance with some embodiments;

[0031] FIG. 25 is a block diagram of a user equipment in accordance with some embodiments;

[0032] FIG. 26 is a block diagram of a network node in accordance with some embodiments;

[0033] FIG. 27 is a block diagram of a host, which may be an embodiment of the host of FIG. 24, in accordance with some embodiments;

[0034] FIG. 28 is a block diagram of a virtualization environment in accordance with some embodiments; and

[0035] FIG. 29 shows a communication diagram of a host communicating via a network node with a user equipment over a partially wireless connection in accordance with some embodiments.DETAILED DESCRIPTION

[0036] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.

[0037] FIG. 2 illustrates an example of MBS delivery procedures. For a multicast communication service, shared and individual delivery modes are specified. Between 5GC and next generation radio access network (“NG-RAN”), there are two possible delivery procedures to transmit the MBS data: 1) A 5GC individual MBS traffic delivery procedure; and 2) a 5GC shared MBS traffic delivery procedure.

[0038] The 5GC individual MBS traffic delivery procedure can only be applied for multicast MBS sessions. 5GC receives a single copy of MBS data packets and delivers separate copies of those MBS data packets to individual UEs via per-UE packet data unit (“PDU”) sessions, hence for each such UE one PDU session is required to be associated with a Multicast MBS session. The MBS data received by the multicast / broadcast user plane function (“MB- UPF”) is replicated towards the UPF(s) where individual delivery is performed via unicast transport over N19mb interface.

[0039] The 5GC shared MBS traffic delivery procedure can be applied for both broadcast and multicast MBS sessions. 5GC receives a single copy of MBS data packets and delivers a single copy of those MBS packets to an NG-RAN node, which then delivers the packets to one or multiple UEs. These incoming MBS traffic packets are delivered from MB-UPF to NG-RAN node via the N3mb interface.

[0040] The 5GC shared MBS traffic delivery procedure can be required in all MBS deployments. The 5GC individual MBS traffic delivery procedure can be required to enable mobility when there is an NG-RAN deployment with non-homogeneous support of MBS.

[0041] Between the NG-RAN and the UE, two delivery procedures are available for the transmission of MBS data packets over radio interface: PTP delivery and PTM delivery. In a PTP delivery, NG-RAN delivers separate copies of MBS data packets over radio interface to individual UE(s). In PTM delivery, NG-RAN delivers a single copy of MBS data packets over radio interface to multiple UEs.

[0042] NG-RAN may use a combination of PTP / PTM to deliver an MBS data packets to UEs.

[0043] A Quality of Experience (“QoE”) framework is described below. QoE measurements (sometimes referred to as “application layer measurements”), have been specified for long term evolution (“LTE”) and universal mobile telecommunications system (“UMTS”) and are being specified for new radio (“NR”) in the third generation partnership project (“3GPP”) release 17. A purpose of the application layer measurements is to measure the end user experience when using certain applications. Currently QoE measurements for streaming services and for mobility telephony service for internet protocol multimedia subsystem (“MTSI”) services are supported. For NR, it is likely that at least virtual reality (“VR”) is added to the list of services for which QoE measurements are specified and supported.

[0044] The procedures for regular QoE are similar in NR, LTE, and UMTS with the overall principles as follows. Quality of Experience Measurement Collection (“QMC”) enables configuration of application layer measurements in the user equipment (“UE”) (also referred to as a communication device) and transmission of QoE measurement result files (commonly referred to as QoE reports) to the network by means of radio resource control (“RRC”) signaling. An application layer measurement configuration (also called QoE measurement configuration or QoE configuration) that the radio access network (“RAN”) receives from the operations, administration, and maintenance (“0AM”) system or the core network (“CN”) is encapsulated in a transparent container, which is forwarded to a UE in a downlink RRC message. An application layer measurement report (also called QoE report) that the UE AccessStratum (“AS”) or UE RRC layer receives from the UE's higher layer (application layer) is encapsulated in a transparent container and sent to network in an uplink RRC message. The RAN then forwards the QoE report to a Measurement Collector Entity (“MCE”).

[0045] The configuration data related to QoE measurements (in standard specifications typically referred to as application layer measurements) consists of a service type indication, an indication of an area in which the measurements are to be performed (denoted area scope), an IP address of the entity that collected measurement results (e.g., the QoE reports) should be sent to (often referred to as a Measurement Collector Entity or Measurement Collection Entity (“MCE”), but the entity may sometimes also be referred to as a Trace Collection Entity), and a set of instructions of which type of measurements that should be performed and details of how these measurements are to be performed. These instructions are intended for the application layer in the UE and are placed in a “container” which the network entities handling it, e.g., forwarding it to the UE, as well as the UE Access Stratum, cannot interpret and do not try to read. The currently specified service types are MTSI and streaming service (DASH), and in 3GPP release 17, at least service type VR will be added. An area scope is defined in terms of cells or network related areas. In UMTS, an area scope is defined as either a list of cells, a list of routing areas or a list of tracking areas. In LTE, an area scope is defined as either a list of cells or a list of tracking areas. In NR, an area scope will be defined as either a list of cells or a list of tracking areas.

[0046] QoE, and in particular QoE configuration, comes in two types: management-based QoE configuration and signaling-based QoE configuration. In both cases the QoE configuration originates in the 0AM system or some other admini strati onal entity (e.g., dealing with customer satisfaction). Herein these entities are sometimes referred to as the 0AM system (where the 0AM system also includes further entities). With management-based QoE (sometimes referred to herein as m-based QoE), the 0AM system is typically interested in general QoE statistics from a certain area (which is configured as an area scope). The m-based QoE configuration is sent directly from the 0AM system to the RAN nodes controlling cells that are within the area scope. Each RAN node then selects UEs that are within the area scope (and also fulfills any other relevant condition, such as supporting the concerned application / service type) and sends the m-based QoE configuration to these UEs.

[0047] With signaling-based QoE (sometimes referred to herein as s-based QoE), the 0AM system is interested in collecting QoE measurement results from a specific UE (e.g., because the user of the UE has filed a complaint). The 0AM system sends the s-based QoE configuration to the home subscriber server (“HSS”) (in evolved packet system (“EPS”) / LTE) or unified datamanagement (“UDM”) (in 5GS / NR), which forwards the QoE configuration to the UE’s current core network node (e.g., an mobility management entity (“MME”) in EPS / LTE or an access and mobility management function (“AMF”) in 5G / NR). The CN then forwards the s-based QoE configuration to the RAN node that serves the concerned UE and the RAN forwards it to the UE.

[0048] Forwarded to the UE are the service type indication and the container with the measurement instructions. The UE is not aware of whether a received QoE configuration is m- based or s-based. In legacy systems, the QoE framework is integrated with the Trace functionality and a Trace 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 mechanisms. In NR and LTE, a globally unique QoE reference (formed of mobile country codes (“MCC”) + mobile network codes (“MNC”) + QMC identifier (“ID”), where the QMC ID is a string of 24 bits) will be associated with each QoE configuration. The QoE reference is included in the container with measurement instructions and also sent to the RAN (e.g., the gNB in NR). For the communication between the gNB and the UE, the QoE reference is replaced by a shorter identifier denoted as measConfigAppLayerld, which is locally unique within a UE (e.g., there is a one-to-one mapping between a measConfigAppLayerld and a QoE reference for each QoE configuration provided to a UE. The measConfigAppLayerld is stored in the UE Access Stratum and also forwarded in an AT Command (which is the type of instructions used in the communication between the UE’s modem part and the UE’s application layer) together with the service type indication and the container with the measurement instructions.

[0049] Reports with collected QoE measurement results (QoE reports) are sent from the UE application layer to the UE Access Stratum, which forwards them to the RAN, which forwards them to the MCE. These QoE measurement results are placed in a “container”, which is uninterpretable for the UE Access Stratum and the RAN. QoE reporting can be configured to be periodic or only sent at the end of an application session. Furthermore, the RAN can instruct the UE to pause QoE reporting (e.g., in case the cell / gNB is in a state of overload).

[0050] The RAN is not aware of when an application session with an associated QoE measurement session is ongoing and the UE Access Stratum is also not automatically aware of this. To alleviate this session start / stop indications has been introduced, which are sent from the application layer in the UE to the UE AS and from the UE AS to the RAN. A session end indication are sent when the application session and the associated QoE measurement session are concluded.

[0051] The QoE measurements configuration can be done using the RRC message RRCReconfiguration and RRCResume containing the IE appLayerMeasConfig. The UE starts collecting QoE measurements when the session starts in the application layer and when a report is ready, it is sent to the network in the RRC message MeasurementReportAppLayer .

[0052] FIG. 3 illustrates an example of RRC signaling for configuration and reporting of QoE measurements.

[0053] FIG. 4 illustrates an example of an ASN.1 definition of the AppLayerMeasConfig IE (with associated field descriptions). Further explanation is available in 3GPP TS 38.331 version 17.6.0. FIG. 5 illustrates an example of AppLayerMeasConfig field descriptions. FIG. 6 illustrates an example of RAN-VisibleParameter field descriptions.

[0054] FIG. 7 illustrates an example of an ASN.1 definition of the MeasurementReportAppLayer message (with associated field descriptions). Further explanation is available in 3GPP TS 38.331 version 17.6.0.

[0055] FIG. 8 illustrates an example of MeasurementReportAppLayer field descriptions.

[0056] FIG. 9 illustrates an example of MeasReportAppLay er field descriptions. FIG. 10 illustrates an example of RAN-VisibleMeasurements field descriptions.

[0057] The third generation partnership project (“3GPP”) Release 18 introduces support for QoE for MBS, i.e., QoE measurements can be collected for an application session carried by MBS when using MBS Multicast, MBS Broadcast and MBS Unicast. MBS is treated as a communication service (i.e. a means for delivery of application session data) - not a service type which is a property of an application that can be the direct target for QoE measurements. No MBS specific QoE metrics are introduced. A UE continues to receive QoE configuration in the same way as in Rel-17, i.e., only while in RRC CONNECTED.

[0058] Continuity of QoE measurements is supported across all RRC states and when switching between Multicast and Unicast during a session. To ensure the continuity of QoE across all RRC states, and in particular when a UE reconnects from RRC IDLE to RRC CONNECTED where the QoE configurations and the RVQoE configurations of the UE are not available, a UE in RRC CONNECTED state receives from the network a “network instance of the QoE configuration”. In RRC IDLE, the UE stores the “network instance of the QoE configuration” and buffers the QoE reports. Upon transitioning from RRC IDLE to RRC CONNECTED, the UE sends to the network the pending QoE reports, the “network instance of the QoE configurations”, and session status indications.

[0059] The “network instance of the QoE configuration” indicates the parameters specific to QoE measurements applicable to RRC IDLE / RRC INACTIVE. In some examples, networkinstance of QoE measurement configuration can include at least one of: Area Scope of QoE Measurement Collection, QMC, Available RAN Visible QoE Metrics; and MDT Alignment information.

[0060] For non-RedCap UE, it is mandatory to support the minimum AS layer memory size of 64KB for QoE measurement reports stored in RRC IDLE / RRC INACTIVE for UEs which support QoE measurement collection in RRC IDLE and RRC INACTIVE. This memory size is additional to “AS layer memory size for QoE paused measurement reports”, where the “AS layer memory size for QoE paused measurement reports” is a mandatory 64kB as the minimum AS layer memory size.

[0061] Furthermore, UE AS buffer optional capability qoe-AdditionalMemoryMeasReport- rl8 indicates the minimum AS layer memory size the UE supports for QoE measurement in RRC IDLE and RRC INACTIVE in addition to the “AS layer memory size for QoE paused measurement reports”. The values can be 128, 256, 512 and 1024KB.

[0062] There currently exist certain challenges. In Rel-17, where QoE measurements are only supported in RRC CONNECTED mode, the MeasurementReportAppLayer RRC IE contains the QoE measurement reports. When the QoE measurement reports are too large, either the RRC segmentation of MeasurementReportAppLayer message will be used, or the encoded RRC message will be discarded. This is acceptable, as the risk of discarding an RRC message is small, which may mainly happen if no RRC segmentation is allowed and if QoE reporting is resumed after a pause. On the other hand, it is still not optimal behavior as there is still a risk to discard the encoded RRC message.

[0063] According to the 3 GPP specifications, when a UE transitions into the RRC IDLE mode, its entire context, including, among other things, the QoE measurement configuration information stored at the serving gNB is deleted from the gNB. Hence, in Rel-18, to support the QoE measurements for MBS in RRC IDLE state, 3 GPP agreed that the UE should store all the information that the gNB serving the UE upon the UE’s transition to RRC IDLE had about QoE measurement configurations (herein referred to as the “network instance of QoE configurations”). Consequently, when UE transitions from RRC IDLE to RRC CONNECTED, it will send together the stored “network instance of QoE configurations” (which consists of a set of parameters where some are only used by the network) and the measurement reports via MeasurementReportAppLayer signaling. Similarly, when the content that needs to be sent by MeasurementReportAppLayer message (including the QoE measurement reports and the network’s instance of QoE configuration) is too large, either RRC segmentation ofMeasurementReportAppLayer message will be used or the encoded RRC message will be discarded.

[0064] However, the probability of discarding the encoded MeasurementReportAppLayer message may be non-negligible. The UE AS can have memory size for buffering QoE reports in RRC IDLE / IN ACTIVE can be 1024 kB or even larger, so it is likely that the QoE measurement results cannot fit in one RRC message even with RRC segmentation where the maximum size for RRC segmentation is 144 kB. Of course, the probability of this problem happening also depends on UE’s implementation.

[0065] Another problem is that the UE may not send the complete stored “network instance of QoE configurations” in one MeasurementReportAppLayer message due to RRC message size restriction or due to UE’s implementation. Consequently, the gNB has no idea whether the entirety of the network instance of the QoE configurations stored at the UE are retrieved from the UE or not.

[0066] If not all the stored QoE configurations are retrieved by gNB, and if the gNB is unaware of this, there is a risk that measConfigAppLayerld collisions may occur if the network sends new QoE configuration(s) to the UE and assigns the same measConfigAppLayerld s) already used by one of the UE’s stored QoE configurations. This will result in a problem that the former QoE configurations will be released, and all the corresponding QoE measurement reports will be discarded, which is a waste on the UE’s power and memory.

[0067] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Various embodiments described herein achieve the purpose of aligning the network and the UE with regards to the list of all UE stored QoE configurations and / or session start / stop indications and / or constructing MeasurementReportAppLayer message under RRC message size restriction with or without RRC segmentation.

[0068] In some embodiments, UE behavior is restricted to transmitting all the stored “network instance of QoE configurations” (or all the stored QoE / RVQoE configurations) with or without session start / stop indications in the first Measure mentReportAppLayer RRC message and / or to construct MeasurementReportAppLayer RRC message with the RRC message size restriction. The information of UE stored “network instance of QoE configurations” (or the stored QoE / RVQoE configurations) can be in different forms.

[0069] In additional or alternative embodiments, indications from the UE information the network (in any forms of indications explicitly or implicitly about all or unsent stored “network instance of QoE configurations” and / or session start / stop indications and / or unsent QoE reports) are leveraged.

[0070] In some embodiments, the terms communication device, “UE”, “terminal equipment”, “wireless terminal” and “terminal” are used interchangeably.

[0071] In additional or alternative embodiments, the terms “node” and “network node” are used interchangeably. A network node can, for example, be a RAN node, a gNB, an eNB, an en-gNB, a ng-eNB, a gNB-CU, a gNB-CU-CP, a gNB-CU-UP, an eNB-CU, an eNB-CU-CP, an eNB-CU-UP, an lAB-node, an lAB-donor DU, an lAB-donor-CU, an IAB-DU, an IAB-MT, an O-CU, an O-CU-CP, an O-CU-UP, an O-DU, an O-RU, an O-eNB, a Non-Real Time RAN Intelligent Controller (Non-RT RIC), a Real-Time RAN Intelligent Controller (RT-RIC), an 0AM node, a Core Network node / function, a Cloud-based network function, a Cloud-based centralized training node.

[0072] In additional or alternative embodiments, the terms “session start / stop indication”, “start / stop indication”, “session status indication” and “QoE measurement session status indication” are used interchangeably.

[0073] In additional or alternative embodiments, the terms “network version of the QoE configuration”, “network instance of the QoE configuration” and “NW-QoE configuration” are equivalent. The same applies for the corresponding UE’s version / instance of the QoE configuration, i.e. the terms “UE version of the QoE configuration”, “UE instance of the QoE configuration” and “UE-QoE configuration” are equivalent. The NW-QoE configuration consists of QoE configuration related parameters stored in the RAN while the UE is in RRC CONNECTED or RRC INACTIVE state, but when the UE is in RRC IDLE state (and the QoE configuration is applicable in RRC IDLE state), the RAN relies on the UE to store the NW-QoE configuration on behalf of the RAN while the UE is in RRC IDLE state. To this end, the RAN can send the NW-QoE configuration to the UE and the UE may return it to the RAN after transiting from RRC IDLE to RRC CONNECTED state. In the endorsed CR to be implemented in a release 18 version of TS 38.331, the NW-QoE configuration is referred to as AppLayerldlelnactiveConfig-r 18. In many 3 GPP documents (agreements and contributions) and possibly also in this invention disclosure, the NW-QoE configuration is often simply referred to as the “QoE configuration” (which unfortunately is an ambiguous term in this context).

[0074] Some embodiments here are equally applicable to QoE and RVQoE measurements.

[0075] Some embodiments herein are equally applicable to QoE configuration and RVQoE configuration.

[0076] In additional or alternative embodiments, the application layer in the UE is also referred to as the “UE application layer” or simply the “application layer”.

[0077] In additional or alternative embodiments, the terms “QoE configuration”, “QoE parameters”, “QoE information” and “QoE configuration information” are used interchangeably. The network, the UE AS and the UE application layer may store various parts thereof.

[0078] In additional or alternative embodiments, the application layer in the UE is also referred to as the “UE application layer” or simply the “application layer”.

[0079] In additional or alternative embodiments, the entity performing the QoE measurements and other actions related to a QoE configuration, such as receiving QoE information from the UE AS, and / or sending QoE information to the UE AS, is an application. The application resides on the application layer in the UE, and hence it is also correct to say that the application layer performs these actions. In the description of the solution, the performer of these various actions is sometimes said to be the application layer and sometimes said to be the application.

[0080] In additional or alternative embodiments, the terms “application layer measurement configuration”, “application measurement configuration”, “QoE measurement configuration”, “QoE configuration”, “QoE measurement and reporting configuration” and “QMC configuration” are used interchangeably. But note that the “QMC configuration file” is not an equivalent term, but instead refers to the part of the QoE configuration consisting of an XML file containing instructions of QoE metrics to be collected etc.

[0081] While some embodiments are described for the interaction between the UE AS and UE application layer when handling / storing QoE information, they may also be applicable to RVQoE information.

[0082] In additional or alternative embodiments, references to the application layer are with respect to the application layer of the UE.

[0083] In additional or alternative embodiments, the term “service” is often used as a short notation for “service type”, therefore “service” and “service types” can be seen as interchangeably unless explicitly stated.

[0084] Some embodiments apply to both signaling- based and management-based QoE / RVQoE measurements (but may also optionally be restricted to apply to only one of them).

[0085] In additional or alternative embodiments, a QoE configuration includes various configuration parameters (such as an instruction on whether the UE should send session start / stop indications) as well as an XML file containing a configuration of QoE measurements to be performed and reported (e.g. indicating QoE metrics to be collected and reported). This XML file is herein referred to with different terms, including at least “QMC configuration file” and “QoE configuration file”.

[0086] In additional or alternative embodiments, the functionality in a UE which 3 GPP has named Access Stratum (where there is corresponding Access Stratum functionality in the network) is herein referred to in various ways, including “Access Stratum”, “AS”, “UE Access Stratum”, “UE AS”, “Access Stratum layer”, “AS layer”, “UE Access Stratum layer”, “UE AS layer” or “radio layer”.

[0087] In additional or alternative embodiments, the terms “LTE” and “LTE node” imply that a network node that serves the UE is serving the UE by using the LTE radio access technology on the air interface (Uu).

[0088] In additional or alternative embodiments, the terms “NR” and “NR node” imply that a network node that serves the UE is serving the UE by using the NR radio access technology on the air interface (Uu).

[0089] In additional or alternative embodiments, the terms information element (IE) and field are used more or less interchangeably in this document. Also the term parameter is sometimes used to denote the same concept.

[0090] In additional or alternative embodiments, when writing message names of a communication protocol, two equivalent principles are used herein. The writing principle “<protocol name> <message name> message”, for example “XnAP HANDOVER REQUEST message”, and the writing principle “<message name> <protocol name> message”, for example “HANDOVER REQUEST XnAP message” are equivalent, both referring to a message (i.e., “<message name>”) of a communication protocol (i.e., “<protocol name>”), e.g., the HANDOVER REQUEST message of the communication protocol XnAP. The same writing format equivalence applies to other communication protocols, such as NGAP.

[0091] In additional or alternative embodiments, param eters / IEs / fields used in ASN.1 code as well as in procedural text in the 3GPP RRC specification for 5G / NR, i.e. 3GPP TS 38.331 version 17.6.0, are often named with a suffix indicating the number of the release of the 3GPP standard the parameter / IE / field was introduced in (e.g. the suffix “-rl7” for a parameter / IE / field introduced in release 17 of the 3GPP standard). Parameters / IEs / fields following this naming convention are typically referred to both with and without the suffix, where the name including the suffix is used in the ASN.l code (and thus defines the formal name from the ASN.l compiler’s perspective), while the name without the suffix is used in running text, e.g. in field descriptions and procedural text. Relevant examples in the context of this document include the parameters / IEs / fields AppLayerMeasConfig-rl71 AppLayerMeasConfig and MeasConfigAppLayer-rl71 MeasConfigAppLayer . In this document, both name variants may occur for various parameters / IEs / fields.

[0092] In additional or alternative embodiments, strictly speaking, the session start / stop indications do not refer to the application session, but rather to the QoE measurement session associated with the application session. However, if / when the terms “session data” or “session data flow” are mentioned, they refer to the data or data flow of the application session with which the QoE measurement session is associated.

[0093] In additional or alternative embodiments, the term “flag” refers to an indication, i.e. a parameter indicating something. An indication referred to as a flag is typically, but not necessarily, an indication that can indicate one of only two possible values, e.g. implemented as a single-bit indicator.

[0094] In additional or alternative embodiments, the terms “QoE report” or “QoE measurement report”, when sent from a UE to a gNB, may primarily refer to the content of a measReportAppLayerContainer IE in a MeasurementReportAppLayer RRC message. However, sometimes the terms may refer to:a MeasurementReportAppLayer RRC message; a MeasReportAppLayer IE in a MeasurementReportAppLayer RRC message; or the content of a MeasReportAppLayer IE, excluding the ran-VisibleMeasurements IE, in a MeasurementReportAppLayer RRC message.

[0095] In additional or alternative embodiments, the terms “RVQoE report” or “RVQoE measurement report”, when sent from a UE to a gNB, refer to the content of a RAN- VisibleMeasurements IE in a MeasurementReportAppLayer RRC message.

[0096] Some embodiments are described in terms of NR, but can also be applied to UMTS, LTE and NR as well as future RATs such as 6G.

[0097] As indicated above, various embodiments herein achieve the purpose of aligning the network’s view and the UE’s view with regards to the list of all UE stored QoE configurations and possibly session start / stop indications and constructing MeasurementReportAppLayer message with RRC message size restriction.

[0098] Embodiments associated with restricting UE behavior are described below.

[0099] In some embodiments, instead of allowing the content of the MeasurementReportAppLayer RRC message to depend entirely on UE implementation, UE behavior may be restricted and specified.

[0100] In additional or alternative embodiments, the UE is required to transmit all the stored “network instance of QoE configurations” in the first MeasurementReportAppLayer message after UE transitions to RRC CONNECTED from RRC IDLE. Thus, all the stored QoE configurations can be retrieved by gNB, and then gNB can keep / modify / release the QoE configurations or add new QoE configuration with no risk of measConfigAppLayerld collisionsbetween an existing configuration at the UE that was not indicated to the gNB and a newly configured configuration by the gNB.

[0101] In additional or alternative embodiments, the UE is required to transmit all the stored “network instance of QoE configurations” and session start / stop indications in the first MeasurementReportAppLayer message after UE transitions to RRC CONNECTED from RRC IDLE.

[0102] In additional or alternative embodiments, in which all the NW-QoE configurations are sent in the first MeasurementReportAppLayer message, the message may also or may not contain one or more stored QoE reports.

[0103] In additional or alternative embodiments, the UE is required to first transmit all the stored NW-QoE configurations using one or more subsequent MeasurementReportAppLayer messages, before sending any reports. In some examples, one MeasurementReportAppLayer message can carry one configuration, or several entire configurations can be contained in one message. In additional or alternative examples, each message may also contain an indicator of whether there are more (yet undelivered) configurations coming in subsequent messages. In additional or alternative examples, the first MeasurementReportAppLayer message with the identifiers informs the gNB of which NW-QoE configurations the UE has stored and informs the gNB of which measConfigAppLayerlds are occupied so that measConfigAppLayerld collisions can be avoided. In additional or alternative examples, the messages may contain the session start / stop indications as well.

[0104] In additional or alternative embodiments, upon transition from RRC IDLE to RRC CONNECTED, and after SRB4 has been established (and the serving gNB optionally has indicated that transmission of application layer measurement reports collected in RRC IDLE and / or RRC INACTIVE state is allowed and that transmission of application layer measurement configurations applicable to RRC IDLE and / or RRC INACTIVE is allowed (i.e. the idlelnactiveReportAllowed IE set to “enabled”) the UE is required to transmit in a first RRC message, such as in a first Measure mentReportAppLayer message, at least (or only) the identifiers of the QoE / RVQoE configurations stored at the UE, where such an identifier may e.g, be the measConfigAppLayerld or the QoE reference or the combination of the QoE reference and the associated measConfigAppLayerld).

[0105] In some examples, the UE is required to transmit in the first RRC message at least the identifiers of all the QoE configurations stored at the UE for which a corresponding RVQoE configuration is defined (or for which Available RVQoE metrics are defined), as well as all theidentifiers of the QoE configurations stored at the UE for which a corresponding RVQoE configuration is not defined (or for which Available RVQoE metrics are not defined).

[0106] In additional or alternative examples, the UE is required to transmit in the first RRC message the identifiers of all the QoE configurations stored at the UE for which a corresponding RVQoE configuration is defined (or for which Available RVQoE metrics are defined), and to not transmit the identifiers of the QoE configurations stored at the UE for which a corresponding RVQoE configuration is not defined (or for which Available RVQoE metrics are not defined).

[0107] In additional or alternative examples, wherein QoE configurations and RVQoE configurations have different set of identifiers, the UE is required to transmit in the first RRC message the identifiers of all the QoE configurations stored at the UE, and to also transmit the identifiers of all the RVQoE configurations stored at the UE.

[0108] In additional or alternative examples, wherein QoE configurations and RVQoE configurations have different set of identifiers, the UE is required to transmit in the first RRC message the identifiers of all the RVQoE configurations stored at the UE, and to not transmit the identifiers of any QoE configurations stored at the UE.

[0109] In additional or alternative examples,, wherein QoE configurations and RVQoE configurations have different set of identifiers, the UE is required to transmit in the first RRC message the identifiers of all the QoE configurations stored at the UE, and to not transmit the identifiers of any RVQoE configurations stored at the UE.

[0110] In additional or alternative embodiments, upon transition from RRC IDLE to RRC CONNECTED, the UE is required to transmit in a first RRC message, such as in a first MeasurementReportAppLayer message at least (or only) the identifiers of the QoE / RVQoE configuration stored at the UE (such as the measConfigAppLayerld) for which a “network instance of the QoE / RVQoE configuration” is stored at the UE.

[0111] In some examples, the UE is required to transmit in the first RRC message at least (or only) the identifiers of the QoE / RVQoE configuration stored at the UE (such as the measConfigAppLayerld).

[0112] In additional or alternative examples, the UE is required to transmit in the first RRC message at least the identifiers (such as the measConfigAppLayerld of the QoE / RVQoE configuration stored at the UE AND session start / stop indications corresponding to the said QoE / RVQoE configuration identifiers.

[0113] In additional or alternative examples, the UE is required to transmit in the first RRC message at least the identifiers (such as the measConfigAppLayerld) of the QoE / RVQoEconfiguration stored at the UE AND indications indicating whether QoE / RVQoE measurement reports corresponding to the said QoE / RVQoE configuration identifiers are available.

[0114] In additional or alternative examples, the UE is required to transmit in the first RRC message at least the identifiers (such as the measConfigAppLayerld of the QoE / RVQoE configuration stored at the UE AND indications indicating whether QoE / RVQoE measurement reports corresponding to the said QoE / RVQoE configuration identifiers are available AND session start / stop indications corresponding to the said QoE / RVQoE configuration identifiers.

[0115] If the stored configurations are indicated by their measConfigAppLayerld, then these IDs can be indicated explicitly, or in the form of a bitmap, where value “1” (“0”) in each position of the bitmap means that the UE has (has not) stored a NW-QoE configuration with the measConfigAppLayerld equal to the position of the bit in the bitmap.

[0116] For each of the above alternative options, the same variations as described in the preceding option to distinguish between QoE and RVQoE configuration can apply. Also, a condition can be introduced to further restrict the sending of the identifiers of the QoE / RVQoE configuration (and / or the corresponding session start / stop indications, and / or the corresponding indications indicating whether QoE / RVQoE measurements report are available), only for the QoE / RVQoE configuration for which a “network instance” is stored at the UE.

[0117] In additional or alternative embodiments, upon transition from RRC IDLE to RRC CONNECTED, the UE is required to transmit a first RRC message, such as in a first MeasurementReportAppLayer message, including at least (or only) the identifiers (such as the measConfigAppLayerld) of the QoE / RVQoE configuration stored at the UE for which the corresponding session is started (or not stopped). The same variations as described in the preceding option to distinguish between QoE and RVQoE configuration can apply to this alternative as well.

[0118] In additional or alternative embodiments, if all the stored “network instance of QoE configurations”, session start / stop indications and stored QoE measurement reports cannot fit in one MeasurementReportAppLayer message with or without RRC segmentation, UE should not discard the encoded RRC message. But when the UE constructs the RRC MeasurementReportAppLayer message, it may choose / select one or a combination of one or more the QoE measurement reports that shall be transmitted in the current message such that the QoE measurement reports fit the size of one MeasurementReportAppLayer message.

[0119] In additional or alternative embodiments, how the UE chooses the QoE measurement reports to fit to the size of one MeasurementReportAppLayer message can be left to UE implementation, or can be based on pre-defined rules, for example, configured priority -based rules, time-based rules and / or based on measConfigtAppLayerld. In one example, the Rel- 18 defined priority of application layer measurement configuration appLayerMeasPriority can be reused and / or newer QoE measurement reports will be transmitted first. In another example, the UE can prioritize the reports pertaining to configurations of certain service types.Alternatively, the reports pertaining to the QoE reference for which the most or the least number of reports are currently stored can be prioritized.

[0120] In additional or alternative embodiments, where the UE transitions from RRC IDLE to RRC CONNECTED state and has stored one or more NW-QoE configuration(s), a core principle to abide by is that the UE may not send any QoE report(s) or session status indication(s) associated with a certain QoE configuration unless the UE has already sent the NW-QoE configuration corresponding to the QoE configuration to the network or the NW-QoE configuration corresponding to the QoE configuration is included in the same message as said QoE report(s) and / or session status indication(s).

[0121] In additional or alternative embodiments, one or more of the following options, variations, rules and / or procedures may apply when the UE has entered RRC CONNECTED state from RRC IDLE state and the gNB has established SRB4.

[0122] In some examples, the UE includes all stored NW-QoE configurations in the first MeasurementReportAppLayer message.

[0123] In additional or alternative examples, the UE sends all stored NW-QoE configurations to the gNB before it sends any pending QoE reports and or session status indications.

[0124] In additional or alternative examples, the UE includes no QoE report and / or session status indication in MeasurementReportAppLayer message which includes one or more NW- QoE configurations.

[0125] In additional or alternative examples, the UE is not allowed to send any QoE report and / or session status indication until in the MeasurementReportAppLayer message which carries the last NW-QoE configuration to be sent or in MeasurementReportAppLayer message sent after that MeasurementReportAppLayer message.

[0126] In additional or alternative examples, the QoE reports, session status indications and NW-QoE configuration(s) are allowed in the same MeasurementReportAppLayer message and QoE reports and / or session status indications may be sent before all stored NW-QoE configurations have been sent, as long as no QoE report or session status indication is sent before the NW-QoE configuration it is associated with is sent (i.e. the NW-QoE configurationhas to be sent in the same MeasurementReportAppLayer message or in a preceding MeasurementReportAppLayer message).

[0127] In some embodiments, when MeasurementReportAppLayer message may contain only NW-QoE configurations, then a means may be introduced to convey the measConfigAppLayerld associated with each sent NW-QoE configuration, since the measConfigAppLayerld is not part of the AppLayerIdleInactiveConfig-rl8 IE in the current endorsed CR for the RRC specification TS 38.331.

[0128] In some examples, the means includes extending the AppLayerldlelnactiveConfig- rl8 IE with the measConfigAppLayerld.

[0129] In additional or alternative examples, the means includes conveying the measConfigAppLayerld associated with a NW-QoE configuration in a MeasConfigAppLayer- rl7 IE containing only a measConfigAppLayerld (i.e. the other parameters in the MeasConfigAppLayer-r 17 IE, which are optional, are omitted).

[0130] In additional or alternative examples, the means includes sending the NW-QoE configurations in a list construction, which in ASN.l is realized as a “SEQUENCE OF” construct, e.g. “SEQUENCE (SIZE (x..y) OF Q”, where each list entry, i.e. each “Q”, includes both an AppLayerIdleInactiveConfig-rl8 IE and a measConfigAppLayerld field indicating the measConfigAppLayerld associated with the AppLayerIdleInactiveConfig-rl8 IE.

[0131] In additional or alternative embodiments, the UE first includes the entire QoE configurations in the MeasurementReportAppLayer message, then a clarification is added that the reports can be included in further MeasurementReportAppLayer messages if all reports cannot fit into one message. This is illustrated in the modified specification excerpt below based on the endorsed CR to be implemented in a release 18 version of TS 38.331.

[0132] A UE capable of application layer measurement reporting in RRC CONNECTED may initiate the procedure when configured with application layer measurement, i.e. when appLayerMeasConfig and SRB4 and / or SRB5 have been configured by the network.Upon initiating the procedure, the UE shall: l>for each stored application layer measurement configuration with configforRRC- Idlelnactive set to true and for which appLayerldlelnactiveConfig has not been transmitted since the UE entered RRC CONNECTED:2> set the parameters in appLayerldlelnactiveConfig in the MeasurementReportAppLayer message to the values stored in the UE variable VarAppLayerIdleConfig l>for each measConfigAppLayerld received from upper layers:2> if the UE AS has received application layer measurement report container from upperlayers which has not been transmitted; and2> if the application layer measurement reporting has not been suspended for the measConfigAppLayerld associated with the application layer measurement report container according to clause 5.3.5.13d:3>set the measReportAppLayerContainer in the MeasurementReportAppLayer message to the received value in the application layer measurement report container;2> set the measConfigAppLayerld in the MeasurementReportAppLayer message to the value of the measConfigAppLayerld received together with application layer measurement report information;2> if session start or stop information has been received from upper layers for the measConfigAppLayerld.3>set the appLayerSessionStatus in the MeasurementReportAppLayer message to the received value of session start or stop information;2> if reportingSRB and ran-VisibleReportingSRB are different for the measConfigAppLayerld'.3> include measReportAppLayerContainer and appLayerSessionStatus in a different MeasurementReportAppLayer message than ran-VisibleMeasurements2> if RAN visible application layer measurement report has been received from upper layers:3>for each appLayerBufiferLevel value in the received RAN visible application layer measurement report:4> set the appLayerBufiferLevel values in the appLayerBufferLevelList in the MeasurementReportAppLayer message to the buffer level values received from the upper layer in the order with the first appLayerBufiferLevel value set to the newest received buffer level value, the second appLayerBufiferLevel value set to the second newest received buffer level value, and so on until all the buffer level values received from the upper layer have been assigned or the maximum number of values have been set according to appLayerBufiferLevef if configured;3>set the playoutDelayForMediaStartup in the MeasurementReportAppLayer message to the received value of playout delay for media startup in the RAN visible application layer measurement report, if any;3>for each PDU session ID value indicated in the received RAN visible application layer measurement report, if any:4> set the PDU-SessionlD in the pdu-SessionldList in theMeasurementReportAppLayer message to the indicated PDU session ID value; 4>for each QoS Flow ID value indicated in the received RAN visible application layer measurement report associated with the PDU Session ID, if any: 5> set the QFI associated with the PDU session ID to the indicated QoS Flow ID value.NOTE 0: If the application layer measurement configurations and reports stored while the UE was in RRC IDLE and / or RRC INACTIVE exceed the size of an RRC message, the UE includes the appLayerldlelnactiveConfig in the first MeasurementReportAppLayer message when the UE enters RRC CONNECTED. The UE includes remaining application layer measurement reports in subsequent MeasurementReportAppLayer mes sage s . l>for each encoded MeasurementReportAppLayer message generated above:2> if reportingSRB or ran-VisibleReportingSRB are not configured:3> if the encoded RRC message is larger than the maximum supported size of one PDCP SDU specified in TS 38.323:4> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received in appLayerMeasConfig'.5> initiate the UL message segment transfer procedure as specified in clause 5.7.7;4> else:5> discard the RRC message;3>else:4> submit the MeasurementReportAppLayer message to lower layers for transmission2> else if reportingSRB or ran-VisibleReportingSRB are configured:3> if the encoded RRC message is larger than the maximum supported size of one PDCP SDU specified in TS 38.323:4> if the RRC message segmentation is enabled based on the field rrc- SegAllowedSRB4 received in appLayerMeasConfig and the reportingSRB is SRB4; or4> if the RRC message segmentation is enabled based on the field rrc- SegAllowedSRB5 received in appLayerMeasConfig and the reportingSRB is SRB5:5>initiate the UL message segment transfer procedure as specified in clause 5.7.7via the SRB indicated in the field reportingSRB in MeasConfigAppLayer, 4> else:5> discard the RRC message;3>else:4> submit the MeasurementReportAppLayer message to lower layers for transmission via the SRB indicated in the field reportingSRB or, if different from reportingSRB, ran-VisibleReportingSRB in MeasConfigAppLayer upon which the procedure ends.Editor ’s Note: FFS on if it needs to be specified what the UE transmits when returning to RRC CONNECTED.NOTE 1 : If the SRB indicated by reportingSRB is not available, the UE may store application layer measurement report containers until the SRB is available. The UE may discard reports when the memory reserved for storing application layer measurement report containers becomes full. Reports with lower appLayerMeasPriority are discarded first. If no appLayerMeasPriority is configured, older reports may be discarded first.NOTE 2: If the SRB indicated by ran-VisibleReportingSRB is not available, the UE discards RAN visible application layer measurement reports.

[0133] Embodiments associated with leveraging indication(s) from the UE informing the network are described below.

[0134] In some embodiments, the UE sends indication(s) related to the information that remains to be transferred to the network e.g. in case it couldn’t include all information in the first MeasurementReportAppLayer message. Alternatively, the UE may prioritize some information to be transferred first.

[0135] In some examples, the UE may indicate if the UE still has unsent stored “network instance of QoE configurations” (or that UE has no unsent stored “network instance of QoE configuration”). This indication can be implicit, e.g., an optional flag can be defined to indicate whether the UE has any unsent stored “network instance of QoE configuration” and absence in the signaling sent from the UE to the network indicates that UE has no unsent stored “network instance of QoE configurations.”

[0136] In additional or alternative examples, the UE may indicate how many unsent, stored “network instance of QoE configurations” the UE still has.

[0137] In additional or alternative examples, the UE may indicate the measConfigAppLayerld(s) of unsent “network instance of QoE configurations.”

[0138] In additional or alternative examples, the UE may indicate the measConfigAppLayerld(s) of all stored “network instances of QoE configurations.”

[0139] In additional or alternative examples, the UE may indicate the latest session start / stop indications of stored QoE configurations.

[0140] In additional or alternative examples, the UE may indicate if the UE still has unsent stored QoE measurement reports.

[0141] In additional or alternative examples, the UE may indicate how many unsent stored QoE measurement reports.

[0142] In additional or alternative examples, the UE may indicate the measConfigAppLayerId(s) of unsent “network instance of QoE configuration(s)” together with the latest session status (i.e. session start / stop indication) for each of them.

[0143] In additional or alternative examples, the UE may indicate the measConfigAppLayerld s) of unsent “network instance of QoE configuration(s)” and an indication of the number of stored QoE measurement report(s) for each of them.

[0144] In additional or alternative examples, the UE may indicate the measConfigAppLayerld s) of unsent “network instance of QoE configuration(s)” together with the latest session status (i.e. session start / stop indication) and an indication of the number of stored QoE measurement report(s) for each of them.

[0145] In additional or alternative examples, the UE may indicate one or more or all of the UE’s stored “network instance(s) of QoE configuration” and an indication of the number of unsent QoE report(s).

[0146] In additional or alternative examples, the UE may indicate one or more or all of the UE’s stored “network instance(s) of QoE configuration” and for each of them an indication of the number of unsent QoE report(s) associated with any of them.

[0147] In additional or alternative examples, the UE may indicate one or more or all of the UE’s stored “network instance(s) of QoE configuration” and for each of them an indication of the number of unsent associated QoE report(s).

[0148] In additional or alternative examples, the UE may indicate an indication of the number of unsent stored “network instance(s) of QoE configuration” and the number of unsent stored QoE reports the UE has.

[0149] In additional or alternative examples, the UE may indicate any of the above together with an indication of the amount of data represented by the unsent “network instance(s) of QoE configuration” and / or QoE measurement report(s).

[0150] In additional or alternative examples, the UE may indicate an indication of the amount of data represented by the unsent “network instance(s) of QoE configuration” and / or QoE measurement report(s).

[0151] In additional or alternative examples, the UE may indicate regardless of the type of data that has not yet been transferred, i.e., either a network instance(s) of QoE configuration or QoE reports corresponding to the configurations, or any other data, the UE may simply indicate via a flag to specify that the entirety of the transmission has not yet been completed.

[0152] In additional or alternative embodiments, the indication(s) is(are) introduced in the MeasurementReportAppLayer RRC message to indicate one or multiple or any combination of the above indications.

[0153] In additional or alternative embodiments, a network node receiving from a UE a request to setup an RRC connection (e.g., in a RRCSetupRequest message), sends - in response - a request to the UE (e.g., in a RRCSetup message) to indicate in subsequent RRC messages (e.g., in a RRCSetupComplete message or in an MeasurementReportAppLayer message) one or multiple or any combination of the above indications(e.g whether the UE has any stored unsent “network instance of QoE configurations”).

[0154] In additional or alternative embodiments, upon receiving an RRCSetup message from a network node, the UE is instructed to determine whether it should send in subsequent RRC messages (e.g., in an RRCSetupComplete message or in an MeasurementReportAppLayer message) an indication from one or multiple or any combination of the above indications (e.g., a flag to indicate whether the UE has stored unsent “network instance of QoE configurations”).

[0155] In additional or alternative embodiments, upon receiving an RRCReconfiguration message from a network node(e.g when the network indicate support of QoE measurement in RRC IDLE / RRC INACTIVE and / or SRB4 / SRB5 is configured), the UE is instructed to determine whether it should send in subsequent RRC messages (e.g., in an RRCReconfigurationComplete message or in an MeasurementReportAppLayer message) an indication from one or multiple or any combination of the above indications (e.g., a flag to indicate whether the UE has stored unsent “network instance of QoE configurations”).

[0156] In additional or alternative embodiments, to avoid the risk of measConfigAppLayerld collisions, gNB can utilize one or multiple of the indication(s) above to keep / modify / release / add the QoE configuration.

[0157] FIGS. 11-21 illustrate a number of examples of how some embodiments may be implemented in ASN.1 code based on the endorsed CR to be implemented in a release 18 version of TS 38.331.

[0158] In Rel-18, measConfigReportAppLayerAvailable is introduced to indicate that the UE has stored one or more application layer measurement reports while the UE was in RRC IDLE / RRC INACTIVE state and / or that the UE is configured with at least one application layer measurement configuration for RRC IDLE / RRC INACTIVE. FIG. 11 illustrates a first example of a MeasurementReportAppLayer message with a measConfigReportAppLayer Available to indicate that the UE has one or more application layer measurement configurations or reports that has not been sent within this or previous MeasurementReportAppLayer message(s).

[0159] FIG. 12 illustrates a second example of MeasurementReportAppLayer message with an idlelnactiveConfigList field that includes an AppLayerldlelnactiveConfig IE and a modified measurementReprotAppLayerList field. FIG. 13 illustrates an example of the MeasurementReportAppLayer field descriptions and FIG. 14 illustrates an example of the AppLayerldlelnactiveConfig IE.

[0160] FIG. 15 illustrates a third example of a MeasurementReportAppLayer message with a MeasurementReportAppLayerList field that includes and AppLayerldlelnactiveConfig IE. FIG. 16 illustrates an example of the MeasurementReportAppLayer field descriptions and FIG. 17 illustrates an example of the AppLayerldlelnactiveConfig IE.

[0161] FIG. 18 illustrates a fourth example of a MeasurementReportAppLayer message with a MeasurementReportAppLayerList field that includes a measConfigAppLayerld. FIG. 19 illustrates an example of the MeasurementReportAppLayer field descriptions.

[0162] FIG. 20 illustrates a fifth example of a MeasurementReportAppLayer message with a MeasurementReportAppLayerList field and a modified MeasReportAppLayer that includes a measConfigAppLayerld. FIG. 21 illustrates an example of the MeasurementReportAppLayer field descriptions.

[0163] Although embodiments that include restricting UE behavior and embodiments that include leveraging information from the UE to the network are described separately above, the embodiments may be used in combination.

[0164] In some embodiments, how and what to be transmitted in MeasurementReportAppLayer RRC message should be specified and some explicit or implicit signaling should be sent from UE to inform network if it still has unsent stored “network instance of QoE configurations”, and / or session start / stop indication and / or QoE measurement reports.

[0165] In additional or alternative embodiments, a UE is required to transmit all the stored “network instance of QoE configurations” and session start / stop indication in the firstMeasurementReportAppLayer message after UE transitions to RRC CONNECTED from RRC IDLE. And an explicit / implicit indication to indicate if there is or how many unsent QoE measurement reports, which gNB can refer to keep / modify / release / add the QoE configurations.

[0166] In additional or alternative embodiments, when UE constructs the MeasurementReportAppLayer message, it should choose some of the QoE measurement reports or even not transmit any of the QoE measurement reports to fit the size of one MeasurementReportAppLayer message and it will send explicit / implicit indication if there is unsent or how many unsent QoE measurement reports, which gNB can refer to keep / modify / release / add the QoE configurations.

[0167] All the options described above can be adopted when UE transitions from RRC IDLE to RRC CONNECTED, and / or when UE transitions from RRC INACTIVE to RRC CONNECTED, and / or when UE in RRC CONNECTED.

[0168] In additional or alternative embodiments, 0AM may configure some rules to help UE to select some QoE measurement reports to transmit, e.g. priority for QoE configuration and reports.

[0169] In additional or alternative embodiments, UE capability signaling may be defined, to indicate to the network which of the features described herein the UE is able to support.

[0170] Operations of the communication device 2500 (implemented using the structure of FIG. 25) will now be discussed with reference to the flow charts of FIG. 22 according to some embodiments of inventive concepts. For example, modules may be stored in memory 2510 of FIG. 25, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 2502, communication device 2500 performs respective operations of the flow chart.

[0171] FIG. 22 illustrates an example of operations performed by a communication device according to some embodiments.

[0172] At block 2210, processing circuitry 2502 stores all of the configuration information known by a network node serving the communication device.

[0173] At block 2220, processing circuitry 2502 transitions from a second state to a first state. At block 2230, processing circuitry 2502 transitions from the first state to the second state. In some embodiments, the first state is a radio resource control, RRC, connected state, and the second state is a RRC idle state.

[0174] At block 2240, processing circuitry 2502 receives, via communication interface 2512, a request to transmit a message and instructions indicating what to include in the message.

[0175] At block 2250, processing circuitry 2502 generates a first message. In some embodiments, the first message includes an indication of at least one of configuration information that was known by a network node that was serving the communication device when the communication device transitioned to a second state; whether there is a portion of the configuration information that has not been transmitted to the network node; a number of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of each configuration in the configuration information; a latest session start indication of the configuration information; a latest session stop indication of the configuration information; a report that has not been transmitted to the network node; and an indication of a number of reports that have not been transmitted to the network node.

[0176] In additional or alternative embodiments, generating the message includes generating the message to include an indication of all of the configuration information that was known by the network node that was serving the communication device when the communication device transitioned to the second state. In some examples, generating the message includes: determining that the message includes all of the configuration information; and responsive to determining that the message includes all of the configuration information, adding the report to the message.

[0177] In additional or alternative embodiments, the configuration information includes at least one of a network instance of quality of experience, QoE, measurement configuration; and a network instance of radio access network-visible QoE, RVQoE, measurement configuration.

[0178] In some examples, a network instance of QoE measurement configuration can include at least one of Area Scope of QoE Measurement Collection, QMC; Measurement Collection Entity, MCE, identifier; MCE IP Address; MCE Uniform Resource Identifier, URI; slice support List for QMC (e.g., a list of S-NSSAI); MDT Alignment information; and Assistance Information for QoE measurement.

[0179] In additional or alternative embodiments, the configuration information includes a plurality of configurations. Generating the message includes generating the message to include an identifier of each configuration of the plurality of configurations. Each identifier of each configuration of the plurality of configurations includes at least one of a measConfigAppLayerld; and a QoE reference.

[0180] In additional or alternative embodiments, generating the first message includes generating the first message based on the instructions provided by the network node.

[0181] At block 2260, processing circuitry 2502 transmits, via communication interface 2512, the first message. In some embodiments, the first message includes a MeasurementReportAppLayer radio resource control, RRC, message. In some examples, the MeasurementReportAppLayer RRC message is a first MeasurementReportAppLayer RRC message transmitted to the network node after transitioning to the first state.

[0182] In additional or alternative embodiments, transmitting the first message includes transmitting the first message subsequent to transitioning to the first state and prior to transmitting any message that includes at least one of: a quality of experience, QoE, report; and an indication of a session status associated with a QoE configuration.

[0183] At block 2270, processing circuitry 2502 generates a second message. In some embodiments, the second message includes an indication of at least one of: whether there is a portion of the configuration information that has not been transmitted to the network node; a number of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of each configuration in the configuration information; a latest session start indication of the configuration information; a latest session stop indication of the configuration information; a report that has not been transmitted to the network node; and an indication of a number of reports that have not been transmitted to the network node.

[0184] At block 2280, processing circuitry 2502 transmits, via communication interface 2512, the second message.

[0185] In some embodiments, the first and / or second message each include a plurality of messages. Generating the message can include generating a plurality of messages. Each message of the plurality of messages can include an indication of whether it is the last message of the plurality of messages to be transmitted. Transmitting the message can include transmitting the plurality of messages.

[0186] Various operations from the flow chart of FIG. 22 may be optional with respect to some embodiments of communication devices and related methods.

[0187] Operations of the network node 2600 (implemented using the structure of FIG. 26) will now be discussed with reference to the flow charts of FIG. 23 according to some embodiments of inventive concepts. For example, modules may be stored in memory 2604 of FIG. 26, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 2602, network node 2600 performs respective operations of the flow chart.

[0188] At block 2310, processing circuitry 2602 releases configuration information. In some embodiments, the network node releases the configuration information in response to a communication device associated with the configuration information transitioning from a first state to a second state. In some examples, the first state is a radio resource control, RRC, connected state. In additional or alternative examples, the second state is a RRC idle state.

[0189] At block 2320, processing circuitry 2602 transmits, via communication interface 2606, a request for the communication device to transmit a message and instructions indicating what to include in the message. In some embodiments, the request is transmitted in response to receiving a setup / connection request from the communication device (e.g., in response to the communication device transitioning from the second state to the first state).

[0190] At block 2330, processing circuitry 2602 receives, via communication interface 2606, a first message from the communication device. In some embodiments, the first message from the communication device includes an indication of at least one of the configuration information; whether there is a portion of the configuration information that has not been transmitted to the network node; a number of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of each configuration in the configuration information; a latest session start indication of the configuration information; a latest session stop indication of the configuration information; a report that has not been transmitted to the network node; and an indication of a number of reports that have not been transmitted to the network node.

[0191] In additional or alternative embodiments, the first message includes an indication of all of the configuration information that was known by the network node when the communication device transitioned to the second state.

[0192] In additional or alternative embodiments, the configuration information includes at least one of a network instance of quality of experience, QoE, measurement configuration; and a network instance of radio access network-visible QoE, RVQoE, measurement configuration.

[0193] In additional or alternative embodiments, the configuration information includes a plurality of configurations. The first message includes an identifier of each configuration of the plurality of configurations. Each identifier of each configuration of the plurality of configurations includes at least one of a measConfigAppLayerld; and a QoE reference.

[0194] In additional or alternative embodiments, the message includes a MeasurementReportAppLayer radio resource control, RRC, message. In some examples, the MeasurementReportAppLayer RRC message is a first MeasurementReportAppLayer RRCmessage received from the communication device after the communication device transitioned from the second state to the first state.

[0195] In additional or alternative embodiments, receiving the message includes receiving the message subsequent to the communication device transitioning to the first state and prior to receiving any message from the communication device that includes at least one of: a quality of experience, QoE, report; and an indication of a session status associated with a QoE configuration.

[0196] At block 2340, processing circuitry 2602 receives, via communication interface 2606, a second message from the communication device. In some embodiments, the second message includes an indication of at least one of: whether there is a portion of the configuration information that has not been transmitted to the network node; a number of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of each configuration in the configuration information; a latest session start indication of the configuration information; a latest session stop indication of the configuration information; a report that has not been transmitted to the network node; and an indication of a number of reports that have not been transmitted to the network node.

[0197] In additional or alternative embodiments, the first message and / or the second message includes a plurality of messages. Receiving the first message and / or the second message comprises receiving a plurality of messages. Each message of the plurality of messages includes an indication of whether it is the last message of the plurality of messages.

[0198] Various operations from the flow chart of FIG. 23 may be optional with respect to some embodiments of network nodes and related methods.

[0199] Example Embodiments are described below.

[0200] Embodiment 1. A method of operating a communication device (2500), in a communications network, the method comprising: responsive to transitioning to a first state, generating (2250) a message to include an indication of at least one of: configuration information that was known by a network node that was serving the communication device when the communication device transitioned to a second state; whether there is a portion of the configuration information that has not been transmitted to the network node; a number of configurations in the portion of the configuration information that hasnot been transmitted to the network node; an identifier of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of each configuration in the configuration information; a latest session start indication of the configuration information; a latest session stop indication of the configuration information; a report that has not been transmitted to the network node; and an indication of a number of reports that have not been transmitted to the network node; and transmitting (2260) the message to the network node.

[0201] Embodiment 2. The method of Embodiment 1, wherein generating the message comprises generating the message to include an indication of all of the configuration information that was known by the network node that was serving the communication device when the communication device transitioned to the second state.

[0202] Embodiment 3. The method of Embodiments 2, wherein generating the message comprises: determining that the message includes all of the configuration information; and responsive to determining that the message includes all of the configuration information, adding the report to the message.

[0203] Embodiment 4. The method of any of Embodiments 1-3, wherein the configuration information comprises at least one of a network instance of quality of experience, QoE, measurement configuration; and a network instance of radio access network-visible QoE, RVQoE, measurement configuration.

[0204] Embodiment 5. The method of any of Embodiments 1-4, wherein the configuration information comprises a plurality of configurations, wherein generating the message comprises generating the message to include an identifier of each configuration of the plurality of configurations, and wherein each identifier of each configuration of the plurality of configurations comprises at least one of a measConfigAppLayerld; and a QoE reference.

[0205] Embodiment 6. The method of any of Embodiments 1-5, wherein the message comprises a MeasurementReportAppLayer radio resource control, RRC, message.

[0206] Embodiment 7. The method of Embodiment 6, wherein theMeasurementReportAppLayer RRC message is a first MeasurementReportAppLayer RRC message transmitted to the network node after transitioning to the first state.

[0207] Embodiment 8. The method of any of Embodiments 1-6, wherein the message comprises a plurality of messages, wherein generating the message comprises generating a plurality of messages, wherein each message of the plurality of messages includes an indication of whether it is the last message of the plurality of messages to be transmitted; and wherein transmitting the message comprises transmitting the plurality of messages.

[0208] Embodiment 9. The method of any of Embodiments 1-8, further comprising: storing (2210) all of the configuration information; subsequent to storing all of the configuration information, transitioning (2220) from the second state to the first state; and subsequent to transitioning from the second state to the first state, transitioning (2230) from the first state to the second state.

[0209] Embodiment 10. The method of any of Embodiments 1-9, wherein the first state is a radio resource control, RRC, connected state, and wherein the second state is a RRC idle state.

[0210] Embodiment 11. The method of any of Embodiments 1-10, wherein transmitting the message comprises transmitting the message subsequent to transitioning to the first state and prior to transmitting any message that includes at least one of: a quality of experience, QoE, report; and an indication of a session status associated with a QoE configuration.

[0211] Embodiment 12. The method of any of Embodiments 1-11, wherein the message comprises a first message, the method further comprising: responsive to transmitting the first message, generating (2270) a second message including an indication of at least one of: whether there is a portion of the configuration information that has not been transmitted to the network node; a number of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of configurations in the portion of the configuration information that has not been transmitted to the network node;an identifier of each configuration in the configuration information; a latest session start indication of the configuration information; a latest session stop indication of the configuration information; a report that has not been transmitted to the network node; and an indication of a number of reports that have not been transmitted to the network node; and transmitting (2280) the second message to the network node.

[0212] Embodiment 13. The method of any of Embodiments 1-12, further comprising: responsive to transmitting a setup request to the network node, receiving (2240) a request to transmit the message and instructions indicating what to include in the message, wherein generating the message comprises generating the message based on the instructions.

[0213] Embodiment 14. A method of operating a network node (2600), in a communications network, the method comprising: responsive to determining that a communication device has transitioned from a first state to a second state, releasing (2310) configuration information associated with the communication device; subsequent to releasing the configuration information, receiving (2330) a message from the communication device including an indication of at least one of: the configuration information; whether there is a portion of the configuration information that has not been transmitted to the network node; a number of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of each configuration in the configuration information; a latest session start indication of the configuration information; a latest session stop indication of the configuration information; a report that has not been transmitted to the network node; and an indication of a number of reports that have not been transmitted to the network node.

[0214] Embodiment 15. The method of Embodiment 14, wherein the message includes an indication of all of the configuration information that was known by the network node when the communication device transitioned to the second state.

[0215] Embodiment 16. The method of any of Embodiments 14-15, wherein the configuration information comprises at least one of: a network instance of quality of experience, QoE, measurement configuration; and a network instance of radio access network-visible QoE, RVQoE, measurement configuration.

[0216] Embodiment 17. The method of any of Embodiments 14-16, wherein the configuration information comprises a plurality of configurations, wherein the message includes an identifier of each configuration of the plurality of configurations, and wherein each identifier of each configuration of the plurality of configurations comprises at least one of: a measConfigAppLayerld; and a QoE reference.

[0217] Embodiment 18. The method of any of Embodiments 14-17, wherein the message comprises a MeasurementReportAppLayer radio resource control, RRC, message.

[0218] Embodiment 19. The method of Embodiment 18, wherein the MeasurementReportAppLayer RRC message is a first MeasurementReportAppLayer RRC message received from the communication device after the communication device transitioned from the second state to the first state.

[0219] Embodiment 20. The method of any of Embodiments 14-18, wherein the message comprises a plurality of messages, wherein receiving the message comprises receiving a plurality of messages, wherein each message of the plurality of messages includes an indication of whether it is the last message of the plurality of messages.

[0220] Embodiment 21. The method of any of Embodiments 14-20, wherein the first state is a radio resource control, RRC, connected state, and wherein the second state is a RRC idle state.

[0221] Embodiment 22. The method of any of Embodiments 14-21, wherein receiving the message comprises receiving the message subsequent to the communication device transitioning to the first state and prior to receiving any message from the communication device that includes at least one of:a quality of experience, QoE, report; and an indication of a session status associated with a QoE configuration.

[0222] Embodiment 23. The method of any of Embodiments 14-22, wherein the message comprises a first message, the method further comprising: subsequent to receiving the first message, receiving (2340) a second message including an indication of at least one of: whether there is a portion of the configuration information that has not been transmitted to the network node; a number of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of configurations in the portion of the configuration information that has not been transmitted to the network node; an identifier of each configuration in the configuration information; a latest session start indication of the configuration information; a latest session stop indication of the configuration information; a report that has not been transmitted to the network node; and an indication of a number of reports that have not been transmitted to the network node.

[0223] Embodiment 24. The method of any of Embodiments 14-23, further comprising: responsive to receiving a setup request from the communication device, transmitting (2320) a request to the communication device to transmit the message to the network node and instructions indicating what to include in the message.

[0224] Embodiment 25. A communication device (2500), configured to perform any of the operations of Embodiments 1-13.

[0225] Embodiment 26. A computer program comprising program code to be executed by processing circuitry (2502) of a communication device (2500), whereby execution of the program code causes the communication device to perform any of the operations of Embodiments 1-13.

[0226] Embodiment 27. A computer program product comprising a non-transitory storage medium (2510) including program code to be executed by processing circuitry (2502) of a communication device (2500), whereby execution of the program code causes the communication device to perform any of the operations of Embodiments 1-13.

[0227] Embodiment 28. A communication device (2500), the communication device comprising: processing circuitry (2502); and memory (2510) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the communication device to perform any of the operations of Embodiments 1-13.

[0228] Embodiment 29. A non-transitory computer-readable medium having instructions stored therein that are executable by processing circuitry (2502) of a communication device (2500) to cause the communication device to perform any of the operations of Embodiments 1- 13.

[0229] Embodiment 30. A network node (2600) configured to perform any of the operations of Embodiments 14-24.

[0230] Embodiment 31. A computer program comprising program code to be executed by processing circuitry (2602) of a network node (2600), whereby execution of the program code causes the network node to perform any of the operations of Embodiments 14-24.

[0231] Embodiment 32. A computer program product comprising a non-transitory storage medium (2606) including program code to be executed by processing circuitry (2602) of a network node (2600), whereby execution of the program code causes the network node to perform any of the operations of Embodiments 14-24.

[0232] Embodiment 33. A network node (2600), the network node comprising: processing circuitry (2602); and memory (2604) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the network node to perform any of the operations of Embodiments 14-24.

[0233] Embodiment 34. A non-transitory computer-readable medium having instructions stored therein that are executable by processing circuitry (2602) of a network node (2600) to cause the network node to perform any of the operations of Embodiments 14-24.

[0234] Embodiment 35. 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 communication device, 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 communication device, the network node having acommunication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of Embodiments 14-24 to transmit the user data from the host to the communication device.

[0235] Embodiment 36. The communication system of the previous embodiment, further comprising: the network node; and / or the communication device.

[0236] Embodiment 37. 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 receipt 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 Embodiments 14-24 to receive the user data from a communication device for the host.

[0237] Embodiment 38. The host of the previous 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 executing on the communication device, the client application being associated with the host application.

[0238] Embodiment 39. The host of any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

[0239] Embodiment 40. A method implemented by a host configured to operate in a communication system that further includes a network node and a communication device, the method comprising: at the host, initiating receipt of user data from the communication device, the user data originating from a transmission which the network node has received from the communication device, wherein the network node performs any of the steps of any of Embodiments 14-24 to receive the user data from the communication device for the host.

[0240] Embodiment 41. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

[0241] 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; anda network interface configured to initiate transmission of the user data to a cellular network for transmission to a communication device, wherein the communication device comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the communication device being configured to perform any of the operations of Embodiments 1-13 to receive the user data from the host.

[0242] Embodiment 43. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the communication device to transmit the user data to the communication device from the host.

[0243] Embodiment 44. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the communication device, the client application being associated with the host application.

[0244] Embodiment 45. A method implemented by a host operating in a communication system that further includes a network node and a communication device, the method comprising: providing user data for the communication device; and initiating a transmission carrying the user data to the communication device via a cellular network comprising the network node, wherein the communication device performs any of the operations of any of Embodiments 1-13 to receive the user data from the host.

[0245] Embodiment 46. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the communication device to receive the user data from the host application.

[0246] Embodiment 47. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the communication device, 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.

[0247] Embodiment 48. 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 communication device, wherein the communication device comprises a communication interface and processing circuitry, the communication interface andprocessing circuitry of the communication device being configured to perform any of the steps of Embodiments 1-13 to transmit the user data to the host.

[0248] Embodiment 49. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the communication device to transmit the user data from the communication device to the host.

[0249] Embodiment 50. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the communication device, the client application being associated with the host application.

[0250] Embodiment 51. A method implemented by a host configured to operate in a communication system that further includes a network node and a communication device, the method comprising: at the host, receiving user data transmitted to the host via the network node by the communication device, wherein the communication device performs any of the steps of any of Embodiments 1-13 to transmit the user data to the host.

[0251] Embodiment 52. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the communication device to receive the user data from the communication device.

[0252] Embodiment 53. The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the communication device, 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.

[0253] FIG. 24 shows an example of a communication system 2400 in accordance with some embodiments.

[0254] In the example, the communication system 2400 includes a telecommunication network 2402 that includes an access network 2404, such as a radio access network (RAN), and a core network 2406, which includes one or more core network nodes 2408. The access network 2404 includes one or more access network nodes, such as network nodes 2410a and 2410b (one or more of which may be generally referred to as network nodes 2410), or any other similar 3rd Generation Partnership Project (3 GPP) access node or non-3GPP access point. Moreover, as will be appreciated by those of skill in the art, the network nodes 2410 are not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integratedby a single vendor. Thus, it will be understood that the network nodes 2410 may include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 2402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 2402 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 2402, including one or more network nodes 2410 and / or core network nodes 2408.

[0255] Examples of an ORAN network node 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, such as a near-real time RAN control application (e.g., xApp) or a non-real time RAN automation application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Intents and content-aware notifications described herein may be communicated from a 3 GPP network node or an ORAN network node over 3GPP-defined interfaces (e.g., N2, N3) and / or ORAN Alliance-defined interfaces (e.g., Al, 01). Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance. The network nodes 2410 facilitate direct or indirect connection of user equipment (UE), such as by connecting wireless devices 2412a, 2412b, 2412c, and 2412d (one or more of which may be generally referred to as UEs 2412) to the core network 2406 over one or more wireless connections. The network nodes 2410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 2412a, 2412b, 2412c, and 2412d (one or more of which may be generally referred to as UEs 2412) to the core network 2406 over one or more wireless connections.

[0256] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables,or other material conductors. Moreover, in different embodiments, the communication system 2400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 2400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0257] The UEs 2412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 2410 and other communication devices. Similarly, the network nodes 2410 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 2412 and / or with other network nodes or equipment in the telecommunication network 2402 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 2402.

[0258] In the depicted example, the core network 2406 connects the network nodes 2410 to one or more hosts, such as host 2416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 2406 includes one more core network nodes (e.g., core network node 2408) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 2408. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0259] The host 2416 may be under the ownership or control of a service provider other than an operator or provider of the access network 2404 and / or the telecommunication network 2402, and may be operated by the service provider or on behalf of the service provider. The host 2416 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded 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, functions for controlling or otherwise interacting withremote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0260] As a whole, the communication system 2400 of FIG. 24 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low- power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0261] In some examples, the telecommunication network 2402 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 2402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 2402. For example, the telecommunications network 2402 may 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 Communication (mMTC) / Massive loT services to yet further UEs.

[0262] In some examples, the UEs 2412 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 2404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 2404. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0263] In the example, the hub 2414 communicates with the access network 2404 to facilitate indirect communication between one or more UEs (e.g., UE 2412c and / or 2412d) and network nodes (e.g., network node 2410b). In some examples, the hub 2414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 2414 may be a broadband router enabling access to the core network 2406 for the UEs. As another example, the hub 2414 may be a controller that sendscommands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 2410, or by executable code, script, process, or other instructions in the hub 2414. As another example, the hub 2414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 2414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 2414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 2414 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 2414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0264] The hub 2414 may have a constant / persistent or intermittent connection to the network node 2410b. The hub 2414 may also allow for a different communication scheme and / or schedule between the hub 2414 and UEs (e.g., UE 2412c and / or 2412d), and between the hub 2414 and the core network 2406. In other examples, the hub 2414 is connected to the core network 2406 and / or one or more UEs via a wired connection. Moreover, the hub 2414 may be configured to connect to an M2M service provider over the access network 2404 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 2410 while still connected via the hub 2414 via a wired or wireless connection. In some embodiments, the hub 2414 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 2410b. In other embodiments, the hub 2414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 2410b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0265] FIG. 25 shows a UE 2500 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rdGeneration Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0266] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0267] The UE 2500 includes processing circuitry 2502 that is operatively coupled via a bus 2504 to an input / output interface 2506, a power source 2508, a memory 2510, a communication interface 2512, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 25. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0268] The processing circuitry 2502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 2510. The processing circuitry 2502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 2502 may include multiple central processing units (CPUs).

[0269] In the example, the input / output interface 2506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device 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. An input device may allow a user to capture information into the UE 2500. Examples of an input device 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 directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0270] In some embodiments, the power source 2508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 2508 may further include power circuitry for delivering power from the power source 2508 itself, and / or an external power source, to the various parts of the UE 2500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 2508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 2508 to make the power suitable for the respective components of the UE 2500 to which power is supplied.

[0271] The memory 2510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 2510 includes one or more application programs 2514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 2516. The memory 2510 may store, for use by the UE 2500, any of a variety of various operating systems or combinations of operating systems.

[0272] The memory 2510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embeddedUICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘ SIM card.’ The memory 2510 may allow the UE 2500 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 2510, which may be or comprise a device-readable storage medium.

[0273] The processing circuitry 2502 may be configured to communicate with an access network or other network using the communication interface 2512. The communication interface 2512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 2522. The communication interface 2512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 2518 and / or a receiver 2520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 2518 and receiver 2520 may be coupled to one or more antennas (e.g., antenna 2522) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0274] In the illustrated embodiment, communication functions of the communication interface 2512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

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

[0276] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0277] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot 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 / moisture sensor, an electrical 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, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 2500 shown in FIG. 25.

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

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

[0280] FIG. 26 shows a network node 2600 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), NR NodeBs (gNBs)), 0-RAN nodes, or components of an 0-RAN node (e.g., intelligent controller, 0-RU, 0-DU, O-CU).

[0281] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0282] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0283] The network node 2600 includes a processing circuitry 2602, a memory 2604, a communication interface 2606, and a power source 2608. The network node 2600 may be composed of multiple physically separate components (e.g., a NodeB component and a RNCcomponent, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 2600 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 2600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 2604 for different RATs) and some components may be reused (e.g., a same antenna 2610 may be shared by different RATs). The network node 2600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 2600.

[0284] The processing circuitry 2602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 2600 components, such as the memory 2604, to provide network node 2600 functionality.

[0285] In some embodiments, the processing circuitry 2602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 2602 includes one or more of radio frequency (RF) transceiver circuitry 2612 and baseband processing circuitry 2614. In some embodiments, the radio frequency (RF) transceiver circuitry 2612 and the baseband processing circuitry 2614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 2612 and baseband processing circuitry 2614 may be on the same chip or set of chips, boards, or units.

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

[0287] The communication interface 2606 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 2606 comprises port(s) / terminal(s) 2616 to send and receive data, for example to and from a network over a wired connection. The communication interface 2606 also includes radio front-end circuitry 2618 that may be coupled to, or in certain embodiments a part of, the antenna 2610. Radio front-end circuitry 2618 comprises filters 2620 and amplifiers 2622. The radio front-end circuitry 2618 may be connected to an antenna 2610 and processing circuitry 2602. The radio front-end circuitry may be configured to condition signals communicated between antenna 2610 and processing circuitry 2602. The radio front-end circuitry 2618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 2618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2620 and / or amplifiers 2622. The radio signal may then be transmitted via the antenna 2610. Similarly, when receiving data, the antenna 2610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2618. The digital data may be passed to the processing circuitry 2602. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0288] In certain alternative embodiments, the network node 2600 does not include separate radio front-end circuitry 2618, instead, the processing circuitry 2602 includes radio front-end circuitry and is connected to the antenna 2610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2612 is part of the communication interface 2606. In still other embodiments, the communication interface 2606 includes one or more ports or terminals 2616, the radio front-end circuitry 2618, and the RF transceiver circuitry 2612, as part of a radio unit (not shown), and the communication interface 2606 communicates with the baseband processing circuitry 2614, which is part of a digital unit (not shown).

[0289] The antenna 2610 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 2610 may be coupled to the radio front-end circuitry 2618 and may be any type of antenna capable of transmitting and receiving data and / orsignals wirelessly. In certain embodiments, the antenna 2610 is separate from the network node 2600 and connectable to the network node 2600 through an interface or port.

[0290] The antenna 2610, communication interface 2606, and / or the processing circuitry 2602 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 2610, the communication interface 2606, and / or the processing circuitry 2602 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0291] The power source 2608 provides power to the various components of network node 2600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2600 with power for performing the functionality described herein. For example, the network node 2600 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 2608. As a further example, the power source 2608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0292] Embodiments of the network node 2600 may include additional components beyond those shown in FIG. 26 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 2600 may include user interface equipment to allow input of information into the network node 2600 and to allow output of information from the network node 2600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2600.

[0293] FIG. 27 is a block diagram of a host 2700, which may be an embodiment of the host 2416 of FIG. 24, in accordance with various aspects described herein. As used herein, the host 2700 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 2700 may provide one or more services to one or more UEs.

[0294] The host 2700 includes processing circuitry 2702 that is operatively coupled via a bus 2704 to an input / output interface 2706, a network interface 2708, a power source 2710, and a memory 2712. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGS. 25 and 26, such that the descriptions thereof are generally applicable to the corresponding components of host 2700.

[0295] The memory 2712 may include one or more computer programs including one or more host application programs 2714 and data 2716, which may include user data, e.g., data generated by a UE for the host 2700 or data generated by the host 2700 for a UE. Embodiments of the host 2700 may utilize only a subset or all of the components shown. The host application programs 2714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 2714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 2700 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 2714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0296] FIG. 28 is a block diagram illustrating a virtualization environment 2800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 2800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, thevirtualization environment 2800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0297] Applications 2802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0298] Hardware 2804 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2808a and 2808b (one or more of which may be generally referred to as VMs 2808), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 2806 may present a virtual operating platform that appears like networking hardware to the VMs 2808.

[0299] The VMs 2808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2806. Different embodiments of the instance of a virtual appliance 2802 may be implemented on one or more of VMs 2808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0300] In the context of NFV, a VM 2808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 2808, and that part of hardware 2804 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 2808 on top of the hardware 2804 and corresponds to the application 2802.

[0301] Hardware 2804 may be implemented in a standalone network node with generic or specific components. Hardware 2804 may implement some functions via virtualization.Alternatively, hardware 2804 may be part of a larger cluster of hardware (e.g. such as in a datacenter or CPE) where many hardware nodes work together and are managed via management and orchestration 2810, which, among others, oversees lifecycle management of applications 2802. In some embodiments, hardware 2804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 2812 which may alternatively be used for communication between hardware nodes and radio units.

[0302] FIG. 29 shows a communication diagram of a host 2902 communicating via a network node 2904 with a UE 2906 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 2412a of FIG. 24 and / or UE 2500 of FIG. 25), network node (such as network node 2410a of FIG. 24 and / or network node 2600 of FIG. 26), and host (such as host 2416 of FIG. 24 and / or host 2700 of FIG. 27) discussed in the preceding paragraphs will now be described with reference to FIG. 29.

[0303] Like host 2700, embodiments of host 2902 include hardware, such as a communication interface, processing circuitry, and memory. The host 2902 also includes software, which is stored in or accessible by the host 2902 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 2906 connecting via an over-the-top (OTT) connection 2950 extending between the UE 2906 and host 2902. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2950.

[0304] The network node 2904 includes hardware enabling it to communicate with the host 2902 and UE 2906. The connection 2960 may be direct or pass through a core network (like core network 2406 of FIG. 24) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0305] The UE 2906 includes hardware and software, which is stored in or accessible by UE 2906 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 2906 with the support of the host 2902. In the host 2902, an executing host application may communicate with the executing client application via the OTT connection 2950 terminating at the UE 2906 and host 2902. In providing the serviceto the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 2950 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 2950.

[0306] The OTT connection 2950 may extend via a connection 2960 between the host 2902 and the network node 2904 and via a wireless connection 2970 between the network node 2904 and the UE 2906 to provide the connection between the host 2902 and the UE 2906. The connection 2960 and wireless connection 2970, over which the OTT connection 2950 may be provided, have been drawn abstractly to illustrate the communication between the host 2902 and the UE 2906 via the network node 2904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0307] As an example of transmitting data via the OTT connection 2950, in step 2908, the host 2902 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 2906. In other embodiments, the user data is associated with a UE 2906 that shares data with the host 2902 without explicit human interaction. In step 2910, the host 2902 initiates a transmission carrying the user data towards the UE 2906. The host 2902 may initiate the transmission responsive to a request transmitted by the UE 2906. The request may be caused by human interaction with the UE 2906 or by operation of the client application executing on the UE 2906. The transmission may pass via the network node 2904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2912, the network node 2904 transmits to the UE 2906 the user data that was carried in the transmission that the host 2902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2914, the UE 2906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2906 associated with the host application executed by the host 2902.

[0308] In some examples, the UE 2906 executes a client application which provides user data to the host 2902. The user data may be provided in reaction or response to the data received from the host 2902. Accordingly, in step 2916, the UE 2906 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 2906. Regardless of the specific manner in which the user data was provided, the UE 2906 initiates, in step 2918, transmission of the user data towards the host 2902 via the network node 2904. In step 2920, in accordance with the teachings of the embodiments describedthroughout this disclosure, the network node 2904 receives user data from the UE 2906 and initiates transmission of the received user data towards the host 2902. In step 2922, the host 2902 receives the user data carried in the transmission initiated by the UE 2906.

[0309] One or more of the various embodiments improve the performance of OTT services provided to the UE 2906 using the OTT connection 2950, in which the wireless connection 2970 forms the last segment. More precisely, the teachings of these embodiments may enable an aligned understanding of UE stored QoE configurations between gNB and UE. In other words, the gNB that serves the UE upon transition from RRC IDLE to RRC CONNECTED can be aware of all the QoE configurations that the UE stored while in RRC IDLE mode.Consequently, uncertainties of the UE behavior and potentially varying behavior between UEs from different vendors can be eliminated. The risk of collision between identities used for QoE / RVQoE configuration already sent / applied by a UE, and identities the network determines for QoE / RVQoE configuration to be sent to the UE (e.g., collisions in the measConfigAppLayerld) can be eliminated. Moreover, the probability of the UE discarding the QoE measurement reports due to RRC message size restriction can be decreased.

[0310] In an example scenario, factory status information may be collected and analyzed by the host 2902. As another example, the host 2902 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 2902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2902 may store surveillance video uploaded by a UE. As another example, the host 2902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 2902 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0311] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 2950 between the host 2902 and UE 2906, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 2902 and / or UE 2906. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2950 passes; the sensors may participate in the measurementprocedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2904. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 2902. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2950 while monitoring propagation times, errors, etc.

[0312] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0313] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may 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 may be provided by the processing circuitry without executing instructions stored on a separate ordiscrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

Claims

CLAIMSWhat is claimed is:

1. A method of operating a communication device (2500), in a communications network, the method comprising: generating (2250) a message to include an indication of all configuration information that was known by a network node that was serving the communication device when the communication device transitioned to an idle state; and transmitting (2260) the message to the network node.

2. The method of Claim 1, wherein the indication of all of the configuration information comprises all of the configuration information that was known by the network node that was serving the communication device when the communication device transitioned to the idle state.

3. The method of any of Claims 1-2, wherein the message further includes at least one of: a latest session start indication of the configuration information; and a latest session stop indication of the configuration information.

4. The method of any of Claims 1-3, wherein generating the message comprises: determining that the message includes the indication of all of the configuration information; and responsive to determining that the message includes the indication of all of the configuration information, adding, to the message, one or more application layer measurement reports that have not been transmitted to the network node and that fit within the message.

5. The method of any of Claims 1-4, wherein the configuration information comprises at least one of: a network instance of quality of experience, QoE, measurement configuration; and a network instance of radio access network-visible QoE, RVQoE, measurement configuration.

6. The method of any of Claims 1-5, wherein the configuration information comprises a plurality of configurations,wherein generating the message comprises generating the message to include an identifier of each configuration of the plurality of configurations, and wherein each identifier of each configuration of the plurality of configurations comprises at least one of a measConfigAppLayerld; and a QoE reference.

7. The method of any of Claims 1-5, wherein the configuration information comprises a plurality of configurations, wherein generating the message comprises generating the message to include each configuration of the plurality of configurations.

8. The method of any of Claims 1-7, wherein the message comprises a MeasurementReportAppLayer radio resource control, RRC, message.

9. The method of Claim 8, wherein the MeasurementReportAppLayer RRC message is a first MeasurementReportAppLayer RRC message transmitted to the network node after transitioning to a connected state.

10. The method of Claim 9, wherein generating the first MeasurementReportAppLayer RRC message comprises: determining that the configuration information and one or more application layer measurement reports stored while the communication device was in the idle state exceed a maximum supported size of a first MeasurementReportAppLayer RRC message; generating the first MeasurementReportAppLayer RRC message to include one or more appLayerldlelnactiveConfig fields that together include the indication of all of the configuration information, the method further comprising: responsive to determining that the configuration information and the one or more application layer measurement reports stored while the communication device was in the idle state exceed the size of an RRC message, generating (2270) one or more subsequent MeasurementReportAppLayer RRC messages that each include one or more application layer measurement reports that were not included in the first MeasurementReportAppLayer RRC message; andtransmitting (2280) the one or more subsequent MeasurementReportAppLayer RRC messages to the network node.

11. The method of any of Claims 1-10, further comprising: storing (2210) all of the configuration information; subsequent to storing all of the configuration information, transitioning (2220) from a connected state to the idle state; and subsequent to transitioning to the idle state, transitioning (2230) from the idle state to the connected state.

12. The method of any of Claims 1-11, wherein transmitting the message comprises transmitting the message subsequent to transitioning to a connected state, wherein the connected state is a radio resource control, RRC, connected state, and wherein the idle state is a RRC idle state.

13. The method of any of Claims 1-12, wherein transmitting the message comprises transmitting the message subsequent to transitioning to a connected state and prior to transmitting any other message that includes at least one of: a quality of experience, QoE, report; and an indication of a session status associated with a QoE configuration.

14. The method of Claim 13, wherein the QoE report comprises at least one of: content of a field measReportAppLayerContainer in a MeasurementReportAppLayer RRC message; the MeasurementReportAppLayer RRC message; a MeasReportAppLayer IE in the MeasurementReportAppLayer RRC message; and content of the MeasReportAppLayer IE excluding a field ran-VisibleMeasurement in theMeasurementReportAppLayer RRC message.

15. The method of any of Claims 1-14, wherein the message comprises a first message, the method further comprising: responsive to transmitting the first message, generating (2270) a second message including an indication of at least one of: a report that has not been transmitted to the network node; anda number of reports that have not been transmitted to the network node; and transmitting (2280) the second message to the network node.

16. The method of any of Claims 1-15, further comprising: receiving (2240) a reconfiguration signal associated with establishment of a signaling radio bearer, the reconfiguration message including a request to transmit the message and instructions indicating what to include in the message, wherein generating the message comprises generating the message based on the instructions.

17. A method of operating a network node (2600), in a communications network, the method comprising: responsive to determining that a communication device has transitioned from a connected state to an idle state, releasing (2310) configuration information associated with the communication device; and subsequent to releasing the configuration information, receiving (2330) a message from the communication device including an indication of the configuration information.

18. The method of Claim 17, wherein the message includes an indication of all of the configuration information that was known by the network node when the communication device transitioned to the idle state.

19. The method of any of Claims 17-18, wherein the message further includes at least one o a latest session start indication of the configuration information; and a latest session stop indication of the configuration information.

20. The method of any of Claims 17-19, wherein the configuration information comprises at least one of: a network instance of quality of experience, QoE, measurement configuration; and a network instance of radio access network-visible QoE, RVQoE, measurement configuration.

21. The method of any of Claims 17-20, wherein the configuration information comprises a plurality of configurations,wherein the message includes an identifier of each configuration of the plurality of configurations, and wherein each identifier of each configuration of the plurality of configurations comprises at least one of a measConfigAppLayerld; and a QoE reference.

22. The method of any of Claims 17-20, wherein the configuration information comprises a plurality of configurations, and wherein the message comprises each configuration of the plurality of configurations.

23. The method of any of Claims 17-22, wherein the message comprises a MeasurementReportAppLayer radio resource control, RRC, message.

24. The method of Claim 23, wherein the MeasurementReportAppLayer RRC message is a first MeasurementReportAppLayer RRC message received from the communication device after the communication device transitioned from the idle state to the connected state.

25. The method of Claim 24, the method further comprising: subsequent to receiving the first MeasurementReportAppLayer RRC message, receiving one or more subsequent MeasurementReportAppLayer RRC messages that each include one or more application layer measurement reports that were not included in the first MeasurementReportAppLayer RRC message.

26. The method of any of Claims 17-25, wherein the connected state is a radio resource control, RRC, connected state, and wherein the idle state is a RRC idle state.

27. The method of any of Claims 17-26, wherein receiving the message comprises receiving the message subsequent to the communication device transitioning to the connected state and prior to receiving any message from the communication device that includes at least one of a quality of experience, QoE, report; and an indication of a session status associated with a QoE configuration.

28. The method of Claim 27, wherein the QoE report comprises at least one of: content of a measReportAppLayerContainer information element, IE, in a MeasurementReportAppLayer RRC message; the MeasurementReportAppLayer RRC message; a MeasReportAppLayer IE in the MeasurementReportAppLayer RRC message; and content of the MeasReportAppLayer IE excluding a ran-VisibleMeasurement IE in the MeasurementReportAppLayer RRC message.

29. The method of any of Claims 17-28, wherein the message comprises a first message, the method further comprising: subsequent to receiving the first message, receiving (2340) a second message including an indication of at least one of: a report that has not been transmitted to the network node; and a number of reports that have not been transmitted to the network node.

30. The method of any of Claims 17-29, further comprising: transmitting (2320) a reconfiguration signal associated with establishment of a signaling radio bearer, the reconfiguration message including a request to the communication device to transmit the message to the network node and instructions indicating what to include in the message.

31. A communication device (2500) configured to perform operations comprising: generating (2250) a message to include an indication of all configuration information that was known by a network node that was serving the communication device when the communication device transitioned to an idle state; and transmitting (2260) the message to the network node.

32. The communication device of Claim 29, the operations further comprising any of the operations of Claims 2-16.

33. A computer program comprising program code to be executed by processing circuitry (2502) of a communication device (2500), whereby execution of the program code causes the communication device to perform operations comprising: generating (2250) a message to include an indication of all configuration information thatwas known by a network node that was serving the communication device when the communication device transitioned to an idle state; and transmitting (2260) the message to the network node.

34. The computer program of Claim 33, the operations further comprising any of the operations of Claims 2-16.

35. A computer program product comprising a non-transitory storage medium (2510) including program code to be executed by processing circuitry (2502) of a communication device (2500), whereby execution of the program code causes the communication device to perform operations comprising: generating (2250) a message to include an indication of all configuration information that was known by a network node that was serving the communication device when the communication device transitioned to an idle state; and transmitting (2260) the message to the network node.

36. The computer program of Claim 35, the operations further comprising any of the operations of Claims 2-16.

37. A network node (2600) configured to perform operations comprising: responsive to determining that a communication device has transitioned from a connected state to an idle state, releasing (2310) configuration information associated with the communication device; and subsequent to releasing the configuration information, receiving (2330) a message from the communication device including an indication of the configuration information.

38. The network node of Claim 37, the operations further comprising any of the operations of Claims 18-30.

39. A computer program comprising program code to be executed by processing circuitry (2602) of a network node (2600), whereby execution of the program code causes the network node to perform operations comprising: responsive to determining that a communication device has transitioned from a connected state to an idle state, releasing (2310) configuration information associated with thecommunication device; and subsequent to releasing the configuration information, receiving (2330) a message from the communication device including an indication of the configuration information.

40. The computer program of Claim 39, the operations further comprising any of the operations of Claims 18-30.

41. A computer program product comprising a non-transitory storage medium (2606) including program code to be executed by processing circuitry (2602) of a network node (2600), whereby execution of the program code causes the network node to perform operations comprising: responsive to determining that a communication device has transitioned from a connected state to an idle state, releasing (2310) configuration information associated with the communication device; and subsequent to releasing the configuration information, receiving (2330) a message from the communication device including an indication of the configuration information.

42. The computer program of Claim 41, the operations further comprising any of the operations of Claims 18-30.

Images