WO2024150987A1

WO2024150987A1 - An application layer architecture and method for managing spatial anchor in a wireless communication system

Info

Publication number: WO2024150987A1
Application number: PCT/KR2024/000008
Authority: WO
Inventors: Sapan Pramodkumar SHAH; Basavaraj Jayawant Pattan
Original assignee: Samsung Electronics Co., Ltd.
Priority date: 2023-01-09
Filing date: 2024-01-02
Publication date: 2024-07-18

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the disclosure related to methods for managing spatial anchor(s) in the metaverse. A spatial anchor management module can manage one or more spatial anchors in the metaverse environment. The spatial anchor management module can enable the spatial anchor management client module to manage at least one spatial anchor. The spatial anchor management module can enable the spatial anchor management client module to create the at least one spatial anchor. The spatial anchor management module can enable the spatial anchor management client module to fetch the at least one spatial anchor.

Description

AN APPLICATION LAYER ARCHITECTURE AND METHOD FOR MANAGING SPATIAL ANCHOR IN A WIRELESS COMMUNICATION SYSTEM

Embodiments disclosed herein relate to metaverse applications, and more particularly to managing spatial anchors in the multiverse.

5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

Moreover, there has been ongoing standardization in air interface architecture/protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture/service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

The principal object of the embodiments herein is to disclose an application layer architecture for managing spatial anchor(s) in the metaverse.

Another object of the embodiments herein is to disclose methods for managing spatial anchor(s) in the metaverse.

Accordingly, the embodiments herein provide a method for managing at least one spatial anchor in a metaverse environment. The method comprises a spatial anchor management module enabling a spatial anchor management client module to manage at least one spatial anchor, wherein managing the at least one spatial anchor; i.e., the spatial anchor management client module can create the at least one spatial anchor; the spatial anchor management client module can update the at least one spatial anchor; the spatial anchor management client module can delete the at least one spatial anchor; and the spatial anchor management client module can fetch the at least one spatial anchor.

Accordingly, the embodiments herein provide a spatial anchor management module configured to enable a spatial anchor management client module to manage at least one spatial anchor; i.e., the spatial anchor management client module can create the at least one spatial anchor; the spatial anchor management client module can update the at least one spatial anchor; the spatial anchor management client module can delete the at least one spatial anchor; and the spatial anchor management client module can fetch the at least one spatial anchor.

These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

FIG. 1 illustrates an example food shop in the metaverse with spatial anchors;

FIG. 2 illustrates an on-network functional architecture for providing spatial anchor management services, according to embodiments as disclosed herein;

FIG. 3 illustrates a network function (NF/Spatial Anchor Management NF/SAMNF) for the 3GPP core network, according to embodiments as disclosed herein;

FIG. 4 illustrates an example on-network functional architecture for providing spatial anchor management services, according to embodiments as disclosed herein;

FIG. 5 illustrates the procedure for creating spatial anchor for metaverse applications, according to embodiments as disclosed herein;

FIG. 6 illustrates the procedure for updating spatial anchor for metaverse applications, according to embodiments as disclosed herein;

FIG. 7 illustrates the procedure for getting spatial anchor details for a metaverse application, according to embodiments as disclosed herein;

FIG. 8 illustrates the procedure for the NF to get spatial anchor details from a metaverse application server, according to embodiments as disclosed herein;

FIG. 9 illustrates a block diagram of a terminal (or a user equipment (UE), according to embodiments of the present disclosure; and

FIG. 10 illustrates a structure of a network entity according to an embodiment of the present disclosure.

The metaverse is considered as a digital world which is a replica of a real world. Digital worlds can be created for events or shops or mall or entertainment park which enables companies to run business online. Such services in the digital world are provided at specific locations, and so such services are called localized services. Each Metaverse application (i.e., digital world of the real world) may need an avatar for the user to interact with the application.

In order to provide a better experience to the users at their current location, the local service provider (i.e., owner of the shop or mall) needs to show appropriate details about their product/item at their appropriate location in 3D space within the metaverse. Such association between space and service is called as a spatial anchor.

FIG. 1 illustrates an example food shop in the metaverse. As shown in FIG. 1, the local service provider associates a service with an anchor, potentially as well as metadata concerning the service (for example, name or price). The local service provider determines what information to share and its location, and any constraints to apply (for example, whom to share the spatial anchor with) and additional information. Most importantly the 'resource' associated with the anchor. The details about spatial anchors for any metaverse application is available to the Public Land Mobile Network (PLMN) operator, either because the local services have been registered with the PLMN operator directly, or are available in maps, registries, or other information sources to which the PLMN operator has access (for example, information that is provided by a User Equipment (UE)). Based on such an association, Augmented Reality (AR) content can be created and shared with the user. The user can recognize anchors associated with locations, and can use the spatial anchor to obtain the associated information.

Considering the Metaverse application and usage of spatial anchors, the following requirements are being considered in 3rd Generation Partnership (3GPP):

- the Fifth Generation (5G) system shall enable an authorized third party to establish an association between a physical location (in three dimensional space, an orientation, etc.) and service information, where the service information is provided to the 5G system, and the spatial anchor is either provided or determined by the 5G system;

- the 5G system shall enable an authorized third party to obtain all of the spatial anchors located in a given three dimensional area; and

- the 5G system shall provide an authorized third party a means to manage the spatial anchor(s), for example, add, remove, or modify spatial anchors, determine privacy and security aspects, etc.

Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms “comprising”, “having” and “including” are to be construed as open-ended terms unless otherwise noted.

The words/phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words/phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” is not necessarily to be construed as preferred or advantageous over other embodiments.

Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (for example, one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts/sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components/modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components/elements/steps is for the purposes of this description and should not be construed as sequential ordering/placement/occurrence unless specified otherwise.

The embodiments herein achieve application layer architecture and methods for managing spatial anchor(s) in the metaverse. Referring now to the drawings, and more particularly to FIGS. 1 through 8, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

FIG. 2 illustrates an on-network functional architecture for providing spatial anchor management services. The architecture, as illustrated, comprises a plurality of entities (entity 1 101, entity 2 102, entity 3 103, and entity 104), and a data storage module 105.

The entity 3 103 and the entity 4 104 are an application client and server respectively, wherein the entity 3 103 and the entity 4 104 provide an application service to the user. The entity 3 103 and the entity 4 104 can be in communication with each other using a wireless communication network (such as, but not limited to, a cellular network (such as, but not limited to, a 3GPP network), a Wi-Fi network, Bluetooth, Matter, ZigBee, Bluetooth Low Energy (BLE), and so on).

The entity 3 103 can be an application client or vertical specific application client residing in a user device 106. The entity 3 103 can provide a metaverse service to the user. The entity 3 103 can use one or more of the other entities (entity 1 101, entity 2 102, and entity 104) to manage spatial anchors for an application residing on the user device 106. Examples of the entity 3 103 can be an application client (AC) or a Vertical Application Layer (VAL) client or an Edge Enable Client (EEC).

The entity 4 104 can refers to an application server/vertical specific Application Server/Edge application server, which provides metaverse services to the client on a service contract. The entity 4 104 can use functionalities of the entity 2 102 to manage spatial anchors for the application. Examples of the entity 4 104 can be, but not limited to, an application server (AS) or a VAL server or an Edge Application Server, or any other service capable of providing application services.

The entity 1 101 and the entity 2 102 can provide client and server side functionalities respectively for managing spatial anchors for an application. The interface between the entity 1 101 and the entity 2 102 can be Interface-UU. The Interface-UU can be used to create/update/delete/get/retrieve spatial anchors for the metaverse application. The entity 2 102 and the entity 1 101 can be in communication with each other using a wireless communication network (such as, but not limited to, a cellular network (such as, but not limited to, a 3GPP network), a Wi-Fi network, Bluetooth, Matter, ZigBee, Bluetooth Low Energy (BLE), and so on).

The entity 1 101 can be a Service Enabler Architecture Layer (SEAL) client providing spatial anchor management service to entity 3 103. The entity 1 101 can act as a SEAL client for spatial anchor management function. The entity 1 101 can support client side functionalities for creating/updating/deleting/getting/retrieving spatial anchors for metaverse application(s). The entity 1 101 can also be responsible for communication with other entities (performing functionalities similar to entity 1 101) of other user devices. In an embodiment herein, the entity 1 101 can be located or implemented within an Edge Enabler Client (EEC) or any SEAL clients (for example, SEAL location management client, SEAL configuration management client, and so on) or any other application enabler client. The

entities

1 and 3 101, 103 are present in the user device 106, and the interface between the entity 1 101 and the entity 3 103 can be an interface-C. The interface-C can be used by the entity 3 103 to share information regarding spatial anchor related information to the entity 1 101. The interface-C can also be used to get spatial anchor related information from the entity 1 101. The entity 1 101 can also be referred to herein as at least one of a Spatial Anchor Management (SAM) Client, or an Anchor Management (AM) Client, or a Spatial Anchor Enabler (SAE) client, or a metaverse application enabler (MAE) client, or any other suitable name.

The entity 2 102 can be a SEAL server providing spatial anchor management service to the entity 4 104. The interface between the entity 2 102 and the entity 4 104 can be an interface-S. The interface-S (SAM-S) can be used to create/update/delete/get/retrieve spatial anchors for the metaverse application(s). The entity 2 102 can interact with the data storage module 105 using an Interface-UDB. If the wireless communication network is a 3GPP network, the entity 2 102 can interact with the 3GPP network using a T8/N33 interface. The entity 2 102 can be a functional entity used to provide services to create/update/delete/get spatial anchors for the metaverse application. The entity 2 102 can be used to communicate to other entities (performing functionalities similar to entity 2 102) in distributed SEAL deployments. In an embodiment herein, the entity 2 102 can be located or implemented within an Edge Enabler Server (EES), or a SEAL Server (for example, SEAL location management client, SEAL configuration management client, and so on), or a Metaverse Application Enabler (MAE) Server or any other application enabler server. The entity 2 102 can also be referred to herein as at least one of a Spatial Anchor Management (SAM) Server, or an Anchor Management (AM) Server, or a Spatial Anchor Enabler (SAE) server, or a metaverse application enabler (MAE) server, or any other suitable name.

The data storage module 105 can be a database, wherein the data storage module 105 can store spatial anchors and its related information. The data storage module 105 can be used to store any other details related to SEAL service or metaverse application service. In an embodiment herein, the data storage module 105 can be located within the entity 2 102.

FIG. 3 illustrates a network function (NF/Spatial Anchor Management NF (SAMNF)) for the 3GPP core network. As shown in FIG. 3, the NF (i.e., SAMNF) 301 (also referred to herein as a second NF) can interact with other 3GPP NFs 302 (such as, but not limited to, Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Exposure Function (NEF), Unified Data Management (UDM), and so on), from the core network over a service based interface. The NF 301 can provide services to create/update/delete/get/retrieve spatial anchors. The NF 301 can have their own repository (not shown) to store special anchors, or the NF 301 can store the spatial anchors in an already existing repository from the core network (such as, but not limited to, Home Subscriber Server (HSS)) (not shown). In FIG. 3, the NF 301 can manage spatial anchors. The NF 301 can determine and provide details to a user based on their location and required application.

FIG. 4 illustrates an example on-network functional architecture for providing spatial anchor management services. The architecture, as illustrated, comprises a spatial anchor management module 401, and a spatial anchor management client module 402. The spatial anchor management module 401 can be at least one of the second Network Function (NF) in a 3rd Generation Partnership Project (3GPP) core network (i.e., SAMNF 301); and an application server, wherein the application server is external to the 3GPP core network.

The spatial anchor management client module 402 can be at least one of a metaverse application server; a Vertical Application Layer (VAL) server; a client; and a first Network Function (NF) (which can be any NF from the 3GPP core network). The spatial anchor management client module 402 can be located or implemented within the Edge Enabler Client (EEC) or any SEAL clients (for example, SEAL location management client, SEAL configuration management client, and so on) or any other application enabler client.

The spatial anchor management module 401 can manage one or more spatial anchors in the metaverse environment. The spatial anchor management module 401 can enable the spatial anchor management client module 402 to manage at least one spatial anchor.

The spatial anchor management module 401 can enable the spatial anchor management client module 402 to create the at least one spatial anchor. The spatial anchor management module 401 can receive a request from the spatial anchor management client module 402, wherein the received request can be for creating the spatial anchor. In an embodiment herein, the request includes a position of the spatial anchor in three dimensions (3D) in the metaverse environment, orientation of a current view (i.e., point of view of the user), an application service identifier, and product information. The spatial anchor management module 401 can authenticate the spatial anchor management client module 402. On successfully authenticating the spatial anchor management client module 402, the spatial anchor management module 401 can create the spatial anchor. The spatial anchor management module can create the spatial anchor, on authenticating the spatial anchor management client module. On creating the spatial anchor, the spatial anchor management module 401 can further send a response to the spatial anchor management client module 402, wherein the response includes an identity of the spatial anchor. The spatial anchor management module 401 can further store information related to the generated spatial anchor in a suitable location such as, but not limited to, the data storage module 105.

The spatial anchor management module 401 can enable the spatial anchor management client module 402 to update the at least one spatial anchor. Updating the at least one spatial anchor can comprise at least one of modifying the at least one spatial anchor; and deleting the at least one spatial anchor. The spatial anchor management module 401 can receive an update request from the spatial anchor management client module 402, wherein the request can be for updating the spatial anchor. The update request can include identity of the spatial anchor, and at least one parameter to be updated in the spatial anchor. The spatial anchor management module 401 can authenticate the spatial anchor management client module 402. On successfully authenticating the spatial anchor management client module 402, the spatial anchor management module 401 can update the spatial anchor based on the received update request. On updating the spatial anchor, the spatial anchor management module 401 can send a response to the spatial anchor management client module 402.

The spatial anchor management module 401 can enable the spatial anchor management client module 402 to fetch the at least one spatial anchor. The spatial anchor management module 401 can receive a fetch request from the spatial anchor management client module 402, wherein the request can be for fetching at least one spatial anchor. The fetch request includes a position of a user in 3D in the metaverse environment, orientation of a view of the user, and an application service identifier. The spatial anchor management module 401 can authenticate the spatial anchor management client module 402. On successfully authenticating the spatial anchor management client module 402, the spatial anchor management module 401 can determine the one or more spatial anchors based on the received fetch request. The spatial anchor management module 401 can send the determined one or more spatial anchors to the spatial anchor management client module 402.

FIG. 5 illustrates the procedure for creating spatial anchor for metaverse applications. The spatial anchor management module 401 can create the spatial anchor, wherein the spatial anchor management module 401 can be at least one of the entity 2 102 or the NF (SAMNF) 301. The spatial anchor management client module 402 can consume the generated spatial anchor. The spatial anchor management client module 402 can be at least one of the entity 1 101 (SAM client) or the entity 4 104 (VAL server) or the NEF, or any NF from the 3GPP core network.

In step 501, the spatial anchor management client module 402 sends a request message to the spatial anchor management module 401 to create the spatial anchor. The request includes a position of the anchor in 3D (i.e., x, y, z coordinates) along with orientation of the view and application service identifier. The request also includes product information (like product/item name, price, total quantity available in the store, product/item type, manufacturing company and date, expiry date, product ratings, product reviews, link to get more details about usage of the produce, etc.).

In step 502, the spatial anchor management module 401 authorizes the spatial anchor management client module 402. If the spatial anchor management client module 402 is authorized, then in step 503, the spatial anchor management module 401 creates the spatial anchor, stores the information received in the request message as spatial anchor details in the data storage module 105 and creates the identity for the spatial anchor. In an embodiment, the position of the anchor in 3D along with application service identifier can be the identity of the spatial anchor. In step 504, the spatial anchor management module 401 sends the response back to the spatial anchor management client module 402 which includes the result of the operation and the spatial anchor identity.

FIG. 6 illustrates the procedure for updating spatial anchor for metaverse applications. The update operation includes modifying an existing spatial anchor or deleting the spatial anchor. In step 601, the spatial anchor management module 401 sends a request message to the spatial anchor management module 401, wherein the request can be for updating the existing spatial anchor; i.e., the request can be for modification or deletion of the spatial anchor. The request message includes the identity of the spatial anchor and the application service identifier. If the request is to modify the existing spatial anchor, the request also includes parameters to be updated.

In step 602, the spatial anchor management module 401 authorizes the spatial anchor management module 401. If the spatial anchor management module 401 is authorized, then in step 603, the spatial anchor management module 401 checks whether the spatial anchor as mentioned in the received request message exists or not. If the spatial anchor does not exist, then spatial anchor management module 401 sends a failure response. Otherwise, in step 604, the spatial anchor management module 401 performs the requested operation. If the request is to modify the existing spatial anchor, then the spatial anchor management module 401 updates the spatial anchor details in the data storage module 105. If the request is to delete the existing spatial anchor, then the spatial anchor management module 401 deletes the spatial anchor details from the data storage module 105. In step 605, the spatial anchor management module 401 sends the response to the spatial anchor management module 401 which includes the result of the operation and the spatial anchor identity (on successful updating of the spatial anchor). In an embodiment herein, the response send by the spatial anchor management module 401 to the spatial anchor management client module 402 may include reason(s) for the failure in updating the spatial anchor.

In an embodiment herein, the spatial anchor management module 401 notifies the users about the update of the spatial anchor (if any user or another application server is already using the spatial anchor). The notification includes the identity of the spatial anchor and the updated parameters of the spatial anchor.

FIG. 7 illustrates the procedure for getting spatial anchor details for a metaverse application. In step 701, the spatial anchor management client module 402 sends a request message to the spatial anchor management module 401 to get or retrieve spatial anchors. The request includes the position of the user in 3D or pose of the user in 3D (i.e., x, y, z coordinates) along with orientation of the view and application service identifier. The request optionally includes other information regarding user’s interest (like product/item type (cloth, food), color, price range, brand/manufacturing company etc.). The request may include identify of the spatial anchor if the user wants to get more details about the specific spatial anchor.

In step 702, the spatial anchor management module 401 authorizes the spatial anchor management client module 402. If the client is authorized, then in step 703, the spatial anchor management module 401 determines one or more spatial anchors from the data storage module 105 based on the parameters provided in the request message. In step 704, the spatial anchor management module 401 sends the response back to the spatial anchor management client module 402 which includes the result of the operation and list of spatial anchor details (including its identity) for successful case. If the request is to get details for the specific spatial anchor, the spatial anchor management module 401 includes all details about the spatial anchor as available in the data storage module 105 in the successful response. In an embodiment, the spatial anchor management client module 402 also subscribes to the spatial anchor management module 401 to receive notification(s) on the update of the spatial anchors using a request message to get or retrieve spatial anchors.

FIG. 8 illustrates the procedure for the NF to get spatial anchor details from a metaverse application server. Here, the NF 301 determines and provides spatial anchor details to the user based on their location and required application. The spatial anchors can be created and managed in a metaverse application server (not shown), so the NF 301 need not interact with the metaverse application server.

Upon receiving the request to get spatial anchors at a specific location for a specific application from a user or a user device 106, in step 801, the 3GPP NFs 302 sends a request to the NF 301 to get spatial anchors details. In an embodiment herein, the 3GPP NFs 302 receives the request from the user or the user device 106 over a NAS message to create/update/delete/get spatial anchors for metaverse applications. The request may include the position of the user in 3D or pose of the user in 3D (i.e., x, y, z coordinates) along with orientation of the view and application service identifier. The request may include identify of the spatial anchor if it is included in the request from the 3GPP NFs 302. If the request from the 3GPP NFs 302 does not include the location of the user, then the NF 301 gets the location from the core network. The request optionally includes other information regarding user’s interest (like product type (cloth, food), product color, price range, brand/manufacturing company etc.). The request may include identify of the spatial anchor if the user wants to get more details about the specific spatial anchor.

The NF 301 authorizes the request and if the user is authorized, in step 802, the NF 301 queries the 3GPP NFs 302 to get the details of the spatial anchors. The query message includes application service identity, spatial anchor identity, user’s identity and parameters received in the request from the 3GPP NFs 302. In step 803, the 3GPP NFs 302 identifies a specific application server (based on the application identity) (i.e., entity 4) 104, and in step 804, sends the query message to the application server 104, wherein the query message includes the parameters received in the request from the NF 301.

In step 805, the application server 104 determines the special anchors based on the input parameters received in the request, and in step 806, the application server 104 sends the list of one or more spatial anchors back to the 3GPP NFs 302. If the request is to get details for the specific spatial anchor, the application server 104 includes all details about the spatial anchor as available in the data storage module 105 in the successful response. On receiving the list of spatial anchor or details about a specific spatial anchor, in step 807, the 3GPP NFs 302 sends the response back to the NF 301, wherein the response contains the list of one or more spatial anchors and their information (if requested). In step 809, the NF 301 sends the acknowledge back to the 3GPP NFs 302.

FIG. 9 illustrates a block diagram of a terminal (or a user equipment (UE)), according to embodiments of the present disclosure. FIG. 9 corresponds to the example of the User device 106 of FIG. 2.

As shown in FIG. 9, the UE according to an embodiment may include a transceiver 910, a memory 920, and a processor 930. The transceiver 910, the memory 920, and the processor 930 of the UE may operate according to a communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. In addition, the processor 930, the transceiver 910, and the memory 920 may be implemented as a single chip. Also, the processor 930 may include at least one processor.

The transceiver 910 collectively refers to a UE receiver and a UE transmitter, and may transmit/receive a signal to/from a base station or a network entity. The signal transmitted or received to or from the base station or a network entity may include control information and data. The transceiver 910 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 910 and components of the transceiver 910 are not limited to the RF transmitter and the RF receiver.

Also, the transceiver 910 may receive and output, to the processor 930, a signal through a wireless channel, and transmit a signal output from the processor 930 through the wireless channel.

The memory 920 may store a program and data required for operations of the UE. Also, the memory 920 may store control information or data included in a signal obtained by the UE. The memory 920 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The processor 930 may control a series of processes such that the UE operates as described above. For example, the transceiver 910 may receive a data signal including a control signal transmitted by the base station or the network entity, and the processor 930 may determine a result of receiving the control signal and the data signal transmitted by the base station or the network entity.

As shown in FIG. 10, the network entity of the present disclosure may include a transceiver 1010, a memory 1020, and a processor 1030. The transceiver 1010, the memory 1020, and the processor 1030 of the network entity may operate according to a communication method of the network entity described above. However, the components of the terminal are not limited thereto. For example, the network entity may include more or fewer components than those described above. In addition, the processor 1030, the transceiver 1010, and the memory 1020 may be implemented as a single chip. Also, the processor 1030 may include at least one processor.

The transceiver 1010 collectively refers to a network entity receiver and a network entity transmitter, and may transmit/receive a signal to/from a base station or a UE. The signal transmitted or received to or from the base station or the UE may include control information and data. In this regard, the transceiver 1010 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 1010 and components of the transceiver 1010 are not limited to the RF transmitter and the RF receiver.

Also, the transceiver 1010 may receive and output, to the processor 1030, a signal through a wireless channel, and transmit a signal output from the processor 1030 through the wireless channel.

The memory 1020 may store a program and data required for operations of the network entity. Also, the memory 1020 may store control information or data included in a signal obtained by the network entity. The memory 1020 may be a storage medium, such as ROM, RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The processor 1030 may control a series of processes such that the network entity operates as described above. For example, the transceiver 1010 may receive a data signal including a control signal, and the processor 1030 may determine a result of receiving the data signal.

Embodiments herein reduce the burden from each application and provide a common framework to manage spatial anchors for each application.

The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

The embodiment disclosed herein describes an application layer architecture and methods for managing spatial anchor(s) in the metaverse. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in for example, high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be for example, hardware means like for example, an application specific integrated circuit (ASIC), or a combination of hardware and software means, for example, an ASIC and an field programmable gate array (FPGA), or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, for example, using a plurality of CPUs.

The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

A method performed by a spatial anchor node in a metaverse environment, the method comprising:

enabling, by a spatial anchor management module, a spatial anchor management client module to manage at least one spatial anchor, wherein managing the at least one spatial anchor comprises:

enabling, by the spatial anchor management module, the spatial anchor management client module to create the at least one spatial anchor;

enabling, by the spatial anchor management module, the spatial anchor management client module to update the at least one spatial anchor; and

enabling, by the spatial anchor management module, the spatial anchor management client module to fetch the at least one spatial anchor.
The method of claim 1, wherein the spatial anchor management client module is at least one of:

a metaverse application server;

a Vertical Application Layer (VAL) server;

a client; and

a first Network Function (NF).
The method of claim 1, wherein the spatial anchor management module is at least one of:

a second Network Function (NF) in a 3rd Generation Partnership Project (3GPP) core network; and

an application server, wherein the application server is external to the 3GPP core network.
The method of claim 1, wherein creating the at least one spatial anchor comprises:

receiving, by the spatial anchor management module, a request from the spatial anchor management client module, for creating the spatial anchor, wherein the request includes a position of the spatial anchor in three dimensions (3D) in the metaverse environment, orientation of a current view, an application service identifier, and product information;

creating, by the spatial anchor management module, the spatial anchor, on authenticating the spatial anchor management client module;

storing, by the spatial anchor management module, information related to the spatial anchor; and

sending, by the spatial anchor management module, a response to the spatial anchor management client module, on successfully creating the spatial anchor, wherein the response includes an identity of the spatial anchor.
The method of claim 1, wherein updating the at least one spatial anchor comprises:

receiving, by the spatial anchor management module, an update request from the spatial anchor management client module, for updating the spatial anchor, wherein the update request includes identity of the spatial anchor, and at least one parameter to be updated in the spatial anchor;

updating, by the spatial anchor management module, the spatial anchor based on the received update request, on authenticating the spatial anchor management client module; and

sending, by the spatial anchor management module, a response to the spatial anchor management client module, on successfully updating the spatial anchor.
The method of claim 1, wherein updating the at least one spatial anchor comprises at least one of:

modifying the at least one spatial anchor; and

deleting the at least one spatial anchor.
The method of claim 1, wherein fetching the at least one spatial anchor comprises:

receiving, by the spatial anchor management module, a fetch request from the spatial anchor management client module for fetching at least one spatial anchor, wherein the fetch request includes a position of a user in 3D in the metaverse environment, orientation of a view of the user, and an application service identifier;

determining, by the spatial anchor management module, one or more spatial anchors based on the received fetch request, on authenticating the spatial anchor management client module; and

sending, by the spatial anchor management module, the determined one or more spatial anchors to the spatial anchor management client module.
A spatial anchor node in a metaverse environment, the spatial anchor comprising:

a transceiver, and

a controller coupled with the transceiver and configured to:

enable a spatial anchor management client module to manage at least one spatial anchor,

enable the spatial anchor management client module to create the at least one spatial anchor,

enable the spatial anchor management client module to update the at least one spatial anchor, and

enable the spatial anchor management client module to fetch the at least one spatial anchor.
The spatial anchor node of claim 8, wherein the spatial anchor management client module is at least one of:

a metaverse application server;

a Vertical Application Layer (VAL) server;

a client; and

a first Network Function (NF).
The spatial anchor node of claim 8, wherein the spatial anchor management module is at least one of:

a second Network Function (NF) in a 3rd Generation Partnership Project (3GPP) core network; and

an application server, wherein the application server is external to the 3GPP core network.
The spatial anchor node of claim 8, wherein the processor is further configured to:

receive, by the spatial anchor management module, a request from the spatial anchor management client module, for creating the spatial anchor, wherein the request includes a position of the spatial anchor in three dimensions (3D) in the metaverse environment, orientation of a current view, an application service identifier, and product information,

create, by the spatial anchor management module, the spatial anchor, on authenticating the spatial anchor management client module,

store, by the spatial anchor management module, information related to the spatial anchor, and

send, by the spatial anchor management module, a response to the spatial anchor management client module, on successfully creating the spatial anchor, wherein the response includes an identity of the spatial anchor.
The spatial anchor node of claim 8, wherein the processor is further configured to:

receive, by the spatial anchor management module, an update request from the spatial anchor management client module, for updating the spatial anchor, wherein the update request includes identity of the spatial anchor, and at least one parameter to be updated in the spatial anchor,

update, by the spatial anchor management module, the spatial anchor based on the received update request, on authenticating the spatial anchor management client module, and

send, by the spatial anchor management module, a response to the spatial anchor management client module, on successfully updating the spatial anchor.
The spatial anchor node of claim 8, wherein the processor is further configured to at least one of:

modify the at least one spatial anchor, and

delete the at least one spatial anchor.
The spatial anchor node of claim 8, wherein the processor is further configured to:

receive, by the spatial anchor management module, a fetch request from the spatial anchor management client module for fetching at least one spatial anchor, wherein the fetch request includes a position of a user in 3D in the metaverse environment, orientation of a view of the user, and an application service identifier,

determine, by the spatial anchor management module, one or more spatial anchors based on the received fetch request, on authenticating the spatial anchor management client module, and

send, by the spatial anchor management module, the determined one or more spatial anchors to the spatial anchor management client module.