Session management

Abstract

The present disclosure provides a method performed by a user equipment (UE) for managing a session associated with an application. The method comprises transmitting (402) a first message to a network node. The first message comprises: first information indicative of the session being stopped or paused in response to the session being paused; or second information indicative of the session being started or resumed in response to the session being resumed. Fig. 4 to accompany the abstract.

Description

SESSION MANAGEMENT TECHNICAL FIELD

[0001] The present disclosure relates to methods for managing a session associated withan application, and a user equipment and network node configured to perform those methods. BACKGROUND

[0002] Multicast and Broadcast Services (MBS) is a point-to-multipoint service in whichservices and data are transmitted from a single source entity to multiple recipients, either to allUser Equipments (UEs) in a broadcast service area, or to users in a multicast group as definedin the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 23.247 Version(V) 18.3.0.

[0003] A Fifth Generation (5G) New Radio (NR) system enables delivery of MBS in aresource-efficient way. Via the MBS, the same service and the same specific content data froma single source can be provided simultaneously to all User Equipments (UEs) in a geographicalarea (in the broadcast communication service) or to a dedicated set of UEs (in the multicastcommunication service). That is, all UEs in a broadcast area can receive the data, while not allUEs are authorized to receive the data in a multicast area.

[0004] A User Equipment (UE) can receive a broadcast MBS communication serviceindependently of its Radio Resource Control (RRC) state, while a multicast MBS service canbe received only by the UEs in an RRC_CONNECTED state. Multicast communication datacan 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 beapplied to both of these mechanisms, as specified in 3GPP TS 38.300 V18.0.0.

[0005] QoE measurements, also referred to as “application layer measurements”, havebeen specified for Long Term Evolution (LTE) and Universal Mobile TelecommunicationSystem (UMTS) and are being specified for New Radio (NR) in 3GPP Release 17. The purposeof the application layer measurements is to measure the end user experience when using certain applications.

[0006] The solutions in LTE and UMTS are similar with the overall principles as follows.Quality of Experience Measurement Collection (QMC) enables configuration of application layer measurements in the UE and transmission of QoE measurement result files (commonly referred to as QoE reports) to the network (e.g. Radio Access Network (RAN)) by means ofRRC signaling. The network (e.g. RAN) may then forward the QoE report to a MeasurementCollector Entity (MCE).

[0007] The network (e.g. RAN) is not aware of when an application session with anassociated QoE measurement session is ongoing, and this can have negative consequences. Forexample, a QoE configuration may be kept unnecessarily or released at the wrong time, theQoE reporting behavior may not be the most appropriate, resource utilization may not be optimized, and so on.

[0008] There thus currently exist certain challenge(s).SUMMARY

[0009] As mentioned above, there currently exist certain challenge(s) in relation to thenetwork (e.g. RAN) not being aware of when an application session with an associated QoE measurement session is ongoing. The current frameworks for QoE measurements and RVQoE measurements do not properly consider the consequences arising when an application session, on which QoE or RVQoE measurements are performed, is paused and later resumed.

[0010] Certain aspects of the disclosure and their embodiments may provide solutions tothese or other challenges.

[0011] Accordingly, in one aspect, there is provided a first method performed by a userequipment (UE) for managing a session associated with an application. The first methodcomprises transmitting a first message to a network node. The first message comprises: first information indicative of the session being stopped or paused in response to the session beingpaused; or second information indicative of the session being started or resumed in response tothe session being resumed.

[0012] In another aspect, there is provided a second method performed by a network nodefor managing a session associated with an application. The second method comprises receiving a first message from a UE. The first message comprises: first information indicative of thesession being stopped or paused in response to the session being paused; or second informationindicative of the session being started or resumed in response to the session being resumed.

[0013] In another aspect, there is provided a UE comprising processing circuitryconfigured to cause the UE to perform the first method described earlier.

[0014] In another aspect, there is provided a network node comprising processing circuitryconfigured to cause the network node to perform the second method described earlier.

[0015] In another aspect, there is provided a computer program comprising instructionswhich, when executed by processing circuitry of a UE, cause the UE to perform the first methoddescribed earlier.

[0016] In another aspect, there is provided a computer program comprising instructionswhich, when executed by processing circuitry of a network node, cause the network node to perform the second method described earlier.

[0017] In another aspect, there is provided a computer program product, embodied on anon-transitory machine-readable medium, comprising instructions which are executable byprocessing circuitry of a UE to cause the UE to perform the first method described earlier.

[0018] In another aspect, there is provided a computer program product, embodied on anon-transitory machine-readable medium, comprising instructions which are executable by processing circuitry of a network node to cause the network node to perform the second method described earlier. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] For a better understanding of the embodiments of the present disclosure, and toshow how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0020] Fig. 1 illustrates example MBS delivery methods;

[0021] Fig. 2 illustrates the signaling involved in a QoE measurement configuration;

[0022] Fig. 3 illustrates an example configuration and reporting of QoE measurements;

[0023] Fig. 4 is a flow chart illustrating a method in accordance with some embodiments;

[0024] Fig. 5 is a flow chart illustrating a method in accordance with some embodiments;

[0025] Fig. 6 illustrates the signaling involved in application layer measurementreporting;

[0026] Fig. 7 shows an example of a communication system in accordance with someembodiments;

[0027] Fig. 8 shows a UE in accordance with some embodiments;

[0028] Fig. 9 shows a network node in accordance with some embodiments; and

[0029] Fig. 10 is a block diagram illustrating a virtualization environment in whichfunctions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION

[0030] Some of the embodiments contemplated herein will now be described more fullywith 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.

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

[0032] Other objectives, features and advantages of the enclosed embodiments will beapparent from the following description.

[0033] Multicast and Broadcast Services (MBS) is a point-to-multipoint service in whichservices and data are transmitted from a single source entity to multiple recipients, either to allUser Equipments (UEs) in a broadcast service area, or to users in a multicast group as definedin the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 23.247 Version(V) 18.3.0.

[0034] A Fifth Generation (5G) New Radio (NR) system enables delivery of MBS in aresource-efficient way. Via the MBS, the same service and the same specific content data froma single source can be provided simultaneously to all User Equipments (UEs) in a geographicalarea (in the broadcast communication service) or to a dedicated set of UEs (in the multicastcommunication service). That is, all UEs in a broadcast area can receive the data, while not allUEs are authorized to receive the data in a multicast area.

[0035] A User Equipment (UE) can receive a broadcast MBS communication serviceindependently of its Radio Resource Control (RRC) state, while a multicast MBS service canbe received only by the UEs in an RRC_CONNECTED state. Multicast communication datacan 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 beapplied to both of these mechanisms, as specified in 3GPP TS 38.300 V18.0.0.

[0036] Fig. 1 illustrates MBS delivery methods as shown in 3GPP TS 23.247 V18.3.0.

[0037] For a multicast communication service, shared and individual delivery modes arespecified in 3GPP TS 23.247 V18.3.0. Between the Fifth Generation Core (5GC) and the NextGeneration Radio Access Network (NG-RAN), there are two possible delivery methods totransmit the MBS data, which are the following: -5GC Individual MBS Traffic Delivery Method: This method is (e.g. only)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 Protocol 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 User Plane Function(s) (UPF(s)) where individual delivery is performed via unicast transport over the N19mb interface. -5GC Shared MBS Traffic Delivery Method: This method is applied for bothbroadcast 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 the MB-UPF to the NG- RAN node via the N3mb interface.

[0038] The 5GC Shared MBS Traffic Delivery Method is required in all MBSdeployments. The 5GC Individual MBS Traffic Delivery Method is required to enable mobility when there is an NG-RAN deployment with non-homogeneous support of MBS.

[0039] Between the NG-RAN and the UE, two delivery methods are available for thetransmission of MBS data packets over radio interface, which are the following: ^Point-to-Point (PTP) Delivery Method: NG-RAN delivers separate copiesof MBS data packets over the radio interface to individual UE(s). ^Point-to-Multipoint (PTM) Delivery Method: NG-RAN delivers a singlecopy of MBS data packets over the radio interface to multiple UEs.

[0040] NG-RAN may use a combination of PTP and PTM to deliver an MBS data packetsto UEs.

[0041] An MBS Radio Bearer (MRB) will now be described. An MBS Session Resourcemay be associated with one or more MBS Quality of Service (QoS) flows, and each of thoseflows is associated with a QoS profile. A radio base station in NR (gNB) provides one or moremulticast MRB configurations to the UE via RRC signaling, as described in 3GPP TS 38.300 V18.0.0, clause 16.10.3. For a multicast session, the gNB may change the MRB type using RRC signaling. For a broadcast session, the gNB provides a broadcast MRB with oneDownlink (DL)-only Radio Link Control Unacknowledged Mode (RLC-UM) entity for PTMtransmission, i.e. only one type of MRB is specified at the moment for the broadcastcommunication transmission. Network and protocol architectures are described in detail in3GPP TS 38.300 V18.0.0, chapters 16.10.2 and 16.10.3.

[0042] Group scheduling and group paging will now be described. Group schedulingmechanisms for MBS delivery are described in 3GPP TS 38.300 V18.0.0, clause 16.10.4. ARadio Network Temporary Identifier (RNTI) is used for the group transmission where a UEcan receive different services using the same or different Group RNTI(s) (G-RNTI(s)) or GroupConfigured Scheduling RNTIs (G-CS-RNTIs), as defined in 3GPP TS 38.300 V18.0.0. NG-RAN performs certain functions to support MBS. They include management of MBS QoS flows, delivery of MBS data packets from the 5GC to multiple UEs via PTP or PTM,configuration of UE for MBS QoS flow reception at Access Stratum (AS) layer, controllingswitching between PTM and PTP delivery per UE, support for multicast session servicecontinuity during Xn and Next Generation (NG) handovers, and support for group paging atmulticast session activation over radio toward UEs in a Connected Mode Idle (CM-IDLE) stateand Connected Mode Connected (CM-CONNECTED) with RRC Inactive (RRC_INACTIVE)state. Xn is the interface between two gNBs.

[0043] An MBS interest indication will now be described. To ensure service continuityof MBS broadcast, a UE in an RRC_CONNECTED state may send an MBS interest indication to the gNB. The MBS interest indication can comprise the following information: ^a list of MBS frequencies that the UE is interested in receiving, e.g. sorted indecreasing order of interest; ^a priority between the reception of all listed MBS frequencies and thereception of any unicast bearer; ^a list of MBS broadcast services that the UE is interested in receiving, in caseSystem Information Block 21 (SIB21) is scheduled by the UE’s Primary Cell(PCell); and ^the UE’s priority to MBS broadcast versus unicast reception.

[0044] MBS interest indication information reporting can be implicitly enabled or disabledby the presence of SIB21.

[0045] Mobility support during an MBS session will now be described. Mobility supportfor service continuation when a UE is in an MBS session depends on whether a broadcast or multicast session is taking place, and on whether the source and target nodes support MBS. For the multicast MBS session, three cases can be distinguished: 1) handover from an NG- RAN node supporting MBS to a node not supporting MBS, 2) handover from an NG-RAN node not supporting MBS to a node supporting MBS, and 3) a handover from a node supporting MBS to another node supporting MBS.

[0046] In the Multicast MBS case:- When the Handover (HO) takes place from a node that supports MBS to anode that does not support MBS, or vice versa, the 5GC Shared MBS Traffic Delivery and 5GC Individual MBS Traffic Delivery Methods can co-exist temporarily upon handover. ^Mapping information about unicast QoS flows for multicast datatransmission and the information of associated multicast QoS flows are provided to an NG-RAN node. ^The delivery method is switched from 5GC Shared MBS TrafficDelivery to 5GC Individual MBS Traffic Delivery via establishing the N3 tunnel of the PDU Session for individual delivery. The Session Management Function (SMF) realizes that the target node does notsupport MBS. ^A General Packet Radio Service Tunneling Protocol (GTP) tunnelbetween the UPF and the MB-UPF for 5GC individual MBS traffic delivery is activated by the SMF and Multicast Broadcast Session Management Function (MB-SMF).- When the HO takes place from a Radio Access Network (RAN) node thatsupports MBS to another node that also supports MBS, if the shared delivery for the MBS session has not been established towards the target NG-RAN node, it uses an MB-SMF and an MB-UPF to establish the shared deliveryfor the MBS session. ^The PDU sessions, including the one associated with the MBSmulticast session and used for the 5GC individual MBS traffic delivery, are handed over to the target NG-RAN node.o The SMF triggers the mode switch from the individual to theshared delivery mode. oThe target node establishes the shared delivery for the MBSsession upon receiving the MBS session context. o5GC individual MBS traffic delivery is terminated by the 5GCand changed to the 5GC shared MBS traffic delivery.

[0047] In the Broadcast MBS case:- The UE may receive the same service in the target node (which supportsMBS) if the same MBS session is established with the 5GC shared MBS traffic delivery. -Currently, a case of when a UE is handed over to a node not supporting theMBS within the broadcast area, is not specified.

[0048] An overview of a Quality of Experience (QoE) framework will now be described.A regular QoE is also known as an “encapsulated QoE”.

[0049] QoE measurements, also referred to as “application layer measurements”, havebeen specified for Long Term Evolution (LTE) and Universal Mobile TelecommunicationSystem (UMTS) and are being specified for NR in 3GPP Release 17. The purpose of theapplication layer measurements is to measure the end user experience when using certain applications. Currently QoE measurements for streaming services and for Mobility TelephonyService 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 QoEmeasurements are specified and supported.

[0050] The solutions in LTE and UMTS are similar with the overall principles as follows.Quality of Experience Measurement Collection (QMC) enables configuration of application layer measurements in the UE and transmission of QoE measurement result files (commonly referred to as QoE reports) to the network by means of RRC signaling. An application layer measurement configuration (also called QoE measurement configuration or QoE configuration) that the RAN receives from the Operation and Maintenance (OAM / O&M)system, or the Core Network (CN) is encapsulated in a transparent container, which isforwarded to a UE in a downlink RRC message. An application layer measurement report (also called QoE report) that the UE Access Stratum (UE AS) or UE RRC layer receives from the UE’s higher layer (application layer) is encapsulated in a transparent container and sent to the network in an uplink RRC message. The RAN then forwards the QoE report to a Measurement Collector Entity (MCE).

[0051] In 3GPP Release 17, a new study item for “Study on NR QoE management andoptimizations for diverse services” for NR has been approved and concluded. The specification work for 3GPP Release 17 is still ongoing. The purpose of the study item is to study solutions for QoE measurements in NR. QoE management in NR will not just collect the quality of experience parameters of streaming services but also consider the typical performancerequirements of diverse services (e.g., Augmented Reality and / or Virtual Reality (AR / VR) andUltra Reliable Low Latency Communication (URLLC), of which at least VR seems to be covered in 3GPP Release 17). Based on the requirements of the services, the NR study also included more adaptive QoE management schemes that enable network optimization to satisfy user experience for diverse services.

[0052] The configuration data related to QoE measurements (in standard specificationstypically 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 Internet Protocol (IP) address of the entity to which the collected measurement results (i.e.the QoE reports) are to be sent (often referred to as a Measurement Collector Entity orMeasurement 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 are to be performed and details of how these measurements are to be performed. These instructions areintended for the application layer in the UE and are placed in a “container”, which the networkentities handling it (e.g. forwarding it to the UE, as well as the UE Access Stratum) cannotinterpret and do not try to read. The currently specified service types are MTSI and Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH), and in 3GPP Release 17, atleast service type Virtual Reality (VR) will be added. An area scope is defined in terms of cellsor 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.

[0053] QoE, and in particular QoE configuration, comes in two flavors: management-based (m-based) QoE configuration and signaling-based (s-based) QoE configuration. In bothcases, the QoE configuration originates in the OAM system or some other administrationalentity, e.g. dealing with customer satisfaction. All of these entities can be referred to herein asthe OAM system (where the OAM system may also comprise further entities). Withmanagement-based QoE (m-based QoE), the OAM system is typically interested in general QoE statistics from a certain area (which is configured as an area scope). The m-based QoEconfiguration is sent directly from the OAM 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 (andfulfills any other relevant condition, such as supporting the concerned application or servicetype) and sends the m-based QoE configuration to these UEs.

[0054] With s-based QoE, the OAM system is interested in collecting QoE measurementresults from a specific UE, e.g. because the user of the UE has filed a complaint. The OAMsystem sends the s-based QoE configuration to the Home Subscriber Server (HSS) (in the caseof an Evolved Packet System (EPS) or LTE) or the Unified Data Management (UDM) (in thecase of a Fifth Generation System (5GS) or NR), which forwards the QoE configuration to theUE’s current core network (CN) node, e.g. a Mobility Management Entity (MME) in EPS / LTEor an Access and Mobility Management Function (AMF) in 5G / NR. The CN node thenforwards the s-based QoE configuration to the RAN node that serves the concerned UE, and the RAN forwards it to the UE.

[0055] The service type indication and the container with the measurement instructionsare forwarded to the UE. 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 tracefunctionality and a Trace Identifier (ID) is associated with each QoE configuration. In NR, theQoE functionality will be 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 a Mobile Country Code (MMC) + Mobile Network Code (MNC) + QoEMeasurement Collection (QMC) ID, where the QMC ID may be a string of 24 bits) will beassociated with each QoE configuration. The QoE reference is included in the container withmeasurement instructions and sent to the RAN (i.e. the gNB in NR). For the communication between the gNB and the UE, the QoE reference is replaced by a shorter identifier denoted as measConfigAppLayerId, which is locally unique within a UE (i.e. there is a one-to-onemapping between a measConfigAppLayerId and a QoE reference for each QoE configurationprovided to a UE. The measConfigAppLayerId is stored in the UE AS and forwarded in anAttention (AT) command (which is the type of instructions used in the communication betweenthe UE’s modem part and the UE’s application layer) together with the service type indication and the container with the measurement instructions.

[0056] Reports with collected QoE measurement results (i.e. QoE reports) are sent fromthe UE application layer to the UE AS, which forwards them to the RAN, which forwards them to the MCE. These QoE measurement results are placed in a “container”, which isuninterpretable for the UE AS and the RAN. QoE reporting can be configured to be periodicor only sent at the end of an application session. Furthermore, the RAN can instruct the UE topause QoE reporting, e.g. in case the cell or gNB is in a state of overload.

[0057] The RAN is not aware of when an application session with an associated QoEmeasurement session is ongoing, and the UE AS is also not automatically aware of this. Toalleviate this, session start or stop indications can be introduced, which can be sent from theapplication layer in the UE to the UE AS and from the UE AS to the RAN. A session stop indication may be implicit in the form of a QoE report sent when the application session and the associated QoE measurement session are concluded.

[0058] The RAN may decide to release a QoE configuration in a UE at any time, as animplementation-based decision. Typically, it is done when the UE has moved outside an areaconfigured for the QoE measurements, commonly referred to as the area scope.

[0059] One opportunity provided by legacy solutions is also to be able to keep the QoEmeasurement for the whole session, even during a handover situation. It is also discussed toallow the UE to continue with the QoE measurements on an ongoing application session untilthe application session ends, even if the UE in the meantime moves out of the configured area scope.

[0060] QoE measurements and their results are intended for analysis in the O&M system(or in other entities that neither belong to the core network nor belong to the RAN) and subsequent possible non-real-time optimizations. The QoE reports are forwarded transparently by the RAN to a configured receiver, e.g. an MCE. However, the RAN could also benefit from receiving measurement results of metrics measured or collected at the application layer, e.g. as a complement to the more radio related measurements, i.e. the Radio Resource Management (RRM) measurements (e.g. Reference Symbol / Signal Received Power (RSRP), ReferenceSymbol / Signal Received Quality (RSRQ), Signal to Interference and Noise Ratio (SINR), etc.).For instance, the RAN could use such measurement results for real-time or semi-real-time adaptations or optimizations of the treatment of an ongoing application session, e.g. in terms of scheduling priorities.

[0061] For this reason, in 3GPP Release 17, the 3GPP introduced the so-called RANVisible QoE (RVQoE), which comprises periodic reporting of measured application layermetrics in a format that the RAN can understand. These metrics, denoted as RVQoE metricsare, in 3GPP Release 17, limited to QoE metrics, in particular the buffer level QoE metric forDASH (specified in 3GPP TS 26.247 V17.4.1, which in turn references annex D.4.5 in International Organization for Standardization / International Electrotechnical Commission(ISO / IEC) 23009-1, and represented in 3GPP TS 38.331 V18.0.0 (i.e. the RRC specification)as the AppLayerBufferLevel-r17 field) and the playout delay for media start-up QoE metric forDASH (specified in 3GPP TS 26.247 V17.4.1 and represented in 3GPP TS 38.331 V18.0.0(i.e. the RRC specification) as the playoutDelayForMediaStartup-r17 field). In addition tothese two RVQoE metrics, a MeasurementReportAppLayer message may contain a PDUsession ID list (in the form of the pdu-SessionIdList-r17 field) as part of the reported RVQoEinformation (i.e. in the RAN-VisibleMeasurements-r17 IE). Thus, an example of QoE isRVQoE, and these terms can be used interchangeably herein.

[0062] The configuration for QoE and RVQoE are performed via an RRCreconfiguration message containing the AppLayerMeasConfig Information Element (IE),whose Abstract Syntax Notation One (ASN.1) definition is shown below. The configurationof legacy QoE metrics is done via the measConfigAppLayerContainer IE, which specifiesthe configuration to the application-layer in the UE as an octet string (a compressedExtensible Markup Language (XML) file). RVQoE parameters are specified as part of theRAN-VisibleParameters IE. The following ASN.1 code is from 3GPP TS 38.331 V18.0.0.-- ASN1START-- TAG-APPLAYERMEASCONFIG-STARTAppLayerMeasConfig-r17 ::= SEQUENCE { measConfigAppLayerToAddModList-r17 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OFMeasConfigAppLayer-r17 OPTIONAL, -- Need NmeasConfigAppLayerToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OFMeasConfigAppLayerId-r17 OPTIONAL, -- Need Nrrc-SegAllowed-r17 ENUMERATED {enabled}OPTIONAL, -- Need R..., [[ Rrc-SegAllowedSRB5-r18 ENUMERATED {enabled}OPTIONAL, -- Need RidleInactiveReportAllowed-r18 ENUMERATED {enabled}OPTIONAL, -- Need R]] }MeasConfigAppLayer-r17 ::= SEQUENCE {measConfigAppLayerId-r17 MeasConfigAppLayerId-r17, measConfigAppLayerContainer-r17 OCTET STRING (SIZE (1..8000))OPTIONAL, -- Need NserviceType-r17 ENUMERATED {streaming, mtsi, vr, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M pauseReporting-r17 BOOLEANOPTIONAL, -- Need MtransmissionOfSessionStartStop-r17 BOOLEANOPTIONAL, -- Need Mran-VisibleParameters-r17 SetupRelease {RAN-VisibleParameters-r17}OPTIONAL, -- Cond ServiceType..., [[ reportingSRB-r18 ENUMERATED {srb4, srb5, spare2, spare1}OPTIONAL, -- Need MappLayerMeasPriority-r18 INTEGER (1..16)OPTIONAL, -- Need MappLayerIdleInactiveConfig-r18 AppLayerIdleInactiveConfig-r18 OPTIONAL -- Need M ]] } RAN-VisibleParameters-r17 ::= SEQUENCE { ran-VisiblePeriodicity-r17 ENUMERATED {ms120, ms240, ms480, ms640, ms1024}OPTIONAL, -- Need SnumberOfBufferLevelEntries-r17 INTEGER (1..8)OPTIONAL, -- Need RreportPlayoutDelayForMediaStartup-r17 BOOLEANOPTIONAL, -- Need M..., [[ ran-VisibleReportingSRB-r18 ENUMERATED {srb4, srb5, spare2, spare1} OPTIONAL -- Need M ]] }-- TAG-APPLAYERMEASCONFIG-STOP-- ASN1STOP

[0063] Herein, SRB denotes Signaling Radio Bearer. QoE measurements have beenspecified for LTE and UMTS, and they are being specified for NR. The purpose of the application layer measurements is to measure the end user experience when using certainapplications. Currently QoE measurements for streaming services and for MTSI services aresupported.

[0064] The solutions in LTE and UMTS are similar with the overall principles as follows.QoE measurement collection enables configuration of application layer measurements in theUE and transmission of QoE measurement result files by means of RRC signaling. An application layer measurement configuration received by the RAN from the O&M or the CN is encapsulated in a transparent container, which is forwarded to a UE in a downlink RRC message. Application layer measurement results received from UE’s higher layer are encapsulated in a transparent container and sent to network in an uplink RRC message. The result container is forwarded to a Trace Collector Entity (TCE).

[0065] In 3GPP Release 17, a study item for “Study on NR QoE management andoptimizations for diverse services” for NR has been carried out. The purpose of the study item was to study solutions for QoE measurements in NR. QoE management in NR will not just collect the experience parameters of streaming services but also consider the typical performance requirements of diverse services (e.g. AR / VR and URLLC).

[0066] The measurements may be initiated towards RAN in a management-based manner,i.e. from an O&M node in a generic way e.g. for an unspecific group of UEs, which may be selected by the RAN, or they may also be initiated in a signaling-based manner, i.e. initiatedfrom CN (on request from the O&M system) to RAN e.g. for a single specific UE. Theconfiguration of the measurement includes the measurement details, which are encapsulated in a container that is transparent to the RAN.

[0067] When initiated via the core network, the measurement is started towards a specificUE. For the LTE case, a “TRACE START” S1AP message is used, which carries, e.g. among other information, the details about the configuration of the measurement the application should perform (in the “Container for application layer measurement configuration” IE, transparent to the RAN) and the details to reach the TCE to which the measurements should be sent. S1AP is the S1 Application Protocol. S1 is the interface between the RAN and the CN in LTE.

[0068] Notifications of started and stopped application sessions with associated QoEmeasurement configurations are introduced, where these notifications are conveyed from the application layer in the UE and to the UE Access Stratum (i.e. the radio layers in the UE) and then forwarded to the network. This allows the network (at least the RAN) to be aware of when QoE measurements on an application session are ongoing. It is an implementation decision when the RAN stops or releases the measurement configuration. Typically, it is done when the UE has moved outside a certain area in which the measurements should be performed (also referred to as the area scope), if configured, or when the release is ordered by the O&M, directly towards the RAN or via the CN. Releasing the QoE configuration when the UE moves out of the area scope may however have to be flexible, adapting to the principle that ongoing QoE measurements on an ongoing application session should preferably be allowed to continue until the session has ended.

[0069] Fig. 2 is a signaling diagram from 3GPP TS 28.405 V18.4.0, which provides anoverview of the signaling involved in a management-based QoE measurement configuration, from the O&M system to the UE. Fig.2 corresponds to “Figure 4.2.1-1: QMC activation andreporting in LTE” in 3GPP TS 28.405 V18.4.0. However, Fig. 2 illustrates the basic signaling(without showing all details) involved in the management-based QoE measurementconfiguration, from the O&M system to the UE.

[0070] One opportunity provided by the legacy solution is to be able to keep the QoEmeasurement for the whole application session, even during a handover situation, so that reported QoE measurement data cover complete application sessions.

[0071] 3GPP TS 26.346 V17.4.0 defines QoE metrics for the Multimedia BroadcastMulticast Service (MBMS) in LTE, in addition to QoE metrics for DASH streaming that can also be used. Table 1 shows these metrics from 3GPP TS 26.346 V17.4.0. QoE Metric StreamingDownload Metric type delivery method delivery method Corruption duration metric ✓ MediaRebuffering duration metric ✓ SessionInitial buffering duration✓ Sessionmetric Successive loss of RTP packets ✓ MediaFrame rate deviation ✓ MediaJitter duration ✓ MediaContent Access / Switch Time ✓ SessionNetwork Resource ✓ ✓ SessionAverage codec bitrate ✓ MediaCodec information ✓ MediaLoss of Objects ✓ SessionDistribution of Symbol Count✓ SessionUnderrun for Failed Blocks Table 1

[0072] QoE measurements are configured in the UE by means of RRC signaling. Theconfiguration is done using the RRC message RRCReconfiguration containing the IEappLayerMeasConfig. 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 messageMeasurementReportAppLayer. The same RRC messages are used for both regular QoE and RAN visible QoE.

[0073] Fig. 3 illustrates a configuration and reporting of QoE measurements using RRCsignaling.

[0074] The following is the ASN.1 definition of the AppLayerMeasConfig IE (withassociated field descriptions), from 3GPP TS 38.331 V18.0.0. -- ASN1START-- TAG-APPLAYERMEASCONFIG-STARTAppLayerMeasConfig-r17 ::= SEQUENCE { measConfigAppLayerToAddModList-r17 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayer-r17 OPTIONAL, -- Need N measConfigAppLayerToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OFMeasConfigAppLayerId-r17 OPTIONAL, -- Need Nrrc-SegAllowed-r17 ENUMERATED {enabled}OPTIONAL, -- Need R..., [[ Rrc-SegAllowedSRB5-r18 ENUMERATED {enabled}OPTIONAL, -- Need RidleInactiveReportAllowed-r18 ENUMERATED {enabled} OPTIONAL, -- Need R ]] } MeasConfigAppLayer-r17 ::= SEQUENCE { measConfigAppLayerId-r17 MeasConfigAppLayerId-r17, measConfigAppLayerContainer-r17 OCTET STRING (SIZE (1..8000))OPTIONAL, -- Need NserviceType-r17 ENUMERATED {streaming, mtsi, vr, spare5, spare4,spare3, spare2, spare1} OPTIONAL, -- Need MpauseReporting-r17 BOOLEANOPTIONAL, -- Need MtransmissionOfSessionStartStop-r17 BOOLEANOPTIONAL, -- Need Mran-VisibleParameters-r17 SetupRelease {RAN-VisibleParameters-r17} OPTIONAL, -- Cond ServiceType]]} RAN-VisibleParameters-r17 ::= SEQUENCE { ran-VisiblePeriodicity-r17 ENUMERATED {ms120, ms240, ms480, ms640, ms1024}OPTIONAL, -- Need SnumberOfBufferLevelEntries-r17 INTEGER (1..8)OPTIONAL, -- Need RreportPlayoutDelayForMediaStartup-r17 BOOLEAN OPTIONAL, -- Need M ..., [[ ran-VisibleReportingSRB-r18 ENUMERATED {srb4, srb5, spare2, spare1}OPTIONAL -- Need M]] }-- TAG-APPLAYERMEASCONFIG-STOP-- ASN1STOPAppLayerMeasConfig field descriptions measConfigAppLayerContainer The field contains configuration of application layer measurements, see Annex L (normative) in TS 26.247

[0068] , clause 16.5 in TS 26.114

[0069] and TS 26.118

[0070] . pauseReportingThe field indicates whether the transmission of measReportAppLayerContainer is pausedor not. Value true indicates the transmission of measReportAppLayerContainer is paused;value false indicates the transmission of measReportAppLayerContainer is not paused.ran-VisibleParameters The field indicates whether RAN visible application layer measurements shall be reported or not. rrc-SegAllowedThis field indicates that RRC segmentation of MeasurementReportAppLayer is enabled. Itmay be present only if the UE supports RRC segmentation of theMeasurementReportAppLayer message in uplink (UL).serviceTypeIndicates the type of application layer measurement. Value streaming indicates Quality ofExperience Measurement Collection for streaming services (see TS 26.247

[0068] ), valuemtsi indicates Quality of Experience Measurement Collection for MTSI (see TS 26.114

[0069] ) and value vr indicates Quality of Experience Measurement Collection for VR service(see TS 26.118

[0070] ). The network always configures serviceType when application layermeasurements are initially configured and at fullConfig. transmissionOfSessionStartStopValue true indicates that the UE shall transmit indications when the measurement sessionin the application layer starts and stops. Value false indicates that the UE shall not transmitany session status indications. The UE transmits a session start indication uponconfiguration of this field set to value true if a session already has started in the applicationlayer.RAN-VisibleParameters field descriptions numberOfBufferLevelEntries The field contains the maximum number of buffer level entries that can be reported for RAN visible application layer measurements. This field is also used by application layer to calculate the interval of RAN visible buffer level measurement, which is equal to the periodicity of RAN visible application layer measurements reporting divided by numberOfBufferLevelEntries. ran-VisiblePeriodicity The field indicates the periodicity of RAN visible application layer measurements reporting. Value ms120 indicates 120 ms, value ms240 indicates 240 ms and so on. If this field isabsent, the periodicity of RAN visible application layer measurements reporting is the same as the reporting periodicity indicated in measConfigAppLayerContainer. reportPlayoutDelayForMediaStartup The field indicates whether the UE shall report Playout Delay for Media Startup for RAN visible application layer measurements.

[0075] The following is the ASN.1 definition of the MeasurementReportAppLayermessage (with associated field descriptions), from 3GPP TS 38.331 V18.0.0.-- ASN1START-- TAG-MEASUREMENTREPORTAPPLAYER-STARTMeasurementReportAppLayer-r17 ::= SEQUENCE { criticalExtensions CHOICE { measurementReportAppLayer-r17 MeasurementReportAppLayer-r17-IEs, criticalExtensionsFuture SEQUENCE {} } }MeasurementReportAppLayer-r17-IEs ::= SEQUENCE {measurementReportAppLayerList-r17 MeasurementReportAppLayerList-r17, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{}OPTIONAL} MeasurementReportAppLayer-v1800-IEs ::= SEQUENCE { measurementReportAppLayerList-r18 MeasurementReportAppLayerList-r18 OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL }MeasurementReportAppLayerList-r17 ::= SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasReportAppLayer-r17 MeasurementReportAppLayerList-r18 ::= SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasReportAppLayer-r18 MeasReportAppLayer-r17 ::= SEQUENCE { measConfigAppLayerId-r17 MeasConfigAppLayerId-r17, measReportAppLayerContainer-r17 OCTET STRING OPTIONAL, appLayerSessionStatus-r17 ENUMERATED {start, stop} OPTIONAL, ran-VisibleMeasurements-r17 RAN-VisibleMeasurements-r17 OPTIONAL }OPTIONAL, ... } RAN-VisibleMeasurements-r17 ::= SEQUENCE { appLayerBufferLevelList-r17 SEQUENCE (SIZE (1..8)) OF AppLayerBufferLevel-r17 OPTIONAL, playoutDelayForMediaStartup-r17 INTEGER (0..30000) OPTIONAL, pdu-SessionIdList-r17 SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF PDU- SessionID OPTIONAL, ..., [[ pdu-SessionIdList-r18 SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF QFI- List-r18 OPTIONAL ]] } AppLayerBufferLevel-r17 ::= INTEGER (0..30000) QFI-List-r18 ::= SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI-- TAG-MEASUREMENTREPORTAPPLAYER-STOP-- ASN1STOPMeasReportAppLayer field descriptions appLayerSessionStatus Indicates that an application layer measurement session in the application layer starts or ends. measReportAppLayerContainer The field contains the application layer measurement report container, see Annex L (normative) in TS 26.247

[0068] , clause 16.5 in TS 26.114

[0069] and TS 26.118

[0070] . ran-VisibleMeasurements The field contains the RAN visible application layer measurement report. RAN-VisibleMeasurements field descriptions appLayerBufferLevelList The field indicates a list of application layer buffer levels, and each AppLayerBufferLevel indicates the application layer buffer level in ms. Value 0 corresponds to 0ms, value 1 corresponds to 10ms, value 2 corresponds to 20 ms and so on. If the buffer level is larger than the maximum value of 30000 (5 minutes), the UE reports 30000. playoutDelayForMediaStartup Indicates the application layer playout delay for media start-up in ms. Value 0 corresponds to 0ms, value 1 corresponds to 1ms, value 2 corresponds to 2 ms and so on. If the playout delay for media start-up is larger than the maximum value of 30000ms, the UE reports 30000. pdu-SessionIdList Contains the identity of the PDU session, or the identities of the PDU sessions, used for application data flows subject to the RAN visible application layer measurements.

[0076] QFI denotes QoS Flow Identifier.

[0077] AT commands are used for communication between the AS (radio) layer and theapplication layer in the UE. The AT commands are defined in 3GPP TS 27.007 V18.4.0. The AT commands are used in QoE for transferring the configuration from the RRC layer in the UE AS to the application and for transferring reports from the application layer to the RRC layer. The AT command used for sending a QoE configuration (and / or an RVQoE configuration) from the UE AS to the UE application layer in NR is denoted as +CAPPLEVMCNR and is specified as follows in 3GPP TS 27.007 V18.4.0:Command Possible response(s)+CAPPLEVMCNR=[<n>] +CME ERROR: <err>+CAPPLEVMCNR? +CAPPLEVMCNR: <n>+CAPPLEVMCNR=? +CAPPLEVMCNR: (list of supported <n>s)Table 2Table 2 corresponds to “Table 8.84-1: +CAPPLEVMCNR parameter command syntax”in 3GPP TS 27.007 V18.4.0.A description of this command is as follows. This command allows control of the applicationlevel measurement configuration according to 3GPP TS 38.331

[0160] .The set command controls the presentation of the unsolicited result code+CAPPLEVMCNR: (list of [<CR><LF>,<meas_config_app_layer_id>,[<start-stop_measurement>,[<ran_visible_release_only>]],[<app- meas_config_file_length>,<app-meas_config- file>],[<transmission_of_session_start- end>],[<ran_visible_periodicity>],[<number_of_buffer_level_entries>],[<report_playout_delay_for_media_startup>],[<app-meas_service_type>]]s) providingdata for the configuration. Refer clause 9.2 for possible <err> values.Read command returns the current value of<n>. Test command returns values supported as a compound value. It is noted that defined values are omitted for brevity of the description, but more details canbe found in section 8.84 in 3GPP TS 27.007 V18.4.0.

[0078] The AT command used for sending QoE reports (and / or RVQoE reports) from theUE application layer to the UE AS in NR is denoted as +CAPPLEVMRNR and is specified as follows in 3GPP TS 27.007 V18.4.0:Command Possible response(s)+CAPPLEVMR=(list of+CME ERROR: <err><CR><LF>,<meas_config_app_layer_id>,[<ap p-meas_report_length>,<app- meas_report>],[<number-of-pdu- session_id-entries>,(list of <pdu- session_id>s)],[<number_of_buffer_level_ entries>,(list of <application_layer_buffer- level>s)],[<qoe_measurement_status>],[],[<numbe r-of-pdu-session_id-entries>,(list of <pdu-session_id>,<number-of-qfi- entries>,(<list of <qfi>s)s)]s) +CAPPLEVMRNR=? Table 3Table 3 corresponds to “Table 8.85-1: +CAPPLEVMRNR action command syntax” in 3GPPTS 27.007 V18.4.0. A description of this command is as follows. This command allows the Mobile Terminal(MT) to provide a list of application level measurement reports according to3GPP TS 38.331

[0160] . Refer clause 9.2 for possible <err> values.It is noted that defined values are omitted for brevity of the description, but more details canbe found in section 8.85 in 3GPP TS 27.007 V18.4.0.

[0079] In LTE, the corresponding AT commands are denoted respectively as+CAPPLEVMC and +CAPPLEVMR.

[0080] Video streaming over DASH will now be described. DASH is presently theindustry standard in delivering streaming video to end-user devices. The specification andrequirements of DASH are in ISO / IEC 23009 series. While the DASH standard specifies good practices around video quality adaptation and ground requirements to be fulfilled, it does notexactly specify the buffer strategy or the representation switch behavior. In ISO / IEC 23009-1,it is mentioned that the problem that a client would need to solve is formulated as choosing the representation of the next video segment such that constraints in terms of the current buffer level, estimated download rate, and the minimum volume of data required in the buffer to prevent stalling are satisfied.

[0081] However, in practice having only the minimum amount of data left over in thebuffer when the next segment has completed downloading should be avoided by all means as other factors such as delay, jitter, throughput variations, etc., may result in the client stalling.

[0082] Most on-demand DASH clients strive to maintain a buffer that is in the order oftens of seconds of playout time so that the streaming session can be shielded from any temporary fluctuation in the network. In academic literature, there are several disclosed ways to choose a representation for the next segment of the video, and how the sizing of the buffer should be handled so that the overall QoE is optimized. The most common among these is by applying two thresholds on the buffer, one to determine when to suspend content download and the other to determine when to resume a suspended content download, where the suspend threshold is always larger than the resume threshold.

[0083] The suspend content download threshold is chosen such that the client does notdownload too much content beforehand (in case that it may abandon the viewing session, or it might download too much data at a poor representation index) and the resume content download threshold is chosen such that it is not too small which would risk that uponencountering network issues, the video would stall. The difference between these twothresholds should also not be so large that long-term network changes affect the QoE.

[0084] In 3GPP Release 18, the 3GPP is specifying QoE measurements for MBS in anRRC_INACTIVE and RRC_IDLE state. To this end, the 3GPP working groups RAN3 andRAN2 have made a number of agreements and working assumptions related to QoEconfiguration or measurements for MBS in an RRC_INACTIVE and RRC_IDLE state. Ofinterest in the context of the disclosure are the agreements that in essence contain the following:^ MBS is regarded as a communication service carrying application sessionsof various service types. That is, in the context of QoE, MBS is not regarded as a service type. ^A UE can be configured to perform QoE measurements on applicationsessions carried by MBS in any RRC state (i.e. the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED state). Thus, a UE which is configured to perform QoE measurements on application sessions carried byMBS in the RRC_IDLE state shall retain the QoE configuration in the RRC_IDLE state (which is different from other QoE configurations which the UE releases when it transits to the RRC_IDLE state).^ Since the RAN (in contrast to the AMF in the core network) deletes the UEcontext (e.g. configuration and state information related to the UE) when the UE transits, e.g. is released by the RAN, to the RRC_IDLE state, the RAN’s configuration parameters related to the QoE configuration that the UE retains in the RRC_IDLE state (which are herein referred to as “the network version of the QoE configuration”, abbreviated “NW-QoE configuration”) must be re-instated in the gNB when a UE (which has retained a QoE configuration in the RRC_IDLE state) connects and transits from the RRC_IDLE to the RRC_CONNECTED state in a cell controlled by the gNB. NW-QoE configuration is the network version of the QoE configuration (of a QoE configuration which the UE retains in RRC_IDLE state), which is stored in the UE (the UE-based solution) or in the CN (the CN-based solution) while the UE is in an RRC_IDLE state, and re-instated in the gNB that the UE connects to when it subsequently transits from the RRC_IDLE to an RRC_CONNECTED state. There are two solutions being considered for this: oA UE-based solution. With this solution, the UE stores the NW-QoEconfiguration on behalf of the RAN while the UE is in the RRC_IDLE state, and sends the NW-QoE configuration to the gNB when the UE connects to the gNB and transits from the RRC_IDLE state to the RRC_CONNECTED state. This solution is the working assumption in RAN3. oA CN-based solution. With this solution, the NW-QoE configurationis stored in the CN (e.g. in the AMF) while the UE is in the RRC_IDLE state and is sent to the gNB that the UE connects to when it subsequently transits from the RRC_IDLE state to the RRC_CONNECTED state. oWhen the UE (which has retained and applied a QoE configuration inthe RRC_IDLE state) transits from the RRC_IDLE state to the RRC_CONNECTED state, the UE indicates an availability of any stored QoE report(s) (e.g. QoE reports that the UE has generated in theRRC_IDLE state). If the UE indicates the availability of such stored QoE report(s), the gNB may retrieve the QoE report(s) by establishing Signaling Radio Bearer 4 (SRB4), which triggers the UE to send the stored QoE report(s) to the gNB on SRB4.

[0085] 3GPP TS 32.422 V18.0.0 describes the activation mechanisms for Minimization ofDrive Tests (MDT) in NG-RAN in clause 4.1.1.9. Of interest in the context of the disclosure is the logged MDT measurements, which are also referred to in the 3GPP specifications as “logged measurements” and which are configured using theLoggedMeasurementConfiguration RRC message.

[0086] A management system sends a trace session activation request to the gNB. Thisrequest includes parameters for configuring UE measurements, such as any one or more of those listed below (note that at the same time not all the parameters may be present and thecriteria for which parameters may be present are described in clause 5 of 3GPP TS 32.422V18.0.0): -Job type- Area scope- List of measurements- Reporting Trigger- Report Interval- Report Amount- Event Threshold- Logging Interval- Logging Duration- Trace Reference- IP address of TCE- Anonymization of MDT data- Collection period for RRM measurements NR (only if any of M4, M5, M6or M7 measurements are requested) -Positioning method.- MDT Public Land Mobile Network (PLMN) List.- MDT report type (periodical logged or event-triggered measurement) forlogged MDT only -Event Threshold, Hysteresis and Time to trigger (present only if L1 event isconfigured for logged MDT)- MDT specific events list for event-triggered measurement for logged MDTonly -Area Configuration for neighboring cells for logged MDT only- Sensor information for logged MDT and immediate MDT

[0087] The logging duration (the loggingDuration IE) configures the start value of a timerT330 in the UE, which defines how long the UE must keep the logged measurement configuration. At expiration of the timer T330, the UE shall release the QoE configuration. However, the UE must still keep any stored (not yet sent) logged measurement reports for at least an additional 48 hours. That is, 48 hours after the expiration of timer T330, the UE is allowed to discard any stored unsent logged measurement reports.

[0088] The loggingDuration IE is mandatory in the logged measurement configuration(e.g. in the LoggedMeasurementConfiguration RRC message), and it has a range between 10minutes and 120 minutes, and there is no default value.

[0089] The timer T330 is started when the UE receives the logged measurementconfiguration (e.g. the LoggedMeasurementConfiguration RRC message).

[0090] There currently exist certain challenge(s). The current frameworks for QoEmeasurements and RVQoE measurements do not properly consider the consequences arising when an application session, on which QoE or RVQoE measurements are performed, is paused and later resumed.

[0091] The parameter used to configure a UE application to send indications when asession is started or ended, as well as the parameter used for sending such notifications, are defined to enable the UE application to notify the network at the start and end of a session. This clearly does not include pausing and resuming of a session, since pausing and resuming neither starts nor ends a session. Furthermore, the session start and end notifications refer to the QoE measurement session (i.e. not to the application session with which the QoE measurements are associated), which is what a user pauses and resumes.

[0092] Pausing and resuming of a DASH video is captured in the QoE metrics in 3GPPTS 26.247 V17.4.1. Pausing can be indicated as an inactivityType in the AvgThroughput metricin case the average throughput is zero during the entire measurement interval. When the userpauses the video playout, this is also reflected in that the stopreason parameter indicates “userrequest” in the PlayList (where “user request” also covers other possible user actions that maystop the continuous playout, such as seeking or jumping on the playout timeline). Resume ofthe paused DASH video is indicated as the value “Resume from pause” of the starttype parameter in the PlayList.

[0093] The PlayList contains useful information, which can be used to draw variousconclusions regarding the video session and the properties of the communication channel between the application server and the application client. However, none of this is available for the RAN in any RVQoE metric. Still, it is very relevant for the RAN to know if a video playout is paused. For instance, a UE playing a video that is being paused may be given lower scheduling priority than a UE with an actively playing video.

[0094] A further issue is that it is not clear how the application should treat a prolongedperiod of paused video versus an ended video session. A similar unclarity relates to the QoE or RVQoE measurement session associated with a video session that is paused for a short or long period of time. For instance, it is not clear how RVQoE reporting should be handled while the video session the RVQoE measurement pertains to is paused.

[0095] All of the above problems are equally relevant for VR as for DASH videoapplications.

[0096] Certain aspects of the disclosure and their embodiments may provide solutions tothese or other challenges. The disclosure relates to methods for notifying the network of pauseor resume events, methods for determining when to consider a paused session as ended, andmethods for QoE (e.g. RVQoE) reporting in conjunction with pause or resume of a session. The disclosure also relates to network actions when receiving pause or resume indications, additional UE behavior when a session is paused or resumed, mechanisms related to inter-node mobility aspects of pause or resume, methods related to pause or resume indications between entities in a split gNB architecture, and methods related to session paused indication when session delivery started or continued in a non-RRC_CONNECTED state.

[0097] Certain embodiments may provide one or more of the following technicaladvantage(s). In the manner described herein, open issues related to QoE or RVQoEmeasurements and pausing and resuming of an associated application session are resolved. Theteachings of certain embodiments may improve the data rate, latency, and power consumption.

[0098] Fig. 4 depicts a first method in accordance with particular embodiments. The firstmethod 4 may be performed by a UE or wireless device (e.g. the UE 712 or UE 800 as describedlater with reference to Figs. 7 and 8 respectively). The first method is for managing a sessionassociated with an application. The first method begins at step 402 with transmitting a firstmessage to a network node. The first message comprises: first information indicative of thesession being stopped or paused in response to the session being paused; or second informationindicative of the session being started or resumed in response to the session being resumed.

[0099] Transmitting the first message to the network node may comprise periodicallytransmitting the first message to the network node.

[0100] Transmitting the first message to the network node may comprise transmitting thefirst message to the network node in response to receiving third information indicative of thesession being paused or resumed. In this case, the first message may comprise: the firstinformation in response to the third information being indicative of the session being paused;or the second information in response to the third information being indicative of the sessionbeing resumed. Transmitting the first message to the network node in response to receivingthe third information may comprise transmitting the first message to the network node inresponse to an Access Stratum of the UE receiving the third information from an application layer of the UE. Transmitting the first message to the network node in response to receivingthe third information may comprise transmitting the first message to the network node inresponse to receiving the third information for a measurement configuration application layeridentifier (measConfigAppLayerId).

[0101] The third information may be a QoE report, such as a Radio Access NetworkVisible QoE, RVQoE, report. The QoE report being empty may be indicative of the sessionbeing paused. The QoE report comprising measurement results may be indicative of thesession being resumed.

[0102] The first message may be a measurement report application layer(MeasurementReportAppLayer) message, or the first message may be different from ameasurement report application layer (MeasurementReportAppLayer) message. The firstmessage may be dedicated to information related to management of the session.

[0103] Transmitting the first message may be prioritized over transmitting other messages.

[0104] The first message may be transmitted via a signaling radio bearer (SRB) of higherpriority than an SRB dedicated for sending Quality of Experience (QoE) reports, such as RadioAccess Network Visible QoE (RVQoE) reports.

[0105] The first message may comprise a session status field and the session status fieldmay comprise the first information or the second information. The first information or thesecond information may be a suffix in the session status field. The session status field may bean application layer session status (appLayerSessionStatus) field.

[0106] The first message may comprise a session status field and a different field maycomprise the first information or the second information.

[0107] The first information may be a first value and the second information may be asecond value. The first value and second value may be different.

[0108] The first information may be indicative of the session being paused.

[0109] The second information may be indicative of the session being resumed.

[0110] The session may comprise one or both of an application session of the applicationand a QoE measurement session on the application session of the application. The session maycomprise the application session and the QoE measurement session and the first message maybe transmitted to the network node in response to at least the QoE measurement session beingpaused or resumed. The QoE measurement session may be an RVQoE, measurement session.

[0111] The first message may comprise a QoE report (such as an RVQoE report), and theQoE report may comprise measurement results. The QoE report may comprise the first information or the second information. The QoE report may comprise one or more QoE metrics and the one or more QoE metrics may comprise the first information or the second information. The QoE report may comprise one or more QoE metrics and a different QoE metric maycomprise the first information or the second information. The one or more QoE metrics maycomprise one or both of a play list (PlayList) metric and an average throughput (AvgThroughput) metric.

[0112] The first method may comprise suspending transmission of a QoE report (such asan RVQoE) report comprising measurement results in response to the session being paused orin response to the session being paused for a time duration that exceeds a threshold.

[0113] The first method may comprise setting a timer in response to the session beingpaused and determining that the session has stopped in response to expiry of the timer. Thefirst method may comprise transmitting a second message to the network node. The secondmessage may comprise: fourth information indicative that the session has stopped in responseto determining that the session has stopped; or fifth information indicative that the session hasresumed in response to the session being resumed prior to expiry of the timer. The session may comprise an application session of the application and a QoE measurement session on theapplication session, and determining that the session has stopped may comprise determiningthat only the QoE measurement session has stopped or determining that both the applicationsession and the QoE measurement session have stopped. The first method may comprisestarting another QoE measurement session on the application session in response to theapplication session being resumed. The first method may comprise transmitting a thirdmessage to the network node. The third message may comprise sixth information indicative of the session being started or resumed.

[0114] The session may comprise an application session of the application and a QoEmeasurement session on the application session and the first method may comprise stoppingthe QoE measurement session in response to the application session being paused. The firstmethod may comprise transmitting a fourth message to the network node. The fourth messagemay comprise seventh information indicative of the session being stopped or paused. The first method may comprise starting another QoE measurement session on the application session inresponse to the application session being resumed. The first method may comprise transmittinga fifth message to the network node. The fifth message may comprise eighth informationindicative of the session being started or resumed.

[0115] The session may comprise an application session of the application and a QoEmeasurement session on the application session and the first method may comprise setting afirst timer and a second timer in response to the session being paused, stopping the QoEmeasurement session in response to expiry of the first timer, and determining that theapplication session has stopped in response to expiry of the second timer. The first methodmay comprise transmitting a sixth message to the network node in response to stopping theQoE measurement session. The sixth message may comprise ninth information indicative ofthe session being stopped or paused. The first method may comprise stopping the first timerin response to the second timer expiring prior to expiry of the first timer, and determining thatthe QoE measurement session has stopped. The first method may comprise transmitting aseventh message to the network node in response to determining that the QoE measurement session has stopped. The seventh message may comprise tenth information indicative of the session being stopped or paused.

[0116] The session may comprise an application session of the application and a QoEmeasurement session on the application session and the first method may comprise determiningthat the application session has stopped in response to the application session being paused foran implementation specific time, and determining that the QoE measurement session hasstopped in response to determining that the application session has stopped. The first methodmay comprise transmitting an eighth message to the network node in response to determiningthat the QoE measurement session has stopped. The eighth message may comprise eleventhinformation indicative of the session being stopped or paused.

[0117] The first method may comprise evaluating one or more conditions for the sessionin response to the session being resumed. Evaluating one or more conditions for the session in response to the session being resumed may comprise evaluating one or more conditions for the session in response to the session being resumed after being paused for a time duration thatexceeds a threshold. The session may comprise an application session of the application and aQoE measurement session on the application session, and evaluating one or more conditionsfor the session in response to the session being resumed may comprise evaluating one or more conditions for the session in response to both the application session and the QoE measurement session being resumed.

[0118] The first message may be transmitted to the network node when the UE connectsto the network node to prepare for or execute a conditional handover (CHO) of the UE to thenetwork node.

[0119] Transmitting the first message to the network node may comprise transmitting thefirst message to the network node in response to the UE transitioning from a Radio ResourceControl (RRC) inactive state or an RRC idle state to an RRC connected state.

[0120] The first message may comprise twelfth information indicative of one or both of atime at which the session began being paused and a duration of time since the session began being paused.

[0121] Fig. 5 depicts a second method in accordance with particular embodiments. Thesecond method 5 may be performed by a network node (e.g. the network node 710 or networknode 900 as described later with reference to Figs. 7 and 9 respectively). The second methodis for managing a session associated with an application. The second method begins at step502 with receiving a first message from UE. The first message comprises: first informationindicative of the session being stopped or paused in response to the session being paused; orsecond information indicative of the session being started or resumed in response to the session being resumed.

[0122] Receiving the first message from the UE may comprise periodically receiving thefirst message from the UE.

[0123] Receiving the first message from the UE may comprise receiving the first messagefrom the UE in response to the UE receiving third information indicative of the session being paused or resumed. In this case, the first message may comprise: the first information inresponse to the third information being indicative of the session being paused; or the secondinformation in response to the third information being indicative of the session being resumed. The first message may be received from an Access Stratum of the UE. Receiving the first message from the UE in response to the UE receiving the third information may comprise receiving the first message from the UE in response to the UE receiving the third information for a measurement configuration application layer identifier (measConfigAppLayerId). The third information may be a QoE report (such as an RVQoE report). The QoE report beingempty may be indicative of the session being paused. The QoE report may comprise measurement results is indicative of the session being resumed.

[0124] The first message may be a measurement report application layer(MeasurementReportAppLayer) message, or the first message may be different from ameasurement report application layer (MeasurementReportAppLayer) message.

[0125] The first message may be dedicated to information related to management of thesession.

[0126] Receiving the first message may be prioritized over receiving other messages.

[0127] The first message may be received via a signaling radio bearer (SRB) of higherpriority than an SRB dedicated for sending QoE reports, such as RVQoE reports.

[0128] The first message may comprise a session status field and the session status fieldcomprises the first information or the second information. The first information or the secondinformation may be a suffix in the session status field. The session status field may be anapplication layer session status (appLayerSessionStatus) field.

[0129] The first message may comprise a session status field and a different field maycomprise the first information or the second information.

[0130] The first information may be a first value and the second information may be asecond value. The first value and second value may be different.

[0131] The first information may be indicative of the session being paused.

[0132] The second information may be indicative of the session being resumed.

[0133] The session may comprise one or both of an application session of the applicationand a QoE measurement session on the application session of the application. The session maycomprise the application session and the QoE measurement session, and the first message maybe received from the UE in response to at least the QoE measurement session being paused orresumed. The QoE measurement session may be an RVQoE measurement session.

[0134] The first message may comprise a QoE report (such as an RVQoE report) and theQoE report may comprise measurement results. The QoE report may comprises the firstinformation or the second information. The QoE report may comprise one or more QoE metrics and the one or more QoE metrics may comprise the first information or the second information.The QoE report may comprise one or more QoE metrics and a different QoE metric maycomprise the first information or the second information. The one or more QoE metrics may comprise one or both of a play list (PlayList) metric and an average throughput (AvgThroughput) metric.

[0135] The first message may be received from the UE when the UE connects to thenetwork node to prepare for or execute a conditional handover (CHO) of the UE to the networknode.

[0136] Receiving the first message from the UE may comprise receiving the first messagefrom the UE in response to the UE transitioning from a Radio Resource Control (RRC) inactivestate or an RRC idle state to an RRC connected state.

[0137] The first message may comprise twelfth information indicative of one or both of atime at which the session began being paused and a duration of time since the session began being paused.

[0138] The network node may be a first network node and the first message may betransmitted from the first network node to a second network node during a handover of the UE from the first network node to the second network node.

[0139] The second method may comprise transferring the first information between aCentral Unit (CU) of the network node and a Distributed Unit (DU) of the network node.

[0140] The second method may comprise reducing a priority with which the UE isscheduled in response to the first message comprising the first information.

[0141] The second method may comprise increasing the priority with which the UE isscheduled in response to the first message comprising the second information.

[0142] The second method may comprise setting the priority with which the UE isscheduled based on a QoE metric for the UE.

[0143] The second method may comprise prioritizing processing of data corresponding tothe session in response to the first message comprising the first information.

[0144] The second method may comprise prioritizing delivery of data to the UE inresponse to detecting a degraded QoE for the session and the first message comprising the first information.

[0145] The second method may comprise releasing or inactivating a QoE configurationfor the session in the UE in response to the first message comprising the first information. The second method may comprise releasing the QoE configuration in the UE in response to the first message comprising the first information and in the absence of receiving, within a predefined time period after the first message is received, information indicative of the session being resumed.

[0146] The first information may be indicative of the session being paused and the secondmethod may comprise determining that the session is ongoing in the absence of information indicative of the session being stopped.

[0147] The second method may comprise releasing a Minimization of Drive Tests (MDT)configuration in the UE in response to the first message comprising the first information.

[0148] There is also provided a UE comprising processing circuitry configured to causethe UE to perform the first method described earlier. The UE may comprise at least one memory for storing instructions which, when executed by the processing circuitry of the UE, cause the UE to operate according to the first method.

[0149] There is also provided a network node comprising processing circuitry configuredto cause the network node to perform the second method described earlier. The network node may comprise at least one memory for storing instructions which, when executed by the processing circuitry of the network node, cause the network node to operate according to the second method.

[0150] There is also provided a system (or network) comprising the UE and the networknode.

[0151] There is also provided a computer program comprising instructions which, whenexecuted by processing circuitry of a UE, cause the UE to perform the first method.

[0152] There is also provided a computer program comprising instructions which, whenexecuted by processing circuitry of a network node, cause the network node to perform the second method.

[0153] There is also provided a computer program product, embodied on a non-transitorymachine-readable medium, comprising instructions which are executable by processingcircuitry of a UE to cause the UE to perform the first method.

[0154] There is also provided a computer program product, embodied on a non-transitorymachine-readable medium, comprising instructions which are executable by processing circuitry of a network node to cause the network node to perform the second method.

[0155] There are also disclosed QoE and RVQoE considerations when a session is paused.

[0156] Herein, the terms “UE”, “terminal equipment”, “wireless terminal”, and “terminal”can be used interchangeably. Also, herein, the terms “node” and “network node” can be used interchangeably. A network node can, for example, be a RAN node, a New Radio NodeB (gNB), an Evolved Universal Terrestrial Radio Access Network NodeB (eNB), an en-gNB, ang-eNB, a gNB-CU, a gNB-CU-Control Plane (CP), a gNB-CU-UP (User Plane), an eNB-CU,an eNB-CU-CP, an eNB-CU-UP, an Integrated Access and Backhaul (IAB)-node, an IAB-donor DU, an IAB-donor-CU, an IAB-DU, an IAB-Mobile Terminal (MT), an Open CentralUnit (O-CU), an O-CU-CP, an O-CU-UP, an O-DU, an Open Radio Unit (O-RU), an O-eNB, a Non-Real Time RAN Intelligent Controller (Non-RT RIC), a Real-Time RAN IntelligentController (RT-RIC), an OAM node, a Core Network node / function, a Cloud-based network function, or a Cloud-based centralized training node.

[0157] Herein, the terms “session start / stop indication”, “start / stop indication”, “sessionstatus indication” and “QoE measurement session status indication” can be usedinterchangeably. In some embodiments, the concept is extended to also cover sessionpause / resume or session paused / resumed indications.

[0158] Herein, the application layer in the UE can also be referred to as the “UEapplication layer” or simply the “application layer”.

[0159] Herein, the terms “QoE configuration”, “QoE parameters”, “QoE configurationinformation”, “application layer measurement configuration”, “application measurement configuration”, “QoE measurement configuration”, “QoE measurement and reporting configuration”, “application layer measurement and reporting configuration” and “QMCconfiguration” can be used interchangeably. The network, the UE AS and the UE applicationlayer may store various parts thereof. However, it is to be noted that the “QMC configurationfile” is not an equivalent term, and can instead refer to the part of the QoE configurationconsisting of an XML file containing instructions of QoE metrics to be collected, etc. Inaddition, the term “QoE information” may refer to either a QoE measurement configuration or QoE measurement report or the type of information that may be included in a QoE measurement report, session status indications or any other kind of QoE related information.

[0160] The entity performing the QoE measurements and other actions related to a QoEconfiguration, such as receiving QoE information from the UE AS, and / or sending QoEinformation to the UE AS, can be an application. The application resides on the applicationlayer in the UE, and hence it can also be said that the application layer performs these actions.In the disclosure, the performer of these various actions is sometimes said to be the application layer and sometimes said to be the application. All references to the application layer are with respect to the application layer of the UE.

[0161] The term “service” is often used as a short notation for “service type”, therefore“service” and “service type” can be seen as interchangeable unless explicitly stated otherwise or unless the context clearly implies another interpretation.

[0162] The disclosure applies to both signaling-based and management-based QoE orRVQoE measurements. It may also optionally be restricted to apply to only one of them.

[0163] A QoE configuration may include various configuration parameters (such as aninstruction on whether the UE should send session start or stop indications) as well as an XMLfile containing a configuration of QoE measurements to be performed and reported (e.g.indicating QoE metrics to be collected and reported). This XML file may herein be referredto with different terms, including at least “QMC configuration file”, “QMC configuration XML file”, “QoE configuration file”, “QoE configuration XML file”, “QMC configuration container” and “QoE configuration container”.

[0164] The functionality in a UE, which 3GPP has named Access Stratum (where there iscorresponding Access Stratum functionality in the network), can be herein referred to invarious 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”.

[0165] The terms “LTE” and “LTE node” can imply that a network node that serves theUE is serving the UE by using the LTE radio access technology on the air interface (Uu). The terms “NR” and “NR node” can 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).

[0166] The terms information element (IE) and field can be used more or lessinterchangeably herein. Also, the term parameter can sometimes be used to denote the sameconcept.

[0167] When writing message names of a communication protocol, two equivalentprinciples can be 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 XnAPmessage” can be equivalent, both referring to a message (i.e., “<message name>”) of acommunication protocol (i.e., “<protocol name>”), e.g., the HANDOVER REQUEST messageof the communication protocol XnAP. The same writing format equivalence can apply to othercommunication protocols, such as NGAP and F1AP. XnAP denotes the Xn ApplicationProtocol.

[0168] Parameters / IEs / fields used in ASN.1 code as well as in procedural text in the 3GPPRRC specification for 5G / NR, i.e. 3GPP TS 38.331 V18.0.0, can often be named with a suffixindicating the number of the release of the 3GPP standard the parameter / IE / field was introduced in (e.g. the suffix “-r17” for a parameter / IE / field introduced in Release 17 of the 3GPP standard). Parameters / IEs / fields following this naming convention are typically referredto both with and without the suffix, where the name including the suffix can be used in theASN.1 code (and thus defines the formal name from the ASN.1 compiler’s perspective), whilethe name without the suffix can used in running text, e.g. in field descriptions and proceduraltext. Relevant examples in the context of this disclosure include the parameters / IEs / fieldsAppLayerMeasConfig-r17 / AppLayerMeasConfig and MeasConfigAppLayer-r17 / MeasConfigAppLayer. Herein, both name variants may occur for variousparameters / IEs / fields.

[0169] The session start or stop indications introduced in the RRC protocol in Release 17of the 3GPP standard (in the form of the appLayerSessionStatus-r17 field, the use of which isconfigured by means of the transmissionOfSessionStartStop-r17 field) do not refer to the application session, but rather to the QoE measurement session associated with the applicationsession. However, if or when the terms “session data” or “session data flow” are mentioned,they can refer to the data or data flow of the application session with which the QoE measurement session is associated.

[0170] Herein, the term “flag” can refer to an indication, i.e. a parameter indicatingsomething. An indication referred to as a flag is typically, but not necessarily, an indicationthat can indicate one of only two possible values, e.g. implemented as a single-bit indicator.

[0171] The terms “QoE report” or “QoE measurement report”, when sent from a UE to anetwork node (e.g. gNB), may primarily refer to the content of ameasReportAppLayerContainer IE in a MeasurementReportAppLayer RRC message.However, sometimes the terms may refer to: oa MeasurementReportAppLayer RRC message;o a MeasReportAppLayer IE in a MeasurementReportAppLayer RRCmessage; oro the content of a MeasReportAppLayer IE, excluding the ran-VisibleMeasurements IE, in a MeasurementReportAppLayer RRC message.

[0172] The terms “RVQoE report” or “RVQoE measurement report”, when sent from aUE to a network node (e.g. gNB), may refer to the content of a RAN-VisibleMeasurements IEin a MeasurementReportAppLayer RRC message.

[0173] Unless stated otherwise, session pause / resume events may refer to the pausing andresuming of an application session and / or pausing and resuming of a QoE / RVQoE measurement session.

[0174] Herein, embodiments may primarily be described in terms of NR, but it is to beunderstood that they can also be applied to UMTS, LTE, and NR as well as future Radio AccessTechnologies (RATs), such as sixth generation (6G).

[0175] All embodiments and examples presented herein are non-limiting.

[0176] The following embodiments are described, which address certain issues:- How to notify the network about pause / resume events. This can includeany of the following:o Sending notifications similar to the appLayerSessionStatus-r17 fieldin a MeasurementReportAppLayer message. The sessionpause / resume notifications may be combined with the session status (i.e. start / stop) notifications (e.g. combined into a common IE) or may be specified in the form of a separate IE completely independent of the appLayerSessionStatus-r17 field.o Reuse QoE metrics containing information from which the sessionpause / resume status may be derived with some certainty. Thisconcerns mainly the PlayList QoE metric and the AvgThroughputQoE metric. oIntroduce a new RVQoE metric conveying session pause / resumeevents or status without a corresponding QoE metric. oLet session pause / resume events be triggering events for event-triggered RVQoE reporting.- When to consider a paused session as ended. This can involve various time-based methods, where the end of the application session and the QoE / RVQoE measurement session may be considered jointly or separately.- RVQoE reporting in conjunction with pause / resume. This can involve anyof the following: oThe UE application continues with the RVQoE reporting while theapplication session is paused. ^Herein, when the UE AS receives, from the application,RVQoE reports produced while the session is paused, the UE AS may (as one option) or may not (as another option) forward the RVQoE reports to the network. oThe UE application suspends the RVQoE reporting while theapplication is paused. oThe UE application suspends the RVQoE reporting if the time sincethe application session was paused exceeds a threshold. oThe principle for periodic QoE reporting is reused for periodicRVQoE reporting, i.e. a report is sent only if at least one of the report metrics has changed since the latest sent report. oThe above-mentioned principle for periodic QoE reporting is reusedfor RVQoE reporting while the session is paused, but with one ormore extension(s) of the condition for reporting, e.g. that the change of a certain metric must exceed a certain threshold to trigger reporting. Additional condition(s) may also be applied to combinations of metrics. oThe UE application reports a subset of or a different set of RVQoEmetrics and / or sends the RVQoE reports with a different periodicity while the application session is paused.- Network actions when receiving pause / resume indications. This caninclude possible network actions related to the UE’s scheduling priority (which, for example, may be reduced when the application session is indicated as paused), area scope (e.g. whether the network releases the QoE / RVQoE configuration if the UE is outside the area scope when the session is paused), and aligned MDT measurements (e.g. whether the network releases aligned MDT measurements when the session is paused).- Additional UE behavior when a session is paused or resumed. This caninclude various ways to consider the specified (e.g. in 3GPP TS 26.247 V17.4.1) principle that the UE evaluates any condition(s) for the QoE / RVQoE measurements only at the start of the application session. For example, it may include any of the following:o The UE may evaluate the condition(s) (if any) when the session isresumed. oThe UE may not evaluate the condition(s) when the session isresumed (i.e., the UE relies on the check of the condition(s) (if any) that was performed when the session started). oThe UE may evaluate the condition(s) (if any) when the session isresumed, if at least a certain time has elapsed since the session was paused, otherwise not. oThe UE’s behavior may depend on whether only the applicationsession is paused or both the application session and the QoE / RVQoE measurement session are paused. As an example, the UE mayevaluate the condition(s) (if any) if both the application session and the QoE / RVQoE measurement session are paused, but not if only the application session is paused.- Inter-node mobility aspects. This elaborates how session paused / notpaused status information can be conveyed to the target network node (e.g. gNB) in conjunction with inter-network node (e.g. gNB) mobility. Forconditional handover (CHO), the UE may inform the target network node(e.g. gNB) when it executes the conditional handover and connects to the target network node (e.g. gNB). For a regular handover, there may also bethe alternative that the information may be passed from the source networknode (e.g. gNB) to the target network node (e.g. gNB) during the handover preparation phase, e.g. in the HANDOVER REQUEST XnAP message. Apossible optimization is that the source network node (e.g. gNB) may send the session paused / not paused status to the target network node (e.g. gNB), or candidate target network node (e.g. gNB), during the handover, or conditional handover, preparation phase, and the UE may subsequentlysend the session paused / not paused status to the target network node (e.g. gNB) upon execution of the handover, or CHO, only if the status has changed since (e.g. slightly) before the UE received the HandoverCommand (i.e. the RRCReconfiguration to be applied in the target cell) orConditional Handover Command (i.e. the conditional RRCReconfiguration to be applied in the candidate target cell).- Transfer of session paused / resumed indications between entities of anetwork node in a split architecture deployment. This elaborates how session paused / resumed indications can be passed between a network node(e.g. gNB) Central Unit (CU) and a network node (e.g. gNB) DistributedUnit (DU), e.g. in a QoE INFORMATION TRANSFER F1AP message.F1AP denotes the Functional Split (F1) Application Protocol (AP). Thetransfer may or may not be preceded by a request from the network node (e.g. gNB) DU. It is further described how corresponding paused / resumed indications for alignment / correlation between radio related measurements (e.g. MDT measurements) and QoE / RVQoE measurements can be transferred between a network node (e.g. gNB) CU and a network node (e.g. gNB) DU.- Session paused indication when the session delivery started or continued ina non-RRC_CONNECTED state. This may include that, if a UE in anRRC_INACTIVE or RRC_IDLE state has a session (i.e. the session waseither started in the RRC_INACTIVE or RRC_IDLE state or was allowedto continue in the RRC_INACTIVE or RRC_IDLE state) and transits to an RRC_CONNECTED state, then, if the session is in a paused state, the UE may indicate this by sending a session paused indication to the network upon transiting to RRC_CONNECTED state. The UE may also providetime information (e.g. a timestamp) together with the session paused indication, which indicates when the session was paused and / or for how long it has been paused.

[0177] Methods for how to notify the network of pause / resume events

[0178] Session pause / resume events are related to session start / stop events, and it may beattractive to use similar means for notifying the network of session pause / resume events as for session start / stop events. In the current RRC specification (3GPP TS 38.331 V18.0.0), transmission of session start / stop indications are configured using thetransmissionOfSessionStartStop-r17 field in the MeasConfigAppLayer-r17 IE in anRRCReconfiguration message from the UE’s serving network node (e.g. gNB) to the UE. Ifconfigured to send session start / stop indications, the UE sends such indications using theappLayerSessionStatus-r17 field in a MeasurementReportAppLayer message.

[0179] One way to introduce session pause / resume notifications is to specify extendedversions of the transmissionOfSessionStartStop-r17 and appLayerSessionStatus-r17 fields(e.g. transmissionOfSessionStartStopPauseResume-rXX and appLayerSessionStatusExt-rXX),which would thus be used for configuration and reporting of start / stop events, pause / resume events, or both start / stop and pause / resume events.

[0180] An alternative to the above is to extend the use of the existingappLayerSessionStatus-r17 IE without any change of the structure of the IE, so that it is usedfor indicating both session start / stop and session pause / resume. Since the IE itself is notchanged, but only the interpretation of it is extended, the network will not be able to distinguish the differences between start and resume and between stop and pause. However, an advantage is that existing signaling can be reused. It may still be useful for the network to receive the information about a paused session as the network actions may be similar for a paused as for a stopped session. The UE’s behavior may depend on whether only the application session has been paused or both the application session and the QoE / RVQoE measurement session havebeen paused. As an example, if only the application session has been paused, while theQoE / RVQoE measurement session continues, then the UE may not transmit a session stopindication to the network. On the other hand, if the QoE / RVQoE measurement session ispaused (or stopped) when the application session is paused (possibly with some delay), the UE may transmit the session stop indication to the network.

[0181] A separate configuration parameter for transmission of pause / resume indicationsmay also be an alternative, e.g. using a transmissionOfPauseResume-rXX field. Note thatsession start / stop indications pertain to QoE measurement sessions rather than application sessions (when there is any difference), whereas a pause / resume indication may, as one option, pertain to the application session, since the QoE measurements may optionally continue (at least for a while) even when the application session is paused. Letting the pause / resume indications pertain to the QoE / RVQoE measurement session is another possible option. In another alternative, the codepoints of the configuration parameter may explicitly indicate whether the pause / resume applies to measurement or whether it applies to the application session. In a further alternative, codepoints for indicating start / stop of an application sessionmay be defined. As yet another alternative, two parameters can be introduced, one forindicating pause / resume of an application session and one for indicating pause / resume of a QoE / RVQoE measurement session.

[0182] In another embodiment, an empty QoE and / or RVQoE report (e.g. containing onlythe measConfigAppLayerId of the QoE / RVQoE configuration, but without any measurementresults) may be an indication that the session is paused. Also, a non-empty QoE and / or RVQoE report after a previously indicated pause may serve as an implicit indication that the session is resumed.

[0183] An alternative to the above-described notification method is to make pause / resumeevents configurable triggering events for RVQoE reporting. As one option, this can becombined with event-dependent RVQoE report content (i.e. where the content of the RVQoE report may depend on the event that triggered the transmission of the RVQoE report).

[0184] The content of an RVQoE report may include information about sessionpause / resume events. Transmission of an RVQoE report containing such information may be triggered by a session pause / resume event, but as another option, it may be sent as a periodic RVQoE report (in accordance with configuration).

[0185] In some embodiments, the message carrying the pause and / or resume indicationmay also carry an RVQoE report, even if the RVQoE report is not due at that time. The intention with including the RVQoE measurement results together with the indication, even if they are not due at a given moment, is to provide to the network a snapshot of RVQoE conditions so that the network can plan its actions appropriately.

[0186] Information about session pause / resume events pertaining to the applicationsession may be included in the QoE metrics for DASH streaming PlayList and AvgThroughput.Hence, one way to enable the inclusion of information about pausing / resuming of anapplication session in RVQoE reports can be to specify PlayList and / or AvgThroughputRVQoE metrics corresponding to the PlayList and / or AvgThroughput QoE metrics. ThePlayList RVQoE metric may be the full PlayList, i.e. a copy of the PlayList QoE metric, or asimplified version of the PlayList QoE metric, e.g. a PlayList RVQoE metric containing asubset of the parameters in the PlayList QoE metric.

[0187] An alternative to enabling inclusion of information related to pausing / resuming ofan application session in RVQoE reports, which still allows adhering to the principle of reusingspecified QoE metrics, is to specify pause / resume event indications as a QoE metric / parameterseparate from the PlayList and AvgThroughput metrics (i.e. separate / different from andpossibly more advanced than the existing means described earlier) and then specifycorresponding configuration and reporting parameters for RVQoE. Such a new QoEmetric / parameter for reporting may optionally be associated with timestamp information (either the real time, the media time or both). Such timestamp information may make off-line (non-real-time) analysis useful but may be less useful additional information for the RAN. Hence, as one option, the session pause / resume event information QoE parameter for reportingmay have associated timestamp information, but the corresponding session pause / resumeRVQoE parameter for RVQoE reporting may not have any associated timestamp information.

[0188] Another alternative is to specify pause / resume events as RVQoE metrics ormeasurement parameters independently of QoE metrics, i.e. without any corresponding QoEmetric in an associated QoE configuration. This can be done for an RVQoE configuration withan associated QoE configuration and / or for a separate “stand-alone” RVQoE configuration without an associated QoE configuration.

[0189] If session pause / resume event information is specified as information that may beincluded in RVQoE reports, it may be possible for the RAN to indicate in the RVQoEconfiguration, or in the overall QoE / RVQoE configuration (i.e., in the MeasConfigAppLayer-r17 IE) that the UE should collect and report the metric / parameter specified for such sessionstart / resume information.

[0190] As the session pause / resume indications can originate in the UE application layerand be transferred to the UE AS for further forwarding to the network (e.g. a network node,such as a gNB), a way to transfer these indications from the UE application layer to the UE ASmay have to be specified in the AT command framework (which is specified in 3GPP TS27.007 V18.4.0). One way to do this is to extend the +CAPPLEVMRNR AT command withthis information. Another way is to specify a new AT command for the transfer of thisinformation.

[0191] Another alternative for the transfer of pause / resume event information from the UEto the network that uses methods outside the QoE / RVQoE reporting paradigm is that whichmay use Medium Access Control (MAC) Control Element (CE) indications to indicatepause / resume event information. There may be value in decoupling pause / resume indication from other QoE / RVQoE mechanisms as using the MAC CE mechanism may mean that the RAN is notified of the user interaction much faster than it would get the information if it were incorporated in the RVQoE framework and carried in RRC messages, e.g. inMeasurementReportAppLayer messages.

[0192] Another alternative for sending the pause / resume indications may be to send theseindications separately from the MeasurementReportAppLayer (which is as of today sent onSRB4), but rather in a new RRC IE or a new RRC message dedicated to sending informationrelated to management of QoE / RVQoE measurement sessions that can be sent on an SRB ofhigher priority. Given that the information about pause / resume may potentially influence UEand data scheduling, it may be beneficial to deliver this information to the RAN as quick aspossible.

[0193] Methods for when to consider a paused session as ended

[0194] An issue in the context of pausing of a (e.g. video / VR) session is that it is not clearhow the application and / or network is to treat a (e.g. prolonged) period of a paused (e.g.video / VR) session versus an ended (e.g. video / VR) session, in particular in the context ofQoE / RVQoE measurements. For instance, it is useful to know after how long a time theapplication and / or network is to regard the session as ended. It is also useful to know how theapplication is to indicate a (e.g. prolonged) period of paused (e.g. video / VR) session versus anended (e.g. video / VR) session to the network.

[0195] When addressing this issue, the approach may be that it is be a joint decision forthe application session and the QoE / RVQoE measurement session or a separate decisions forthe application session and the QoE / RVQoE measurement session. For example, any of the following is possible: -When a timer (which may be started when the application session is paused)expires, the application layer may regard both the application session and the QoE / RVQoE measurement session as ended (and may send a session stop indication, if configured to do so).- When a timer (which may be started when the application session is paused)expires, the application layer may regard the QoE / RVQoE measurement session as ended (and may send a session stop indication, if configured todo so), but the application session (and the application layer’s perception of the application session or the status of the application session) may not beaffected. If the application session is subsequently resumed, a newQoE / RVQoE measurement session may be started (and a session startindication may be sent, if the application layer is configured to do so).- When the application session is paused, the UE application may end theQoE / RVQoE measurement session (and may send a session stop indication, if configured to do so). If the application session is subsequently resumed, the UE application may start a new QoE / RVQoE measurement session associated with the resumed application session (and may send a session start indication, if configured to do so).- When a first timer expires, the QoE / RVQoE measurement session may beended (and a session stop indication is sent, if configured to do so). When a second timer expires, the application layer may regard the application session as ended. If the second timer expires while the first timer is still running, the application layer may stop the first timer and regard the QoE / RVQoE measurement session as ended too (and may send a session stop indication, if configured to do so). Both the first and the second timer may be started when the application session is paused.- The application layer may determine in an implementation specific way thatthe application session has ended, and then it may regard the QoE / RVQoE measurement session as ended too (and may send a session stop indication, if configured to do so).- The methods above can be used with or without the UE sending the pauseindication to the network. For example, once the session is paused, a timer governing when the session is regarded as ended may be started, the UEmay (as one option) or may not (as another option) send a pause indication to the network. Once the timer expires, the UE may send the stop indication to the network. If the session resumes prior to expiration of the timer, the UE may send a resume indication (optionally only if a pause indication waspreviously sent), or QoE / RVQoE reporting may merely continue (in case QoE / RVQoE reporting was paused).

[0196] Another approach can be that, when the application session is paused, theQoE / RVQoE measurement session may be paused too, or the QoE / RVQoE measurementsession may be paused after a timer (which may be started when the application session ispaused) expires, and if / when the application session is resumed (and the QoE / RVQoE measurement has not ended in accordance with any of the above options), the QoE / RVQoEmeasurement session may be resumed too. If this alternative is used, the pause / resumeindications may pertain to the QoE / RVQoE measurement session instead of the application session.

[0197] Another approach (or an approach which can be used together with the previousapproaches) can be that, when the application session is paused, the QoE / RVQoE measurementsession may be ended, and the corresponding QoE / RVQoE configuration may be inactivated(or paused), and if / when the application session is resumed, the corresponding QoE / RVQoEconfiguration may be resumed, and the QoE / RVQoE measurement session may be resumedtoo.

[0198] If the existing appLayerSessionStatus-r17 field is reused for transmission ofsession pause / resume indications, the UE may send the session start / stop indication directly when the session is paused / resumed, or after the application session has been paused / resumed for a time period exceeding a configured or specified (in a standard specification) or UEimplementation specific threshold. The different options in the list above may be used fordefining when the UE shall send the session / start stop indications.

[0199] Another approach (which may be used independently or partly together withprevious solutions) that may be used for determining that a session (either a QoE / RVQoE measurement session or an application session) has ended (e.g. after previously having beenpaused) when there is a lack of explicit indication thereof can be based on observing othermetrics connected either to the application or the transport session. In this case, the metricsconnected to the application may be that the playback session is in the foreground, or the user is present in front of the device although the playback session is paused, etc.

[0200] Other relevant metrics above to determine the end of a session that has previouslybeen paused can be the device activity on the transport session. As discussed before, a session that has been paused may continue downloading data corresponding to the same session, and as long as such download is active, it may not be reasonable to assume that the session hascompleted / ended. From a network element’s perspective, e.g. a network node (such as a gNB),this approach may imply observing the activity on the Transmission Control Protocol or UserDatagram Protocol (TCP / UDP) ports associated with the application session. When portscorresponding to the session are closed (after a prior pause indication had been received), it may be safe to assume that the application session has now ended. A suitable timeout may also be added after the time at which a port may be closed to ensure that the application opens no further new ports.

[0201] Methods for RVQoE reporting in conjunction with pause / resume

[0202] It may be unnecessary to measure and report QoE related information while thesession is essentially put on hold (i.e. paused). Hence, in one embodiment, QoE reporting andRVQoE reporting may be suspended while the measured application session is paused, e.g.after notifying the network that the session is paused. Optionally, the notification of the session being paused may be sent only if RVQoE measurements are configured. In a variation of thisembodiment, only RVQoE reporting may be suspended, while QoE reporting continues. Anysuspended QoE reporting and / or RVQoE reporting may be resumed if / when the applicationsession is resumed.

[0203] The embodiment above is based on the assumption that QoE / RVQoE measurementand reporting is unnecessary while the application session that is measured on is paused.However, this may not be the case. For instance, the application client may keep downloading content to fill up the buffer while the session / video is paused, and the resulting increased buffer level may be of interest for the network to know. Hence, in another embodiment, QoE reporting and RVQoE reporting may continue while the application session that is measured on is paused.

[0204] Another embodiment may be seen as a compromise between the two embodimentsabove. In this embodiment, the UE application may continue with the RVQoE reporting acertain time after the application session that is measured on has been paused. However, whenthe time since the application session that is measured on was paused exceeds a configured,specified or implementation-specific threshold, the UE application may suspend the RVQoEreporting. Alternatively, the UE application may keep generating RVQoE reports and keepdelivering them to the UE AS, but the UE AS may discard them instead of forwarding them tothe network while the session is paused. If the RVQoE reporting is suspended, it may be resumed if / when the application session is resumed.

[0205] The above embodiments include options involving configuration from the network.The embodiments with such options assume that the UE is instructed how to act by the network.In another embodiment, the UE application may decide whether to continue or pause reportingwhen a session is paused, based on whether the data for the session continues to arrive during the pause or not.

[0206] In another embodiment, QoE / RVQoE measurement and reporting may continueeven during the period during which the application session may be paused. However, the application behavior may be well-defined where the application will stay active, e.g.downloading / buffering future session data (e.g. video content) until it satisfies a certainconstraint (such as 10 seconds of additional video in a buffer after a pause event), and uponsatisfaction of the constraint, the application session may be considered complete, and the application may trigger the release of RVQoE reporting for the concerned session with the corresponding indication to the network.

[0207] In yet another embodiment, it may be assumed that the network does not have tobe informed of application layer matters, e.g. QoE / RVQoE measurement results, while the application session is paused, provided that the network is informed of the session pause event. Then, in this embodiment, it is sufficient that the UE reports the relevant QoE / RVQoE metrics when the application session is resumed, e.g. when the UE notifies the network of the session resume event (while reporting is suspended between the pause and resume events). In avariation of this embodiment, only RVQoE reporting may be suspended between the sessionpause and session resume events, while QoE reporting may continue. In another variation ofthe embodiment, a QoE and / or RVQoE report may be sent when the application session that ismeasured on is resumed (e.g. when the UE notifies the network of the session resume event) only if relevant QoE / RVQoE metrics (e.g. the buffer level) have changed between the session pause and session resume events (as one option), or (as another option) only if relevant QoE / RVQoE metrics (e.g. the buffer level) have change significantly, e.g. with a significant amount.

[0208] There is a specified principle for periodic QoE reporting (see, for example, 3GPPTS 26.247 V17.4.1) that states that the application should not send a scheduled periodic QoE report if none of the metrics to be included in the report has changed since the last sent report.In one embodiment, that principle may be reused for periodic RVQoE reporting too, and thatwill result in appropriate RVQoE reporting behavior while the application session that ismeasured on is paused. Optionally, the condition for sending an RVQoE report may be morerestrictive, e.g. requiring that a certain metric, or at least one of a certain set / subset of metrics, has changed since the last sent RVQoE report.

[0209] As an extension to the above, thresholds (or other conditions) can be placed on themeasured / reported metrics, either on individual metrics or on a combination of metrics, todetermine when sending a report while the application is paused. This may be beneficial tohave in addition to other constraints as described above. For example, instead of just requiring that at least a metric has changed to trigger an RVQoE report, the condition for triggering an RVQoE report may, for example, be that: -a certain metric, or at least one of a certain set of metrics has changed morethan a certain configured or specified (in a standard) threshold; -at least N out of a set of M metrics have changed (where M and N areintegers and M > 0 and 0 < N ≤ M); -all of a certain set of metrics have changed; or- all of a certain set of metrics have changed more than a certain configuredor specified (in a standard) threshold.

[0210] As another extension applicable to several situations described above, the UEapplication may only report a subset or a different set of metrics with a different periodicity while the application session is paused.

[0211] In all of the above embodiments, options, alternatives, variations and variantswhere RVQoE reporting is suspended, this suspension may be implemented and executed atthe application layer (i.e. the application may not generate and / or deliver any RVQoE reportsto the UE AS). Alternatively, the suspension of the RVQoE reporting may be implementedand executed / enforced in the UE AS. That is, the application may keep generating RVQoEreports and keep delivering them to the UE AS, but the UE AS may discard them instead offorwarding them to the network while the RVQoE reporting is suspended.

[0212] Network actions when receiving pause / resume indications

[0213] In some embodiments, the network (e.g. a network node (e.g. gNB), such as theUE’s serving network node), may initiate certain actions when it receives a session pause indication. For example: -The network node may adapt the way the concerned UE, or the concernedUE’s communication or data flow(s), is treated (e.g. with the purpose to optimize the resource utilization of the UE’s serving cell), for example:o The network node may reduce the UE’s priority / weight in thescheduling, e.g. giving more resources to other UEs (e.g. UEs with active application sessions) at the expense of the UE which sent the session pause indication. In particular, if the UE had previously been given increased scheduling priority in order to ensure good QoE of the concerned application session, the network node may reduce theUE’s scheduling priority, e.g. reset it to a normal / regular / default level. If / when the network node subsequently receives a sessionresume indication from the UE, the network may choose to undo, or mitigate or modify, its adaptive actions, e.g. giving the UE the scheduling priority it had before the session pause indication was received. In a variation of this, the network may choose to give theUE a scheduling priority that is proportional to or inversely proportional to (or a function of) a QoE / RVQoE metric (e.g. the buffer level, e.g. the playout buffer of a video session, e.g. applying a higher scheduling priority the lower the buffer level is) whose value may have changed between the session pause and session resume events. In another variation, the network may decide to first deliver a certain amount of data to the UE before suspending or reducing scheduling of resources for the UE until the session resumes. Theamount of data to be delivered before suspension or reduction of scheduling of resources for the UE may depend on the buffer level (e.g. a video playout buffer) for the session indicated by the previous RVQoE reports. oIn another option, where a particular UE has sent a session pauseindication, but the user-plane is still carrying uplink (UL) and / ordownlink (DL) data in the Data Radio Bearers (DRBs) correspondingto the (e.g. video) session, the network may determine that these areend-of-line packets and processing such packets sooner might help decrease resource reservation on the network. oIn another option, where a particular UE has sent a session pauseindication and where prior QoE and RVQoE reports have indicated a degraded quality of experience, the network may decide to prioritize the delivery of data to the UE regardless of the session status. The user-initiated session pause action may in fact be an effort from the user to buffer enough content (e.g. to playback a video) withoutstalling events (e.g. during playback).- If the UE is outside the area scope associated with the concerned QoEconfiguration, and the network node is waiting for the ongoing QoE measurement session to conclude before the network node releases the QoEconfiguration (i.e. following 3GPP Working Group (WG) SA4’srequirement or recommendation that QoE measurements and reports shouldcover complete application sessions), there are various options for the network node’s possible actions, for example:o As one option, the network node may release the QoE configurationin the UE when the network node receives a session pause indication. oAs another option, the network node may wait for a specified orimplementation or configuration specific time and if no sessionresume indication has been received, the network node may releasethe QoE configuration in the UE after the specified or implementation or configuration specific waiting time. oAs another option, the network node may keep regarding the QoEmeasurement session as ongoing until a session stop indication is received (upon which the network node may choose to release the QoE configuration in the UE, at least if the UE is still outside the area scope).- If the network has configured the UE with MDT measurements, which aresupposed to be aligned with the concerned QoE measurements, the network node may, for example, do any one or more of the following:o As one option, the network node may release the MDT configuration(and thus the MDT measurements) in the UE, and if a session resume indication (pertaining to the paused session) is received from the UE, the network node may configure the UE with the same MDT configuration again. ^Optionally, the network node may do this only if the sessionpause indication pertains to the application session and the UE’s behavior is to end the QoE measurement session when the application session is paused and start a new QoE measurement session if the application session is subsequently resumed. ^As another option, the network node may do this only if thesession pause indication (and session possible resume indication) pertains to the QoE measurement session (or pertains to both the QoE measurement session and an associated RVQoE measurement session).o As another option, the alignment between the QoE / RVQoEmeasurements for an application session and the MDT measurements may follow the pause and resume of the application session. In one variant, for RVQoE measurements, the network node, upon receiving a session pause indication, may consider the alignment between MDT measurements and RVQoE measurements as inactivated (e.g. “on hold”). The network can later consider the alignment between MDT measurements and RVQoE measurements as terminated, provided that a certain time as elapsed (the time can correspond to the expiry of a timer whose value may either configured or may obtained in animplementation specific way). In the same variant, upon receiving an indication of session resume, the network node may consider the alignment between MDT measurements and RVQoE measurements as reactivated (e.g. “in use”). In another variant, for RVQoE measurements, the network node may use the indications of session pause and session resume to discriminate when alignment between MDT measurements and RVQoE measurements is “in use” or “not in use”. According to this, upon receiving the indication of a session pause, the network node may consider the alignment between MDT measurements and RVQoE measurements as terminated (or “no longer in use”). Instead, upon receiving the indication of a session resume, the network node may consider the alignment between MDTmeasurements and RVQoE measurements as “in use”. In a variation of the above, the described mechanisms may apply with RVQoE measurements replaced by QoE measurements. In another variation,the above described mechanisms may apply for both QoE and RVQoE measurements.- If the network node receives an indication that a session is paused, thenetwork node can determine to inactivate the QoE / RVQoE configuration corresponding to the application whose session has been paused. Alternatively, the network node can determine to release the QoE / RVQoE configuration corresponding to the application whose session has been paused.- If the network node receives an indication that a session is paused and italso receives a time-related indication (e.g. a timestamp) indicating the time at which the session has been paused, or an equivalent time-related indication, based on which the network node can deduce / calculate the time elapsed since the session was paused. Based on this elapsed time, the network node can determine to inactivate the QoE / RVQoE configuration corresponding to the application whose session has been paused. Alternatively, based on the elapsed time since the session was paused, the network node can determine to release the QoE / RVQoE configurationcorresponding to the application whose session has been paused.

[0214] Additional UE behavior when a session is paused or resumed

[0215] There are 3GPP standard specifications related to QoE measurements (e.g. 3GPPTS 26.247 V17.4.1), which state that the UE application checks any conditions for QoEmeasurements (in accordance with the QoE configuration), such as restriction to a certain area, only at the start of a QoE measurement session. This statement can be considered in different ways when it comes to the case where the session is paused and subsequently resumed, for example: -The UE may evaluate the condition(s), e.g. the UE’s location in relation tothe area scope, when the application session is resumed and continues, resumes or restarts the QoE / RVQoE measurement session (where “restarts” means that a new QoE / RVQoE measurement session is started) only if the condition(s) is / are fulfilled. -The UE may rely on the check of the conditions it performed when theapplication session started and may not evaluate the conditions again whenthe application session is resumed. -If, at the time when the application session is resumed, the applicationsession has been paused for a time exceeding a configured or specified (in a standard specification) or UE implementation specific threshold, the UE application may check the condition(s), otherwise not.- The UE’s behavior may depend on whether only the application session hasbeen paused or both the application session and the QoE / RVQoE measurement session have been paused. As an example, if only theapplication session has been paused, while the QoE / RVQoE measurementsession continues, then the UE application may not evaluate any conditionsfor QoE / RVQoE measurements when the application session is resumed. While on the other hand, if the QoE / RVQoE measurement session is paused when the application session is paused (possibly with some delay), the UE application may evaluate the condition(s) (if any) when the application session and the QoE / RVQoE measurement session are resumed.

[0216] Inter-node mobility aspects

[0217] The session paused / not paused status may be transferred from a source networknode (e.g. gNB) to a target network node (e.g. gNB) (or a candidate target network node (e.g.gNB)) during a handover preparation phase, e.g. in the HANDOVER REQUEST XnAPmessage (or in the HANDOVER REQUIRED and HANDOVER REQUEST NGAPmessages). NGAP denotes the Next Generation Application Protocol.

[0218] Upon a conditional handover (CHO) execution, the UE may indicate to the targetnetwork node (e.g. gNB) whether a session in the UE application layer is paused. If thismechanism is used, then the source network node (e.g. gNB) does not have to send anyindication of session paused / not paused status to a candidate target network node (e.g. gNB).An optimization may be that the source network node (e.g. gNB) does send an indication ofthe session paused / not paused status to the candidate target network node (e.g. gNB), and theUE may indicate its session paused / not paused status to the target network node (e.g. gNB)upon CHO execution only if the session paused / not paused status has changed since the UEreceived the RRCReconfiguration message from the source network node (e.g. gNB) whichcontained the Handover Command (i.e. the RRCReconfiguration to be applied in the targetcell), or since a short time, e.g. 2 seconds, before the UE received the RRCReconfigurationmessage from the source network node (e.g. gNB) which contained the Handover Command(i.e. the RRCReconfiguration to be applied in the target cell).

[0219] The latter principle may be extended to apply also for regular handover, i.e. thesource network node (e.g. gNB) may send the session paused / not paused status to the targetnetwork node (e.g. gNB) during the handover preparation and the UE may send its sessionpaused / not paused status to the target network node (e.g. gNB) upon handover execution onlyif the session paused / not paused status has changed since the UE received the HandoverCommand (i.e. the RRCReconfiguration to be applied in the target cell), or since a short time,(e.g. 1 or 2 seconds) before the UE received the Handover Command (i.e. theRRCReconfiguration to be applied in the target cell).

[0220] In all of the above, a further optimization may be that transmission of the sessionpaused / not paused status (from the source network node (e.g. gNB) to the (candidate) targetnetwork node (e.g. gNB)) or from the UE to the target network node (e.g. gNB) occurs only ifthe overall session status (e.g. as indicated by the appLayerSessionStatus-r17 field in theMeasurementReportAppLayer message) is that a session is ongoing (e.g. indicated by anappLayerSessionStatus-r17 field set to “start”).

[0221] Another optimization can be that the UE does not send its session paused / notpaused status if the target network node (e.g. gNB) is the same as the source network node (e.g.gNB) (i.e. during intra-network node (e.g. gNB) (conditional) handovers).

[0222] The session paused / not paused status may also be transferred from one networknode (e.g. gNB) to another network node (e.g. gNB) during a UE context fetch operation, e.g.in the RETRIEVE UE CONTEXT RESPONSE XnAP message, e.g. when the UE resumes from RRC_INACTIVE to RRC_CONNECTED state in a new network node (e.g. gNB).

[0223] In all of the above, sending of the session paused / not paused status may apply perQoE configuration or per QoE configuration with an ongoing (but possibly paused) session (i.e. a session for which the overall session status (e.g. as indicated by theappLayerSessionStatus-r17 field in the MeasurementReportAppLayer message) is that asession is ongoing (e.g. indicated by an appLayerSessionStatus-r17 field set to “start”)).

[0224] Transfer of session paused / resumed indication between entities of a network nodein split architecture deployment

[0225] Concerning the transfer of RVQoE measurement information between a first entityof a network node (e.g. a network node (e.g. gNB) CU) and a second entity of the same network node (e.g. a network node (e.g. gNB) DU controlled by the network node (e.g. gNB) CU), the signaling between the two entities (e.g., the QOE INFORMATION TRANSFER F1AP message) can be extended with at least one IE indicating whether a session for which RVQoE measurements are being collected has been paused or resumed. As an example of implementation, the IE can be realized as an ENUMERATED type ASN.1 parameter, with one value indicating “paused” (or equivalent) and another value indicating “resumed” (or equivalent). In one case, a session status “paused” and / or “resumed” can be indicated as particular values of an IE indicating the measurement status for a session associated with a particular QoE reference. For instance, the QOE INFORMATION TRANSFER F1AP message sent from the network node (e.g. gNB) CU to the network node (e.g. gNB) DU can beextended with a new IE named Measurement Status with one value, e.g. “paused”, indicatingthat the corresponding session for the UE is paused, and another value, e.g. “resumed”, indicating that the corresponding session for the UE is resumed.

[0226] In one embodiment, a second entity of a network node (e.g. a DU of a networknode, such as a gNB-DU) requests a first entity of the network node (e.g. the CU of the networknode, such as the gNB-CU, controlling the DU of the network node, such as the gNB-DU) toreceive indication(s) concerning session paused and / or session resumed (i.e. the second entity(e.g. the DU of the network node, such as the gNB-DU) requests the first entity (e.g. the CU ofthe network node, such as the gNB-CU) to send such indication(s) to the second entity (e.g. theDU of the network node, such as the gNB-DU). The indication(s) may be provided per QoEreference, i.e. may be associated with a certain QoE reference.

[0227] In one embodiment, a first entity of a network node (e.g. a CU of a network node,such as a gNB-CU) may send to a second entity of the network node (e.g. a DU of the networknode, such as gNB-DU), an indication to signal whether alignment / correlation between radio related measurements (e.g. MDT measurements) and QoE / RVQoE measurements is to be paused or resumed. The indication can be implicitly signaled via the indication of sessionpaused or resumed, wherein the sending of an indication of a session being paused may indicatethat alignment / correlation between radio measurements and the concerned QoE / RVQoE measurements is (no longer) wanted (i.e. the alignment / correlation is e.g. to be paused, put onhold, suspended or terminated), and vice versa when an indication of a session being resumedis signaled. Alternatively, the indication can be signaled explicitly.

[0228] In some embodiments, the new IE may also indicate the “start” and / or “stop”codepoints (i.e. whether the session is ongoing or not ongoing).

[0229] Session paused indication when session delivery started or continued in a non-RRC_CONNECTED state

[0230] In one embodiment, when a session of an application for which QoE / RVQoEmeasurement data is being collected, is at least partially delivered when the UE AS is in a non- connected RRC state (i.e. in another RRC state than RRC_CONNECTED state, e.g. while the UE AS is in RRC_IDLE and / or in RRC_INACTIVE state) the UE AS and / or the UEapplication layer may store the indication that a session is paused. Upon (re)establishing theconnection to a network node from RRC_IDLE to RRC_CONNECTED state, or upon resuming the connection from RRC_INACTIVE to RRC_CONNECTED state, the UE may send to the network node an indication indicating that a session is paused.

[0231] In another embodiment, for a session at least partially delivered when the UE ASis in a non-connected RRC state (i.e. in another RRC state than RRC_CONNECTED state, e.g.while the UE AS is in RRC_IDLE and / or in RRC_INACTIVE state), the UE AS and / or the UE application layer may store the indication that a session is paused, together with time- related information, e.g. a time-related indication (e.g. a timestamp) indicating the time at which the session was been paused. Upon (re)establishing the connection to a network node (e.g. a gNB) from RRC_IDLE to RRC_CONNECTED state, or upon resuming the connectionfrom RRC_INACTIVE to RRC_CONNECTED state, the UE may send to the network nodean indication indicating that a session is paused together with the associated time-related information (e.g. an indication of the time when the session was paused or for how long it has been paused, e.g. the elapsed time since the session was paused). As a further option, the sending of such time information related to the pausing of the session may itself constitute asession paused indication (i.e. then a separate session paused indication is not needed).

[0232] UE capabilities

[0233] For the embodiments of the disclosure, UE capability signaling may be defined, toindicate to the network which of the features described herein the UE is able to support.

[0234] Examples of how the ideas disclosed herein may impact existing standardspecifications will now be described. That is, examples illustrating how some aspects andembodiments of the disclosure may be realized in terms of standardization will now bedescribed. Firstly, an example implementation of a solution for incorporation in 3GPP TS38.331 V18.0.0, where the UE actions are described in procedure text, will be described. The new parts are underlined.5.7.16 Application layer measurement reporting5.7.16.1 GeneralFig. 6 (corresponds to Figure 5.7.16.1-1 in 3GPP TS 38.331 V18.0.0): Application layermeasurement reporting. The purpose of this procedure is to send application layermeasurement reports to the network.5.7.16.2 InitiationA UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when configured with application layer measurement, i.e. whenappLayerMeasConfig and SRB4 and / or SRB5 have been configured by the network.Upon initiating the procedure, the UE shall: 1>for each measConfigAppLayerId received from upper layers:2> if the UE AS has received application layer measurement report container fromupper layers which has not been transmitted; and 2>if the application layer measurement reporting has not been suspended for the measConfigAppLayerId associated with the application layer measurement reportcontainer according to clause 5.3.5.13d: 3>set the measReportAppLayerContainer in the MeasurementReportAppLayermessage to the received value in the application layer measurement report container; 2>set the measConfigAppLayerId in the MeasurementReportAppLayer message to thevalue of the measConfigAppLayerId received together with application layermeasurement report information; 2>if session start or stop information or session pause or resume information has beenreceived from upper layers for the measConfigAppLayerId: 3>set the appLayerSessionStatus in the MeasurementReportAppLayer message tothe received value of session start or stop information or session pause or resumeinformation; 2>if reportingSRB and ran-VisibleReportingSRB are different for themeasConfigAppLayerId: 3>include measReportAppLayerContainer and appLayerSessionStatus in a differentMeasurementReportAppLayer message than ran-VisibleMeasurements;2> if RAN visible application layer measurement report has been received from upperlayers: 3>for each appLayerBufferLevel value in the received RAN visible application layermeasurement report: 4>set the appLayerBufferLevel values in the appLayerBufferLevelList in the MeasurementReportAppLayer message to the buffer level values receivedfrom the upper layer in the order with the first appLayerBufferLevel value set to the newest received buffer level value, the second appLayerBufferLevel 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 appLayerBufferLevel,if configured; 3>set the playoutDelayForMediaStartup in the MeasurementReportAppLayermessage 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-SessionID in the pdu-SessionIdList 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 FlowID value. >for each stored application layer measurement configuration with configforRRC- IdleInactive set to true and for which appLayerIdleInactiveConfig has not beentransmitted since the UE entered RRC_CONNECTED: 2>set the parameters in appLayerIdleInactiveConfig in theMeasurementReportAppLayer message to the values stored in the UE variableVarAppLayerIdleConfig;>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 Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) specified inTS 38.323 [5]: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 clause5.7.7; 4>else: 5> discard the RRC message;3>else: 4>submit the MeasurementReportAppLayer message to lower layers fortransmission.2>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 [5]: 4> if the RRC message segmentation is enabled based on the field rrc-SegAllowedSRB4 received in appLayerMeasConfig and the reportingSRB isSRB4; or 4>if the RRC message segmentation is enabled based on the field rrc- SegAllowedSRB5 received in appLayerMeasConfig and the reportingSRB isSRB5: 5> initiate the UL message segment transfer procedure as specified in clause5.7.7 via the SRB indicated in the field reportingSRB inMeasConfigAppLayer; 4>else: 5> discard the RRC message;3>else: 4>submit the MeasurementReportAppLayer message to lower layers fortransmission via the SRB indicated in the field reportingSRB or, if differentfrom reportingSRB, ran-VisibleReportingSRB in MeasConfigAppLayer uponwhich the procedure ends.

[0235] An example ASN.1 impact based on 3GPP TS 38.331 V18.0.0 is as follows:MeasurementReportAppLayer message-- ASN1START-- TAG-MEASUREMENTREPORTAPPLAYER-STARTMeasurementReportAppLayer-r17 ::= SEQUENCE { criticalExtensions CHOICE { measurementReportAppLayer-r17 MeasurementReportAppLayer-r17-IEs, criticalExtensionsFuture SEQUENCE {} } } MeasurementReportAppLayer-r17-IEs ::= SEQUENCE { measurementReportAppLayerList-r17 MeasurementReportAppLayerList-r17, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } MeasurementReportAppLayer-v1800-IEs ::= SEQUENCE { measurementReportAppLayerList-r18 MeasurementReportAppLayerList-r18 OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } MeasurementReportAppLayerList-r17 ::= SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasReportAppLayer-r17MeasurementReportAppLayerList-r18 ::= SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OFMeasReportAppLayer-r18 MeasReportAppLayer-r17 ::= SEQUENCE { measConfigAppLayerId-r17 MeasConfigAppLayerId-r17, measReportAppLayerContainer-r17 OCTET STRINGOPTIONAL, appLayerSessionStatus-r17 ENUMERATED {start, stop} OPTIONAL, ran-VisibleMeasurements-r17 RAN-VisibleMeasurements-r17 OPTIONAL }MeasReportAppLayer-r18 ::= SEQUENCE { idleInactiveConfig-r18 AppLayerIdleInactiveConfig-r18 OPTIONAL, ..., [[RAN-VisibleMeasurements-r17 ::= SEQUENCE { appLayerBufferLevelList-r17 SEQUENCE (SIZE (1..8)) OF AppLayerBufferLevel-r17 OPTIONAL, playoutDelayForMediaStartup-r17 INTEGER (0..30000) OPTIONAL, pdu-SessionIdList-r17 SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF PDU- SessionID OPTIONAL, ..., [[ pdu-SessionIdList-r18 SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF QFI- List-r18 OPTIONAL ]] } AppLayerBufferLevel-r17 ::= INTEGER (0..30000) QFI-List-r18 ::= SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI-- TAG-MEASUREMENTREPORTAPPLAYER-STOP-- ASN1STOPMeasReportAppLayer field descriptions appLayerSessionStatus The version of the field with suffix “-r17” (i.e. appLayerSessoinStatus-r17) indicates that an application layer measurement session in the application layer starts or ends. The version of the field with suffix “-r19” (i.e. appLayerSessoinStatus-r19) indicates that an application layer measurement session in the application layer starts or ends or pauses or resumes. For application layer measurements applicable to RRC_IDLE or RRC_INACTIVE, the UE transmits appLayerSessionStatus upon transfer to RRC_CONNECTED.measReportAppLayerContainer The field contains the application layer measurement report container, see Annex L (normative) in TS 26.247

[0068] , clause 16.5 in TS 26.114

[0069] and TS 26.118

[0070] . ran-VisibleMeasurements The field contains the RAN visible application layer measurement report.

[0236] In an alternative realization example, the 3GPP Release 17 appLayerSessionStatus-r17 field is reused also for indications when a session is paused or resumed. This is illustratedin the following field description: MeasReportAppLayer field descriptions appLayerSessionStatus Indicates that an application layer measurement session in the application layer starts or ends or pauses or resumes. The UE transmits the value start if the application layermeasurement session starts or resumes and the value stop if the application layermeasurement session stops or pauses. For application layer measurements applicable toRRC_IDLE or RRC_INACTIVE, the UE transmits appLayerSessionStatus upon transfer toRRC_CONNECTED. measReportAppLayerContainer The field contains the application layer measurement report container, see Annex L (normative) in TS 26.247

[0068] , clause 16.5 in TS 26.114

[0069] and TS 26.118

[0070] . ran-VisibleMeasurements The field contains the RAN visible application layer measurement report.

[0237] In the following, an implementation example incorporated in TS 38.473 V18.0.0 isprovided. New parts are underlined.9.2.16.1 QOE INFORMATION TRANSFERThis message is sent by a gNB-CU to a gNB-DU, to indicate information related to RAN visible QoE.Direction: gNB-CU ^ gNB-DU.IE / Group Name Presence Range IE type andSemanticsCriticality Assignedreference description Criticality Message Type M 9.3.1.1 YES ignoregNB-CU UEM 9.3.1.4 YES rejectF1AP ID gNB-DU UEM 9.3.1.5 YES rejectF1AP ID QoE0..1 YES ignoreInformation List >QoE 1..<maxnEACH ignoreInformation oofQoEInf Item ormation> >>QoEO 9.3.1.260 - -Metrics >>DRB List 0..1 YES ignore>>>DRB 1.. The List of List Item <maxnoof DRBs DRBs> correspondin g to the QoE Information. >>>>DRBM 9.3.1.8ID >>SessionO ENUMERAIndicates the- -Status TED status of the (started, application stopped, session for paused, which QoE resumed, measuremen …) ts are configured for the UE.Range bound ExplanationmaxnoofQoEInformation Maximum no. of QoE information for one UE, themaximum value is 16. maxnoofDRBs Maximum no. of DRB allowed towards one UE,the maximum value is 64.

[0238] Fig. 7 shows an example of a communication system 700 in accordance with someembodiments.

[0239] In the example, the communication system 700 includes a telecommunicationnetwork 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes, such as network nodes 710a and 710b (one or more of which may be generally referred to as network nodes 710), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, aswill be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated bya single vendor. Thus, it will be understood that network nodes include disaggregatedimplementations or portions thereof. For example, in some embodiments, thetelecommunication network 702 includes one or more Open-RAN (ORAN) network nodes. AnORAN network node is a node in the telecommunication network 702 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 702, including one or more network nodes 710 and / or core network nodes 708.

[0240] Examples of an ORAN network node include an open radio unit (O-RU), an opendistributed 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 control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combinationthereof (the adjective “open” designating support of an ORAN specification). The networknode may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul userplane interface, or an open fronthaul management plane interface. Moreover, an ORAN accessnode may be a logical node in a physical node. Furthermore, an ORAN network node may beimplemented in a virtualization environment (described further below) in which one or morenetwork functions are virtualized. For example, the virtualization environment may include anO-Cloud computing platform orchestrated by a Service Management and OrchestrationFramework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.The network nodes 710 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 712a, 712b, 712c, and 712d (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.

[0241] Example wireless communications over a wireless connection include transmittingand / 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 700 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 700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0242] The UEs 712 may be any of a wide variety of communication devices, includingwireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 710 and other communication devices. Similarly, the network nodes 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 712 and / or with other network nodes or equipment in the telecommunication network 702 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 702.

[0243] In the depicted example, the core network 706 connects the network nodes 710 toone or more host computing systems, such as host 716. 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 706 includes one more core network nodes (e.g., core network node 708) 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 708. 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 ServerFunction (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).

[0244] The host 716 may be under the ownership or control of a service provider otherthan an operator or provider of the access network 704 and / or the telecommunication network 702. The host 716 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 with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0245] As a whole, the communication system 700 of Fig.7 enables connectivity betweenthe 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.

[0246] In some examples, the telecommunication network 702 is a cellular network thatimplements 3GPP standardized features. Accordingly, the telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 702. For example, the telecommunications network 702 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 IoT services to yet further UEs.

[0247] In some examples, the UEs 712 are configured to transmit and / or receiveinformation without direct human interaction. For instance, a UE may be designed to transmit information to the access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. Additionally,a UE may be configured for operating in single- or multi- Radio Access Technology (RAT) ormulti-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 – DualConnectivity (EN-DC).

[0248] In the example, the hub 714 communicates with the access network 704 to facilitateindirect communication between one or more UEs (e.g., UE 712c and / or 712d) and network nodes (e.g., network node 710b). In some examples, the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 714 may be a broadband router enabling access to the core network 706 for the UEs. As another example, the hub 714 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 710, or by executable code, script, process, or other instructions in the hub 714. As another example, the hub 714 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 714 may be a content source. For example,for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 714may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

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

[0250] Fig. 8 shows a UE 800 in accordance with some embodiments. The UE 800presents additional details of some embodiments of the UE 712 of Fig. 7. As used herein, a UErefers 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 ordevice, music storage / playback device, wearable terminal device, wireless endpoint, mobilestation, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME),an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premiseequipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0251] A UE may support device-to-device (D2D) communication, for example byimplementing a 3GPP 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, anend user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0252] The UE 800 includes processing circuitry 802 that is operatively coupled via a bus804 to an input / output interface 806, a power source 808, a memory 810, a communication interface 812, and / or any other component, or any combination thereof. Certain UEs mayutilize all or a subset of the components shown in Fig. 8. The level of integration between thecomponents 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.

[0253] The processing circuitry 802 is configured to process instructions and data and maybe configured to implement any sequential state machine operative to execute instructionsstored as machine-readable computer programs in the memory 810. The processing circuitry 802 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 802 may include multiple central processing units (CPUs). The processing circuitry 802 may be configured to cause the UE 802 to perform the methodsas described with reference to Fig. 4.

[0254] In the example, the input / output interface 806 may be configured to provide aninterface 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 800. 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.

[0255] In some embodiments, the power source 808 is structured as a battery or batterypack. 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 808 may further include power circuitry for delivering power from the power source 808 itself, and / or an external power source, to the various parts of the UE 800 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 808. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 808 to make the power suitable for the respective components of the UE 800 to which power is supplied.

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

[0257] The memory 810 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), suchas a Universal Subscriber Identity Module (USIM) and / or International Subscriber IdentityModule (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 810 may allow the UE 800 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 810, which may be or comprise a device- readable storage medium.

[0258] The processing circuitry 802 may be configured to communicate with an accessnetwork or other network using the communication interface 812. The communication interface 812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 822. The communication interface 812 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 818 and / or a receiver 820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 818 and receiver 820 may be coupled to one or more antennas (e.g., antenna 822) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0259] In the illustrated embodiment, communication functions of the communicationinterface 812 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-basedcommunication 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 / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0260] Regardless of the type of sensor, a UE may provide an output of data captured byits sensors, through its communication interface 812, 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 fromseveral sensors), in response to a triggering event (e.g., when moisture is detected an alert issent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0261] As another example, a UE comprises an actuator, a motor, or a switch, related to acommunication 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.

[0262] A UE, when in the form of an Internet of Things (IoT) device, may be a device foruse 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 IoT 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, asurveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactileaugmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, asensor 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 IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described inrelation to the UE 800 shown in Fig. 8.

[0263] As yet another specific example, in an IoT scenario, a UE may represent a machineor 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 3GPP 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.

[0264] In practice, any number of UEs may be used together with respect to a single usecase. 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.

[0265] Fig. 9 shows a network node 900 in accordance with some embodiments. As usedherein, 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) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0266] 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, ormacro 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 basestation such as centralized digital units, distributed units (e.g., in an O-RAN access node)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).

[0267] 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).

[0268] The network node 900 includes a processing circuitry 902, a memory 904, acommunication interface 906, and a power source 908. The network node 900 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 900 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 900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 904 for different RATs) and some components may be reused (e.g., a same antenna 910 may be shared by different RATs). The network node 900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 900, 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 900.

[0269] The processing circuitry 902 may comprise a combination of one or more of amicroprocessor, 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 900 components, such as the memory 904, to provide network node 900 functionality. For example, the processing circuitry 902 may be configured to cause the network node to perform the methodsas described with reference to Fig. 5.

[0270] In some embodiments, the processing circuitry 902 includes a system on a chip(SOC). In some embodiments, the processing circuitry 902 includes one or more of radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914. In some embodiments, the radio frequency (RF) transceiver circuitry 912 and the baseband processing circuitry 914 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 912 and baseband processing circuitry 914 may be on the same chip or set of chips, boards, or units.

[0271] The memory 904 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 processing circuitry 902. The memory 904 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 902 and utilized by the network node 900. The memory 904 may be used to store any calculations made by the processing circuitry 902 and / or any data received via the communication interface 906. In some embodiments, the processing circuitry 902 and memory 904 is integrated.

[0272] The communication interface 906 is used in wired or wireless communication ofsignaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 906 comprises port(s) / terminal(s) 916 to send and receive data, for example to and from a network over a wired connection. The communication interface 906 also includes radio front-end circuitry 918 that may be coupled to, or in certain embodiments a part of, the antenna 910. Radio front-end circuitry 918 comprises filters 920 and amplifiers 922. The radio front-end circuitry 918 may be connected to an antenna 910 and processingcircuitry 902. The radio front-end circuitry may be configured to condition signals communicated between antenna 910 and processing circuitry 902. The radio front-end circuitry 918 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 918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 920 and / or amplifiers 922. The radio signal may then be transmitted via the antenna 910. Similarly, when receiving data, the antenna 910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 918. The digital data may be passed to the processing circuitry 902. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0273] In certain alternative embodiments, the network node 900 does not include separateradio front-end circuitry 918, instead, the processing circuitry 902 includes radio front-end circuitry and is connected to the antenna 910. Similarly, in some embodiments, all or some of the RF transceiver circuitry 912 is part of the communication interface 906. In still other embodiments, the communication interface 906 includes one or more ports or terminals 916, the radio front-end circuitry 918, and the RF transceiver circuitry 912, as part of a radio unit (not shown), and the communication interface 906 communicates with the baseband processing circuitry 914, which is part of a digital unit (not shown).

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

[0275] The antenna 910, communication interface 906, and / or the processing circuitry 902may 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 910, the communication interface 906, and / or the processing circuitry 902 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.

[0276] The power source 908 provides power to the various components of network node900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 908 may further comprise, or be coupledto, power management circuitry to supply the components of the network node 900 with power for performing the functionality described herein. For example, the network node 900 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 908. As a further example, the power source 908 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.

[0277] Embodiments of the network node 900 may include additional components beyondthose shown in Fig. 9 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 900 may include user interface equipment to allow input of information into the network node 900 and to allow output of information from the network node 900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 900. In some embodiments providing a core network node, such as core network node 108 of FIG.7, some components, such as the radio front-end circuitry 918 and the RF transceiver circuitry 912 may be omitted.

[0278] Fig. 10 is a block diagram illustrating a virtualization environment 1000 in whichfunctions 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 1000 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., acore network node or host), then the node may be entirely virtualized. In some embodiments,the virtualization environment 1000 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and OrchestrationFramework via an O-2 interface. Virtualization may facilitate distributed implementations of anetwork node, UE, core network node, or host.

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

[0280] Hardware 1004 includes processing circuitry, memory that stores software and / orinstructions 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 1006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1008a and 1008b (one or more of which may be generally referred to as VMs 1008), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to the VMs 1008.

[0281] The VMs 1008 comprise virtual processing, virtual memory, virtual networking orinterface and virtual storage, and may be run by a corresponding virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of VMs 1008, 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.

[0282] In the context of NFV, a VM 1008 may be a software implementation of a physicalmachine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1008, and that part of hardware 1004 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 1008 on top of the hardware 1004 and corresponds to the application 1002.

[0283] Hardware 1004 may be implemented in a standalone network node with generic orspecific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1010, which, among others, oversees lifecycle management of applications 1002. In some embodiments, hardware 1004 is coupled to one or more radio units that eachinclude 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 1012 which may alternatively be used for communication between hardware nodes and radio units.

[0284] Although the computing devices described herein (e.g., UEs, network nodes) mayinclude 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 thecommunication interface. In another example, non-computationally intensive functions of anyof such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0285] In certain embodiments, some or all of the functionality described herein may beprovided 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 or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a 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 theprocessing 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.

[0286] Other embodiments of the present disclosure are defined in the following numberedstatements: Group A EmbodimentsEmbodiment 1. A method performed by a user equipment, UE, for managing a sessionassociated with an application, the method comprising: transmitting a first message to a network node, wherein the first message comprises: first information indicative of the session being stopped or paused in response to the session being paused; or second information indicative of the session being started or resumed in response to the session being resumed.Embodiment 2. The method of embodiment 1, wherein:transmitting the first message to the network node comprises periodically transmitting the first message to the network node.Embodiment 3. The method of embodiment 1 or 2, wherein:transmitting the first message to the network node comprises transmitting the first message to the network node in response to receiving third information indicative of the session being paused or resumed, wherein the first message comprises: the first information in response to the third information being indicative of the session being paused; or the second information in response to the third information being indicative of the session being resumed.Embodiment 4. The method of embodiment 3, wherein:transmitting the first message to the network node in response to receiving the third information comprises: transmitting the first message to the network node in response to an Access Stratum of the UE receiving the third information from an application layer of the UE.Embodiment 5. The method of embodiment 3 or 4, wherein:transmitting the first message to the network node in response to receiving the third information comprises: transmitting the first message to the network node in response to receiving the third information for a measurement configuration application layer identifier, measConfigAppLayerId.Embodiment 6. The method of any of embodiments 3 to 5, wherein:the third information is a QoE report, such as a Radio Access Network Visible QoE, RVQoE, report; the QoE report being empty is indicative of the session being paused; and the QoE report comprising measurement results is indicative of the session being resumed.Embodiment 7. The method of any of embodiments 1 to 6, wherein:the first message is a measurement report application layer, MeasurementReportAppLayer, message; or the first message is different from a measurement report application layer, MeasurementReportAppLayer, message.Embodiment 8. The method of any of embodiments 1 to 7, wherein:the first message is dedicated to information related to management of the session.Embodiment 9. The method of any of embodiments 1 to 8, wherein:transmitting the first message is prioritized over transmitting other messages.Embodiment 10. The method of any of embodiments 1 to 9, wherein:the first message is transmitted via a signaling radio bearer, SRB, of higher prioritythan an SRB dedicated for sending Quality of Experience, QoE, reports, such as RadioAccess Network Visible QoE, RVQoE, reports.Embodiment 11. The method of any of embodiments 1 to 10, wherein:the first message comprises a session status field and the session status field comprises the first information or the second information.Embodiment 12. The method of embodiment 11, wherein:the first information or the second information is a suffix in the session status field.Embodiment 13. The method of embodiment 11 or 12, wherein:the session status field is an application layer session status, appLayerSessionStatus, field.Embodiment 14. The method of any of embodiments 1 to 13, wherein:the first message comprises a session status field and a different field comprises the first information or the second information.Embodiment 15. The method of any of embodiments 1 to 14, wherein:the first information is a first value and the second information is a second value, wherein the first value and second value are different.Embodiment 16. The method of any of embodiments 1 to 15, wherein:the first information is indicative of the session being paused.Embodiment 17. The method of any of embodiments 1 to 16, wherein:the second information is indicative of the session being resumed.Embodiment 18. The method of any of embodiments 1 to 17, wherein:the session comprises one or both of: an application session of the application; and a Quality of Experience, QoE, measurement session on the application session of the application.Embodiment 19. The method of embodiment 18, wherein:the session comprises the application session and the QoE measurement session; and the first message is transmitted to the network node in response to at least the QoEmeasurement session being paused or resumed.Embodiment 20. The method of embodiment 18 or 19, wherein:the QoE measurement session is a Radio Access Network Visible QoE, RVQoE, measurement session.Embodiment 21. The method of any of embodiments 1 to 20, wherein:the first message comprises a Quality of Experience, QoE, report, such as a RadioAccess Network Visible QoE, RVQoE, report and the QoE report comprises measurementresults.Embodiment 22. The method of embodiment 21, wherein:the QoE report comprises the first information or the second information.Embodiment 23. The method of embodiment 22, wherein:the QoE report comprises one or more QoE metrics and the one or more QoE metrics comprise the first information or the second information.Embodiment 24. The method of embodiment 22, wherein:the QoE report comprises one or more QoE metrics and a different QoE metric comprises the first information or the second information.Embodiment 25. The method of embodiment 23 or 24, wherein:the one or more QoE metrics comprise one or both of a play list, PlayList, metric and an average throughput, AvgThroughput, metric.Embodiment 26. The method of any of embodiments 1 to 20, the method comprising:suspending transmission of a QoE report, such as a Radio Access Network VisibleQoE, RVQoE, report, comprising measurement results in response to the session beingpaused or in response to the session being paused for a time duration that exceeds a threshold.Embodiment 27. The method of any of embodiments 1 to 26, the method comprising:setting a timer in response to the session being paused; and determining that the session has stopped in response to expiry of the timer.Embodiment 28. The method of embodiment 27, the method comprising:transmitting a second message to the network node, wherein the second message comprises: fourth information indicative that the session has stopped in response to determining that the session has stopped; or fifth information indicative that the session has resumed in response to the session being resumed prior to expiry of the timer.Embodiment 29. The method of embodiment 27 or 28, wherein:the session comprises an application session of the application and a Quality of Experience, QoE, measurement session on the application session; and determining that the session has stopped comprises: determining that only the QoE measurement session has stopped; or determining that both the application session and the QoE measurement session have stopped.Embodiment 30. The method of embodiment 29, the method comprising:starting another QoE measurement session on the application session in response to the application session being resumed.Embodiment 31. The method of embodiment 30, the method comprising:transmitting a third message to the network node, wherein the third message comprises sixth information indicative of the session being started or resumed.Embodiment 32. The method of any of embodiments 1 to 26, wherein:the session comprises an application session of the application and a Quality of Experience, QoE, measurement session on the application session; and the method comprises stopping the QoE measurement session in response to the application session being paused.Embodiment 33. The method of embodiment 32, the method comprising:transmitting a fourth message to the network node, wherein the fourth message comprises seventh information indicative of the session being stopped or paused.Embodiment 34. The method of embodiment 32 or 33, the method comprising:starting another QoE measurement session on the application session in response to the application session being resumed.Embodiment 35. The method of embodiment 34, the method comprising:transmitting a fifth message to the network node, wherein the fifth message comprises eighth information indicative of the session being started or resumed.Embodiment 36. The method of any of embodiments 1 to 26, wherein:the session comprises an application session of the application and a Quality of Experience, QoE, measurement session on the application session; and the method comprises: setting a first timer and a second timer in response to the session being paused; stopping the QoE measurement session in response to expiry of the first timer; and determining that the application session has stopped in response to expiry of the second timer.Embodiment 37. The method of embodiment 36, the method comprising:transmitting a sixth message to the network node in response to stopping the QoE measurement session, wherein the sixth message comprises ninth information indicative of the session being stopped or paused.Embodiment 38. The method of embodiment 36 or 37, the method comprising:stopping the first timer in response to the second timer expiring prior to expiry of the first timer; and determining that the QoE measurement session has stopped.Embodiment 39. The method of embodiment 38, the method comprising:transmitting a seventh message to the network node in response to determining that the QoE measurement session has stopped, wherein the seventh message comprises tenth information indicative of the session being stopped or paused.Embodiment 40. The method of any of embodiments 1 to 26, wherein:the session comprises an application session of the application and a Quality ofExperience, QoE, measurement session on the application session; and the method comprises: determining that the application session has stopped in response to the application session being paused for an implementation specific time; and determining that the QoE measurement session has stopped in response to determining that the application session has stopped.Embodiment 41. The method of embodiment 40, the method comprising:transmitting an eighth message to the network node in response to determining that the QoE measurement session has stopped, wherein the eighth message comprises eleventh information indicative of the session being stopped or paused.Embodiment 42. The method of any of embodiments 1 to 41, the method comprising:evaluating one or more conditions for the session in response to the session being resumed.Embodiment 43. The method of embodiment 42, wherein:evaluating one or more conditions for the session in response to the session being resumed comprises evaluating one or more conditions for the session in response to the session being resumed after being paused for a time duration that exceeds a threshold.Embodiment 44. The method of embodiment 42 or 43, wherein:the session comprises an application session of the application and a Quality of Experience, QoE, measurement session on the application session; and evaluating one or more conditions for the session in response to the session being resumed comprises evaluating one or more conditions for the session in response to both the application session and the QoE measurement session being resumed.Embodiment 45. The method of any of embodiments 1 to 44, wherein:the first message is transmitted to the network node when the UE connects to the network node to prepare for or execute a conditional handover, CHO, of the UE to the network node.Embodiment 46. The method of any of embodiments 1 to 45, wherein:transmitting the first message to the network node comprises transmitting the first message to the network node in response to the UE transitioning from a Radio Resource Control, RRC, inactive state or an RRC idle state to an RRC connected state.Embodiment 47. The method of any of embodiments 1 to 46, wherein:the first message comprises twelfth information indicative of one or both of a time at which the session began being paused and a duration of time since the session began being paused. Group B EmbodimentsEmbodiment 48. A method performed by a network node for managing a session associatedwith an application, the method comprising: receiving a first message from a user equipment, UE, wherein the first message comprises: first information indicative of the session being stopped or paused in response to the session being paused; or second information indicative of the session being started or resumed in response to the session being resumed.Embodiment 49. The method of embodiment 48, wherein:receiving the first message from the UE comprises periodically receiving the first message from the UE.Embodiment 50. The method of embodiment 48 or 49, wherein:receiving the first message from the UE comprises receiving the first message from the UE in response to the UE receiving third information indicative of the session being paused or resumed, wherein the first message comprises: the first information in response to the third information being indicative of the session being paused; or the second information in response to the third information being indicative of the session being resumed.Embodiment 51. The method of embodiment 50, wherein:receiving the first message from an Access Stratum of the UE.Embodiment 52. The method of embodiment 50 or 51, wherein:receiving the first message from the UE in response to the UE receiving the third information comprises: receiving the first message from the UE in response to the UE receiving the third information for a measurement configuration application layer identifier, measConfigAppLayerId.Embodiment 53. The method of any of embodiments 50 to 52, wherein:the third information is a QoE report, such as a Radio Access Network Visible QoE, RVQoE, report; the QoE report being empty is indicative of the session being paused; and the QoE report comprising measurement results is indicative of the session being resumed.Embodiment 54. The method of any of embodiments 48 to 53, wherein:the first message is a measurement report application layer, MeasurementReportAppLayer, message; or the first message is different from a measurement report application layer, MeasurementReportAppLayer, message.Embodiment 55. The method of any of embodiments 48 to 54, wherein:the first message is dedicated to information related to management of the session.Embodiment 56. The method of any of embodiments 48 to 55, wherein:receiving the first message is prioritized over receiving other messages.Embodiment 57. The method of any of embodiments 48 to 56, wherein:the first message is received via a signaling radio bearer, SRB, of higher priority thanan SRB dedicated for sending Quality of Experience, QoE, reports, such as Radio AccessNetwork Visible QoE, RVQoE, reports.Embodiment 58. The method of any of embodiments 48 to 57, wherein:the first message comprises a session status field and the session status field comprises the first information or the second information.Embodiment 59. The method of embodiment 58, wherein:the first information or the second information is a suffix in the session status field.Embodiment 60. The method of embodiment 58 or 59, wherein:the session status field is an application layer session status, appLayerSessionStatus, field.Embodiment 61. The method of any of embodiments 48 to 60, wherein:the first message comprises a session status field and a different field comprises the first information or the second information.Embodiment 62. The method of any of embodiments 48 to 61, wherein:the first information is a first value and the second information is a second value, wherein the first value and second value are different.Embodiment 63. The method of any of embodiments 48 to 62, wherein:the first information is indicative of the session being paused.Embodiment 64. The method of any of embodiments 48 to 63, wherein:the second information is indicative of the session being resumed.Embodiment 65. The method of any of embodiments 48 to 64, wherein:the session comprises one or both of: an application session of the application; and a Quality of Experience, QoE, measurement session on the application session of the application.Embodiment 66. The method of embodiment 65, wherein:the session comprises the application session and the QoE measurement session; and the first message is received from the UE in response to at least the QoE measurementsession being paused or resumed.Embodiment 67. The method of embodiment 65 or 66, wherein:the QoE measurement session is a Radio Access Network Visible QoE, RVQoE, measurement session.Embodiment 68. The method of any of embodiments 48 to 67, wherein:the first message comprises a QoE report, such as a Radio Access Network VisibleQoE, RVQoE, report and the QoE report comprises measurement results.Embodiment 69. The method of embodiment 68, wherein:the QoE report comprises the first information or the second information.Embodiment 70. The method of embodiment 69, wherein:the QoE report comprises one or more QoE metrics and the one or more QoE metrics comprise the first information or the second information.Embodiment 71. The method of embodiment 69, wherein:the QoE report comprises one or more QoE metrics and a different QoE metric comprises the first information or the second information.Embodiment 72. The method of embodiment 70 or 71, wherein:the one or more QoE metrics comprise one or both of a play list, PlayList, metric and an average throughput, AvgThroughput, metric.Embodiment 73. The method of any of embodiments 48 to 72, wherein:the first message is received from the UE when the UE connects to the network node to prepare for or execute a conditional handover, CHO, of the UE to the network node.Embodiment 74. The method of any of embodiments 48 to 73, wherein:receiving the first message from the UE comprises receiving the first message from the UE in response to the UE transitioning from a Radio Resource Control, RRC, inactive state or an RRC idle state to an RRC connected state.Embodiment 75. The method of any of embodiments 48 to 74, wherein:the first message comprises twelfth information indicative of one or both of a time at which the session began being paused and a duration of time since the session began being paused.Embodiment 76. The method of any of embodiments 48 to 75, whereinthe network node is a first network node; and the first message is transmitted from the first network node to a second network node during a handover of the UE from the first network node to the second network node.Embodiment 77. The method of embodiment 48 to 76, the method comprising:transferring the first information between a Central Unit, CU, of the network node and a Distributed Unit, DU, of the network node.Embodiment 78. The method of any of embodiments 48 to 77, the method comprising:reducing a priority with which the UE is scheduled in response to the first message comprising the first information.Embodiment 79. The method of any of embodiments 48 to 78, the method comprising:increasing the priority with which the UE is scheduled in response to the first message comprising the second information.Embodiment 80. The method of any of embodiments 48 to 79, the method comprising:setting the priority with which the UE is scheduled based on a Quality of Experience, QoE, metric for the UE.Embodiment 81. The method of any of embodiments 48 to 80, the method comprising:prioritizing processing of data corresponding to the session in response to the firstmessage comprising the first information.Embodiment 82. The method of any of embodiments 48 to 81, the method comprising:prioritizing delivery of data to the UE in response to detecting a degraded Quality of Experience, QoE, for the session and the first message comprising the first information.Embodiment 83. The method of any of embodiments 48 to 82, the method comprising:releasing or inactivating a Quality of Experience, QoE, configuration for the session in the UE in response to the first message comprising the first information.Embodiment 84. The method of embodiment 83, the method comprising:releasing the QoE configuration in the UE in response to the first message comprising the first information and in the absence of receiving, within a predefined time period after the first message is received, information indicative of the session being resumed.Embodiment 85. The method of any of embodiments 48 to 84, wherein:the first information is indicative of the session being paused; and the method comprises determining that the session is ongoing in the absence of information indicative of the session being stopped.Embodiment 86. The method of any of embodiments 48 to 85, the method comprising:releasing a Minimization of Drive Tests, MDT, configuration in the UE in response to the first message comprising the first information. Group C EmbodimentsEmbodiment 87. A user equipment, UE, comprising processing circuitry configured to causethe UE to perform the method of any of the Group A embodiments.Embodiment 88. The UE of the previous embodiment, wherein the UE comprises at least onememory for storing instructions which, when executed by the processing circuitry, cause the UE to perform the method of any of the Group A embodiments.Embodiment 89. A network node comprising processing circuitry configured to cause thenetwork node to perform the method of any of the Group B embodiments.Embodiment 90. The network node of the previous embodiment, wherein the network nodecomprises at least one memory for storing instructions which, when executed by the processing circuitry, cause the network node to perform the method of any of the Group B embodiments.Embodiment 91. A user equipment for managing a session associated with an application,comprising: processing circuitry configured to cause the user equipment to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.Embodiment 92. A network node for managing a session associated with an application, thenetwork node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.Embodiment 93. A user equipment (UE) for managing a session associated with anapplication, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to cause the user equipment to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.Embodiment 94. A computer program comprising instructions which, when executed byprocessing circuitry of a user equipment, cause the user equipment to perform the method according to any of the Group A embodiments.Embodiment 95. A computer program comprising instructions which, when executed byprocessing circuitry of a network node, cause the network node to perform the method according to any of the Group B embodiments.Embodiment 96. A computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry of a user equipment to cause the user equipment to perform the method according to any of the Group A embodiments.Embodiment 97. A computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry of a network node to cause the network node to perform the method according to any of the Group B embodiments.

[0287] It should be noted that the above-mentioned embodiments illustrate rather thanlimit the idea, and that those skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the claims. Any reference signs in the claims shall not be construed so as to limit their scope.

Claims

CLAIMS1. A method performed by a user equipment, UE, for managing a session associated withan application, the method comprising: transmitting (402) a first message to a network node, wherein the first message comprises: first information indicative of the session being stopped or paused in response to the session being paused; or second information indicative of the session being started or resumed in response to the session being resumed.

2. The method of claim 1, wherein:transmitting the first message to the network node comprises periodically transmitting the first message to the network node.

3. The method of claim 1 or 2, wherein:transmitting the first message to the network node comprises transmitting the first message to the network node in response to receiving third information indicative of the session being paused or resumed, wherein the first message comprises: the first information in response to the third information being indicative of the session being paused; or the second information in response to the third information being indicative of the session being resumed.

4. The method of claim 3, wherein:transmitting the first message to the network node in response to receiving the third information comprises: transmitting the first message to the network node in response to an Access Stratum of the UE receiving the third information from an application layer of the UE.

5. The method of claim 3 or 4, wherein:transmitting the first message to the network node in response to receiving the third information comprises:transmitting the first message to the network node in response to receiving the third information for a measurement configuration application layer identifier, measConfigAppLayerId.

6. The method of any of claims 3 to 5, wherein:the third information is a QoE report, such as a Radio Access Network Visible QoE, RVQoE, report; the QoE report being empty is indicative of the session being paused; and the QoE report comprising measurement results is indicative of the session being resumed.

7. The method of any of claims 1 to 6, wherein:the first message is a measurement report application layer, MeasurementReportAppLayer, message; or the first message is different from a measurement report application layer, MeasurementReportAppLayer, message.

8. The method of any of claims 1 to 7, wherein:the first message is dedicated to information related to management of the session; transmitting the first message is prioritized over transmitting other messages; and / or the first message is transmitted via a signaling radio bearer, SRB, of higher prioritythan an SRB dedicated for sending Quality of Experience, QoE, reports, such as RadioAccess Network Visible QoE, RVQoE, reports.

9. The method of any of claims 1 to 8, wherein:the first message comprises a session status field and the session status field comprises the first information or the second information; or the first message comprises a session status field and a different field comprises the first information or the second information.

10. The method of any of claims 1 to 9, wherein:the session comprises an application session of the application and a Quality ofExperience, QoE, measurement session on the application session of the application; and the first message is transmitted to the network node in response to at least the QoEmeasurement session being paused or resumed.

11. The method of claim 10, wherein:the QoE measurement session is a Radio Access Network Visible QoE, RVQoE, measurement session.

12. The method of any of claims 1 to 11, wherein:the first message comprises a Quality of Experience, QoE, report, such as a RadioAccess Network Visible QoE, RVQoE, report; andthe QoE report comprises:measurement results; andthe first information or the second information.

13. The method of any of claims 1 to 11, the method comprising:suspending transmission of a QoE report, such as a Radio Access Network VisibleQoE, RVQoE, report, comprising measurement results in response to the session beingpaused or in response to the session being paused for a time duration that exceeds a threshold.

14. The method of any of claims 1 to 13, the method comprising:setting a timer in response to the session being paused; and determining that the session has stopped in response to expiry of the timer.

15. The method of claim 14, the method comprising:transmitting a second message to the network node, wherein the second message comprises: fourth information indicative that the session has stopped in response to determining that the session has stopped; or fifth information indicative that the session has resumed in response to the session being resumed prior to expiry of the timer.

16. The method of claim 14 or 15, wherein:the session comprises an application session of the application and a Quality of Experience, QoE, measurement session on the application session; and determining that the session has stopped comprises:determining that only the QoE measurement session has stopped; or determining that both the application session and the QoE measurement session have stopped.

17. The method of claim 16, the method comprising:starting another QoE measurement session on the application session in response to the application session being resumed.

18. The method of claim 17, the method comprising:transmitting a third message to the network node, wherein the third message comprises sixth information indicative of the session being started or resumed.

19. The method of any of claims 1 to 13, wherein:the session comprises an application session of the application and a Quality of Experience, QoE, measurement session on the application session; and the method comprises stopping the QoE measurement session in response to the application session being paused.

20. The method of claim 19, the method comprising:transmitting a fourth message to the network node, wherein the fourth message comprises seventh information indicative of the session being stopped or paused.

21. The method of claim 19 or 20, the method comprising:starting another QoE measurement session on the application session in response to the application session being resumed.

22. The method of claim 21, the method comprising:transmitting a fifth message to the network node, wherein the fifth message comprises eighth information indicative of the session being started or resumed.

23. A method performed by a network node for managing a session associated with anapplication, the method comprising: receiving (502) a first message from a user equipment, UE, wherein the first message comprises:first information indicative of the session being stopped or paused in response to the session being paused; or second information indicative of the session being started or resumed in response to the session being resumed.

24. The method of claim 23, wherein:receiving the first message from the UE comprises periodically receiving the first message from the UE.

25. The method of claim 23 or 24, wherein:receiving the first message from the UE comprises receiving the first message from the UE in response to the UE receiving third information indicative of the session being paused or resumed, wherein the first message comprises: the first information in response to the third information being indicative of the session being paused; or the second information in response to the third information being indicative of the session being resumed.

26. The method of claim 25, wherein:receiving the first message from the UE in response to the UE receiving the third information comprises: receiving the first message from the UE in response to the UE receiving the third information for a measurement configuration application layer identifier, measConfigAppLayerId.

27. The method of claim 25 or 26, wherein:the third information is a QoE report, such as a Radio Access Network Visible QoE, RVQoE, report; the QoE report being empty is indicative of the session being paused; and the QoE report comprising measurement results is indicative of the session being resumed.

28. The method of any of claims 23 to 27, wherein:the first message is a measurement report application layer, MeasurementReportAppLayer, message; or the first message is different from a measurement report application layer, MeasurementReportAppLayer, message.

29. The method of any of claims 23 to 28, wherein:the first message is dedicated to information related to management of the session; receiving the first message is prioritized over receiving other messages; and / or the first message is received via a signaling radio bearer, SRB, of higher priority thanan SRB dedicated for sending Quality of Experience, QoE, reports, such as Radio AccessNetwork Visible QoE, RVQoE, reports.

30. The method of any of claims 23 to 29, wherein:the first message comprises a session status field and the session status field comprises the first information or the second information; or the first message comprises a session status field and a different field comprises the first information or the second information.

31. The method of any of claims 23 to 30, wherein:the session comprises an application session of the application and Quality ofExperience, QoE, measurement session on the application session of the application; and the first message is received from the UE in response to at least the QoE measurementsession being paused or resumed.

32. The method of claim 31, wherein:the QoE measurement session is a Radio Access Network Visible QoE, RVQoE, measurement session.

33. The method of any of claims 23 to 32, wherein:the first message comprises a QoE report, such as a Radio Access Network VisibleQoE, RVQoE, report; andthe QoE report comprises:measurement results; and the first information or the second information.

34. The method of any of claims 23 to 33, whereinthe network node is a first network node; and the first message is transmitted from the first network node to a second network node during a handover of the UE from the first network node to the second network node.

35. The method of any of claims 23 to 34, the method comprising any one or more of:transferring the first information between a Central Unit, CU, of the network node and a Distributed Unit, DU, of the network node; reducing a priority with which the UE is scheduled in response to the first message comprising the first information; increasing the priority with which the UE is scheduled in response to the first message comprising the second information; setting the priority with which the UE is scheduled based on a Quality of Experience, QoE, metric for the UE; prioritizing processing of data corresponding to the session in response to the firstmessage comprising the first information; prioritizing delivery of data to the UE in response to detecting a degraded Quality ofExperience, QoE, for the session and the first message comprising the first information; andreleasing or inactivating a Quality of Experience, QoE, configuration for the session in the UE in response to the first message comprising the first information.

36. The method of claim 35, the method comprising:releasing the QoE configuration in the UE in response to the first message comprising the first information and in the absence of receiving, within a predefined time period after the first message is received, information indicative of the session being resumed.

37. The method of any of claims 23 to 36, wherein:the first information is indicative of the session being paused; and the method comprises determining that the session is ongoing in the absence of information indicative of the session being stopped.

38. The method of any of claims 23 to 37, the method comprising:releasing a Minimization of Drive Tests, MDT, configuration in the UE in response tothe first message comprising the first information.

39. A user equipment, UE, comprising processing circuitry configured to cause the UE toperform the method of any of claims 1 to 22.

40. A network node comprising processing circuitry configured to cause the network nodeto perform the method of any of claims 23 to 38.

41. A computer program comprising instructions which, when executed by processingcircuitry of a user equipment, cause the user equipment to perform the method according to any of claims 1 to 22.

42. A computer program comprising instructions which, when executed by processingcircuitry of a network node, cause the network node to perform the method according to any of claims 23 to 38.

Images