Field

[0001] The subject matter disclosed herein relates generally to the field of implementing service experience analytics in a wireless communication network. This document defines a network node of a wireless communication system and a method in a network node of a wireless communication system.

Introduction

[0002] Herein, extended Reality (XR) is used as an umbrella term for different types of realities of which Virtual Reality, Augmented Reality, and Mixed Reality are examples. [0003] XR application traffic is subject to strict bandwidth and latency limitations in order to deliver an appropriate Quality of Service and Quality of Experience to an end user of an XR service. Such strict bandwidth and latency limitations can make delivery of XR application traffic over a wireless communication network challenging.

Summary

[0004] In the context of XR media traffic, 3GPP SA2 Work Group recently introduced the concept of a ‘PDU sef to group a series of PDUs carrying a unit of information at the application-level. Each PDU within a PDU set can thus be treated according to an identical set of QoS requirements and associated constraints of delay budget and error rate while providing support to a RAN for differentiated QoS handling at PDU set level. This improves the granularity of legacy 5G QoS flow framework allowing the RAN to optimize the mapping between QoS flow and DRBs to meet stringent XR media requirements (e.g., high-rate transmissions with short delay budget).

[0005] There is required a mechanism to allow a consumer of analytics information to determine if PDU-set QoS requirements requested for a video application are sustainable. Further, the consumer may wish to determine if the user service experience is acceptable. Such determinations may be usefully provided for a specific area, time period. Based on such analytics information, the consumer might determine to upgrade the requested PDU-set QoS requirements to improve the performance of the video application when traffic is routed via the 5GS system. [0006] Disclosed herein are procedures for service experience analytics in a wireless communication network. Said procedures may be implemented by a network node of a wireless communication system and a method in a network node of a wireless communication system.

[0007] There is provided a network node of a wireless communication system, the network node comprising: a processor; and a memory coupled with the processor. The processor is configured to cause the network node to: receive a request from an analytics consumer, the request comprising a request for analytics of service experience for a particular service when the particular service is using a specific quality requirement; collect service performance data from a network function; collect network performance data from at least one other network node; derive from the service performance data and network performance data, service experience analytics; and send the service experience analytics to the analytics consumer.

[0008] There is further provided a method in a network node of a wireless communication system, the method comprising: receiving a request from an analytics consumer, the request comprising a request for analytics of service experience for a particular service when the particular service is using a specific quality requirement. The method further comprises collecting service performance data from a network function; collecting network performance data from at least one other network node; deriving from the service performance data and network performance data, service experience analytics; and sending the service experience analytics to the analytics consumer.

[0009] Such an arrangement allows the analytics consumer to determine if QoS requirements for the particular service are sustainable, and as such determine if the user service experience is acceptable. Such a determination may be made in respect of a specific area and/ or time period. The specific area and/ or time period may be defined by the specific PDU-set. Based on the analytic information received from the network node, the analytics consumer may elect to make a corrective action. Such a corrective action may comprise upgrading PDU-set quality of service (QoS) requirements to improve the performance of the service when traffic carrying data for the service is routed via the 5GS system.

Brief description of the drawings

[0010] In order to describe the manner in which advantages and features of the disclosure can be obtained, a description of the disclosure is rendered by reference to certain apparatus and methods which are illustrated in the appended drawings. Each of these drawings depict only certain aspects of the disclosure and are not therefore to be considered to be limiting of its scope. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

[0011] Methods and apparatus for service experience analytics in a wireless communication network will now be described, by way of example only, with reference to the accompanying drawings, in which:

Figure 1 depicts an embodiment of a service experience analytics in a wireless communication network;

Figure 2 depicts a user equipment apparatus;

Figure 3 depicts further details of the network node;

Figure 4 illustrates an overview of a core network architecture handling of PDU sets;

Figure 5 illustrates an example wireless communication system;

Figure 6 is a messaging diagram illustrating a procedure as described herein; and Figure 7 illustrates a method in a network node of a wireless communication system.

Detailed description

[0012] As will be appreciated by one skilled in the art, aspects of this disclosure may be embodied as a system, apparatus, method, or program product. Accordingly, arrangements described herein may be implemented in an entirely hardware form, an entirely software form (including firmware, resident software, micro-code, etc.) or a form combining software and hardware aspects.

[0013] For example, the disclosed methods and apparatus may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed methods and apparatus may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.

[0014] Furthermore, the methods and apparatus may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/ or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/ or non-transmission. The storage devices may not embody signals. In certain arrangements, the storage devices only employ signals for accessing code.

[0015] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0016] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store, a program for use by or in connection with an instruction execution system, apparatus, or device.

[0017] Reference throughout this specification to an example of a particular method or apparatus, or similar language, means that a particular feature, structure, or characteristic described in connection with that example is included in at least one implementation of the method and apparatus described herein. Thus, reference to features of an example of a particular method or apparatus, or similar language, may, but do not necessarily, all refer to the same example, but mean “one or more but not all examples” unless expressly specified otherwise. The terms “including”, “comprising”, “having”, and variations thereof, mean “including but not limited to”, unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a”, “an”, and “the” also refer to “one or more”, unless expressly specified otherwise.

[0018] As used herein, a list with a conjunction of “and/ or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and/ or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of’ includes one, and only one, of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C” includes one and only one of A, B, or C, and excludes combinations of A, B, and C.” As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.

[0019] Furthermore, the described features, structures, or characteristics described herein may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the disclosure. One skilled in the relevant art will recognize, however, that the disclosed methods and apparatus may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well- known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

[0020] Aspects of the disclosed method and apparatus are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flowchart diagrams and/ or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions /acts specified in the schematic flowchart diagrams and/or schematic block diagrams.

[0021] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/ act specified in the schematic flowchart diagrams and/or schematic block diagrams.

[0022] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions /acts specified in the schematic flowchart diagrams and/ or schematic block diagram.

[0023] The schematic flowchart diagrams and/ or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s). [0024] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0025] The description of elements in each figure may refer to elements of proceeding Figures. Like numbers refer to like elements in all Figures.

[0026] Figure 1 depicts an embodiment of a wireless communication system 100 for implementing service experience analytics in a wireless communication network. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100. The remote unit 102 may be embodied as a user equipment apparatus 200, a UE 435, and/ or a UE 504 as described herein. Further, network unit 104 may be embodied as a network node 300, RAN 430, NWDAF 1 510, NWDAF 2 512, and/ or a NWDAF 610 as described herein. [0027] In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle onboard computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smartwatches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0028] The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an AP, NR, a network entity, an Access and Mobility Management Function (“AMF”), a Unified Data Management Function (“UDM”), a Unified Data Repository (“UDR”), a UDM/UDR, a Policy Control Function (“PCF”), a Radio Access Network (“RAN”), an Network Slice Selection Function (“NSSF”), an operations, administration, and management (“OAM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), an application function, a service enabler architecture layer (“SEAL”) function, a vertical application enabler server, an edge enabler server, an edge configuration server, a mobile edge computing platform function, a mobile edge computing application, an application data analytics enabler server, a SEAL data delivery server, a middleware entity, a network slice capability management server, or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicab ly coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0029] In one implementation, the wireless communication system 100 is compliant with New Radio (NR) protocols standardized in 3GPP, wherein the network unit 104 transmits using an Orthogonal Frequency Division Multiplexing (“OFDM”) modulation scheme on the downlink (DL) and the remote units 102 transmit on the uplink (UL) using a Single Carrier Frequency Division Multiple Access (“SC-FDMA”) scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0030] The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/ or spatial domain.

[0031] Figure 2 depicts a user equipment apparatus 200 that may be used for implementing the methods described herein. The user equipment apparatus 200 is used to implement one or more of the solutions described herein. The user equipment apparatus 200 is in accordance with one or more of the user equipment apparatuses described in embodiments herein. In particular, the user equipment apparatus 200 may be embodied as a remote unit 102, a UE 435, and/ or a UE 504 as described herein. The user equipment apparatus 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

[0032] The input device 215 and the output device 220 may be combined into a single device, such as a touchscreen. In some implementations, the user equipment apparatus 200 does not include any input device 215 and/ or output device 220. The user equipment apparatus 200 may include one or more of: the processor 205, the memory 210, and the transceiver 225, and may not include the input device 215 and/ or the output device 220.

[0033] As depicted, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 may communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 225 may be operable on unlicensed spectrum. Moreover, the transceiver 225 may include multiple UE panels supporting one or more beams. Additionally, the transceiver 225 may support at least one network interface 240 and/ or application interface 245. The application interface(s) 245 may support one or more APIs. The network interface(s) 240 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 240 may be supported, as understood by one of ordinary skill in the art.

[0034] The processor 205 may include any known controller capable of executing computer-readable instructions and/ or capable of performing logical operations. For example, the processor 205 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. The processor 205 may execute instructions stored in the memory 210 to perform the methods and routines described herein. The processor 205 is communicatively coupled to the memory 210, the input device 215, the output device 220, and the transceiver 225. [0035] The processor 205 may control the user equipment apparatus 200 to implement the user equipment apparatus behaviors described herein. The processor 205 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.

[0036] The memory 210 may be a computer readable storage medium. The memory 210 may include volatile computer storage media. For example, the memory 210 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/ or static RAM (“SRAM”). The memory 210 may include non-volatile computer storage media. For example, the memory 210 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 210 may include both volatile and non-volatile computer storage media.

[0037] The memory 210 may store data related to implement a traffic category field as described herein. The memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on the apparatus 200. [0038] The input device 215 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. The input device 215 may be integrated with the output device 220, for example, as a touchscreen or similar touch-sensitive display. The input device 215 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/ or by handwriting on the touchscreen. The input device 215 may include two or more different devices, such as a keyboard and a touch panel.

[0039] The output device 220 may be designed to output visual, audible, and/ or haptic signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 220 may include, but is not limited to, a Liquid Crystal Display (“LCD”), a Light- Emitting Diode (“LED”) display, an Organic LED (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 220 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 200, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 220 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0040] The output device 220 may include one or more speakers for producing sound. For example, the output device 220 may produce an audible alert or notification (e.g., a beep or chime). The output device 220 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 220 may be integrated with the input device 215. For example, the input device 215 and output device 220 may form a touchscreen or similar touch-sensitive display. The output device 220 may be located near the input device 215.

[0041] The transceiver 225 communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver 225 operates under the control of the processor 205 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 205 may selectively activate the transceiver 225 (or portions thereof) at particular times in order to send and receive messages.

[0042] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The one or more transmitters 230 may be used to provide uplink communication signals to a base unit of a wireless communication network. Similarly, the one or more receivers 235 may be used to receive downlink communication signals from the base unit. Although only one transmitter 230 and one receiver 235 are illustrated, the user equipment apparatus 200 may have any suitable number of transmitters 230 and receivers 235. Further, the trans mi tter(s) 230 and the receiver(s) 235 may be any suitable type of transmiters and receivers. The transceiver 225 may include a first transmiter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmiter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

[0043] The first transmitter/ receiver pair may be used to communicate with a mobile communication network over licensed radio spectrum and the second transmiter/ receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. The first transmitter/receiver pair and the second transmiter/receiver pair may share one or more hardware components. For example, certain transceivers 225, transmiters 230, and receivers 235 may be implemented as physically separate components that access a shared hardware resource and/ or software resource, such as for example, the network interface 240.

[0044] One or more transmiters 230 and/ or one or more receivers 235 may be implemented and/ or integrated into a single hardware component, such as a multitransceiver chip, a system-on-a-chip, an Application-Specific Integrated Circuit (“ASIC”), or other type of hardware component. One or more transmiters 230 and/ or one or more receivers 235 may be implemented and/ or integrated into a multi-chip module. Other components such as the network interface 240 or other hardware components/ circuits may be integrated with any number of transmiters 230 and/ or receivers 235 into a single chip. The transmitters 230 and receivers 235 may be logically configured as a transceiver 225 that uses one more common control signals or as modular transmitters 230 and receivers 235 implemented in the same hardware chip or in a multi-chip module.

[0045] Figure 3 depicts further details of the network node 300 that may be used for implementing the methods described herein. The network node 300 may be one implementation of an entity in the wireless communication network, e.g. in one or more of the wireless communication networks described herein. The network node 300 may be embodied as network unit 104, a RAN 430, an NWDAF 1 510, an NWDAF 2 512, and/ or an NWDAF 610 as described herein. The network node 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325. [0046] The input device 315 and the output device 320 may be combined into a single device, such as a touchscreen. In some implementations, the network node 300 does not include any input device 315 and/ or output device 320. The network node 300 may include one or more of: the processor 305, the memory 310, and the transceiver 325, and may not include the input device 315 and/ or the output device 320.

[0047] As depicted, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with one or more remote units 200. Additionally, the transceiver 325 may support at least one network interface 340 and/ or application interface 345. The application interface(s) 345 may support one or more APIs. The network interface(s) 340 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 340 may be supported, as understood by one of ordinary skill in the art.

[0048] The processor 305 may include any known controller capable of executing computer-readable instructions and/ or capable of performing logical operations. For example, the processor 305 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller. The processor 305 may execute instructions stored in the memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.

[0049] The memory 310 may be a computer readable storage medium. The memory 310 may include volatile computer storage media. For example, the memory 310 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/ or static RAM (“SRAM”). The memory 310 may include non-volatile computer storage media. For example, the memory 310 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 310 may include both volatile and non-volatile computer storage media.

[0050] The memory 310 may store data related to establishing a multipath unicast link and/ or mobile operation. For example, the memory 310 may store parameters, configurations, resource assignments, policies, and the like, as described herein. The memory 310 may also store program code and related data, such as an operating system or other controller algorithms operating on the network node 300.

[0051] The input device 315 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. The input device 315 may be integrated with the output device 320, for example, as a touchscreen or similar touch-sensitive display. The input device 315 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/ or by handwriting on the touchscreen. The input device 315 may include two or more different devices, such as a keyboard and a touch panel.

[0052] The output device 320 may be designed to output visual, audible, and/ or haptic signals. The output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 320 may include a wearable display separate from, but communicatively coupled to, the rest of the network node 300, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 320 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0053] The output device 320 may include one or more speakers for producing sound. For example, the output device 320 may produce an audible alert or notification (e.g., a beep or chime). The output device 320 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 320 may be integrated with the input device 315. For example, the input device 315 and output device 320 may form a touchscreen or similar touch-sensitive display. The output device 320 may be located near the input device 315.

[0054] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. The one or more transmitters 330 may be used to communicate with the UE, as described herein. Similarly, the one or more receivers 335 may be used to communicate with network functions in the PLMN and/ or RAN, as described herein. Although only one transmitter 330 and one receiver 335 are illustrated, the network node 300 may have any suitable number of transmitters 330 and receivers 335. Further, the transmitter(s) 330 and the receiver(s) 335 may be any suitable type of transmitters and receivers.

[0055] In Release 18, 3GPP is studying enhancements to support XR (extended reality) media within 3GPP core network. The main principle of solutions being discussed is to allow the core network to guarantee delivery of media packets that are important at the application level for recovering the media traffic even when the media packet is sent via a best effort bearer. [0056] Most of the solutions proposes in 3GPP SA2 propose that the network identify important packets in a PDU-set. The PDU-set terminology in 3GPP TR 23.700-60 is as follows:

• PDU Set: A PDU Set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XRM Services, as used in TR 26.926. In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts all or of the information unit, when some PDUs are missing.

[0057] PDU-set specific QoS requirements may be defined that are either preconfigured in the 3GPP core network or provided by an AF. The QoS requirements for a PDU-set may be defined using any combination of the following parameters:

• PDU Set Delay Budget (PSDB);

• PDU Set Error Rate (PSER); and

• Whether a PDU is essential.

[0058] PDU Set Delay Budget (PSDB) defines an upper bound for the time that a PDU- Set may be delayed between the UE and the N6 termination point at the UPF. PSDB applies to the DL PDU-Set received by the UPF over the N6 interface, and to the UL PDU-Set sent by the UE,

[0059] PDU Set Error Rate (PSER) defines a ratio of dropped PDU-set by NG-RAN compared to total PDU-set sent to the UE.

[0060] Whether a PDU is essential indicates whether all PDUs of a PDU-set are required by a receiver.

[0061] The packets belonging to a PDU-set are handled by the core network as shown in Figure 4 which illustrates an overview of a core network (CN) XRM architecture handling of PDU sets. Figure 4 shows a system 400 comprising an Extended Reality Media Application Function (XRM AF) 410, a Policy and Control Function (PCF) 415, a Session Management Function (SMF) 420, an Access and Mobility Function (AMF) 425, a Radio Access Network (RAN 430, a User Equipment (UE) 435, a User Plane Function (UPF) 440, and an Extended Reality Application 445. The UE 435 may comprise a remote unit 102, a user equipment apparatus 200 and/ or a UE 504 as described herein.as described herein. The RAN 430 may comprise a base unit 104, a network node 300, an NWDAF 1 510, an NWDAF 2 512, and/or an NWDAF 610 as described herein. The operation of system 400 will now be described in the example of downlink traffic, a similar process may operate for uplink traffic.

[0062] At 480, the XRM AF 410 determines PDU set requirements.

[0063] At 481, the XRM Application Function 410 provides QoS requirements for packets of a PDU set to the PCF 415 and information to identify the application (i.e. 4- tuple or application id). The QoS requirements may comprise PSDB and PSER. The XRM AF 410 may also include an importance parameter for a PDU set and information for the core network to identify packets belonging to a PDU set.

[0064] At 482, the PCF 415 derives QoS rules for the XR application and specific QoS requirements for the PDU set. The QoS rules may use a 4G QoS identifier (5QI) for XR media traffic. The PCF 415 sends the QoS rules to the SMF 420. The PCF 415 may include in the communication to the SMF 420 Policy and Charging Control (PCC) rules per importance of a PDU set. The PCC rules may be derived according to information received from the XRM AF 410 or based on an operator configuration.

[0065] At 483, the SMF 420 establishes a QoS flow according to the QoS rules by the PCF 415 and configures the UPF to route packets of the XR application to a QoS flow, and, in addition, to enable PDU set handling. The SMF 420 also provides the QoS profile containing PDU set QoS requirements to the RAN 430 via the AMF 425. The AMF 425 may provide the QoS profile containing PDU set QoS requirements to the RAN 430 in an N2 Session Management (SM) container. Further, the AMF 425 may provide the QoS rules to the UE 435 in an N1 SM container.

[0066] At 484, the UPF 440 inspects the packets and determines packets belonging to a PDU set. The packet inspection may comprise inspecting the RTP packets. When the UPF 440 detects packets of a PDU set the UPF 440 marks the packets belonging to a PDU set within a GTP-U header. The GTP-U header information includes a PDU set sequence number and the size of the PDU set. The UPF 440 may also determine the importance of the PDU set either based on UPF 440 implementation means, information provided by the XRM AF 410 or information provided as metadata from an XRM application server. Based on the importance of the PDU set the UPF 440 may route the traffic to a corresponding QoS flow 1 (according to the rules received from the SMF 420) or include the importance of the PDU set within a GTP-U header. QoS flow 1 may comprise GTP-U headers, and these may include PDU set information.

[0067] At 485, the RAN 430 identifies packets belonging to a PDU set (based on the GTP-U marking) and handles the packets of the PDU set according to the QoS requirements of the PDU set provided by the SMF 420. RAN 430 may receive QFIs, QoS profile of QoS flow from SMF 420 (via AMF 425) during PDU session establishment/modification which includes PDSB and PSER. RAN 430 inspects GTP- U headers and ensures all packets of the same PDU set are handled according to the QoS profile. This may include packets of PDU set in a radio bearer carrying QoS flow 1.

This may also include sending packets not belonging to the PDU set in a different radio bearer carrying QoS flow 2.

[0068] The above example relates to downlink (DL) traffic. Reciprocal processing is applicable to uplink (UL) traffic wherein the role of UPF 440 packet inspection is taken by the UE 435 which is expected to inspect uplink packets, determine packets belonging to a PDU set, and signal accordingly the PDU set to the RAN 430 for scheduling and resource allocation corresponding to an associated DRB capable of fulfilling the PDU set QoS requirements (i.e., PSDB and PSER). The low-level signaling mechanism associated with the UL UE-to-RAN information passing are up to the specification and implementations of RAN signaling procedures.

[0069] Herein, extended Reality (XR) is used as an umbrella term for different types of realities, of which Virtual Reality, Augmented Reality, and Mixed Reality are examples. [0070] Virtual Reality (VR) is a rendered version of a delivered visual and audio scene. The rendering is in this case designed to mimic the visual and audio sensory stimuli of the real world as naturally as possible to an observer or user as they move within the limits defined by the application. Virtual reality usually, but not necessarily, requires a user to wear a head mounted display (HMD), to completely replace the user's field of view with a simulated visual component, and to wear headphones, to provide the user with the accompanying audio. Some form of head and motion tracking of the user in VR is usually also necessary to allow the simulated visual and audio components to be updated to ensure that, from the user's perspective, items and sound sources remain consistent with the user's movements. In some implementations additional means to interact with the virtual reality simulation may be provided but are not strictly necessary. [0071] Augmented Reality (AR) is when a user is provided with additional information or artificially generated items, or content overlaid upon their current environment. Such additional information or content will usually be visual and/ or audible and their observation of their current environment may be direct, with no intermediate sensing, processing, and rendering, or indirect, where their perception of their environment is relayed via sensors and may be enhanced or processed. [0072] Mixed Reality (MR) is an advanced form of AR where some virtual elements are inserted into the physical scene with the intent to provide the illusion that these elements are part of the real scene.

[0073] XR refers to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. It includes representative forms such as AR, MR and VR and the areas interpolated among them. The levels of virtuality range from partially sensory inputs to fully immersive VR. In some circles, a key aspect of XR is considered to be the extension of human experiences especially relating to the senses of existence (represented by VR) and the acquisition of cognition (represented by AR).

[0074] In 3GPP Release 17, 3GPP SA4 Working Group analyzed the Media transport Protocol and XR traffic model in the Technical Report TR 26.926 (vl.1.0) titled “Traffic Models and Quality Evaluation Methods for Media and XR Services in 5G Systems”, and decided the QoS requirements in terms of delay budget, data rate and error rate necessary for a satisfactory experience at the application level. These led to 4 additional 5G QoS Identifiers (5QIs) for the 5GS XR QoS flows. These 5Qis are defined in 3GPP TS 23.501 (vl7.5.0), Table 5.7.4-1, presented there as delay-critical GBR 5QIs valued 87-90. The latter are applicable to XR video streams and control metadata necessary to provide the immersive and interactive XR experiences.

[0075] The XR video traffic is mainly composed of multiple DL/UL video streams of high resolution (e.g., at least 1080p dual-eye buffer usually), frames-per-second (e.g., 60+ fps) and high bandwidth (e.g., usually at least 20-30 Mbps) which needs to be transmitted across a network with minimal delay (typically upper bounded by 15-20 ms) to maintain a reduced end-to-end application round-trip interaction delay. The latter requirements are of critical importance given the XR application dependency on cloud/ edge processing (e.g., content downloading, viewport generation and configuration, viewport update, viewport rendering, media encoding/ transcoding etc.).

[0076] The following additional assumptions have also been agreed:

• NG-RAN is the only entity that drops packet of a PDU-set in case of congestion.

• For a QoS flow there can be multiple priority PDU-sets. The NG-RAN drops the lower priority PDU-sets in case of congestions

• The NG-RAN drops all PDUs of a PDU-set

[0077] In addition, 3GPP has defined in 3GPP TS 23.288 vl 7.2.0 an architecture to support providing network analytics. In the architecture the NWDAF provides analytic output to one or more Analytics Consumer NFs based on Data Collected from one or more Data Producer NFs.

[0078] Figure 5 illustrates an example wireless communication system 500. The system 500 comprises a UE 504 an NWDAF Analytics Logical Functions (ANLF) 510, a an NWDAF Model Training Logical Function (MTLF) 512, a plurality of Data Producer Network Functions, in this example am Application Function (AF) 520, a 5G Network Function 522, and an Operations, Administration and Maintenance (OAM) 524. The wireless communication system 500 further comprises a plurality of Analytics Consumer Network Functions which in this example include an Application Function 530, a 5G Network Function 532, and an OAM 534. In the current Release 16 and Release 17 3GPP architecture, the NWDAFs 510, 512 (defined in 3GPP Technical Specification 23.288 vl7.2.0) provide analytic output to one or more of the Analytics Consumer NFs 530, 532, and 534 based on data collected from one or more Data Producer NFs 520, 522 and 524. The analytic output may be derived by the NWDAFs 510, 512 using Analytics sharing and/ or Federated Learning. The UE 504 may be embodied as a remote unit 102, a user equipment apparatus 200, and/ or a UE 435 as described herein. The NWDAF 1 510 and NWDAF 2 512, may be embodied as a network unit 104, a network node 300, RAN 430, and/ or a NWDAF 610 as described herein.

[0079] The Analytics Consumer NF may be one or more of an AF, OAM and 5G Core NFs (e.g., SMF, AMF, PCF). A full list of potential Analytics Consumer NF for each Analytics output the NWDAF provides is described in table 1 below.

Table 1: Example Analytics Consumer NFs

[0080] In particular, to support XR services, the following analytics are relevant to this disclosure. Such analytics can be beneficial for mobile XR users, or for the XR service provider/ vertical who needs to deploy the XRM service in a target area and time (e.g. for an event) and who requires the statistics /predictions on the QoS/ network performance and availability.

[0081] Observed experience analytics provide an indication of a service consumer experience for application traffic when routed via the 3GPP network. Examples include the average of observed Service MoS and/ or variance of observed Service MoS indicating service MOS distribution for services such as audio-visual streaming as well as services that are not audio-visual streaming such as V2X and Web Browsing services. [0082] The solutions proposed herein provide enhanced network analytics to allow a consumer (e.g. PCF or AF) to be aware how PDU-set marking affects the performance of the network and/ or the observed service experience of an application.

[0083] The observed service experience is enhanced to allow the consumer (e.g. an AF) to determine the observed service experience of XR applications that requested specific PDU-Set QoS requirements for the XR traffic and/ or the observed service experience. The application may comprise services configured with specific video /application quality. The XR media traffic may be routed via 5GS.

[0084] The consumer may include within Analytics Filter Information (in addition to the ones defined in Table 6.4.1-1 of 3GPP TS 23.288 vl7.2.0) any single piece or a combination of the following information.

[0085] A service experience of the XR application when 3rd party requests specific PDU-Set QoS requirements. Such a service experience may comprise a PDU set delay budget and PDU set error rate requested by the consumer.

[0086] A service experience of the XR application when the XR application uses a specific video quality. Alternatively, there may be included a service experience of the XR application when the XR application uses a general application quality. The consumer may provide this information in a request message.

[0087] A video quality (or application quality in general) can include: video resolution (4k, 2k etc), frame rate, codec configuration used (includes use of error correction techniques), number of important PDU-sets/ratio of I-frames to P/B frames in the video, and/or number of video coding spatial/ temporal enhancement layers.

[0088] The consumer may optionally include a list of location waypoints for a UE. The analytics consumer may include the location waypoints if the consumer requires service experience analytics for a mobile UE. [0089] If a new slice is defined for XR traffic, then the analytics consumer may include the S-NSSAI of the XR slice to determine the service experience of the user when XR traffic is routed via the XR slice.

[0090] The analytics request may include an indication to be notified if a service experience threshold according to the analytic result is not met (e.g. if the service experience falls bellow a certain threshold the NWDAF should notify the analytics consumer) .

[0091] When the NWDAF collects input data to determine analytics the NWDAF in addition to input data specified in clause 6.4.2 of 3GPP TS 23.288 vl7.2.0 additionally collects the following information:

• AF: Information on the quality of the video application (e.g. 4k video, frame rate, codec configuration used, number of important PDU-sets/ratio of I-frames to P/B frames in the video, and/ or a number of video coding spatial/ temporal enhancement layers). In an alternative embodiment the AF may include general information on the application quality (e.g. if the application is non-video related). The application quality can be represented as a metric value (1 to 10) with 10 being the application uses the highest quality settings (e.g. 4k gaming) and 1 the lowest (e.g. 320p video). The value used is negotiated based on agreements between the third party application provider and the network operator.

• AF: Performance data associated with the communication session of the UE with the application server for the XRM service related to packets of PDU-sets which includes, average PDU-set packet delay, average PDU-set packet loss rate and PDU-set packet throughput. In general, the AF has a capability to measure the performance of the XRM application session.

• SMF: QoS Flow Identifier of the QoS flow that includes the requested PDU-set QoS requirements.

• UPF/OAM/RAN or RAN monitoring entity: Observed PDU-set packet delay/PDU-set error rate, ratio of identified PDU-sets compared to PDUs not belonging to a PDU-set, ratio of higher/lower importance PDU-sets.

• OAM/RAN or RAN monitoring entity: Percentage of discarded PDU-Sets in the NG-RAN, average size of PDU-set and similar statistics filtered by aggregation based on the PDU-set priority/ importance levels as signaled for instance in the GTP-U header over N3 interface to RAN (e.g., average size of PDU sets and percentage of discarded PDU sets for high-importance PDU sets, such as video coded I-frames/slices/tiles).

[0092] The output analytics may include any selection of the following information:

• Service Experience analytics statistics and predictions when a session is created with specific PDU-set QoS requirements /targets.

• Service Experience analytics statistics and predictions when a session is created with specific video /application quality settings.

• A combination of the above can be provided if the analytics consumer includes both parameters within analytics filters in the analytics request.

[0093] Where the AF is a consumer, the AF can use the service experience analytics to determine if it needs to adjust the PDU-Set QoS requirements (e.g. reduce the PSDB to enhance service experience) when requesting a session over the 3GPP access to route application traffic or adjust the codec or frame rate of the video application.

[0094] Additionally, the AF as a consumer may carry out the following actions:

• Change encoder configuration.

• Change PDU-set grouping configuration.

• Change FEC codec redundancy or source block size.

[0095] By way of example, if the application server has the capability to include PDU-set information within RIP headers, then the application server may encode differently the PDU-set information within RTP header information taking into account analytics provided by the NWDAF.

[0096] Where the PCF is a consumer, the PCF may determine to modify the QoS rules moving the flow to a higher 5QI or adjusting the PSDB/PSER parameters.

[0097] Figure 6 is a messaging diagram illustrating a procedure 600 as described herein. The procedure 600 is an example of an observed service experience for video application using PDU-set QoS requirements. Figure 6 shows a Consumer 630, a Network Data Analytics Function (NWDAF) 610, a Network Exposure Function (NEF) 640, an Application Function (AF) 620, and a Network Function (NF) 624. The consumer 630 may be a further Network Function. The NWDAF 610 may be embodied as a network unit 104, a network node 300, a RAN 430, an NWDAF 1 510, and/ or an NWDAF 2 512 as described herein.

[0098] The procedure 600 begins at 671, where the Consumer 630 requests service experience for a video application. The consumer 630 additionally includes in the request PDU-set QoS requirements /targets and/or video quality/ application quality information to determine the service experience of a user when the video application is using specific PDU-set QoS requirements or video quality. The request may include an analytics identity. The analytics identity may comprise a Service Experience Analytic Filter, which may take the form of a PDU set QoS requirement, and/ or a video quality. [0099] At 672a, the NWDAF 610 collects input data from an AF 620 serving the video application. Based on the additional filters in step 671 the NWDAF 610 determines to collect information on the quality of the video application by collecting one or more of the following: video resolution (4k, 2k etc), frame rate (frame per second of the video) , number of important PDU-sets/ratio of I-frames to P/B frames in the video, number of video encoded enhancement layers in the video (e.g., spatial or temporal enhancement layers) and/ or an application quality metric (a scalar value). The collection at 672a may be initiated by a subscription message, the subscription message comprising an event identity, the event identity comprising Service Experience information (such as Video Quality) .

[0100] At 672b, the NWDAF 610 collects input data from UPF/OAM/SMF. The NWDAF 610 determines the UPF that carries out PDU-set marking serving the UE by querying the SMF. The NWDAF 610 additionally collects one or more of the following: observed PDU-set packet delay, observed PDU-set error rate, a ratio of identified PDU- sets compared to PDUs not belonging to a PDU-set, ratio of higher/lower importance PDU-sets, and from the OAM, the percentage of discarded PDU-Sets in the NG-RAN, and/ or the average size of a PDU-set. The collection at 672b may be initiated by a subscription message comprising an event identity; the event identity may comprise additional PDU-set information.

[0101] The process 600 is illustrated in Figure 6 with the specific example of the NWDAF 610 collecting input data from a Network Function 624. The data collection step may comprise collecting data from a plurality of Network Functions 624. Furthermore, the data collection step may comprise collecting data from a node which is not a network function, such as, for example, an Operations, Administration and Maintenance (OAM). Further still, the data collection step may comprise collecting data from a RAN monitoring entity.

[0102] At 672c, the NWDAF 610 derives analytics taking into account the additional information based on the analytic filters requested in step 671.

[0103] At 673, the NWDAF 610 provides analytics information to the consumer 630. The analytics information may comprise an estimated Service Experience. [0104] There is provided a network node of a wireless communication system, the network node comprising: a processor; and a memory coupled with the processor. The processor is configured to cause the network node to: receive a request from an analytics consumer, the request comprising a request for analytics of service experience for a particular service when the particular service is using a specific quality requirement; collect service performance data from a network function; collect network performance data from at least one other network node; derive from the service performance data and network performance data, service experience analytics; and send the service experience analytics to the analytics consumer.

[0105] The network function may comprise an application function. The service may be an XRM service. The network node may comprise an analytics function. The network node may comprise an NWDAF.

[0106] Such an arrangement allows the analytics consumer to determine if QoS requirements for the particular service are sustainable, and as such determine if the user service experience is acceptable. Such a determination may be made in respect of a specific area and/ or time period. The specific area and/ or time period may be defined by the specific PDU-set. Based on the analytic information received from the network node, the analytics consumer may elect to make a corrective action. Such a corrective action may comprise upgrading PDU-set quality of service (QoS) requirements to improve the performance of the service when traffic carrying data for the service is routed via the 5GS system.

[0107] The specific quality requirement may define a specific video quality for the particular service. The specific quality requirement may define a service experience threshold for the particular service. The specific quality requirement may be defined by a provider of the particular service. The specific quality requirement may comprise a quality requirement for a class of PDU-set.

[0108] The class of PDU-set may be defined as a PDU-set used for delivering a service. The class of PDU set may comprise a PDU-set used for delivering video. The class of PDU-set may be a type of PDU-set. The class of PDU-set may be defined by QoS requirements. The QoS requirements may comprise at least one PDU-set QoS requirement.

[0109] The specific quality requirement may comprise a PDU-set QoS requirement for the particular service. The derived service experience analytics may be filtered so as to be limited to the specific quality requirement. The derived service experience analytics may be limited to when the service was delivered meeting the specific quality requirement.

[0110] The specific quality requirement may comprise at least one of: a QoS target for protocol data units of a service belonging to a PDU-set; a specific quality for the particular service set by a provider of the particular service; and a service experience threshold.

[0111] The QoS target may comprise QoS requirements for a PDU-set. The PDU-set may deliver data for the service. The PDU-set QoS requirements may comprise PDU- set Delay Budget and PDU-set error rate. The service experience threshold may define a measure of the service experience which once passed, triggers a notification to be sent from the network node to the analytics consumer. The session for the service may comprise an application session. The definition of the quality of a session for the service may comprise at least one of: frame rate, video quality, and/ or codec used. The session for the service may comprise a communication session.

[0112] A session used to deliver the service from an application server to a user equipment may include a connection via a 5G System.

[0113] The service performance data may comprise at least one of: information on the application quality; frame rate; video quality; codec used; a characteristic of the communication session used to deliver the service from the application server to a user equipment; and/ or a PDU set delay. The codec used may be the codec used to encode the video, where the service includes video delivered via the wireless communication system.

[0114] The network performance data comprise the observed performance of the service with the specific quality requirement.

[0115] The observed performance of the service with a specific PDU-set QoS requirements may comprise any combination of: PDU-set packet delay; PDU-set error rate; a ratio of identified PDU-sets compared to PDUs not belonging to a PDU-set; a ratio of higher and/or lower importance PDU-sets; a percentage of discarded PDU-Sets in the wireless communication system; and/ or an average size of a PDU-set.

[0116] The percentage of discarded PDU-Sets in the NG-RAN may be obtained from an Operations, Administration and Maintenance function (OAM). The average size of PDU-set may be derived from an OAM.

[0117] The at least one other network node may comprise any of: one or more network functions; a RAN monitoring entity; and/ or an OAM for the service. [0118] The wireless communication network may comprise a Radio access Network (RAN). The one or more network functions may comprise an SMF and/ or a UPF.

[0119] Figure 7 illustrates a method 700 in a network node of a wireless communication system, the method comprising: receiving 710 a request from an analytics consumer, the request comprising a request for analytics of service experience for a particular service when the particular service is using a specific quality requirement. The method 700 further comprises collecting 720 service performance data from a network function; collecting 730 network performance data from at least one other network node; deriving 740 from the service performance data and network performance data, service experience analytics; and sending 750 the service experience analytics to the analytics consumer.

[0120] In certain embodiments, the method 700 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0121] The network function may comprise an application function. The service may be an XRM service. The network node may comprise an analytics function. The network node may comprise an NWDAF.

[0122] Such an arrangement allows the analytics consumer to determine if QoS requirements for the particular service are sustainable, and as such determine if the user service experience is acceptable. Such a determination may be made in respect of a specific area and/ or time period. The specific area and/ or time period may be defined by the specific PDU-set. Based on the analytic information received from the network node, the analytics consumer may elect to make a corrective action. Such a corrective action may comprise upgrading PDU-set quality of service (QoS) requirements to improve the performance of the service when traffic carrying data for the service is routed via the 5GS system.

[0123] The specific quality requirement may define a specific video quality for the particular service. The specific quality requirement may define a service experience threshold for the particular service. The specific quality requirement may be defined by a provider of the particular service.

[0124] The specific quality requirement may comprise a quality requirement for a class of PDU-set. The class of PDU-set may be defined as a PDU-set used for delivering a service. The class of PDU set may comprise a PDU-set used for delivering video. The class of PDU-set may be a type of PDU-set. The class of PDU-set may be defined by QoS requirements. The QoS requirements may comprise at least one PDU-set QoS requirement. The specific quality requirement may comprise a PDU-set QoS requirement for the particular service.

[0125] The derived service experience analytics are filtered so as to be limited to the specific quality requirement. The derived service experience analytics may be limited to when the service was delivered meeting the specific quality requirement.

[0126] The specific quality requirement may comprise at least one of: a QoS target for protocol data units of a service belonging to a PDU-set; a specific quality for the particular service set by a provider of the particular service; and a service experience threshold.

[0127] The QoS target may comprise QoS requirements for a PDU-set. The PDU-set may deliver data for the service. The PDU-set QoS requirements may comprise PDU- set Delay Budget and PDU-set error rate.

[0128] The service experience threshold may define a measure of the service experience which once passed, triggers a notification to be sent from the network node to the analytics consumer. The session for the service may comprise an application session. The definition of the quality of a session for the service may comprise at least one of: frame rate, video quality, and/ or codec used. The session for the service may comprise a communication session.

[0129] A session used to deliver the service from an application server to a user equipment may include a connection via a 5G System.

[0130] The service performance data may comprise at least one of: information on the application quality; frame rate; video quality; codec used; a characteristic of the communication session used to deliver the service from the application server to a user equipment; and/ or a PDU set delay.

[0131] The network performance data may comprise the observed performance of the service with the specific quality requirement.

[0132] The observed performance of the service with a specific PDU-set QoS requirements may comprise any combination of: PDU-set packet delay; PDU-set error rate; a ratio of identified PDU-sets compared to PDUs not belonging to a PDU-set; a ratio of higher and/or lower importance PDU-sets; a percentage of discarded PDU-Sets in the wireless communication system; and/ or an average size of a PDU-set. [0133] The percentage of discarded PDU-Sets in the NG-RAN may be obtained from an Operations, Administration and Maintenance function (OAM) . The average size of PDU-set may be derived from an OAM.

[0134] The method at least one other network node may comprise any of: one or more network functions; a RAN monitoring entity; and/ or an OAM for the service.

[0135] The wireless communication network may comprise a Radio access Network (RAN). The one or more network functions may comprise an SMF and/ or a UPF.

[0136] The solution described herein allows a consumer via analytics information to the NWDAF to determine if the PDU-set QoS requirements requested for a video application are sustainable in a specific area/ time period and/or if the user service experience is acceptable. Based on the analytic information received the consumer can determine to upgrade the requested PDU-set QoS requirements to improve the performance of the video application when traffic is routed via the 5GS system.

[0137] The solution presented herein enhances the existing analytics provided by the NWDAF (observed service experience, QoS sustainability, network performance analytics) to additionally provide statistics or predictions when specific PDU-set QoS requirements are requested and/ or a specific video quality is used for the video application traffic routed via the 5GS system.

[0138] The service experience, QoS sustainability, and network performance analytics provided by the NWDAF are already defined in 3GPP TS 23.288 vl7.2.0 but they cannot be used to determine the performance of the network when PDU-set QoS requirements are requested.

[0139] There is provided herein a method wherein a network data analytics function receives a first request from an analytics consumer the request including analytics of service experience with specific PDU-set QoS targets/ specific video quality for an XRM service; determines to collect application performance data from a second network function [such as an AF] for the XRM service wherein the performance data additionally includes information on the application quality and performance data associated to the communication session of the XRM service between the UE and the application. The information on the application quality may comprise frame rate, video quality, codec used etc. The performance date may comprise PDU set delay etc.

[0140] The method further comprises determining to collect network performance data from a list containing at least one of one or more network functions [such as SMF, UPF], a RAN monitoring entity or OAM for the XRM service wherein the data additionally includes the observed performance of the application with specific PDU-set QoS requirements, and derives and provides service experience analytics to the analytics consumer.

[0141] The specific PDU-set QoS requirements may comprise Observed PDU-set packet delay/PDU-set error rate, ratio of identified PDU-sets compared to PDUs not belonging to a PDU-set, ratio of higher/lower importance PDU-sets, OAM: Percentage of discarded PDU-Sets in the NG-RAN, average size of PDU-set.

[0142] The PDU-set QoS requirements may be PDU-set Delay Budget and PDU-set error rate.

[0143] An XRM service may be associated with an XRM service related communication session for an application between the UE and an application server via 5GS

[0144] The analytic request may include a service experience threshold to be notified if the analytic output exceeds the threshold.

[0145] The analytics request may include a quality of the application session. The quality of the application session may include one or more of frame rate, video quality, codec used etc.

[0146] It should be noted that the above-mentioned methods and apparatus illustrate rather than limit the invention, and that those skilled in the art will be able to design many alternative arrangements 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.

[0147] Further, while examples have been given in the context of particular communication standards, these examples are not intended to be the limit of the communication standards to which the disclosed method and apparatus may be applied. For example, while specific examples have been given in the context of 3GPP, the principles disclosed herein can also be applied to another wireless communication system, and indeed any communication system which uses routing rules.

[0148] The method may also be embodied in a set of instructions, stored on a computer readable medium, which when loaded into a computer processor, Digital Signal Processor (DSP) or similar, causes the processor to carry out the hereinbefore described methods. [0149] The described methods and apparatus may be practiced in other specific forms.

The described methods and apparatus are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

[0150] The following abbreviations are relevant in the field addressed by this document: UE, User Equipment; PDU, Protocol Data Unit; PDU-set, Protocol Data Unit Set; UL, Uplink; DL, Downlink; QoS, Quality of Service; XR, Extended Reality; PSDB, PDU Set Delay Budget; PDB, Packet Delay Budget; PSER, PDU Set Error Rate; NWDAF,

Network Data Analytics Function; UPF, User Plane Function; SMF, Session Management Function; and OAM, Operations, Administration and Maintenance.