Dynamic creation and management of spatial anchors

Abstract

Systems, apparatuses, and methods for dynamic creation and management of spatial anchors are described. According to a first aspect of the present specification, there is described an apparatus comprising: means for receiving, from a service provider, a request to initiate a spatial anchor associated with a moving object; means for generating a spatial anchor associated with the moving object based on the received request; means for receiving, from a service provider or user equipment, a request for acquisition of a spatial anchor associated with the moving object; means for acquiring the position of the moving object; means for updating the spatial anchor with the acquired position of the moving object; and means for providing the updated spatial anchor to a service provider or user equipment.

Description

Technical Field

[0001] The present application describes systems, apparatus, and methods for dynamic creation and management of spatial anchors. Background Art

[0002] A spatial anchor is an association between a location in space (e.g., three dimensions) and service information that can be used to identify and access services, such as information for accessing augmented reality (AR) media content. The service information may include information that enables users to discover and access services, such as service type, URL, configuration data, distance between the user and the spatial anchor, etc.

[0003] In the context of mobile metaverse services (including mobile AR), 3GPP TR 22.856 further defines the concept of digital assets as “information stored in a digital manner that is uniquely identifiable and that can realize value in accordance with its licensing conditions and applicable regulations. Examples of digital assets include digital images (avatars), software licenses, gift certificates, and files purchased under a license that permits resale (e.g., music files)”. Additionally, a set of requirements has been defined to manage digital assets, potentially via digital asset containers within the 5GC. Summary of the invention

[0004] According to a first aspect of the present specification, an apparatus is described, comprising: a component for receiving a request to initiate a spatial anchor associated with a mobile object from a service provider; a component for generating a spatial anchor associated with the mobile object based on the received request; a component for receiving a request to obtain a spatial anchor associated with the mobile object from a service provider or a user device; a component for obtaining a position of the mobile object; a component for updating the spatial anchor using the obtained position of the mobile object; and a component for providing the updated spatial anchor to the service provider or the user device.

[0005] The means for generating a spatial anchor associated with a mobile object may include means for generating a digital asset representing the spatial anchor, the digital asset including one or more spatial anchor attributes; and means for storing the digital asset in a digital asset container.

[0006] The one or more spatial anchor attributes may include: a spatial anchor ID that uniquely identifies the object; service information that identifies one or more services associated with the spatial anchor; and a spatial location. The service information may include one or more of the following: a service description; a service URL; media content information; and / or configuration data for the service.

[0007] The method may also include: means for receiving an update request for the spatial anchor from the service provider; and means for updating one or more of the one or more attributes of the spatial anchor based on the update request. The update request for the spatial anchor may include an identifier of the user device from which the request originated.

[0008] The one or more spatial anchor attributes may include one or more timestamps indicating: a spatial anchor creation time; a spatial anchor attribute update time; and / or a spatial anchor position update time.

[0009] The one or more spatial anchor attributes may include the location of one or more restricted areas. The apparatus may also include: a component for determining whether the mobile object is within the restricted area based on the location of the mobile object; and a component for updating the spatial anchor with a warning indication in response to determining that the mobile object is within the restricted area. The apparatus may also include: a component for triggering one or more actions based on the warning indication.

[0010] The apparatus may also include means for limiting and / or preventing access to the spatial anchor based at least in part on the identity of the service provider or user device.

[0011] According to another aspect of the present specification, an apparatus is described, comprising: a component for initiating a request from a network for a spatial anchor associated with a mobile object; a component for receiving a request from a user device for a service that utilizes the object as a spatial anchor; a component for requesting the network to update one or more attributes of the spatial anchor based on the request for the service; a component for receiving an updated spatial anchor from the network; and a component for causing transmission of the updated spatial anchor to the user device.

[0012] The updated spatial anchor may include the current position of the moving object.

[0013] The updated spatial anchor may include a warning message indicating that the current position of the mobile object is within the restricted area.

[0014] According to another aspect of the present specification, a computer-implemented method is described, including: receiving a request from a service provider to initiate a spatial anchor associated with a mobile object; generating a spatial anchor associated with the mobile object based on the received request; receiving a request from a service provider or a user device to obtain a spatial anchor associated with the mobile object; obtaining a position of the mobile object; updating the spatial anchor using the obtained position of the mobile object; and providing the updated spatial anchor to the service provider or the user device.

[0015] According to another aspect of the present specification, a computer-implemented method is described, including: initiating a request from a network to a spatial anchor associated with a mobile object; receiving a request from a user device for a service utilizing the object; requesting the network to update one or more attributes of the spatial anchor based on the request for the service; receiving the spatial anchor from the network; and causing transmission of the spatial anchor to the user device. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Example embodiments will now be described by way of non-limiting examples with reference to the accompanying drawings, in which:

[0017] Figure 1 A schematic diagram of a system for providing services to UEs based on a mobile space anchor is shown;

[0018] Figure 2 An example of a signaling diagram for a method of providing services based on a mobile space anchor is shown;

[0019] Figure 3 An example of a signaling diagram of a method for providing services based on mobile spatial anchors in the presence of restricted areas is shown;

[0020] Figure 4 A flow chart illustrating an example method for dynamically creating and / or managing mobile space anchors;

[0021] Figure 5 A flow chart illustrating an example method for providing services based on a mobile spatial anchor is shown;

[0022] Figure 6 An apparatus / system is shown which may form at least a part of a user equipment or a network node according to some example embodiments; and

[0023] Figure 7 Non-transitory media according to some embodiments are shown. DETAILED DESCRIPTION

[0024] Currently, spatial anchors are typically static, tied to a specific location (e.g., precise or identified by a limited 3D region in space) and service information, which is provided by the supplier to the consumer via a mobile service provider (e.g., a metaverse provider). Using mobile spatial anchors (i.e., whose location may change over time) provides additional challenges that need to be addressed.

[0025] For example, mobile space anchors may be associated with real objects, whose positions may be derived and tracked by relying on a location management function (LMF) (e.g., 3GPP LMF). Additionally or alternatively, additional features may be attached to the mobile space anchors as "filters" to more accurately track them in some 3D space, such as via computer vision based on pre-identified objects (e.g., based on markers, pictures, or 3D models / shapes).

[0026] Another challenge lies in managing mobile spatial anchors (e.g., connected cars or other objects) as they traverse restricted areas (e.g., “no-go zones”) and need to dynamically update their location and service information for comparison with specific zones to ensure regulatory compliance, safety, and real-time service accuracy.

[0027] Additionally, ensuring the authenticity of these anchors and other service information, such as associated objects or shapes (e.g., connected cars or devices), is an important consideration.

[0028] To meet these needs, a wireless network operator (e.g., a 5G operator) that operates at least a portion of a core network (e.g., a 5GC) can own and manage a spatial anchor system to facilitate the management of dynamic spatial anchors for content producers, customers, and metaverse service providers. The core network provides spatial anchors as a service, where the core network opens an API to request spatial anchors or manage or create spatial anchors on the core network. The core network is responsible for managing the security and privacy of spatial anchors and associated users. The core network also handles the movement of spatial anchors relative to restricted areas. However, the content of the spatial anchor is defined in application data provided by a third-party service provider (e.g., a metaverse service provider).

[0029] Figure 1 A schematic diagram of a system 100 for providing services to a UE 102 based on mobile spatial anchors is shown. The system includes a UE 102 located in a spatial region 114 (also referred to herein as an "environment") that contains one or more mobile objects 112a, 112b that are used as spatial anchors for services provided by a service provider 104 (e.g., a metaverse service provider). The spatial anchors associated with the mobile objects 112a, 112b are managed by a core network 110 (e.g., a 5GC network), which stores and manages each spatial anchor as a digital asset in a digital asset container 106 (DAC), and obtains location data for the mobile objects using a location management function 108 (LMF) (e.g., a 3GPP LMF).

[0030] UE 102 can be any device that a user can use to wirelessly communicate with a network (e.g., core network 110 or network of service provider 104). Examples of such UE 102 include, but are not limited to, smartphones, tablets, smart glasses, etc. UE 102 can execute one or more applications that provide access to one or more services operated / managed by service provider 104 and that utilize spatial anchors associated with mobile objects 112a, 112b. For example, service provider 104 can be a metaverse service provider that provides augmented reality (AR) content to users via applications on UE 102.

[0031] In some examples, the mobile objects 112a, 112b are networked devices, such as further UEs, IoT devices, etc. Such networked devices may communicate wirelessly with the core network 110. The LMF 106 of the core network 110 may directly determine the location of the networked device using any wireless positioning technology known in the art.

[0032] In some examples, the mobile objects 112a, 112b are not networked objects, such as objects in a store or objects in an environment. In such examples, the positions of the mobile objects 112a, 112b can be determined indirectly, such as using computer vision capabilities of the UE 102. For example, additional features can be attached to digital assets representing the mobile objects 112a, 112b that act as "filters" to more accurately track them in a certain 3D space, such as via computer vision based on pre-identified objects (e.g., markers, pictures, or 3D models / shapes).

[0033] Using DAC 106 as a spatial anchor repository can ensure that the spatial anchor lifecycle is managed securely and efficiently through the DAC authorization service. DAC 106 receives real-time updates from service providers 104 (or other systems managed by the owner) to ensure that it has the latest and most accurate spatial anchor service information.

[0034] When a user engages in a service that utilizes spatial anchors (e.g., an augmented reality (AR) service), the user's UE 102 and / or the service provider 104 providing the service requests the DAC 106 for spatial anchors within a specific location space. This involves the DAC 106 acquiring spatial anchors associated with the mobile objects 112a, 112b, during which the DAC 106 can automatically acquire the current physical locations of the mobile objects 112a, 112b via the LMF 108. The DAC 106 then dynamically generates spatial anchors by combining the real-time location information of the mobile objects 112a, 112b with the relevant service information, thereby ensuring the accuracy and efficiency of the process. Alternatively, the DAC 106 can provide quick access to the spatial anchor location based on a previously acquired location without the need for a real-time location lookup, thereby ensuring the accuracy and reliability of the data through regular database updates.

[0035] In some examples, the DAC 106 provides service information for spatial anchors, including optional privacy filters (e.g., only provided to authorized users), within the spatial anchor metadata provided by various stakeholders (such as metaverse service providers, operators, and content providers, etc.). The DAC 106 can also implement a privacy and consent framework for collecting new types of data (e.g., camera data, sensor data, etc.), i.e., the core network 110 must not collect this data without obtaining new consent from the user. In some examples, consent can also be performed at a per-spatial anchor level.

[0036] In some implementations, the 5G operator and / or service provider 104 provides the location of the restricted area to the DAC 106, and the DAC 106 checks whether the location of the mobile objects 112a, 112b falls within any of these restricted areas. If so, the DAC 106 can generate a spatial anchor with a warning message indicating that the mobile objects 112a, 112b exist in the restricted area. This warning message can trigger appropriate actions to ensure compliance, security, and data privacy in sensitive areas. In other cases, due to security issues, the DAC 106 will avoid providing spatial anchors to users, such as when encountering false spatial anchors (e.g., uncertified or provided by a supplier who is not responsible for the location). In some implementations, the DAC 106 can send warning messages and error logs to the operation and maintenance (O&M) system of the 5G network. This information can allow the O&M system to improve its capabilities and take proactive measures to prevent the creation of false spatial anchors in the future.

[0037] Figure 2 An example of a signaling diagram for a method for providing a service based on a mobile spatial anchor is shown. This example will be described for an AR service that guides a user to a rental car, but other examples (both AR-based and non-AR-based) are possible. The method may be Figure 1system execution.

[0038] Prior to using an object 212 as a spatial anchor by a UE 202, a service provider 204 associated with the object 212 submits a request 214 for creation of a spatial anchor to the core network. In some examples, the request 214 to create a spatial anchor is a one-time process for each object 212.

[0039] Request 214 includes information about the object sufficient to enable a spatial anchor to be initiated. For example, request 214 may include one or more of the following: an identifier for the requesting entity (i.e., service provider 204); an anchor ID, e.g., a numeric or alphanumeric identifier for a spatial anchor; an anchor entity, used to identify object 212; a 3D model and / or picture of object 212, used to perform computer vision recognition of object 212; and / or one or more asset details, indicating properties of object 212. In some examples, the current location of object 212 is also included. Alternatively, a core network request for obtaining the current location of object 212 using location management function 208 may be included.

[0040] In some examples, the core network collects location information of networked devices (e.g., 3GPP devices) with the prior consent of the device owner.

[0041] For the car rental example, a sample request could be:

[0042]

[0043]

[0044] The core network sets the spatial anchor as a digital asset and stores the digital asset in a digital asset container 206 (DAC). The digital asset representing the spatial anchor includes: a spatial location; service information; and a spatial anchor ID.

[0045] The spatial location includes at least one valid position in three-dimensional space. It may include reference coordinates, such as (X, Y, Z). This information can help accurately locate and align the relationship of virtual content or services to the real world environment. In some examples, it can be used to filter spatial anchors related to the consumer / UE location. Note that although this location information is provided to the consumer / UE, it may not be provided / known by the service provider itself, but may provide the 3GPP unique identifier of the associated UE (to be tracked by the core network), or some related information, allowing the core network to indirectly obtain this identifier (for example, via a directory / database).

[0046] A spatial anchor may include relevant service information to enable identification and access of associated services. For example, this may include details such as: service type; service description; URL and / or endpoint for accessing the service; media content information (e.g., AR media); and / or configuration data required to utilize the service.

[0047] Each spatial anchor may be assigned a unique identifier or ID that serves as a reference for easy identification and retrieval. The ID may be used to uniquely associate the spatial anchor with the service information corresponding to the spatial anchor.

[0048] In some examples, the digital asset also includes one or more timestamps / time information, such as indicating: the time / date when the spatial anchor was created and / or last modified; and / or the time / date when the spatial anchor position was last updated.

[0049] In some examples, the digital asset also includes additional metadata, such as creator information, versioning details, privacy settings, and / or any other relevant attributes that provide further context or management capabilities for the spatial anchor.

[0050] Once the spatial anchor has been set as a digital asset, it can be used in services provided by third-party service providers. UE 202 (also referred to herein as "user UE") then requests 216 a service from service provider 204, for example, initiating an AR experience with a car rental service provider and sending a car rental request to the metaverse of service provider 204. Request 214 can include a selection of a particular service, for example, picking a car from a collection of available rental cars.

[0051] Once the user completes the service selection via their device 202 or otherwise, the service provider 204 proceeds to update 218 the properties of the spatial anchor(s) associated with the mobile object(s) for the local service, granting the user authorization to utilize the spatial anchors, thereby enabling them to access the service. For example, once the user 202 completes the car rental process and selects a car (i.e., mobile object 212), the car rental company (i.e., service provider 204) proceeds to update 218 the spatial anchors associated with the specific car of that category, granting the user authorization, thereby enabling them to view and access the selected car in AR.

[0052] After the local update 218 of the spatial anchor attributes, the service provider 204 initiates an updated spatial anchor creation request 220 by providing metadata to the DAC 206 to obtain the identity of each mobile object 212 (e.g., obtaining IMSI1 for a rental car) or directly including the identity of the mobile object 212 (e.g., IMSI1 for a car). In addition, the request may contain an identifier of the user 202 requesting the service (e.g., IMSI2 in the case of a rental car).

[0053] As an illustrative example, an example update request 220 by user 202 associated with a car rental may be given by:

[0054]

[0055]

[0056] While the update request is being processed, the user UE 202 may initiate a service, such as starting a mobile AR experience at the user's location (not shown).

[0057] In some examples, when user 202 starts a service (e.g., a mobile AR experience for finding a car), the core network can request an OTP or token (not shown) from the user to verify that the user is at a location associated with the service and / or the requested spatial anchor. In some examples, the token or OTP may only be accessible from that location (e.g., based on a visual display, QR code, etc.). Additionally, this security mechanism can be associated with metadata about the request, such as a pre-configured anchor type / ID, to help further optimize the search process.

[0058] The DAC 206 manages 222 service information related to the requested service (e.g., car rental) in its asset list. For example, the DAC 206 updates the spatial anchor based on the update request 220 from the service provider 204. When the object identifier for the mobile object (e.g., IMSI1) is not provided in the request, the DAC 206 can obtain the identifier of the connected mobile object and match the identifier of the connected mobile object with the attributes provided in the update request 220 (e.g., "asset_details" mentioned in the request).

[0059] In some examples, managing 222 service information related to the requested service includes verifying permission for location information collection for the mobile object by checking a consent flag stored in a unified data management (UDM) system of the core network. This flag ensures that the core network collects location data, sensor and / or camera information for spatial anchor creation only with the prior consent of the device owner, which is consistent with the user's privacy preferences.

[0060] In some examples, managing 222 service information related to the requested service includes obtaining a list of spatial anchors based on the requested anchor type and / or ID, if a spatial anchor has been created. Managing 222 service information may also include checking the current location(s) of the mobile object(s) and ensuring that they are within a specific location range. The location range may include a range defined by the service provider 204, such as one or more physical locations associated with the service provider, such as a store location, a factory location, a warehouse location, an event location, etc. The DAC 206 may also verify the authenticity and authentication of the spatial anchors, considering whether they are provided by an authorized provider of the corresponding location.

[0061] In some examples, DAC 206 prioritizes user identity and enforces user-specific permissions using role-based access control (RBAC). The RBAC mechanism determines the permissions of the requesting user 202, allowing them to access and view relevant service information when they are authorized to do so.

[0062] To determine the location of the mobile object, in some examples, the DAC 206 requests 224 a location management function (LMF) to obtain the current location of the mobile object 212. In some examples, this triggers the LMF 208 to obtain 226 the current location of the mobile object, e.g., using any LMF-based positioning method known in the art, and provide the mobile object location 228 to the service provider 204.

[0063] Alternatively, in some examples, the LMF 208 periodically obtains 330 the position of the mobile object 212, stores it, and provides the position of the mobile object 212 to the service provider 204 upon request 224, i.e., the DAC 206 subscribes to the mobile object position for periodic updates on position changes. Such an implementation can enable the DAC 206 to provide fast access to the spatial anchor position without relying on real-time location lookup. This approach can be used in scenarios where real-time location information is not important or may not be feasible. In addition, the DAC ensures the accuracy and reliability of the data by regularly updating the spatial anchor position in its database, providing users with the latest and most relevant information.

[0064] The option of achieving fast access to spatial anchor locations without relying on real-time location lookups can be achieved by preloading / caching spatial anchor data in the DAC 206. The DAC periodically updates its database with the latest spatial anchor information. These updates can be scheduled at specific intervals, or based on certain event triggers, such as environmental changes or service information associated with the spatial anchor.

[0065] In one example, the location information received from the mobile object 212 may be provided as latitude and longitude values ​​that will be geospatial transformed. This process converts the data into precise three-dimensional coordinates (X, Y, Z) to accurately represent the position and orientation of the mobile object within the spatial anchor.

[0066] The specific method used to obtain the location information may vary, for example, based on the device capabilities of the mobile object 212, the application requirements for the service, and / or the accuracy level required for a particular use case. The mobile object 212 sends the location information to the access and mobility management function 210 (AMF) via control plane signaling, and the AMF 210 may relay the information to the LMF 208. The LMF 208 may then process the location information and use it for various purposes, such as spatial anchor management, AR communication, or asset tracking, depending on the application functionality.

[0067] Once the current position 228 of the mobile object 212 has been acquired, the DAC 206 dynamically generates / updates the spatial anchor by combining the location information and the service information. In some examples, the core network / DAC 206 can generate the spatial anchor using sensor data, AI, machine learning, and / or network data analysis function analysis (e.g., 5G NWDAF).

[0068] By combining location information and service information, DAC 206 can effectively associate the provided services with the corresponding physical locations, thereby facilitating seamless access to augmented reality (AR) content and services. In some examples, DAC 206 can add privacy filters to spatial anchors to limit the visibility of certain spatial anchors to specific users and / or user groups. This can enhance data privacy and better control who can access service information. In other words, spatial anchors can be selectively shared based on user permissions, operator policies, and / or other predefined criteria. This ensures that only authorized users and / or designated groups have access to certain AR content or services, thereby protecting sensitive or restricted information.

[0069] The DAC 206 supplies accurate spatial anchors with comprehensive service information, such as optional filters (such as 3D models and car pictures). Privacy filters are provided to limit access to specific users or groups, thereby enhancing data privacy. When the DAC 206 publishes 234 the spatial anchor to the service provider 204, these settings will be sent as configuration data within the spatial anchor metadata, allowing the service provider 204 to implement and share 236 the spatial anchor with the user 202.

[0070] Once one or more spatial anchors used in the service are published 236, the spatial anchors are utilized by the user UE 202 to provide the service to the user. For example, the user 202 is guided by the spatial anchor to the rental car they have rented.

[0071] As another example of the importance of dynamic spatial anchors in a real-world context, consider the use of spatial anchors when providing services in a cheese shop. In order for this concept to flourish in real-world applications, it is useful to keep the spatial anchors dynamic rather than static. This flexibility allows the store owner to freely rearrange the cheese slices (symbolizing brand logos and / or packaging) at the physical store location while retaining the association with the corresponding service information. To achieve this, the store owner captures an image of each slice of cheese (e.g., packaging and / or brand logo), creating a unique "filter" linked to the corresponding spatial anchor. All spatial anchors representing cheese slices are associated with the 3D space of the store as their location.

[0072] When a user / consumer enters the store, they are granted virtual access to observe all identified cheese slices, precisely located in the store based on the computer vision capabilities of their User Equipment (UE). When in the application used by the store, the UE may actively scan various picture filters. This allows for seamless tracking if any slice of cheese moves over time. Only spatial anchors from that specific store owner are visible in the store, ensuring a personalized and relevant consumer experience.

[0073] This example highlights the important role of dynamic spatial anchors in effectively associating location and service information. Through computer vision technology, consumers can virtually explore and interact with content, creating a truly immersive and engaging experience.

[0074] Figure 3 An example of a signaling diagram of a method for providing services based on mobile spatial anchors in the presence of restricted areas is shown. The call flow is described for a practical use case of a user remotely managing one or more devices, for example, a robot owner remotely managing a robot via a digital twin representation in a factory-owned metaverse service. However, it will be understood that other use cases are possible.

[0075] The service provider 304 creates and stores 316 the spatial anchor in the DAC 306, and securely updates or creates service information (such as for Figure 2 It acquires and shares spatial anchors with the user as needed, such as for Figure 2 In some examples, the authenticity of the service information for the spatial anchor can be ensured by limiting the authority to modify the service information of the spatial anchor to only the asset owner (e.g., the service provider 304, a subordinate organization of the service provider, or some other third party) by implementing role-based access control (RBAC) issued by the DAC 306. The DAC 306 can receive real-time updates from the service provider 304 or other systems managed by the owner to ensure that it has the latest and most accurate service information.

[0076] Once a spatial anchor is created, the object / device 312 associated with the spatial anchor may periodically provide location updates 332 (e.g., regarding Figure 2 described above).

[0077] After creating the spatial anchor, the user can remotely manage one or more devices via the user UE 302 and request 318 the spatial anchor from the service provider 304 to effectively manage and interact with the one or more devices 312. An example of such a request would be in conjunction with Figure 2 In response, the service provider 304 initiates a spatial anchor acquisition request 320 to the DAC 306 to obtain the required spatial anchor, such as in conjunction with Figure 2 Upon receiving the request 320 from the service provider 304, the DAC 306 requests 322 the current location of the device 312 from the LMF 308, and the LMF 308 returns 322 the current object location in response. An example of such location acquisition will be described in conjunction with Figure 2 is described in more detail.

[0078] DAC monitors 326 the current location of device 312 relative to the location of one or more restricted areas. Operator 314 provides the location of restricted areas to DAC 106, which are areas where the presence of the device is restricted or not allowed. DAC 106 then checks the received location 324 of device 312 to determine whether it is located in these restricted areas.

[0079] If the device 312 is found to be located within a restricted region, the DAC 106 normally generates 328 a spatial anchor with service information, i.e., as described with respect to Figure 2 described.

[0080] If the device 312 is found to be located within a restricted area, the DAC 106 generates 328 a spatial anchor with service information, including a warning message. The warning message indicates that the device 312 is currently located within a restricted area. The warning may trigger appropriate actions, such as notifying the user, ceasing operation, or issuing a warning 330 to relevant authorities or stakeholders. This mechanism helps ensure compliance with regulations, safety measures, and data privacy requirements for sensitive or restricted areas.

[0081] In some examples, due to safety concerns, the DAC 106 will avoid providing spatial anchors to the user, especially when encountering false spatial anchors.

[0082] To detect false spatial anchors, DAC 106 may employ data consistency checking and validation methods, such as cross-referencing the location data with reliable historical values ​​and sources maintained by the operator. If discrepancies occur, DAC 106 may retain the spatial anchor to prevent the dissemination of misleading or inaccurate information.

[0083] In addition, DAC 106 can ensure the authenticity of service information associated with spatial anchors. By carefully checking service-related elements such as URIs, endpoint details, and 3D models, DAC 106 can prevent spatial anchors containing false or malicious content from being shared with users. By implementing these security measures, DAC 106 safeguards the integrity and reliability of the spatial anchor system, thereby facilitating trusted and accurate location-based services within the 5G network environment.

[0084] In some implementations, the DAC 106 can send warning messages and error logs to the 5G network's operations and maintenance 314 (O&M) system. The O&M system 314 can use this valuable information to enhance its capabilities, enabling proactive measures to prevent the creation of false spatial anchors in the future.

[0085] The DAC 106 transmits 330 the spatial anchor with service information to the user UE 302 via the service provider 304. If the device 312 associated with the spatial anchor is located in a restricted region, the service information includes a warning message indicating the "restricted region" to the user. Alternatively, for example, if the spatial anchor is false, the response 330 from the DAC 106 may not include the spatial anchor.

[0086] The spatial anchor information enables the user to make an informed decision, thereby enabling actions to redirect the device or cease its operation as needed.

[0087] Figure 4 A flowchart of an example method for dynamically creating and / or managing mobile space anchors is shown. The method may be performed by an apparatus / system including components for performing each operation of the method. For example, the method may be performed by a device / system including components for performing each operation of the method. Figure 6 For convenience, the method is described as being performed by a system, for example, a system forming part of a core network.

[0088] At operation 402, the system receives a request from a service provider to initiate a spatial anchor associated with a mobile object. In some examples, the mobile object is a networked device, such as a user device. In some examples, the mobile object is a non-networked object, such as a product.

[0089] The request may include service information to be associated with the mobile object, such as one or more attributes of the mobile object; one or more attributes of the service associated with the mobile object; one or more attributes of the service provider (e.g., an identifier, one or more locations, etc.); a list of permissions for accessing the spatial anchor, etc.

[0090] At operation 404, the system generates a spatial anchor associated with the mobile object based on the received request. Generating the spatial anchor associated with the mobile object may include generating a digital asset representing the spatial anchor. The digital asset may be stored in a digital asset container (DAC).

[0091] The digital asset includes one or more spatial anchor attributes, such as a spatial anchor ID that uniquely identifies the object (e.g., a numeric or alphanumeric identifier), service information identifying one or more services associated with the spatial anchor (e.g., service type, service description, URL or endpoint for accessing the service, media content information (such as AR media), or configuration data required to utilize the service), and / or a spatial location (e.g., coordinates in a 3D reference frame, such as longitude, latitude, and altitude, or Cartesian coordinates relative to some reference point / origin).

[0092] In some implementations, one or more spatial anchor attributes include one or more timestamps, the one or more timestamps indicating: when the spatial anchor was created; when the spatial anchor attributes were updated; and / or when the spatial anchor position was updated. In some implementations, one or more spatial anchor attributes include metadata, the metadata including one or more of the following: creator information; version control details; privacy settings; and / or any other relevant attributes that provide further context or management capabilities for the spatial anchor.

[0093] In some implementations, the system receives an update request for a spatial anchor from a service provider. The update request may be based on the identity of the user requesting the service, for example, the update request may assign the spatial anchor to the user and / or indicate that the user is authorized to use the spatial anchor. The update request may identify the user using a unique ID of a UE associated with the user. For example, in the case of a car rental, the update request may include an identifier for a user assigned to a particular rental car. Additionally or alternatively, the update request may include an updated value for one or more attributes of the spatial anchor, a request to add one or more further attributes to the spatial anchor, and / or a request to remove one or more attributes from the spatial anchor.

[0094] In response to the update request, the system updates one or more of the one or more properties of the spatial anchor based on the update request, that is, the properties of the digital asset are updated and stored in the DAC.

[0095] At operation 406, the system receives a request for acquisition of a spatial anchor associated with a mobile object from a service provider or a user equipment. In an example where the request is received from a service provider, the request may have been triggered by a request for service issued by the UE to the service provider. In some examples, the request for acquisition of a spatial anchor associated with a mobile object is or is combined with an update request for a spatial anchor, for example, the update request itself also serves as a request for acquisition of a spatial anchor associated with a mobile object.

[0096] At operation 408, the system obtains the position of the mobile object. The system may obtain the position of the mobile object in response to a request for a spatial anchor. Alternatively, the system may periodically obtain the position of the mobile object.

[0097] In some implementations, the system uses a network location management function to obtain and / or monitor the location of a mobile object. The location management function can obtain the location of a mobile object in response to a request for the location of the object from the DAC, i.e., obtain the current location of the object using any positioning technology known in the art. Alternatively, the LMF can receive location updates for the object periodically, or when one or more threshold conditions are met (such as an object that is or has been moving) and provide the latest location to the DAC upon request.

[0098] In some implementations, one or more spatial anchor attributes include the location of one or more restricted areas, i.e., areas in which the mobile object is not allowed to be located. In such an implementation, the system compares the mobile object location with the location of one or more restricted areas to determine whether the mobile object is located within the restricted area. In response to determining that the mobile object is located within the restricted area, the system updates the spatial anchor with a warning indication (e.g., a service information used as a warning message). This warning message indicates that the device is currently present in the restricted area and may trigger one or more additional actions, such as notifying the user, stopping the operation of the mobile object / user UE, and / or issuing a warning to relevant agencies or stakeholders.

[0099] At operation 410, the system updates the spatial anchor using the acquired position, ie, dynamically generates the latest spatial anchor. If the retrieved position is within the restricted area, the system updates the service information to include a warning.

[0100] At operation 412, the system provides the updated spatial anchor to the service provider or user device. The service provider and / or user device uses the spatial anchor (and, in some examples, one or more additional spatial anchors) to provide services to the user, such as augmented reality services.

[0101] Figure 5A flowchart of an example method for providing services based on a mobile space anchor is shown. The method may be performed by an apparatus / system including components for performing each operation of the method. For example, the method may be performed by Figure 6 For convenience, the method is described as being performed by a system (eg, a system of a service provider).

[0102] At operation 502, the system requests the initiation of a spatial anchor associated with a mobile object from a network. The request may include service information to be associated with the mobile object, for example, one or more attributes of the mobile object; one or more attributes of the service associated with the mobile object; one or more attributes of the service provider (e.g., an identifier, one or more locations, etc.); a permission list for accessing the spatial anchor, etc.

[0103] At operation 504, the system receives a request from a user device for a service that utilizes an object as a spatial anchor. The request may originate from an application running on a user device associated with a service provider. The application may be an augmented reality application.

[0104] At operation 506, the system requests the network to update one or more attributes of the spatial anchor based on the received request for service. The update request may, for example, include a request to associate the requesting user device with the spatial anchor.

[0105] The update request may also serve as a request for a spatial anchor from the network (eg, a DAC from the core network). Alternatively, the update request may be accompanied by an explicit request for a spatial anchor.

[0106] At operation 508, the system receives an updated spatial anchor from the network. The spatial anchor may be updated with the current location of the mobile object. In some examples, if the object is determined by the network to be in a restricted area, the service information of the updated spatial anchor may include a warning that the object is in a restricted area.

[0107] At operation 510, the system causes transmission of the updated spatial anchor to the user device. The user device uses the spatial anchor (and, in some examples, one or more additional spatial anchors) to provide services to the user, such as augmented reality services.

[0108] Figure 6An apparatus / system according to some example embodiments is shown, which may form at least a part of a user equipment or a network node. The apparatus may be configured to perform the operations described herein, for example, the operations described with reference to any disclosed process. The apparatus comprises at least one processor 600 and at least one memory 601 directly or closely connected to the processor. The memory 601 comprises at least one random access memory (RAM) 601A and at least one read-only memory (ROM) 601B. Computer program code (software) 605 is stored in the ROM 601B. The apparatus may be connected to a transmitter (TX) and a receiver (RX). The apparatus may optionally be connected to a user interface (UI) for instructing the apparatus and / or for outputting data. At least one processor 500, at least one memory 601 and computer program code 605 are arranged to cause the apparatus to at least perform at least the method or a part of the method according to any previous process, for example as described with respect to Figure 2 and / or the signaling diagram of 3 and / or Figure 4 And / or the flowchart of 5 and its related features disclosed.

[0109] Figure 7 A non-transitory medium 700 according to some embodiments is shown. The non-transitory medium 700 is a computer readable storage medium. It may be, for example, a CD, a DVD, a USB stick, a Blu-ray disc, etc. The non-transitory medium 700 stores computer program code causing the apparatus to perform methods of any previous process, for example as disclosed with respect to the flow charts and their related features.

[0110] The names of network elements, protocols, and methods are based on current standards. In other versions or other technologies, the names of these network elements and / or protocols and / or methods may be different, as long as they provide corresponding functions. For example, embodiments may be deployed in 2G / 3G / 4G / 5G networks and other generations of 3GPP, and may also be deployed in non-3GPP radio networks, such as Wi-Fi.

[0111] Memory can be either volatile or non-volatile. For example, it can be RAM, SRAM, flash memory, FPGA block ram, DCD, CD, USB stick, and Blu-ray disc.

[0112] Unless otherwise specified or the context clearly dictates otherwise, stating that two entities are different means that they perform different functions. This does not necessarily mean that they are based on different hardware. That is, each entity described in this specification may be based on different hardware, or some or all of the entities may be based on the same hardware. This does not necessarily mean that they are based on different software. That is, each entity described in this specification may be based on different software, or some or all of the entities may be based on the same software. Each entity described in this specification may be embodied in the cloud.

[0113] The implementation of any of the above blocks, devices, systems, techniques or methods includes (but is not limited to) hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof. Some embodiments may be implemented in the cloud.

[0114] It should be understood that the above is what is presently considered to be the preferred embodiment. However, it should be noted that the description of the preferred embodiment is given by way of example only and that various modifications may be made without departing from the scope defined in the appended claims.

Claims

1. A device comprising: means for receiving a request from a service provider to initiate a spatial anchor associated with a mobile object; means for generating the spatial anchor associated with the mobile object based on the received request; means for receiving a request from said service provider or user equipment for acquisition of said spatial anchor associated with a mobile object; means for obtaining the position of the mobile object; means for updating the spatial anchor using the acquired position of the mobile object; as well as Means for providing the updated spatial anchor to the service provider or the user equipment.

2. The apparatus of claim 1, wherein the means for generating the spatial anchor associated with the moving object comprises: means for generating a digital asset representing the spatial anchor, the digital asset comprising one or more spatial anchor attributes; as well as Means for storing the digital asset in a digital asset container.

3. The apparatus of claim 2, wherein the one or more spatial anchor attributes include: A spatial anchor ID uniquely identifying the object; service information identifying one or more services associated with the spatial anchor; and spatial location.

4. The apparatus of claim 3, wherein the service information comprises one or more of: a service description; a service URL; media content information; and / or configuration data for the service.

5. The device according to any one of claims 2 to 4, further comprising: means for receiving an update request for the spatial anchor from the service provider; as well as Means for updating one or more of the one or more properties of the spatial anchor based on the update request.

6. The apparatus of claim 5, wherein the update request for the spatial anchor comprises: An identifier of the user equipment from which the request originated.

7. The apparatus according to any one of claims 2 to 6, wherein the one or more spatial anchor attributes include one or more timestamps, and the one or more timestamps indicate: a spatial anchor creation time; a spatial anchor attribute update time; and / or a spatial anchor position update time.

8. The apparatus of any one of claims 2 to 7, wherein the one or more spatial anchor attributes include the location of one or more restricted areas, and wherein the apparatus further comprises: means for determining whether the mobile object is within a restricted area based on the position of the mobile object; as well as Means for updating the spatial anchor with a warning indication in response to determining that the mobile object is within a restricted area.

9. The device according to claim 8, wherein the device further comprises: Means for triggering one or more actions based on the warning indication.

10. The apparatus according to any preceding claim, further comprising: Means for limiting and / or preventing access to the spatial anchor based at least in part on an identity of the service provider or the user device.

11. An apparatus comprising: Means for requesting an initiation of a spatial anchor associated with a mobile object from a network; means for receiving, from a user device, a request for a service utilizing the object as a spatial anchor; means for requesting the network to update one or more properties of the spatial anchor based on the request for the service; means for receiving updated spatial anchors from said network; as well as Means for causing transmission of the updated spatial anchor to the user equipment.

12. The apparatus of claim 11, wherein the updated spatial anchor comprises: The current position of the mobile object.

13. The apparatus according to any one of claims 11 or 12, wherein the updated spatial anchor comprises a warning message indicating that the current position of the mobile object is within a restricted area.

14. A computer-implemented method comprising: receiving a request from a service provider to initiate a spatial anchor associated with a mobile object; generating the spatial anchor associated with the mobile object based on the received request; receiving a request for acquisition of the spatial anchor associated with the mobile object from the service provider or user equipment; Obtaining the position of the mobile object; updating the spatial anchor using the acquired position of the mobile object; as well as The updated spatial anchor is provided to the service provider or the user equipment.

15. A computer-implemented method comprising: Initiation of requesting a spatial anchor associated with a mobile object from a network; receiving, from a user device, a request for a service utilizing the object; requesting the network to update one or more attributes of the spatial anchor based on the request for the service; receiving the spatial anchor from the network; as well as causing transmission of the spatial anchor to the user equipment.

Images