Device discovery in virtual experience service in wireless communication network

Abstract

A configuration entity in a wireless communication network is provided, the configuration entity comprising a receiver, a processor, and a transmitter. The receiver is arranged to receive service requirements for communication of virtual devices within a virtual experience service at the wireless communication network, wherein each virtual device corresponds to a physical device identified by a subscriber identity. The processor is arranged to discover a plurality of candidate digital and physical devices for a given area and based on the received service requirements. The processor is further arranged to derive one or more session requirements from the received service requirements; wherein a session is established between any combination of the plurality of candidate numbers and physical devices. The processor is still further arranged to determine parameters for each session. The transmitter is arranged to transmit the determined parameter to at least one network node.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to the field of implementing device discovery in a virtual experience service in a wireless communication network. This document defines a configuration entity in a wireless communication network and a method in a configuration entity. Background Art

[0002] Virtual reality (VR), augmented reality (AR) and extended reality (XR) are types of virtual experience services whereby users of electronic devices can interact with each other. Such virtual experience services can be traded using cryptocurrencies. Such transactions may include the exchange of digital works, including (but not limited to) non-fungible tokens (NFTs).

[0003] The Metaverse is an instance of this virtual space that can be provided by a virtual experience service. 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 dimensional than current technology supports. Rather than just watching digital content, users in the Metaverse will be able to immerse themselves in a space where the digital and physical worlds converge.

[0004] In the Metaverse, everything a user creates and owns in the Metaverse is his or her asset, whether it is a piece of virtual real estate or an artifact. The Metaverse grants its users the privilege of full ownership. In addition, the persistence factor is very important because even if the user leaves the Metaverse, the digital avatar will still be in the Metaverse. It will operate normally when other users participate 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 may look exactly the same as the user or device in the real world or may be enhanced. Therefore, the avatar UE can be regarded as a digital representation of a user device virtualized in the Metaverse. The user's device may be a mobile phone, a cellular phone, smart glasses, and / or a smart watch.

[0005] There is a need to provide localized metaverse services in wireless communication networks. Summary of the invention

[0006] A virtual experience service may be provided via a wireless communication network. In addition to real objects that may host devices of the wireless communication network, their corresponding virtual objects may also interact with each other and with physical objects via the wireless communication network. Therefore, there is a need to optimize the implementation of virtual experience services in wireless communication networks. Specifically, a mechanism is needed to support discovery of devices in a virtual experience service provided by a wireless communication network.

[0007] A procedure for discovering devices in a virtual experience service in a wireless communication network is disclosed herein. The procedure may be implemented by a configuration entity in a wireless communication network and a method in the configuration entity.

[0008] A configuration entity in a wireless communication network is provided, the configuration entity comprising a receiver, a processor, and a transmitter. The receiver is arranged to receive service requirements for communication of virtual devices within a virtual experience service at the wireless communication network, wherein each virtual device corresponds to a physical device identified by a subscriber identity. The processor is arranged to discover a plurality of candidate digital and physical devices for a given area and based on the received service requirements. The processor is further arranged to derive one or more session requirements from the received service requirements; wherein a session is established between any combination of the plurality of candidate digital and physical devices. The processor is further arranged to determine parameters for each session. The transmitter is arranged to transmit the determined parameters to at least one network node.

[0009] A method in a configuration entity is further provided, the configuration entity being located in a wireless communication network. The method includes receiving a service requirement for communication of a virtual device within a virtual experience service at the wireless communication network, wherein each virtual device corresponds to a physical device identified by a subscriber identity. The method further includes discovering a plurality of candidate digital and physical devices for a given area and based on the received service requirement. The method further includes deriving one or more session requirements from the received service requirement; wherein a session is established between any combination of the plurality of candidate digital and physical devices. The method further includes determining parameters for each session. The method further includes transmitting the determined parameters to at least one network node. 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, a description of the present disclosure is provided by reference to certain devices and methods illustrated in the accompanying drawings. Each of these drawings depicts only certain aspects of the present disclosure and therefore should not be considered to limit its scope. The drawings have been simplified for clarity and are not necessarily drawn to scale.

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

[0012] FIG1 depicts an embodiment of a wireless communication system for device discovery in 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 further details of network nodes that may be used to implement the methods described herein;

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

[0016] Figure 5 Explain 5G-enabled traffic flow simulation with situational awareness;

[0017] Figure 6 A method in a configuration entity is described, the configuration entity being located in a wireless communication network;

[0018] Figure 7 Describes a system as an example of implementing the method described herein;

[0019] Figure 8 Describe the methods used to support, discover, and translate meta-service requests; and

[0020] Fig. 9 Describes the methods used to configure network policies for discovered sessions. DETAILED DESCRIPTION

[0021] 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.

[0022] 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.

[0023] 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.

[0024] 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 thereof.

[0025] 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 thereof. 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.

[0026] Throughout this specification, reference to an example or similar language of a particular method or device means that a particular 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 features or similar language of an example of a particular method or device does 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, a list of enumerated items 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".

[0027] 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 any single item in the list, one and only one. 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.

[0028] In addition, the described features, structures or characteristics described herein may be combined in any suitable manner. In the following description, numerous specific details of examples such as programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc. are provided to provide a thorough understanding of the present disclosure. 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 so as not to make aspects of the present disclosure unclear.

[0029] 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.

[0030] The code may also be stored in a storage device, which can 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.

[0031] 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.

[0032] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products. In this regard, each box in the schematic flowcharts 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.

[0033] 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.

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

[0035] FIG. 1 depicts an embodiment of a wireless communication system 100 for device discovery in 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. Even though a specific number of remote units 102 and network units 104 are depicted in FIG. 1 , those 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, a remote unit 710, or a meta-application enabler client 814, 914, as described herein. The network unit 104 may include a network function configured to support a virtual experience service, a network node 300, a configuration entity, a meta-aware network function 752, a meta-aware application function 754, or a meta-enabler 852, 952, as described herein. In a further implementation, the network node 300 may be deployed as an application function specific 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 mobile metaverse services. This network node may be implemented according to 3GPP SA4.

[0036] 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 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 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.

[0037] The network elements 104 may be distributed over a geographic area. In some 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 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 known to those of ordinary skill in the art.

[0038] 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. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfoxx and other protocols. The present disclosure is not intended to be limited to implementing any particular wireless communication system architecture or protocol.

[0039] 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.

[0040] The wireless communication system may be adapted to more efficiently accommodate the use cases and potential requirements of localized virtual experience services. In the context of localized virtual experience services defined herein, "localized" may refer to a cell area, a tracking area, an edge service area, a dedicated network area (e.g., a factory), or a local geographic area (e.g., a stadium). Some examples of such use cases are discussed below.

[0041] Since the industrial age, engineering design has become an extremely demanding activity. Collaborative and concurrent engineering is a concept and method 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 actual 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 key applications in industrial fields such as aerospace engineering, automotive engineering, medical engineering, and education and entertainment. The technology range includes cave-like automated virtual environments (better known as the recursive acronym CAVE) environments, reality theaters, power walls, holographic workbenches, personal immersive systems, head-mounted displays, tactile sensing interfaces, tactile feedback devices, multi-sensory devices, voice interfaces, and mixed reality systems.

[0042] The multimodal feedback service based on the mobile virtual experience service describes the situation where multiple physical entities or their digital avatars interact with each other. New feedback modalities are also introduced in this use case to meet new scenarios and requirements in the mobile metaverse. For example, 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 modalities 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 for different scenarios in the mobile metaverse, it is very important to explore these time synchronization or asynchronous boundaries of audio, video, touch, smell, taste, etc.

[0043] 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 may be one-to-one, many-to-one, or one-to-many. The physical space may be defined as the physical world or real environment, including physical objects and / or devices running software that provides virtual experience services. The hardware that provides virtual experience services may be geographically distributed and distributed in different software environments. The hardware may be physically close to where the physical users of the virtual experience service are physically located.

[0044] 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 one or more of the user equipment devices described according to the embodiments herein. In particular, the user equipment device 200 may include the remote unit 102, the remote unit 710, or the meta-application enabler client 814, 914, 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] The memory 210 may store data related to implementing the 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 device 200.

[0051] 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, such 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.

[0052] Output device 220 may be designed to output visual, auditory, and / or tactile signals. Output device 220 may include an electronically controllable display or a display device capable of outputting visual data to a user. For example, 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, output device 220 may include a wearable display that is separate from but communicatively coupled to the remainder of user equipment device 200, such as a smart watch, smart glasses, a head-mounted display, or the like. In addition, 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.

[0053] Output device 220 may include one or more speakers for producing sounds. For example, output device 220 may produce an auditory alarm or notification (e.g., a beep or ring tone). Output device 220 may include one or more haptic devices for producing vibration, motion, or other tactile feedback. All or part of output device 220 may be integrated with input device 215. 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.

[0054] 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.

[0055] 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.

[0056] 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, for example, the network interface 240.

[0057] The one or more transmitters 230 and / or the one or more receivers 235 may be implemented and / or integrated as 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 as 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 modular transmitters 230 and receivers 235 implemented in the same hardware chip or multi-chip module.

[0058] Figure 3 Depicts more details of a network node 300 that can be used to implement the methods described herein. The network node 300 may include, for example, a network function configured to support a virtual experience service, a network element 104, a configuration entity, a meta-aware network function 752, a meta-aware application function 754, or a meta-enabler 852, 952, as described herein. In a further embodiment, the network node 300 may be deployed as an application function specific 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.

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

[0060] 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 a processor 305, a memory 310, and a transceiver 325, and may not include an input device 315 and / or an output device 320.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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, such 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.

[0066] Output device 320 may be designed to output visual, auditory 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, LED display, OLED display, projector, or 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, 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.

[0067] 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 ring tone). Output device 320 may include one or more haptic devices for producing vibration, motion, or other tactile feedback. All or part of output device 320 may be integrated with input device 315. 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.

[0068] 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.

[0069] Figure 4A 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 nearby or not nearby. Figure 4 Explain how multimodal feedback services are applied in the mobile metaverse and the main impact on 3GPP is whether and how to use 5GS to better utilize different feedback cues and realize multimodal feedback cues about experiences of multi-physical entities.

[0070] Figure 5 Illustration of 5G-enabled traffic flow simulation with situational awareness. With the support of 5GS, real-time information and data about real objects can be provided to virtual objects in the metaverse. Figure 5 A 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 objects 510 and provides this to the digital twin objects 560. The wireless communication network 520 provides context information from the digital twin objects 560 in the virtual space back to the real objects 510. This context 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 context awareness and real-time path guidance and real-time safety or security alerts can also be generated for ICVs as well as drivers and passengers.

[0071] 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 needs to be further enhanced to meet the service requirements for 5G-enabled traffic flow simulation and situational awareness. At the same time, in addition to the real objects 510 that can host the UE of the cellular system, their corresponding virtual objects 560 can also interact with each other and interact with the physical objects 510 via 5GS.

[0072] For all scenarios, it is necessary to define how digital devices instantiate and onboard to a wireless communication network platform (which supports the mobile virtual experience service) and how digital devices discover other digital devices within the mobile virtual experience service.

[0073] Therefore, there is a need to support discovery and grouping of digital devices to interact via mobile networks. There is also a need to configure Quality of Service (QoS) for sessions within a virtual experience service. This document proposes solutions to these problems.

[0074] A configuration entity in a wireless communication network is provided, the configuration entity comprising a receiver, a processor, and a transmitter. The receiver is arranged to receive service requirements for communication of virtual devices within a virtual experience service at the wireless communication network, wherein each virtual device corresponds to a physical device identified by a subscriber identity. The processor is arranged to discover a plurality of candidate digital and physical devices for a given area and based on the received service requirements. The processor is further arranged to derive one or more session requirements from the received service requirements; wherein a session is established between any combination of the plurality of candidate digital and physical devices. The processor is still further arranged to determine parameters for each session. The transmitter is arranged to transmit the determined parameters to at least one network node.

[0075] Therefore, a mechanism is provided to support the discovery and translation of service requirements for virtual experience services provided by a wireless communication network. A mechanism is further provided to configure network policies for discovered sessions. Such mechanisms facilitate the provision of virtual experience services over a wireless communication network while ensuring adequate performance and providing optimized use of wireless communication network resources.

[0076] The service requirements may be performance requirements, availability requirements, KPIs, application QoS requirements, user QoE requirements, virtual experience service QoE requirements, or a combination thereof.

[0077] The discovery of multiple candidate digital and physical devices for a given area may be based on device capabilities and mobile metaverse application support as well as other factors such as the device's battery level, network conditions, network status (i.e., connected or not), dependencies on other devices, absolute or relative location of the device in physical or virtual space, mobility pattern (static vs. dynamic), reliability of the device, trustworthiness of the device, type of device, or a combination thereof. Discovery may occur with the support of a Common API Framework (CAPIF). CAPIF is specified in 3GPP TS 23.222 v17.6.0. In particular, the CAPIF Core Function (CCF) may be utilized by edge / cloud data networks that deploy meta servers / enabler servers.

[0078] The session requirements may correspond to a network or application session between two or more devices and / or between a device and a server or network entity. Such session requirements may include one or more of the performance, availability, load, QoE, QoS requirements of the corresponding session.

[0079] The user identity may be associated with a wireless communication network subscription. The virtual device is arranged to interact within a digital reality. The digital reality may be a metaverse. The virtual experience service may include a metaverse. The service requirements may include metaverse-related service requirements. A given area may be defined as a physical area or a digital area.

[0080] The parameters may include network policies. The network nodes may include application functions. The network nodes may include OAM, NF or UE. The processor may be arranged to discover multiple candidate digital and physical devices for a given area and based on received service requirements using physical distances between devices and / or virtual distances between avatars associated with the devices. The physical devices may include user equipment (UE) defined by 3GPP.

[0081] The parameters may include at least one of: network configuration or PDU set marking, slice selection, radio access technology (RAT) selection and / or interface selection.

[0082] A session may be an application layer session and / or a PDU session.

[0083] Service requirements may include smart contracts for transactions between virtual devices within the virtual experience service. Smart contracts can be conducted between meta-users and meta-service providers. Smart contracts in the metaverse exist to automate operations and ensure that actions and transactions such as buying and selling are completed according to predetermined rules. Smart contracts are digital contracts programmed and run on the blockchain.

[0084] The processor may be arranged to discover a plurality of candidate digital and physical devices for a given area and based on received service requirements by querying the wireless communication network.

[0085] A session may be established between any pair of multiple candidate digital and physical devices and they communicate using the wireless communication network.

[0086] A plurality of candidate digital and physical devices may support localized virtual experience services. The localized virtual experience services may include localized metaverse services.

[0087] The configuration entity may further include using a simulation engine to provide a simulation based on a virtual object within the virtual experience service. The virtual object may include a virtual device or a digital twin of a physical object. Such simulation may support identification of network parameters and / or policies for the virtual experience service.

[0088] The operation of the simulation engine may be based on requests from servers in a virtual experience service or subscription and include different assumptions about network parameters and / or policies.

[0089] The processor may further be arranged to determine a PDU set delay budget and a PDU set error rate, and the transmitter may be arranged to send the PDU set delay budget and the PDU set error rate to the wireless communication network.

[0090] The transmitter is arranged to send the PDU set delay budget and the PDU set error rate to the wireless communication network as part of a quality of service procedure.

[0091] Figure 6 A method 600 in a configuration entity is described, the configuration entity being located in a wireless communication network. The method 600 includes receiving 610 a service requirement for communication of a virtual device within a virtual experience service at the wireless communication network, wherein each virtual device corresponds to a physical device identified by a subscriber identity. The method 600 further includes discovering 620 a plurality of candidate digital and physical devices for a given area and based on the received service requirement. The method 600 further includes deriving 630 one or more session requirements from the received service requirement; wherein a session is established between any combination of the plurality of candidate digital and physical devices. The method 600 further includes determining 640 parameters for each session. The method 600 further includes transmitting 650 the determined parameters to at least one network node.

[0092] Therefore, a mechanism is provided to support the discovery and translation of service requirements for virtual experience services provided by a wireless communication network. A mechanism is further provided to configure network policies for discovered sessions. Such mechanisms facilitate the provision of virtual experience services over a wireless communication network while ensuring adequate performance and providing optimized use of wireless communication network resources.

[0093] The user identity may be associated with a wireless communication network subscription. The virtual device is arranged to interact within a digital reality. The digital reality may be a metaverse. The virtual experience service may include a metaverse. The service requirements may include metaverse-related service requirements. A given area may be defined as a physical area or a digital area.

[0094] The parameters may include network policies. The network nodes may include application functions. The network nodes may include OAM, NF or UE. The processor may be arranged to discover multiple candidate digital and physical devices for a given area and based on received service requirements using physical distances between devices and / or virtual distances between avatars associated with the devices. The physical devices may include user equipment (UE) defined by 3GPP.

[0095] The parameters may include at least one of: network configuration or PDU set marking, slice selection, RAT selection and / or interface selection. The session may be an application layer session and / or a PDU session.

[0096] Service requirements may include smart contracts for transactions between virtual devices within the virtual experience service. Smart contracts can be conducted between meta-users and meta-service providers. Smart contracts in the metaverse exist to automate operations and ensure that actions and transactions such as buying and selling are completed according to predetermined rules. Smart contracts are digital contracts programmed and run on the blockchain.

[0097] Multiple candidate digital and physical devices for a given area may be discovered based on received service requirements by querying the wireless communication network.

[0098] A session may be established between any pair of multiple candidate digital and physical devices and they communicate using the wireless communication network.

[0099] A plurality of candidate digital and physical devices may support localized virtual experience services. The localized virtual experience services may include localized metaverse services.

[0100] The method may further include using a simulation engine to provide a simulation based on a virtual object within the virtual experience service. The virtual object may include a virtual device or a digital twin of a physical object. Such simulation may support identification of network parameters and / or policies for the virtual experience service.

[0101] The operation of the simulation engine may be based on requests from servers in a virtual experience service or subscription and include different assumptions about network parameters and / or policies.

[0102] The method may further include determining a PDU set delay budget and a PDU set error rate and sending the PDU set delay budget and the PDU set error rate to the wireless communication network.

[0103] The PDU set delay budget and the PDU set error rate may be sent to the wireless communication network as part of the quality of service procedure.

[0104] Figure 7 A system 700 is illustrated as an example of implementing the methods described herein. The system 700 includes a plurality of remote units 710, a radio access network 730 including at least one base unit 732, a mobile core network 750, a meta-aware network function 752, a meta-aware application function 754, operations, administration, and maintenance (OAM) 760, and a data network 740 including a meta-server 744. The remote unit 710 may include a remote unit 102, a user equipment device 200, or a meta-application enabler client 814, 914, as described herein. The meta-aware network function 752 or the meta-aware application function 754 may include a network unit 104, a network node 300, a configuration entity, or a meta-enabler 852, 952, as described herein.

[0105] Metadatabase 722 may store data related to the operation of the mobile metaverse service. This data may include meta-profiles and include an object database. Metadatabase 722 may include a marketplace. Interactions with metadatabase 722 may be via a blockchain or some distributed ledger network. In certain embodiments, a meta-profile may be one or more NFTs (thus, metadatabase 722 may operate as an NFT marketplace and storage).

[0106] Metadatabase 722 can store meta-profiles and objects or NFTs owned by end users. Such profiles and objects are uploaded at the metadatabase 722 from meta-users (which can be data storage entities at the platform or service provider domain where NFT transactions occur).

[0107] Metadatabase 722 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 metadatabase 722. Such objects may be environmental objects used in the meta-world, such as tables, robots, or some parameters that may change in real time (e.g., weather changes displayed in a virtual world).

[0108] Metadatabase 722 may store NFTs owned by mobile network operators (MNOs), which is the case when communication and computing resources are digitized and provided as a means of interaction between virtual objects. For example, a communication link between two avatars or a network slice 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 722. This allows a metaservice provider to automatically reserve dedicated slices / resources for communication using a blockchain network (without an intermediary).

[0109] Data network 740 includes meta-virtual environment 742, which is a virtual environment that may also be located within meta-server 744 and includes the created metaverse world without avatars / networked virtual devices or dynamic objects. In such an environment, visualization of objects is possible. In addition, rendering can be provided based on object IDs to reconstruct avatars and links between avatars.

[0110] The meta-server 744 is the processing entity where the metaverse services are run. This server can be an edge-deployed / native server or a centralized / cloud server or a federated server (across multiple edges / clouds). The meta-server 744 is deployed by a meta-service provider and hosted at the edge / cloud of the wireless communication network. This server 744 can provide gaming meta-services, social networking services, vertical services, etc.

[0111] Each remote unit 710 includes a meta-application client 712 and a meta-enabling client 714. The meta-application client 712 is an application at the UE side that runs a mobile metaverse service (e.g., a VR headset). The meta-enabling client 714 is an application enabler at the UE side that provides support or "awareness" to the meta-application. Possible capabilities of the meta-enabling client 714 include converting quality of experience (QoE) parameters into requested network quality of service (QoS) parameters and / or traffic steering, monitoring network conditions, and supporting the collection and provision of sensor data. Traffic steering can be implemented through UE routing policy rules. QoS parameters can be metrics such as jitter, delay / latency, packet error rate, channel loss, data rate / throughput, connection density, communication service availability probability, relative delay / latency between two or more digital and / or physical devices, update rate, and / or encoding rate of media traffic. QoE parameters may include metrics such as user satisfaction, metrics related to average throughput, buffering level, playlist, presentation delay, field of view, resolution, refresh rate, MOS ("mean opinion score"), frequency and / or duration of stall events, incidence of transmission interruptions (including their duration), and / or high-resolution real-time video quality. QoS and QoE targets may be based on the targets defined for VR in 3GPP TR 26.929v17.0.0.

[0112] The data network 740 further includes a meta-simulation engine 746. The meta-simulation engine 746 is a platform that creates data samples based on digital twins and provides performance measurements under different hypothetical scenarios. The meta-server 744 can use these outputs to improve the user experience or proactively adjust behavior or trigger changes in network requirements. The meta-simulation engine 746 consists of tools and configurations that perform simulations based on digital twins and real data.

[0113] OAM 760 includes meta-specific slice management services (MnS) 762. Meta-specific MnS 762 may include management functions (MFs) that handle network / slice configuration and adaptation to address meta-SP requirements. This service may be automated and dynamically interact with meta-aware network functions 752.

[0114] The system 700 may include a meta-aware network function 752 or a meta-aware application function 754 or both. The meta-aware network function 752 or the meta-aware application function 754 may be implemented by an enabler server. The meta-aware application function 754 is located at the data network 740 ( Figure 7 Alternatively, the meta-aware network function 752 is located at the mobile core network 750 ( Figure 7Option 2 described in ). Meta-aware network function 752 and / or meta-aware application function 754 support discovery and request translation between meta-server 744 and the underlying network. Meta-aware network function 752 and / or meta-aware application function 754 may perform one or more of the following functions:

[0115] Support discovery and grouping of meta-user and session information of meta-services;

[0116] Translating meta-service requirements (for blockchain-enabled digital objects, such requirements are derived based on smart contracts) into network policies or management triggers; and

[0117] For each discovered session's packets, the parameters of the Packet Data Unit (PDU) set are affected according to the service and provided to the network (to allow the 5GC to identify the PDU set information).

[0118] Figure 8 A method 800 for supporting, discovering, and translating meta-service requirements is described. Figure 8 A system is described, which includes a meta-application enabler client 814 implemented at a UE, an OAM 860, a 5G core 850, a meta-enabler 852, a meta-server 844, and a meta-database 822. The meta-enabler 852 may include a meta-NF, a meta-AF, or a meta-middleware function. The meta-enabler 852 may include a network unit 104, a network node 300, a configuration entity, a meta-aware network function 752, a meta-aware application function 754, or a meta-enabler 952, as described herein. The meta-enabler 852 may include any virtual space enabler and is not necessarily limited to the enablement of a metaverse. The meta-enabler 1052 may include an enablement service at the application layer, which is suitable for a virtual experience service provided via a wireless communication network, such as a mobile metaverse. The meta-application enabler client 814 may be implemented by a remote unit 102, a user equipment device 200, a remote unit 710, or a meta-application enabler client 914, as described herein.

[0119] The illustrated process begins at 871, where the meta-enabler 852 receives application requirements from the meta-server 844. The application requirements may be generated by a meta-service provider (or from a meta-user). The application requirements are used to configure the communication services and / or network requirements of the mobile metaverse service. This application requirement includes a set of application performance metrics (QoE, QoS) and availability targets for the mobile metaverse service. The mobile metaverse service is defined as the communication between physical devices and digital devices (or groups of devices) in the virtual space of the metaverse world via a wireless communication network. For example, video / audio / sensor communication between VR glasses and a metaverse application. In addition, the mobile metaverse service may include communication between two or more digital devices in the metaverse world. For example, video / audio communication between digital avatars in the metaverse world. The video / audio communication is also transmitted to the physical device via the mobile communication network. The application requirements may include the metaverse service coverage area, validity time, and preferred network shard ID.

[0120] At 872, the meta-enabler 852 converts the application requirements into network communication requirements for the mobile metaverse service. This network communication requirement may include communication means, RAT / spectrum considerations, traffic patterns (which may be application traffic scheduling and / or PDU set information for application sessions), network topology areas where the service is applicable. The network communication requirements may include service profiles and areas of interest. Areas of interest may be defined as lists of cells.

[0121] At 873, based on the network communication requirements, the meta-enabler 852 obtains from the 5G core the information (identity / address, meta-capabilities and location information) of all registered / connected UEs within the network coverage area where the Metaverse service is planned to be deployed. This retrieval may be based on the SEAL LMS service (873a) for receiving a list of UEs and their locations in a given area / region or by querying this information directly (via the enabling layer) from the UE via a broadcast transmission via the area of ​​interest (as illustrated by 873b1 / 873b2). For example, at 873b1, a request for UE ID information and capabilities (e.g., meta-support) is broadcast to all UEs in the target area. In response, at 873b2, the UE ID / information and capabilities are sent from the meta-application enabler client 814 in each UE. The UE ID / information and capabilities may include meta-support flags, profiles, energy data, type of UE, such as a VR headset.

[0122] At 874, after obtaining information about UEs in a given area and their status, meta-enabler 852 detects UEs with meta-capability and connected to the network. It should be noted that step 874 may be preceded by 873, ie, the UE interfaces with the application and notifies the AF of the IP address.

[0123] At 875, based on the detected UEs with meta-capability, meta-enabler 852 requests information about digital representations of UEs in this area from meta-DB 822 and identifies which of them have avatars interacting with each other. The meta-device ID may be based on the UE ID / public address of the detected UE.

[0124] For the remaining UEs without avatars, the middleware will create digital twins (operated by the MNO / middleware provider) to introduce or not consider them at the metaverse.

[0125] The discovery of avatar UEs may be based on the receipt of digital UE IDs or NFT IDs and may be a group of digital devices owned by the user (e.g., smartphones, watches, gadgets). The discovery may be performed via the blockchain network or may be obtained off-chain by the metadata repository 822 (e.g., if the metadata repository 822 is deployed at the data network and the digital copy / avatar information is already available from the time the UE registered with the network / middleware).

[0126] At 876, the meta-enabler 852 receives the digital device ID and information (if the digital object is a blockchain-enabled entity) of the digital device / object in the region. A physical UE may be mapped to more than one digital object (e.g., a user has multiple digital assets such as avatars, clothing, and other possessions) or vice versa (an avatar corresponds to one or more physical devices); thus, the mapping may be N to M (although only for tradable digital objects).

[0127] The information of the digital device may optionally include a smart contract. When blockchain is used, this optional smart contract may be employed. This smart contract may include automated scripts that act as transaction rules between blockchain-enabled entities (such as avatars in the metaverse). These smart contracts may affect translation into network parameters, as triggering events will need to be translated into automated triggering actions on the network. By way of further example, it should be noted that smart contracts may be employed by the metaserver 844 to impose some automated pairing of policies and actions applied by the network.

[0128] At 877, the meta-enabler 852 stores the received digital device information, detects digital UEs with possible interactions (based on proximity in the meta-world), and converts the smart contract per digital device into application service requirements for communication between digital UEs when using the optional smart contract.

[0129] Fig. 9 A method 900 of configuring a network policy for a discovered session is described. Fig. 9A system including a meta-application enabler client 914, an OAM 960, a 5G core 950, a meta-enabler 952, a meta-server 944, a meta-database 922, and a meta-simulation engine 946 implemented at a UE is illustrated. The meta-enabler 952 is a discovery and transformation entity and may include a meta-NF, a meta-AF, or a meta-middleware function. The meta-enabler 952 may include any virtual space enabler and is not necessarily limited to the enablement of a metaverse. The meta-application enabler client 914 may be implemented by a remote unit 102, a user equipment device 200, a remote unit 710, or a meta-application enabler client 814, as described herein. As described herein, the meta-enabler 952 may include a network unit 104, a network node 300, a configuration entity, a meta-aware network function 752, a meta-aware application function 754, or a meta-enabler 852.

[0130] At 971, the meta-enabler 952 obtains the application service requirements of the mobile meta-service of the digital device. (This is similar to Figure 8 Equivalent to step 877. )

[0131] At 972, the meta-enabler 952 matches the distance between any two digital UEs (avatars) with the physical communication distance between their physical UEs. This can be done by processing the location of the physical UEs (in terms of Figure 8 This is done by obtaining the avatars in the same way as demonstrated above) and matching them with the digital UE location of the mobile metaverse world (this information can be provided by the meta server). This helps identify application requirements that translate into network requirements, as the relative distance between the avatar and the physical UE (behind the avatar) will identify the performance requirements for the end-to-end session.

[0132] For example, if two UEs are close to each other and the meta-server 944 is deployed at the edge cloud, the network / QoS requirements for the session can be relaxed because the physical to avatar UE session and the physical to physical UE session can be accommodated via the local path. In contrast, if the physical UE is far away and the avatar is close, the data transfer needs to take into account the underlying network delay caused by the different UPF / RAN nodes and interfaces to ensure the appropriate quality of the avatar to avatar dynamic transaction.

[0133] Optionally, at 973, the meta-enabler 952 may request the meta-simulation engine 946 to run a what-if simulation based on the meta-objects and configurations (of spectrum etc.), also using physical and digital UE locations / distances between UEs as input.

[0134] Additionally, optionally and conditional upon 973, at 974, the meta-simulation engine 946 runs the simulation and provides all hypothetical simulation outputs back to the meta-enabler 95s based on the request at 973. Such simulation outputs may also suggest adjustments to application behavior. Adjusting application behavior may include using a different codec or changing the frequency of tactile sensor reporting.

[0135] At 975, the meta-enabler 952 configures the network parameter set (link, spectrum, slice, ...) and the policy for the service area based on the smart contract and optionally configures the analog output of all possible sessions that need to be provided by the network (physical to digital UE, digital to digital UE, physical to physical UE).

[0136] At 976, the meta-enabler 952 sends the Metaverse services and network parameters and policies for a given area to the network entities involved (5GC 950, RAN, OAM 960, UE).

[0137] The network parameters may include per-session QoS requirements for each Metaverse service received / sent by the UE, where each Metaverse service may consist of multimodal type communications to transfer audio, video, or tactile / sensor information from / between the UEs. The meta-enabler 952 may determine specific latency requirements for each session based on such requirements.

[0138] A PDU (Packet Data Unit) set may be defined, which consists of one or more PDUs to carry the payload of one information unit generated at the application layer (e.g., a frame or video slice for an XRM service), which has the same importance at the application layer. The User Plane Function (UPF) at the 5G Core Network (CN) marks important packets, including the PDU set sequence number, the size of the PDU set, and an indication of whether all packets of the same PDU set need to be successfully provided within the PDU set delay budget. From the perspective of the Metaverse AF, the AF needs to determine the optimal PDU set delay budget to provide such packets to the UE. In addition, the Metaverse AF may determine the optimal PDU set error rate, which defines an upper limit on the rate of a PDU set that has been processed by the sender of the link layer protocol (e.g., the RLC in the RAN of a 3GPP access), but in which all PDUs in the PDU set are not successfully provided to the upper layer by the corresponding receiver. The AF may provide the PDU set delay budget and the PDU set error rate to the 5GCN as part of the AF session with QoS procedures. This marking may be done for each identified session.

[0139] At 977, the meta-enabler 952 informs the meta-server 944 of the network configuration and access parameters. This step may also include possible recommendations for changing application parameters based on the simulation output in step 974.

[0140] New virtual spaces (e.g. mobile metaverse) bring a new dimension to XR / VR services (since meta is about persistent large-scale virtual interactive experiences where digital assets are owned or deployed by end users) and require enhancements to future networks (5G and beyond) to ensure connectivity / performance and provide support / optimization. The problem to be solved is how to support discovery and configuration of digital devices (avatars or digital twins of physical users) to interact over mobile networks, and furthermore, a mechanism is needed to configure QoS for sessions within meta-services.

[0141] A mechanism is provided herein at the Meta AF / Enabler Server to: 1) support discovery of meta-user and session information for meta-services; 2) convert meta-service requirements (for blockchain-enabled digital objects, such requirements are derived based on smart contracts) into network policies or management triggers; and 3) group each discovered session, affect the parameters of the PDU set according to the service and provide to the network (to allow 5GC to identify the PDU set information).

[0142] The arrangement described herein facilitates discovery of UE's avatars in virtual space, since two dimensions of interaction between physical and avatar users are captured.Virtual spaces such as mobile metaverse services will bring new requirements in terms of discovery and policy provisioning, mechanisms for which are presented herein.

[0143] This paper provides a mechanism to support the discovery and translation of meta-service requirements of mobile metaverse services. It further provides a mechanism to configure network policies for discovered sessions.

[0144] Therefore, a method for session discovery and configuration for mobile metaverse services is provided. The method includes: a. obtaining service requirements for communication between virtual devices in the application layer corresponding to physical user identities; b. discovering multiple candidate digital and physical UEs for a given digital or physical area based on the metaverse-related service requirements; c. converting the metaverse-related service requirements into a set of service requirements for one or more meta-sessions, where the sessions can be conducted between digital and physical UEs in the area of ​​interest; d. determining network policies and / or parameters for one or more sessions; e. transmitting the determined network policies and / or parameters to at least one application or network node (OAM, NF, UE).

[0145] Policies and / or parameters may include network configuration or PDU set tagging, slice selection, RAT selection or interface selection. Service requirements may include smart contracts between meta-users and meta-service providers. Discovery may include requests or subscriptions.

[0146] A metasession may include any combination of sessions between physical and digital objects that communicate using a mobile network. A set of physical devices corresponding to digital devices may support localized Metaverse services.

[0147] The simulation engine can be used to provide digital object-based simulations to support identification of network parameters and / or policies for Metaverse services. Providing simulations can be based on Metaserver requests or subscriptions and include different assumptions about network parameters and / or policies.

[0148] Although specific examples are given in the context of the metaverse, the methods and apparatus described herein may be applied to any virtual experience service.

[0149] It should be noted that the above methods and apparatus illustrate rather than limit the present invention, and that a person 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 described in the claims. Any reference signs in the claims should not be construed as limiting their scope.

[0150] 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.

[0151] 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 implement the above-described method.

[0152] The described methods and apparatus may be practiced in other specific forms. The described methods and apparatus should be considered in all respects as merely illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than the foregoing description. All changes within the equivalent meaning and scope of the claims are included within their scope.

Claims

1. A configuration entity in a wireless communication network, the configuration entity comprising: a receiver arranged to receive a service requirement for communication of virtual devices within a virtual experience service at the wireless communication network, wherein each virtual device corresponds to a physical device identified by a subscriber identity; a processor arranged to discover, for a given area and based on the received service requirements, a plurality of candidate digital and physical devices; The processor is further arranged to derive one or more session requirements from the received service requirements; in establishing a session between any combination of the plurality of candidate digital and physical devices; The processor is further arranged to determine parameters for each session; and A transmitter arranged to transmit the determined parameters to at least one network node.

2. The configuration entity according to claim 1, wherein the parameters include at least one of the following: network configuration, PDU set marking, slice selection, RAT selection and / or interface selection.

3. The configuration entity according to claim 1 or 2, wherein the service requirements include smart contracts for transactions between virtual devices within the virtual experience service.

4. A configuration entity according to any of the preceding claims, wherein the processor is arranged to discover a plurality of candidate digital and physical devices for a given area and based on the received service requirements by querying the wireless communication network.

5. The configuration entity of any of the preceding claims, wherein a session is established between any pair of the plurality of candidate digital and physical devices and the any pair communicates using the wireless communication network.

6. The configuration entity of any one of the preceding claims, wherein the plurality of candidate digital and physical devices support a localized virtual experience service.

7. The configuration entity of claim 1, further comprising using a simulation engine to provide a simulation based on virtual objects within the virtual experience service.

8. The configuration entity of claim 7, wherein the operation of the simulation engine is based on requests from a server in the virtual experience service or subscription and includes different assumptions about network parameters and / or policies.

9. A configuration entity according to any of the preceding claims, wherein the processor is further arranged to determine a PDU set delay budget and a PDU set error rate, and the transmitter is arranged to send the PDU set delay budget and the PDU set error rate to the wireless communication network.

10. A method in a configuration entity, the configuration entity being located in a wireless communication network, the method comprising: receiving a service request for communication of virtual devices within a virtual experience service at the wireless communication network, wherein each virtual device corresponds to a physical device identified by a subscriber identity; discovering a plurality of candidate digital and physical devices for a given area and based on the received service requirements; deriving one or more session requirements from the received service requirements; wherein a session is established between any combination of said plurality of candidate digital and physical devices; Determine the parameters of each session; and The determined parameters are transmitted to at least one network node.

11. The method of claim 10, wherein the parameters include at least one of: network configuration or PDU set marking, slice selection, RAT selection and / or interface selection.

12. The method according to claim 10 or 11, wherein the service requirements include smart contracts for transactions between virtual devices within the virtual experience service.

13. The method of any of claims 10-12, wherein discovering a plurality of candidate digital and physical devices for a given area is based on the received service requirements by querying the wireless communication network.

14. The method of any of claims 10 to 13, wherein a session is established between any pair of the plurality of candidate digital and physical devices and the any pair communicates using the wireless communication network.

15. The method of any one of claims 10 to 14, wherein the plurality of candidate digital and physical devices support localized virtual experience services.

16. The method of claim 10, further comprising using a simulation engine to provide a simulation based on virtual objects within the virtual experience service.

17. The method of claim 16, wherein the operation of the simulation engine is based on requests from a server in the virtual experience service or subscription and includes different assumptions about network parameters and / or policies.

18. The method of any one of claims 10 to 17, further comprising determining a PDU set delay budget and a PDU set error rate and sending the PDU set delay budget and the PDU set error rate to the wireless communication network.

Images