Quality of service coordination for virtual experience services in wireless communication networks

Abstract

An enabling entity for a virtual experience service is provided, the enabling entity in a wireless communication network, the enabling entity comprising a receiver, a processor, and a transmitter. The receiver is arranged to receive application service requirements corresponding to a plurality of devices operating in a physical space or in a virtual space of the virtual experience service or both. The processor is arranged to decompose the application service requirements into a plurality of session requirements, where the session requirements are suitable for a plurality of communication sessions provided between devices in both a physical space and a virtual space and derive a set of joint quality of service parameters for the plurality of sessions based on the session requirements. The transmitter is arranged to transmit the set of joint quality of service parameters to one or more network entities in the wireless communication network.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to the field of implementing quality of service coordination of virtual experience services in wireless communication networks. An enabling entity for a virtual experience service and a method in an enabling entity for a virtual experience service are defined herein. Background Art

[0002] Virtual reality (VR), augmented reality (AR), and extended reality (XR) are types of virtual spaces where users of electronic devices can interact with each other. Electronic devices can communicate using wireless communication networks. This virtual space can be traded using cryptocurrency. Such transactions can include the exchange of digital works, including but not limited to non-fungible tokens (NFTs).

[0003] The Metaverse is an example of this virtual space. The Metaverse is an open, shared, and persistent virtual world that provides access to 3D virtual spaces, solutions, and environments created by users. The Metaverse is a digital reality that combines aspects of social media, online games, augmented reality (AR), virtual reality (VR), and cryptocurrency to allow users to interact virtually. As the Metaverse develops, it will create an online space where user interactions are more multidimensional than current technology supports. Users in the Metaverse will be able to immerse themselves in a space where the digital and physical worlds merge, rather than just watching digital content.

[0004] In the Metaverse, everything a user creates and owns in the Metaverse is their asset, whether it is virtual real estate or artifacts. The Metaverse grants its users the privilege of full ownership. In addition, the persistence factor is very important because even if a user exits the Metaverse, the digital avatar will still be in the Metaverse. It will function normally when other users interact and interact with the Metaverse. Avatars, digital objects, virtual devices, objects in the Metaverse, and digital twins are all different representations of objects / devices instantiated / deployed in the virtual space of a virtual experience service. According to some definitions, avatars are our digital representations in virtual space. For example, a user's Metaverse avatar is essentially a representation of the user and / or his or her user equipment in the Metaverse. The avatar can look exactly like the user or device in the real world, or it can be enhanced. Therefore, the avatar UE can be regarded as a digital representation of a virtualized user device in the Metaverse. The user's device can be a mobile phone, a cellular phone, smart glasses, and / or a smart watch.

[0005] There is a need to optimize the delivery of virtual experience services in wireless communication networks. Summary of the invention

[0006] In order to support traffic flow simulation and situational awareness services of virtual experience services, wireless communication networks need to provide low latency, high data rate and high reliability transmission. Wireless communication networks may also need to be enhanced to meet the service requirements for traffic flow simulation and situational awareness. At the same time, in addition to the real objects of the UE that can host the cellular system, their corresponding virtual objects can also interact with each other and interact with physical objects via the wireless communication network. Therefore, it is necessary to optimize the implementation of virtual experience services in wireless communication networks.

[0007] Disclosed herein is a procedure for quality of service coordination for a virtual experience service in a wireless communication network. The procedure may be implemented by an enabling entity for a virtual experience service and a method in an enabling entity for a virtual experience service.

[0008] An enabling entity for a virtual experience service is provided, the enabling entity being in a wireless communication network, the enabling entity comprising a receiver, a processor and a transmitter. The receiver is arranged to receive application service requirements corresponding to a plurality of devices, the plurality of devices operating in a physical space or in a virtual space of the virtual experience service or in both. The processor is arranged to decompose the application service requirements into a plurality of session requirements, wherein the session requirements are suitable for a plurality of communication sessions provided between devices in both a physical space and a virtual space and a set of joint quality of service parameters for the plurality of sessions are derived based on the session requirements. The transmitter is arranged to send the set of joint quality of service parameters to one or more network entities in the wireless communication network.

[0009] A method in an enabling entity for a virtual experience service is further provided, the enabling entity being in a wireless communication network. The method includes receiving application service requirements corresponding to a plurality of devices, the plurality of devices operating in a physical space or in a virtual space of the virtual experience service, or in both. The method further includes decomposing the application service requirements into a plurality of session requirements, wherein the session requirements are suitable for a plurality of communication sessions, the communication sessions being provided between devices in both the physical space and the virtual space, and deriving a set of joint quality of service parameters for the plurality of sessions based on the session requirements. The method further includes sending the set of joint quality of service parameters to one or more network entities in the wireless communication network. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to describe the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is reproduced by reference to certain devices and methods illustrated in the accompanying drawings. Each of these figures depicts only certain aspects of the present disclosure and therefore should not be considered to limit its scope. For clarity, the figures may have been simplified and are not necessarily drawn to scale.

[0011] A method and apparatus for quality of service coordination of a virtual experience service in a wireless communication network will now be described by way of example only with reference to the accompanying drawings, wherein:

[0012] FIG1 depicts a wireless communication system for quality of service coordination of a virtual experience service in a wireless communication network;

[0013] Figure 2 Depicting a user equipment device that can be used to implement the methods described herein;

[0014] Figure 3 Describes other details of a network node that may be used to implement the methods described herein;

[0015] Figure 4 A multi-mode feedback service implemented in a wireless communication network is described;

[0016] Figure 5 Describe 5G-enabled traffic flow simulation that includes situational awareness;

[0017] Figure 6 A method in an enabling entity for a virtual experience service, the enabling entity being in a wireless communication network, is described;

[0018] Figure 7 Examples of multi-mode sessions and multi-mode data flow groups are described;

[0019] Figure 8 describing a system implemented as an example of the method described herein;

[0020] Fig. 9 Explain the possible sessions of the virtual experience service;

[0021] Fig.10 Explain four different application sessions that may exist in a virtual experience service (e.g., a mobile metaverse service);

[0022] Fig.11 Demonstrate the operation of an enabling server operating as a QoS coordination function; and

[0023] Fig.12 A method for coordinating a PDU session at a meta-control network function is described. DETAILED DESCRIPTION

[0024] Those skilled in the art will appreciate that aspects of the present disclosure may be embodied as systems, devices, methods, or program products. Thus, the arrangements described herein may be implemented in full hardware form, full software form (including firmware, resident software, microcode, etc.), or in a combination of software and hardware aspects.

[0025] For example, the disclosed methods and apparatus may be implemented as hardware circuits (including 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 be organized, for example, as an object, procedure, or function.

[0026] In addition, 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 (hereinafter referred to as code). The storage device may be tangible, non-transitory, and / or non-transmitting. The storage device may not embody signals. In some arrangements, the storage device only uses signals to access the code.

[0027] Any combination of one or more computer readable media 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 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.

[0028] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more conductors, 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 disk 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 conjunction with an instruction execution system, apparatus, or device.

[0029] Throughout this specification, reference to an example or similar language of a particular method or device means that a specific feature, structure or characteristic described in conjunction with the example is included in at least one embodiment of the method and device described herein. Therefore, unless otherwise expressly specified, reference to the features or similar language of an example of a particular method or device may refer to but not necessarily all refer to the same example, but means "one or more but not all examples". Unless otherwise expressly specified, the terms "comprise", "include", "have" and their variations mean "including but not limited to". Unless otherwise expressly specified, the list of items listed does not imply that any or all items are mutually exclusive. Unless otherwise expressly specified, the terms "one" and "described" also refer to "one or more".

[0030] As used herein, a list with the conjunction "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 term "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 term "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 a combination of A, B, and C. As used herein, "a member selected from a group consisting of A, B, and C" includes one and only one of A, B, or C and excludes a combination 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.

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

[0032] Aspects of the disclosed methods and devices are described below with reference to schematic flow charts and / or schematic block diagrams of methods, devices, systems, and program products. It should be understood that each frame of the schematic flow charts and / or schematic block diagrams and the combination of frames in the schematic flow charts and / or schematic block diagrams can be implemented by code. This code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create components for implementing the functions / actions specified in the schematic flow charts and / or schematic block diagrams.

[0033] The code may also be stored in a storage device, which may instruct a computer, other programmable data processing equipment or other devices to operate in a specific manner so that the instructions stored in the storage device produce a product containing instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0034] The code may also be loaded onto a computer, other programmable data processing device or other apparatus to cause a series of operational steps to be performed on the computer, other programmable device or other apparatus to produce a computer-implemented process, so that the code executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0035] The schematic flow charts and / or schematic block diagrams in the figures illustrate the architecture, functionality and operation of possible implementations of devices, systems, methods and program products. In this regard, each box in the schematic flow charts and / or schematic block diagrams may represent a code module, segment or portion of one or more executable instructions of the code for implementing the specified logical function.

[0036] It should also be noted that in some alternative implementations, the functions described in the blocks may not occur in the order described in the figures. For example, two blocks shown in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods that are equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated figures are contemplated.

[0037] The description of an element in each figure may refer to an element of a previous figure. Like numbers refer to like elements in all figures.

[0038] FIG1 depicts an embodiment of a wireless communication system 100 for quality of service coordination of a virtual experience service in a wireless communication network. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although a specific number of remote units 102 and network units 104 are depicted in FIG1 , one skilled 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 include a user equipment device 200 or UE 710, 720, 810, 910, 912, 1010, 1020, 1110, 1120, as described herein.

[0039] In one embodiment, the remote unit 102 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a car computer, a network device (e.g., a router, a switch, a modem), an aircraft, a drone, or the like. In some embodiments, the remote unit 102 includes a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, or the like. In addition, the remote unit 102 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or by other terms used in the art. The remote unit 102 may communicate directly with one or more of the network units 104 via UL communication signals. In some embodiments, the remote unit 102 may communicate directly with other remote units 102 via sidelink communications.

[0040] The network elements 104 may be distributed over a geographic area. In certain embodiments, the network elements 104 may also be referred to as access points, access terminals, base stations, base stations, node-Bs, eNBs, gNBs, home node-Bs, relay nodes, devices, core networks, air servers, radio access nodes, APs, NRs, network entities, access and mobility management functions (“AMFs”), unified data management functions (“UDMs”), unified data repositories (“UDRs”), UDM / UDRs, policy control functions (“PCFs”), radio access networks (“RANs”), network slice selection functions (“NSSFs”), or by any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers that are communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and public switched telephone networks, among other networks. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those of ordinary skill in the art.

[0041] In one embodiment, the wireless communication system 100 conforms to the New Radio (NR) protocol standardized in 3GPP, wherein the network unit 104 transmits on the downlink (DL) using an orthogonal frequency division multiplexing ("OFDM") modulation scheme, and the remote unit 102 transmits 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, such as WiMAX, a variant of IEEE 802.11, GSM, GPRS, UMTS, a variant of LTE, CDMA2000, ZigBee, Sigfoxx, and other protocols. The present disclosure is not intended to be limited to implementation of any particular wireless communication system architecture or protocol.

[0042] The network unit 104 may serve a number of remote units 102 within a service area (eg, a cell or cell sector) via wireless communication links. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0043] Wireless communication systems can be adapted to more effectively accommodate use cases and potential requirements for localized Metaverse services. Some examples of such use cases are discussed below.

[0044] Engineering design has become a demanding activity since the industrial age. Collaborative and concurrent engineering is a concept and methodology that emerged at the end of the last century and is defined as a systematic approach to the integrated and collaborative design of products and their related processes. The diversity and complexity of real products require engineers from different geographical locations to collaborate to share ideas and solutions with customers and evaluate product development. VR and AR technologies have found their way into critical applications in industrial fields such as aerospace engineering, automotive engineering, medical engineering, and in the fields of education and entertainment. The technology range includes Cave Automated Virtual Environment (better known by the recursive acronym CAVE) environments, reality theaters, powered walls, holographic workbenches, personal immersive systems, head-mounted displays, tactile sensing interfaces, tactile feedback devices, multi-sensory devices, voice interfaces, and mixed reality systems.

[0045] The multimodal feedback service based on the mobile metaverse describes the situation where multiple physical entities or their digital avatars interact with each other. New feedback modes are also introduced in this use case to meet new scenarios and requirements in the mobile metaverse. Note that the mobile metaverse is a cyberspace parallel to the real world, which tends to make the virtual world more realistic and the real world richer. This service tends to make better use of different feedback clues and implement multimodal feedback clues to adapt to different scenarios, so as to meet the accuracy of tasks and user experience, etc. More modes should be explored to meet more immersive requirements of physical entities in the real world (such as smell and taste). In order to achieve more immersive requirements of different scenarios in the mobile metaverse, it is very important to explore the time synchronization or asynchronous boundaries of audio, video, touch, smell, taste, etc.

[0046] Physical devices, physical entities, and physical objects exist in a physical space, which can be referred to as the real world. This is in contrast to virtual devices, virtual entities, and virtual objects that exist in the virtual space of a virtual experience service. There may be a mapping between physical devices, physical entities, and physical objects and virtual devices, virtual entities, and virtual objects. The mapping can be one-to-one, many-to-one, or one-to-many. The physical space can be defined as the physical world or real environment, which includes physical objects and / or devices running software that provides virtual experience services. The hardware that provides virtual experience services can be geographically distributed and distributed in different software environments. The hardware can be physically close to the physical location where the physical user of the virtual experience service is physically located.

[0047] Figure 2 A user equipment device 200 is depicted that can be used to implement the methods described herein. The user equipment device 200 is used to implement one or more of the solutions described herein. The user equipment device 200 is consistent with one or more of the user equipment devices described in the embodiments herein. In particular, the user equipment device 200 may include a remote unit 102 or UE 710, 720, 810, 910, 912, 1010, 1020, 1110, 1120, as described herein. The user equipment device 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

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

[0049] As depicted, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 can communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 225 can operate on an unlicensed spectrum. In addition, the transceiver 225 can include multiple UE panels supporting one or more beams. In addition, the transceiver 225 can support at least one network interface 240 and / or application interface 245. The application interface 245 can support one or more APIs. The network interface 240 can support 3GPP reference points, such as Uu, N1, PC5, etc. It should be understood by a person of ordinary skill in the art that other network interfaces 240 can be supported.

[0050] 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 a 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.

[0051] Processor 205 may control user equipment device 200 to implement the user equipment device behaviors described herein. Processor 205 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

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

[0053] Memory 210 may store data related to implementing the traffic class field, as described herein. Memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on device 200.

[0054] Input device 215 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, or the like. Input device 215 may be integrated with output device 220, for example, as a touch screen or similar touch-sensitive display. Input device 215 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 215 may include two or more different devices, such as a keyboard and a touch panel.

[0055] The output device 220 may be designed to output visual signals, auditory signals, and / or tactile signals. The output device 220 may include an electronically controllable display or a 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 a 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 that is separate from the rest of the user equipment device 200 but communicatively coupled to the rest, such as a smart watch, smart glasses, a head-mounted display, or the like. In addition, the output device 220 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0056] Output device 220 may include one or more speakers for producing sounds. For example, output device 220 may produce an auditory alarm or notification (such as a beep or chime). Output device 220 may include one or more haptic devices for producing vibration, motion, or other tactile feedback. Output device 220 may be integrated with input device 215 in whole or in part. For example, input device 215 and output device 220 may form a touch screen or similar touch-sensitive display. Output device 220 may be positioned near input device 215.

[0057] The transceiver 225 communicates with one or more network functions of the 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 receive messages, data, and other signals. For example, the processor 205 may selectively activate the transceiver 225 (or a portion thereof) at a particular time in order to send and receive messages.

[0058] 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 device 200 may have any suitable number of transmitters 230 and receivers 235. In addition, the transmitter 230 and the receiver 235 may be any suitable type of transmitter and receiver. The transceiver 225 may include a first transmitter / receiver pair for communicating with a mobile communication network via a licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via an unlicensed radio spectrum.

[0059] The first transmitter / receiver pair may be used to communicate with a mobile communication network via a licensed radio spectrum, and the second transmitter / receiver pair may be used to communicate with a mobile communication network via an unlicensed radio spectrum. The first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some of the transceivers 225, transmitters 230, and receivers 235 may be implemented as physically separate components that access shared hardware resources and / or software resources such as the network interface 240.

[0060] The one or more transmitters 230 and / or the one or more receivers 235 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a single chip system, an application specific integrated circuit ("ASIC"), or other type of hardware component. The one or more transmitters 230 and / or the 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 into a single chip with any number of transmitters 230 and / or receivers 235. The transmitters 230 and receivers 235 may be logically configured as transceivers 225 using one or more common control signals or configured as modular transmitters 230 and receivers 235 implemented in the same hardware chip or multi-chip module.

[0061] Figure 3Describes further details of a network node 300 that may be used to implement the methods described herein. The network node 300 may be one implementation of an entity in a wireless communication network, such as in one or more of the wireless communication networks described herein. For example, the network node 300 may be a network function configured to support a virtual experience service, a meta-aware network function 852, a meta-enabler 1052, 1152, or a meta-control network function 1243. In another implementation, the network node 300 may be deployed as an application function dedicated to a virtual experience service (which may include XR, AR, VR, and / or MR). In addition, the network node 300 may include an application server residing at an edge server, a cloud server, or a server in a wireless communication system. The network node 300 may be a meta-aware application function (AF), a media streaming application function, or a media streaming application server that provides support for a mobile metaverse service. This network node may be implemented in accordance with 3GPP SA4.

[0062] The network node 300 includes a processor 305 , a memory 310 , an input device 315 , an output device 320 , and a transceiver 325 .

[0063] The input device 315 and the output device 320 may be combined into a single device, such as a touch screen. 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 following: a processor 305, a memory 310, and a transceiver 325, and may not include an input device 315 and / or an output device 320.

[0064] 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. In addition, the transceiver 325 can support at least one network interface 340 and / or an application interface 345. The application interface 345 can support one or more APIs. The network interface 340 can support 3GPP reference points such as Uu, N1, N2, and N3. It should be understood by those of ordinary skill in the art that other network interfaces 340 can be supported.

[0065] 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, an FPGA, or a 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.

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

[0067] 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 algorithm operating on the network node 300.

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

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

[0070] Output device 320 may include one or more speakers for producing sounds. For example, output device 320 may produce an auditory alarm or notification (such as a beep or chime). Output device 320 may include one or more haptic devices for producing vibration, motion, or other tactile feedback. Output device 320 may be integrated with input device 315 in whole or in part. For example, input device 315 and output device 320 may form a touch screen or similar touch-sensitive display. Output device 320 may be positioned near input device 315.

[0071] 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 the 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. Furthermore, the transmitters 330 and receivers 335 may be any suitable type of transmitters and receivers.

[0072] Figure 4 A multimodal feedback service implemented in a wireless communication network is described. User interaction 410 with a user device having a display 412 is captured as sensor data, which is sent to one or more edge servers 432, 434 via a 5G network 420. The user equipment is arranged to run an application for allowing the user to interact with the metaverse. Each edge server 432, 434 can provide encoding and rendering services and multimodal feedback services. The edge servers 432, 434 send service data and / or feedback data back to the user equipment. The edge servers 432, 434 send shared data to the cloud server 440. The multimodal feedback service based on the mobile metaverse can be deployed at the edge / cloud servers 432, 434, 440 for different scenarios. During the application runtime period, the physical entity of the wireless communication network can provide an immersive experience to the user via its avatar, and the multimodal feedback data can be exchanged with each other, whether the physical entity is close or not. Figure 4 It illustrates how multimodal feedback services are applied in the mobile metaverse, and the main impact on 3GPP is whether and how 5GS can be used to better utilize different feedback cues and enable multimodal feedback cues for experiences related to multiple physical entities.

[0073] Figure 5 Demonstrating 5G-enabled traffic flow simulation with situational awareness. With 5GS support, real-time information and data about real objects can be delivered to virtual objects in the metaverse. Figure 5A virtual world including multiple real objects 510 and multiple digital twin objects 560 is displayed. The wireless communication network 520 carries sensor data from the real object 510 and delivers this to the digital twin object 560. The wireless communication network 520 delivers situational information from the digital twin object 560 in the virtual space back to the real object 510. Such situational information may include traffic guidance and auxiliary data. In this way, road infrastructure and traffic participants (including vulnerable road users) can form an intelligent traffic metaverse. Real-time processing and calculation can then be performed to support traffic simulation, and situational awareness and real-time path guidance and real-time safety or safety alerts can also be generated for ICVs, drivers and passengers.

[0074] In order to support traffic flow simulation and situational awareness services, the 5G network 520 needs to provide low latency, high data rate and high reliability transmission, and in addition, the 5G network 520 may also need to be further enhanced to meet the service requirements for traffic flow simulation and situational awareness with 5G capabilities. At the same time, in addition to the real objects 510 of the UE that can host the cellular system, their corresponding virtual objects 560 can also interact with each other and interact with the physical objects 510 via 5GS.

[0075] An enabling entity for a virtual experience service is provided, the enabling entity being in a wireless communication network, the enabling entity comprising a receiver, a processor and a transmitter. The receiver is arranged to receive application service requirements corresponding to a plurality of devices, the plurality of devices operating in a physical space or in a virtual space of the virtual experience service or in both. The processor is arranged to decompose the application service requirements into a plurality of session requirements, wherein the session requirements are suitable for a plurality of communication sessions provided between devices in both a physical space and a virtual space and a set of joint quality of service parameters for the plurality of sessions are derived based on the session requirements. The transmitter is arranged to send the set of joint quality of service parameters to one or more network entities in the wireless communication network.

[0076] This enabling entity provides a mechanism for quality of service coordination for multi-user and multi-mode virtual experience services. The enabling entity can be at the 5GC or at the edge / cloud SP domain and supports the conversion of requirements between the virtual experience service and the underlying wireless communication network. The enabling entity can further optimize performance by compensating for possible quality of service changes for one or more sessions.

[0077] The virtual experience service may include a metaverse. The virtual experience service may be a mobile metaverse.

[0078] The plurality of devices may operate in physical or virtual space, or both, and may include: physical devices, digital devices, network entities, application entities, or a combination thereof.

[0079] The received application service requirements may include at least one of: a set of performance requirements for the virtual experience service; subscriptions associated with multiple devices; identities and addresses of multiple devices; a request to coordinate QoS for the mobile virtual experience service; a virtual experience application service profile; and / or a service area to which the requirement applies, or a combination thereof.

[0080] The application service request may be received from the virtual experience service provider and / or the network management system.

[0081] The per-session requirements may be network session requirements or application session requirements and may include quality of service and / or quality of experience objectives.

[0082] The processor may be arranged to derive a set of joint quality of service parameters based on running at least one simulation at the virtual space, the simulation using digital twins of the plurality of devices. The simulation may include a hypothetical quality of service parameterization for one or more sessions.

[0083] Running at least one simulation may include the processor being further arranged to: request a simulation of a set of assumed parameters from a simulation engine based on the digital twin; receive a simulation output based on requesting the simulation; and process the simulation output to determine a quality of service parameter per session.

[0084] In this way, within a virtual experience service that may include a virtual space or metaverse, service performance may be optimized to deliver a defined quality of service and quality of experience using a minimal footprint of network resources.

[0085] The derived joint quality of service parameters may determine a service provisioning policy for the virtual space to be applied by at least one corresponding network function.

[0086] The receiver may further be arranged to receive events related to changes in quality of service for one or more sessions. The processor may be arranged to adapt the set of joint quality of service parameters for the multiple sessions based on the received events. The transmitter may be arranged to send the set of adapted joint quality of service parameters for the multiple sessions to one or more network or application entities.

[0087] Events related to quality of service changes may be received from one of a plurality of devices operating in a physical or virtual space or from a network element in a wireless communication network.

[0088] Figure 6A method 600 in an enabling entity for a virtual experience service, the enabling entity being in a wireless communication network, is described. The method 600 includes receiving 610 application service requirements corresponding to a plurality of devices, the plurality of devices operating in a physical space or in a virtual space of the virtual experience service, or in both. The method 600 further includes decomposing 620 the application service requirements into a plurality of session requirements, wherein the session requirements are for a plurality of communication sessions provided between the devices in both the physical space and the virtual space and deriving a set of joint quality of service parameters for the plurality of sessions based on the session requirements. The method 600 further includes sending 630 the set of joint quality of service parameters to one or more network entities in the wireless communication network.

[0089] This method provides a mechanism for quality of service coordination for multi-user and multi-mode virtual experience services. The enabling entity can be at the 5GC or at the edge / cloud SP domain, and supports the conversion of requirements between the virtual experience service and the underlying wireless communication network. The method can further achieve performance optimization by compensating for possible quality of service changes of one or more sessions.

[0090] The virtual experience service may include a metaverse. The virtual experience service may be a mobile metaverse.

[0091] The plurality of devices operating in physical or virtual space or both may include: physical devices, digital devices, network entities, application entities, or a combination thereof.

[0092] The received application service requirements may include at least one of: a set of performance requirements for the virtual experience service; subscriptions associated with multiple devices; identities and addresses of multiple devices; a request for coordinated QoS of the mobile virtual experience service; a virtual experience application service profile; and a service area to which the requirements apply, or a combination thereof.

[0093] The application service request is received from the virtual experience service provider and / or the network management system.

[0094] Per-session requirements may be network session requirements or application session requirements and may include quality of service (QoS) and / or quality of experience (QoE) targets. QoS parameters may be metrics such as jitter, delay / latency, packet error rate, channel loss, data rate / throughput, connection density, probability of communication service availability, relative delay / latency in two or more digital and / or physical devices, and / or encoding rate of media traffic. QoE parameters may include metrics such as user satisfaction, metrics related to average throughput, buffer level, playlist, presentation delay, field of view, resolution, refresh rate, MOS ("mean opinion score"), frequency and / or duration of stall events, occurrence of transmission discontinuities (including their duration), and / or high-resolution real-time video quality. QoS and QoE targets may be based on the QoS and QoE targets defined for VR in 3GPP TR 26.929v17.0.0.

[0095] Deriving a set of joint quality of service parameters may be based on running at least one simulation at the virtual space, the simulation using digital twins of the plurality of devices. The simulation may include hypothetical quality of service parameterizations for one or more sessions.

[0096] Running at least one simulation may include: requesting a simulation engine to simulate a set of assumed parameters based on the digital twin; receiving a simulation output based on requesting the simulation; and processing the simulation output to determine a quality of service parameter for each session.

[0097] Some typical performance requirements for virtual experience services are described in Table 1 below.

[0098] Touch video Audio Jitter(ms) ≤2 ≤30 ≤30 Delay (ms) ≤50 ≤400 ≤150 Packet loss (%) ≤10 ≤1 ≤1 Update rate (Hz) ≥1000 ≥30 ≥50 Packet size (bytes) 64 to 128 ≤MTU 160 to 320 Throughput (kbit / s) 512 to 1024 2500 to 40000 64 to 128

[0099] Table 1 Typical performance requirements for multi-mode flows

[0100] In the scenario of providing multi-mode communication services to multiple UEs, different UEs are individually served by different PCFs. Each PCF generates a QoS policy for each multi-mode data flow of different UEs. The mechanism presented herein tends to ensure that the same QoS policy is applied to each of the multi-mode data flows.

[0101] The solution proposed herein addresses the scenario of how multiple PCFs coordinate QoS policies for flows (eg, haptic, audio, and video) of multiple UEs in a multi-mode communication session.

[0102] Figure 7 Examples of multimodal sessions and multimodal data flow groups are described. Figure 7A first UE 710 and a second UE 712 are shown communicating with an application server 760 over a 5G communication system (5GS) 740. The first multimode session carries traffic between the first UE 710 and the application server 760. The second multimode session carries traffic between the first UE 712 and the application server 760. The UEs 710, 720 may each include a remote unit 102, a user equipment device 200, or a UE 810, 910, 912, 1010, 1020, 1110, 1120, as described herein.

[0103] Virtual experience services (this metaverse scenario) differ from XR use cases primarily due to persistent nature, multi-user support, and ownership / business models. This difference may require different network support, and in particular, different treatment of Quality of Service (QoS) and Quality of Experience (QoE) targets.

[0104] The arrangement proposed herein configures and coordinates the QoS of sessions within a virtual experience service to ensure that the target end-to-end QoS / QoE is met.

[0105] Figure 8 A system 800 is illustrated as an example implementation of the methods described herein. The system 800 includes a plurality of remote units 810, a radio access network 830 including at least one base unit 832, a mobile core network 850, operations, administration, and maintenance (OAM) 860, and an edge data network 840 including a meta-server 844. The UEs 810 may each include a remote unit 102, a user equipment device 200, or a UE 710, 720, 910, 912, 1010, 1020, 1110, 1120, as described herein.

[0106] Metadatabase 822 provides meta-profiles and includes an object database. Metadatabase 822 may include a marketplace. Interaction with metadatabase 822 may be via a blockchain or some distributed ledger technology network. In certain embodiments, a meta-profile may be one or more NFTs (thus metadatabase 822 may operate as an NFT marketplace and storage device).

[0107] Metadata repository 822 may store data related to the operation of the mobile metaverse service. This data may include meta-profiles and objects or NFTs owned by end users. Such profiles and objects are uploaded to the meta-repository 822 from meta-users (which may be data storage entities at the platform or service provider domain where NFT transactions occur).

[0108] Metadatabase 822 may store meta-profiles / objects or NFTs owned by a meta-service provider, such profiles / objects being pre-configured by the meta-service provider at the metadatabase 822. Such objects may be environmental objects to be used in the meta-world, such as tables, robots, or some parameters that may be changed in real time (e.g., weather changes displayed in a virtual world).

[0109] Metadatabase 822 may store NFTs owned by mobile network operators (MNOs), which is the case when communication and computing resources are digitized and provided as components of interaction between virtual objects. For example, a communication link between two avatars or a network slice to be used for communication between physical and virtual devices may be provided by the MNO as an NFT. Thus, a service provider may purchase this service for a Metaworld service by interacting with the NFT marketplace / metadatabase 822. This allows a metaservice provider to automatically reserve dedicated slices / resources for communications using the blockchain network (without an intermediary).

[0110] The edge data network 840 includes a meta-virtual environment 842 which is a virtual environment that may also be within a meta-server 844 and includes a metaverse world created without avatars / networked virtual devices or dynamic objects. In this environment, object visualization may be possible. In addition, rendering may be provided based on object IDs to recreate avatars and links between avatars.

[0111] The meta-server 844 is a processing entity that runs meta-services. This server can be an edge-deployed / local server or a centralized / cloud server or a federated server (across multiple edges / clouds). The meta-server 844 is deployed by a meta-service provider and hosted at the edge / cloud of a wireless communication network. This server 844 can provide gaming meta-services, social networking services, vertical services, etc.

[0112] Each remote unit 810 includes a meta-application client 812 and a meta-enabling client 814. The meta-application client 812 is an application on the UE side that runs a mobile metaverse service (e.g., a VR headset). The meta-enabling client 814 is an application enabler on the UE side that provides support or "awareness" to the meta-application. Possible capabilities of the meta-enabling client 814 include conversion of quality of experience (QoE) to requested network quality of service (QoS) and / or traffic steering, monitoring network conditions, and supporting sensor data collection and its delivery. Traffic steering can be implemented through UE routing policy rules.

[0113] The edge data network 840 further includes a meta-simulation engine 846. The meta-simulation engine 846 is a platform that creates data samples based on digital twins and provides performance measurements under different what-if scenarios. The meta-server 844 can use these outputs to improve user experience or proactively adapt behavior or trigger changes in network requirements. The meta-simulation engine 846 consists of tools and configurations to perform simulations based on digital twins and real data.

[0114] OAM 860 includes a meta-specific slice management service (MnS) 862. The meta-specific MnS 862 may include a management function (MF) that handles network / slice configuration and adaptation to address meta-SP requirements. This service may be automated and dynamically interact with the meta-aware network function 852. The meta-aware network function 852 may include a meta-enabler 1052, 1152 or a meta-control network function 1243, as described herein.

[0115] The meta-aware network function 852 may be implemented by an application function (AF), a network function (NF), or an enabler server. This entity may be at the mobile core network 850 ( Figure 8 Option 2 described in ) or at the edge data network 840 ( Figure 8 Option 1 described in ). The meta-aware network function 852 supports discovery and request translation between the meta-server 844 and the underlying network. The meta-aware network function 852 can perform one or more of the following functions:

[0116] ● Convert smart contracts into service requirements and network policy or management triggers; and

[0117] ●Support QoS coordination.

[0118] Fig. 9 Describe possible conversations for the Virtual Experience service. Fig. 9 A first UE 910 and a second UE 912 are shown communicating with an application server 960 over a 5G communication system (5GS) 940. A first multimode session carries traffic between the first UE 710 and a virtual first UE 950 via the application server 960. A second multimode session carries traffic between the first UE 912 and a virtual second UE 952 via the application server 960. A third multimode session carries traffic between the first UE 912 and the second UE 952 via the application server 960. The UEs 910, 912 may each include a remote unit 102, a user equipment device 200, or a UE 710, 720, 810, 1010, 1020, 1110, 1120, as described herein.

[0119] 1) The interaction between the UE in the physical world and the virtual UE at the metaverse (for providing sensor data / measurements and getting multimodal feedback) is provided by the first and second multimodal sessions.

[0120] 2) Interactions between digital UEs (or avatar UEs) interact in the Metaverse world. Such avatars may be located in the same or different servers or at the Meta SP domain or at the end user digital wallet. This interaction may be blockchain / DLT enabled and, in certain embodiments, may also be supported by 5GS.

[0121] 3) Interactions between UE1 and UE2 (UE1 and UE2 are close in the metaverse, but can be far away and served by different RATs / networks) via the network are facilitated by a third multi-modal session. This can be for transactions between UEs within the metaverse session. For example, a specific payment or a specific action by the user of the first UE 910 will be perceived as a user of the second UE 912 in the physical world.

[0122] 4) The interaction between the Metaverse server and the UE1 and UE2 avatars is used to configure the interaction of the Metaverse services and provide a digital environment as well as provide SP policies and optionally smart contracts for their interaction.

[0123] Fig.10 System 1000 is illustrated with four different application sessions that may exist in a virtual experience service (eg, a mobile metaverse service). Fig.10 A first UE 1010, a second UE 1020, a 5G system 1040, a meta-enabler 1052, a meta-server 1044, a first virtual UE 1018, and a second virtual UE 1028 are illustrated. The first UE 1010 includes a 3GPP modem 1012, an enabler client 1014, and a mobile metaverse application client 1016. The second UE 1020 includes a 3GPP modem 1022, an enabler client 1024, and a mobile metaverse application client 1026. The 3GPP modems 1012, 1022 allow the UEs 1010, 1020 to communicate with the 5G system 1040. The first UE 1010 has a corresponding first virtual UE 1018, which may include an avatar. The second UE 1020 has a corresponding second virtual UE 1028, which may also include an avatar. UE 1010, 1020 may each include remote unit 102, user equipment device 200, or UE 710, 720, 810, 910, 912, 1110, 1120, as described herein. Meta-enabler 1052 may include meta-aware network function 852, meta-enabler 1152, or meta-control network function 1243, as described herein. Meta-enabler 1052 may include an enabling service at the application layer that is customized for a virtual experience service delivered via a wireless communication network (e.g., a mobile metaverse).

[0124] Considering QoS, PDU session aspects, there may be four different application sessions #1, #2, #3, and #4 in a mobile Metaverse service. End-to-end QoS requirements have different granularity and interpretation, and thus the QoS requirements for avatar-to-avatar interaction are different from physical UE-to-avatar UE requirements, and different from physical UE-to-physical UE requirements. For example, application session #3 is over the Uu or PC5 interface and can be used to exchange application context information and user data between Metaverse-compatible and Metaverse-supported applications.

[0125] Fig.10 The arrangement may provide a mechanism for QoS coordination of mobile metaverse services, as follows.

[0126] The meta-enabler for the application function may receive a meta-universe service requirement with SLA / multi-mode and multi-session QoS requirements. The meta-universe service requirement includes the UE and PLMN to be involved and the ID / address of the digital counterpart / avatar (or the DN where it resides).

[0127] The requirements for QoS requirements per application session and per network session are separated.Sessions include 1) physical to digital UE sessions, 2) physical to physical UE sessions of UEs interacting in the metaverse, 3) digital to digital UE sessions (if mobile networks are used for communication).

[0128] The system further configures / identifies the QoS management capabilities (alternative QoS, QoS prediction) to be supported by the service.

[0129] The system further determines the QoS profile and application QoS attributes for each multi-mode session. For example, a new QoS profile and new QoS attributes to be provided: such as the relative distance between the physical and digital UEs.

[0130] The system further detects expected or predicted changes in one of the sessions (monitoring QoS status / prediction from 5GC or meta server or UE).

[0131] The system may further be arranged to perform simulations based on the digital twin. Such simulations may be used to identify the impact of each possible adjustment to a service or cell area or slice.

[0132] The system is further arranged to dynamically / actively adjust per-session QoS attributes (downgrade, upgrade) based on the simulation to ensure that received Metaverse service requirements are met.

[0133] For alternative QoS features, alternative QoS profiles should be decided based on simulation outputs that can show the impact of deciding each different combination of downgrade / upgrade. This impact can be per service or per cell area / network subnet or per slice.

[0134] The system is further arranged to send the adjusted per-session requirements to the network or metaverse user / server.

[0135] Fig.11 Operations 1100 of an enablement server operating as a QoS coordination function are shown. Fig.11 A first meta-UE 1110, a second meta-UE 1120, a 5G core 1140, a meta-enabler 1152, a first UE avatar 1118, and a second UE avatar 1128 are shown. The first meta-UE 1110 includes a 3GPP user equipment running a meta-client 1116 and an enabler client 1114. The second meta-UE 1120 includes a 3GPP user equipment running a meta-client 1126 and an enabler client 1124. Each meta-UE 1110, 1120 may further include a 3GPP modem to facilitate communication with the 5G core 1140. The meta-enabler 1152 may include application functionality and may include a simulation engine. The first UE avatar 1118 and the second UE avatar 1128 may reside at a meta-server 1144. The meta-server 1144 may be located in a data network or an edge data network. UE 1110, 1120 may each include remote unit 102, user equipment device 200, or UE 710, 720, 810, 910, 912, 1010, 1020, as described herein. Meta-enabler 1152 may include meta-aware network function 852, meta-enabler 1052, or meta-control network function 1243, as described herein.

[0136] Initially, all application sessions of the meta-UE have been established. The application sessions include UE1 and UE2 and the avatar counterparts of UE1 and UE2. The four application sessions can be characterized as follows:

[0137] ● Application Session 1 - 1191: Meta-Client sends sensor data / measurements on the physical environment related to UE1 to avatar UE1. Avatar UE1 sends haptic feedback back to UE1 (for UE1 and / or UE2 and the environment)

[0138] ● Application Session 2 - 1192: Meta-Client sends sensor data / measurements on the physical environment related to UE2 to avatar UE2. Avatar UE1 sends haptic feedback back to UE2 (for UE1 and / or UE2 and the environment)

[0139] ● Application Session 3 - 1193: Exchange of service / feedback data between avatars (this data will be converted and sent to the corresponding partner UE)

[0140] ● Application Session 4 - 1194: Sensor data / measurements / meta-SP policies exchanged between meta-UEs (communication can be via sidelink or Uu)

[0141] The process 1100 starts at 1171 where the meta-service provider (SP) or meta-user 1 (via enabler client 1114) sends a subscription / request message for meta-specific QoS management. This is followed by a response or ACK result. This request message contains the information elements listed in Table 2 below.

[0142]

[0143] Table 2: Meta-QoS Management Request

[0144] At 1172, the meta-enabler 1152 configures application QoS parameters by decomposing the end-to-end QoS requirements (from UE 1 1110 to avatar UE1 1118 and / or avatar UE2 1128 and / or meta-SP and back to UE1 1110 and / or UE2 1120) into application QoS parameters for each individual session (e.g., network session of UE 1, network session of UE 2, network session between avatars) that is part of the end-to-end application session. The meta-enabler 1152 obtains or configures a per-session QoS policy based on the decomposed QoS requirements.

[0145] At 1173a, meta-enabler 1152 receives a trigger event from 5GC 1140 (e.g., from a session management function or a network disclosure function of 5G Core 1140) indicating a QoS degradation notification for the session of UE 1. The trigger event may include a QoS monitoring event (QNC) of one of the application sessions.

[0146] At 1173b, a QoS downgrade trigger event is sent from the meta-UE 1 1110 to the meta-enabler 1152, the QoS downgrade trigger event indicating (experienced or expected) application QoS degradation, e.g., based on experienced packet delay or packet loss (e.g., packet loss greater than a threshold) of the Uu link. The conditions for triggering the QoS degradation indication from the meta-UE 1 1110 are based on thresholds that may be pre-provided by the meta-enabler 1152 (at an end-to-end QoS management response made by the meta-enabler 1152). The QoS downgrade may alternatively be an upgrade. The QoS downgrade (or level) may be for the physical UE 1 application session.

[0147] At 1173c, a QoS downgrade triggering event is sent from the avatar UE 1 1118 to the meta-enabler 1152, thereby indicating (experienced or expected) application QoS downgrade or upgrade, for example, based on the experienced packet delay or packet loss of the Uu link. For example, this QoS downgrade triggering event may include a packet loss greater than a threshold. The QoS downgrade triggering event is for the UE1 application session.

[0148] At 1174, the meta-enabler 1152 evaluates the satisfaction / non-satisfaction of the end-to-end QoS based on the triggering event. The meta-enabler 1152 may retrieve additional information from the UE or avatar UE / meta-SP based on a subscription to support its evaluation. This may be from the 5GC 1140 (NEF monitoring events such as 23.502, QoS sustainability analysis such as in TS23.288) or SEAL LMS (on-demand location reporting of one or both UEs 1 and 2). The meta-enabler 1152 requests / receives supplementary QoS states for sessions with dependencies from the 5GC 1140 or meta-server 1144 or new simulations / samples from the meta-simulation engine to identify the impact when making specific adjustments.

[0149] The meta-enabler 1152 may also trigger the initiation or retrieval of simulations for different what-if analysis assumptions (if simulations are running in the background), and in particular, capture possible outcomes (performance / availability / failure rates) when different QoS related actions are taken. For example, if a QoS upgrade for session #1 is applied as compensation for a downgrade of session #2, then the QoS / resource management impact on other UEs of the same or different services needs to be examined. The simulation runs all possible outcomes for a particular potential decision and simulates different combinations of decisions.

[0150] At 1175, the meta-enabler 1152 determines an action based on the simulation output, which is QoS parameter adaptation of one or more of the links (QoS profile downgrade for links that received QoS notification control and QoS upgrade for upgradeable links). Joint application QoS requirement adaptation may include joint QoS upgrade or downgrade per meta-service session.

[0151] At 1176, the meta-enabler 1152 acting as the AF sends a request to the 5GC 1140 (via NEF to SMF or via N5 to PCF) for changes to the QoS profile mapped to one or more network sessions or an update of the PCC rules for applying the new traffic policy. The mechanism for this update is specified in clause 4.15.6.6a "AF Sessions with Required QoS Update Procedure" in 3GPP TS 23.502. The update of the PCC rules may include a PDU Set Flags change.

[0152] At 1177 , the meta-enabler 1152 sends the new application or network QoS policies / parameters to the involved entities (physical and meta-universe UEs and meta-SPs).

[0153] Fig.12 A method 1200 for coordinating a PDU session at a meta control NF (MCNF) 1243 is illustrated. Fig.12Unified Data Management (UDM) / User Data Repository (UDR) 1241, Policy Control Function (PCF) / Session Management Function (SMF) 1242, Media Control NF (MCNF) 1243, and Metaverse Server 1244 are shown. Meta-control network function 1243 may include meta-aware network function 852 or meta-enabler 1052, 1152, as described herein. In the context of MCNF 1243, "meta-control" refers to control functions at the core network that are configured (e.g., by OAM) to provide control plane services customized to support virtual experience services. Virtual experience services may include mobile metaverse sessions.

[0154] The method 1200 starts at 1270, where the Meta Control NF (MCNF) 1243 obtains a mapping of application to network session type (multi-mode) and traffic requirements for Metaverse services (such information may be provided by OAM or by Meta SP).

[0155] At 1271, the MCNF 1243 receives an AF request from the AF of the meta-SP / meta-UE to establish or update a session with a specific QoS.

[0156] At 1272, MCNF 1243 correlates the request with the partner session (UE ID and AF service ID) within the Metaverse service. This correlation may be based on the mapping at step 1270 or by requesting mapping information from UDM / UDR 1241.

[0157] At 1273, MCNF 1243 calculates QoS parameters (e.g., PDB) for the session and all partner sessions that need to be changed. This calculation may be based on simulating all possible assumptions in a meta-simulation engine or meta-server 1244 (using digital objects as twins to derive data). MCNF 1243 derives alternative service requirements for one or more of the involved sessions based on the use of digital twin-based simulations.

[0158] At 1274, MCNF 1243 provides the updated parameters for each session to PCF / SMF 1242 to trigger a PCC rule update. The PCC rule update may include changing QoS profiles or parameters in a coordinated manner. Such parameters may be updated through meta-service provisioning policies / parameters (at MCNF 1243 or at PCF / SMF 1242 containing this new meta-control function). The updated parameters for each session may be sent to one or more PCF / SMFs involved in the session.

[0159] At 1274a, PCF / SMF 1242 authorizes the request and responds to MCNF 1243.

[0160] At 1275, after authorization from PCF / SMF 1242, MCNF 1243 publishes the updated QoS expectation / prediction parameters to the AF or meta-UE (via AF).

[0161] A mechanism for configuring and coordinating QoS for multiple sessions in a virtual experience service is disclosed herein to ensure that end-to-end QoS / QoE requirements are met. Some of these sessions may be multi-modal. The virtual experience service may be a mobile meta-service.

[0162] A mechanism for QoS coordination of multi-user and multi-mode mobile meta-services is described. This is performed by introducing an entity that can be performed at the 5GC or at the edge / cloud SP domain and supports the translation requirements between the meta-server and the underlying network and optimizes performance by compensating for possible QoS changes of one or more sessions.

[0163] Current QoS coordination and compensation mechanisms only consider dependent sessions in physical space. In addition, for XR, QoS coordination is for multi-mode services, but does not involve variants of meta-services. This variant may include multi-session, multi-mode with different communication endpoints.

[0164] A mechanism is provided for applying QoS coordination at the AF / Enabling Server. A mechanism is also provided for PDU session QoS coordination at the MCNF.

[0165] Therefore, a method for configuring multiple QoS parameters of a mobile metaverse service is provided, the method comprising: obtaining application service requirements corresponding to multiple devices in both physical and virtual spaces, wherein the multiple devices are within the mobile metaverse service; decomposing the requests into multiple session requests, wherein the sessions include communication sessions between physical devices, digital devices, network entities, application entities or a combination thereof; configuring a set of joint QoS parameters for the multiple sessions based on each session requirement; and sending the configured joint QoS parameters to one or more network or application entities.

[0166] The obtained application service requirements may include a set of performance requirements for the Metaverse service, subscriptions of the devices involved, identities and addresses of the network elements involved, a request for coordinated QoS of the mobile Metaverse service, a Metaverse application service profile, the service area to which the request applies, or a combination thereof.

[0167] The acquired application service requirements may be received from a meta-service provider and / or a network management system.

[0168] The per-session requirements may be network session requirements or application session requirements and may include QoS and / or QoE targets.

[0169] Configuration of a set of joint QoS parameters may be based on running a simulation in a virtual space based on a digital twin of the physical device under assumed QoS parameterizations for one or more sessions.

[0170] The simulation run may further include: requesting a simulation engine to simulate a set of hypothetical parameters based on the digital twin; receiving a simulation output based on the request; and processing the simulation output to determine each QoS parameter for each session. The QoS parameter for each session may be determined to optimize the performance of the Metaverse service.

[0171] The configured joint QoS parameters may determine the service provisioning policy for the mobile metaverse service to be applied by the corresponding network function.

[0172] The method may further include: receiving an event related to a QoS change for one or more sessions, wherein the event is received by a device or a network element; adapting the configuration of the set of joint QoS parameters for the multiple sessions based on the received event; and sending the adapted joint QoS parameters to one or more network or application entities.

[0173] It should be noted that the above methods and apparatus illustrate rather than limit the present 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 the claims, "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 should not be construed as limiting their scope.

[0174] Furthermore, although examples are given in the context of a particular communication standard, these examples are not intended to be limiting of the communication standards to which the disclosed methods and apparatus may be applied. For example, although specific examples are given in the context of 3GPP, the principles disclosed herein may also be applicable to another wireless communication system, and in fact, to any communication system that uses routing rules.

[0175] 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 the like, causes the processor to carry out the method described above.

[0176] The described methods and apparatus may be practiced in other specific forms. The described methods and apparatus should be considered in all respects to be illustrative only and not restrictive. The scope of the present invention is therefore indicated by the appended claims rather than by the foregoing description. All changes within the meaning and scope of the equivalents of the claims are included within their scope.

Claims

1. An enabling entity for a virtual experience service, the enabling entity being in a wireless communication network, the enabling entity comprising: a receiver arranged to receive application service requirements corresponding to a plurality of devices operating in a physical space or in a virtual space of the virtual experience service, or in both; a processor arranged to decompose the application service requirement into a plurality of session requirements, wherein the session requirements are for a plurality of communication sessions provided between devices in both a physical space and a virtual space and derive a set of joint quality of service parameters for the plurality of sessions based on the session requirements; and A transmitter is arranged to send the set of joint quality of service parameters to one or more network entities in the wireless communication network.

2. The enabling entity of claim 1, wherein the plurality of devices operating in physical or virtual space or both comprise: A physical device, a digital device, a network entity, an application entity, or a combination thereof.

3. The enabling entity of claim 1 or 2, wherein the received application service requirement comprises at least one of: a set of performance requirements for virtual experience services; subscriptions associated with the plurality of devices; the identities and addresses of the plurality of devices; A request to coordinate QoS of the mobile virtual experience service; Virtual Experience Application Service Configuration File; and The service area to which the requirements apply, or a combination thereof.

4. An enabling entity according to any preceding claim, wherein the application service requirements are received from a virtual experience service provider and / or a network management system.

5. An enabling entity according to any preceding claim, wherein the per-session requirements are network session requirements or application session requirements and comprise quality of service and / or quality of experience targets.

6. An enabling entity according to any preceding claim, wherein the processor is arranged to derive a set of joint quality of service parameters based on running at least one simulation at the virtual space, the simulation using digital twins of the plurality of devices.

7. The enabling entity of claim 6, wherein running the at least one simulation comprises the processor being further arranged to: Requesting a simulation engine to simulate a set of hypothetical parameters based on the digital twin; receiving a simulation output based on the request simulation; The simulation output is processed to determine a per-session quality of service parameter.

8. An enabling entity according to any preceding claim, wherein the derived joint quality of service parameter determines a service provisioning policy for the virtual space to be applied by at least one respective network function.

9. An enabling entity according to any one of claims 1 to 5, wherein: The receiver is further arranged to receive events related to changes in quality of service for one or more sessions; The processor is arranged to adapt the set of joint quality of service parameters for the plurality of sessions based on the received events; The transmitter is arranged to send the adapted set of joint quality of service parameters for the plurality of sessions to one or more network or application entities.

10. The enabling entity of claim 9, wherein the event related to a quality of service change is received from one of the plurality of devices operating in a physical or virtual space or from a network element in the wireless communication network.

11. A method in an enabling entity for a virtual experience service, the enabling entity being in a wireless communication network, the method comprising: receiving application service requests corresponding to a plurality of devices, the plurality of devices operating in a physical space or in a virtual space of the virtual experience service, or in both; decomposing the application service requirement into a plurality of session requirements, wherein the session requirements are for a plurality of communication sessions provided between devices in both a physical space and a virtual space and deriving a set of joint quality of service parameters for the plurality of sessions based on the session requirements; and The joint set of quality of service parameters is sent to one or more network entities in the wireless communication network.

12. The method of claim 11, wherein the plurality of devices operating in physical or virtual space or both comprise: A physical device, a digital device, a network entity, an application entity, or a combination thereof.

13. The method of claim 11 or 12, wherein the received application service requirement comprises at least one of: a set of performance requirements for virtual experience services; subscriptions associated with the plurality of devices; the identities and addresses of the plurality of devices; A request to coordinate QoS of the mobile virtual experience service; Virtual Experience Application Service Configuration File; and The service area to which the requirements apply, or a combination thereof.

14. The method of any one of claims 11 to 13, wherein the application service requirements are received from a virtual experience service provider and / or a network management system.

15. The method of any of claims 11 to 14, wherein the per-session requirements are network session requirements or application session requirements and include quality of service and / or quality of experience targets.

16. The method of any one of claims 11 to 15, wherein a set of joint quality of service parameters is derived based on running at least one simulation at the virtual space, the simulation using digital twins of the plurality of devices.

17. The method of claim 16, wherein running the at least one simulation comprises: Requesting a simulation engine to simulate a set of hypothetical parameters based on the digital twin; receiving a simulation output based on the request simulation; The simulation output is processed to determine a per-session quality of service parameter.

18. The method of any of claims 11 to 17, wherein the derived joint quality of service parameter determines a service provisioning policy for the virtual space to be applied by at least one respective network function.

19. The method of any one of claims 11 to 18, further comprising: receiving events related to changes in quality of service for one or more sessions; adapting the set of joint quality of service parameters for the plurality of sessions based on the received events; The adapted set of joint quality of service parameters for the plurality of sessions is sent to one or more network or application entities.

20. The method of claim 19, wherein the event related to a quality of service change is received from one of the plurality of devices operating in a physical or virtual space or from a network element in the wireless communication network.

Images