Spatial anchor management
By associating spatial anchors with time information for validity, the management of transient anchors ensures accurate and timely presentation, addressing the issue of invalid information in metaverse applications and improving user experience.
Patent Information
- Application Number
- PCT/EP2026/063088
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
Current spatial anchor management systems do not specify valid time durations for spatial anchors, leading to invalid information being presented to users, which degrades the user experience in metaverse applications.
Spatial anchors are created with time information associated with their validity, enabling management of transient anchors through time-based creation, retrieval, and presentation, ensuring anchors are only presented when valid.
This approach prevents the presentation of inactive or expired spatial anchors, thereby enhancing user experience in metaverse applications by providing accurate and timely information.
Smart Images

Figure IMGF000029_0001_TABLE 
Figure IMGF000030_0001_TABLE 
Figure IMGF000031_0001_TABLE
Abstract
Description
SPATIAL ANCHOR MANAGEMENTFIELD
[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for spatial anchor management.BACKGROUND
[0002] Nowadays metaverse is gaining a lot of attention. The metaverse is an immersive digital world which integrates cutting-edge technologies such as augmented reality (AR), virtual reality (VR), artificial intelligence (Al). One of the important features of the metaverse applications is providing spatial anchors. The spatial anchor is an association between space and service information.SUMMARY
[0003] In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: transmit, to a network entity, a spatial anchor request for at least a spatial anchor; receive, from the network entity, a spatial anchor response indicating the spatial anchor, the spatial anchor response comprising time information associated with validity of the spatial anchor; and enable presentation of the spatial anchor based on the time information.
[0004] In a second aspect of the present disclosure, there is provided a network entity. The network entity comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network entity at least to: receive, from a first apparatus, a spatial anchor request for at least a spatial anchor; determine time information associated with validity of the spatial anchor based on a profile of the spatial anchor; and transmit a spatial anchor response indicating the spatial anchor to the first apparatus, the spatial anchor response comprising the time information.
[0005] In a third aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: transmit, to a network entity, a creation request for a spatial anchor, the creation request comprising time information associated with validity of the spatial anchor; and receive, from the network entity, a creation response indicating successful creation of the spatial anchor.
[0006] In a fourth aspect of the present disclosure, there is provided a method. The method comprises: transmitting, to a network entity, a spatial anchor request for at least a spatial anchor; receiving, from the network entity, a spatial anchor response indicating the spatial anchor, the spatial anchor response comprising time information associated with validity of the spatial anchor; and enabling presentation of the spatial anchor based on the time information.
[0007] In a fifth aspect of the present disclosure, there is provided a method. The method comprises: receiving, from a first apparatus, a spatial anchor request for at least a spatial anchor; determining time information associated with validity of the spatial anchor based on a profile of the spatial anchor; and transmitting a spatial anchor response indicating the spatial anchor to the first apparatus, the spatial anchor response comprising the time information.
[0008] In a sixth aspect of the present disclosure, there is provided a method. The method comprises: transmitting, to a network entity, a creation request for a spatial anchor, the creation request comprising time information associated with validity of the spatial anchor; and receiving, from the network entity, a creation response indicating successful creation of the spatial anchor.
[0009] In a seventh aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for transmitting, to a network entity, a spatial anchor request for at least a spatial anchor; means for receiving, from the network entity, a spatial anchor response indicating the spatial anchor, the spatial anchor response comprising time information associated with validity of the spatial anchor; and means for enabling presentation of the spatial anchor based on the time information.
[0010] In an eighth aspect of the present disclosure, there is provided a network entity. The network entity comprises means for receiving, from a first apparatus, a spatial anchor request for at least a spatial anchor; means for determining time information associated with validity of the spatial anchor based on a profile of the spatial anchor; and means for transmitting a spatial anchor response indicating the spatial anchor to the first apparatus, the spatial anchor response comprising the time information.
[0011] In a ninth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for transmitting, to a network entity, a creation request for a spatial anchor, the creation request comprising time information associated with validity of the spatial anchor; and means for receiving, from the network entity, a creation response indicating successful creation of the spatial anchor.
[0012] In a tenth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.
[0013] In an eleventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fifth aspect.
[0014] In a twelfth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the sixth aspect.
[0015] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0017] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0018] FIG. 2 illustrates an example scenario in which example embodiments of the present disclosure can be implemented;
[0019] FIG. 3 illustrates a signaling flow of an example procedure of creation and retrieval of transient spatial anchors in accordance with some example embodiments of the present disclosure;
[0020] FIG. 4 illustrates a signaling flow of an example procedure of maintenance of transient spatial anchors in accordance with some example embodiments of the present disclosure;
[0021] FIG. 5 illustrates a signaling flow of an example procedure of creating the spatial anchor in accordance with some example embodiments of the present disclosure;
[0022] FIG. 6 illustrates a signaling flow of an example procedure of discovering the spatial anchor in accordance with some example embodiments of the present disclosure;
[0023] FIG. 7 illustrates a signaling flow of an example procedure of retrieving the spatial anchor in accordance with some example embodiments of the present disclosure;
[0024] FIG. 8 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;
[0025] FIG. 9 illustrates a flowchart of a method implemented at a network entity in accordance with some example embodiments of the present disclosure;
[0026] FIG. 10 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;
[0027] FIG. 11 illustrates a flowchart of a method implemented at a network entity in accordance with some example embodiments of the present disclosure;
[0028] FIG. 12 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;
[0029] FIG. 13 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;
[0030] FIG. 14 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and
[0031] FIG. 15 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
[0032] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0033] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0034] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0035] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0036] It shall be understood that although the terms “first,” “second,”..., etc. in frontof noun(s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun(s). For example, a first element could be termed a secondelement, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0037] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0038] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0039] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0040] As used in this application, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in analog, digital and / or quantum circuitry) and(b) combinations of hardware ci rcuit(s) and software, such as (as applicable):(i) a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and(ii) any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device, or server, to perform various functions) and(c) any or all portions of hardware circuit(s), such as a microprocessor(s), processor(s) and / or quantum processor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0041] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0042] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-loT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G), 5.5G, the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0043] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
[0044] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehiclemounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node). In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.
[0045] As used herein, the term “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other combination of the time, frequency, space and / or code domain resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0046] FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented. In the communication environment 100, a plurality of communication devices, including a first apparatus 110, and a second apparatus 130 can communicate with a network entity 120 respectively. The first apparatus 110 may include or be included in any suitable device or entity. In an example of FIG. 1, the first apparatus 110 may be one or more of: a UE deployed with a spatial anchor (SAn) client, a UEdeployed with any application client, a UE deployed with any application enabler client, a vertical application layer (VAL) server, an application server (AS) or a network function (NF). Similarly, the second apparatus 130 may include or be included in any suitable device or entity. For example, the second apparatus 130 may be one or more of a UE deployed with an SAn client, a UE deployed with any application client, a UE deployed with any application enabler client, a VAL server, an AS or an NF. The network entity 120 may implement or include a spatial anchor server or an AS, which may provide services related to spatial anchors. As an example, the network entity 120 may be implemented by a service enabler architecture layer (SEAL) server.
[0047] The network entity 120 may be implemented at any suitable part, level or layer of the network. For example, the network entity 120 may be implemented at a core network (CN) entity in the core network. Alternatively, the network entity 120 may be implemented at an application layer, etc.
[0048] It is to be understood that the number of devices and their connections shown in FIG.1 are only for the purpose of illustration without suggesting any limitation. The communication environment 100 may include any suitable number of devices configured to implementing example embodiments of the present disclosure.
[0049] Communications in the communication environment 100 may be implemented according to any proper communication protocol(s), comprising, but not limited to, cellular communication protocols, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0050] In some example embodiments, the first apparatus 110 may act as a consumer of a spatial anchor, which is also referred to as a spatial anchor consumer. The second apparatus 120 may act as a producer of a spatial anchor, which is also referred to as a spatial anchor producer. The network entity 120 may be a spatial anchor server. FIG. 2 illustrates such an example scenario 200, which can be considered as an example of the environment 100.
[0051] As shown in FIG.2, a spatial anchor consumer 210 and a spatial anchor producer 230 may communicate with a spatial anchor server 220. In some example embodiments, the spatialanchor consumer 210 and the spatial anchor producer 230 may be or be included in a UE, respectively. In such example embodiments, the spatial anchor consumer 210 and the spatial anchor producer 230 may include a spatial anchor client, respectively. For example, the spatial anchor client in the spatial anchor consumer 210 may interact with the spatial anchors in the metaverse applications in order to retrieve the service information associated with the spatial anchor for the spatial anchor consumer 210. The spatial anchor client in the spatial anchor consumer 210 may communicate with the spatial anchor server 220 to discover or retrieve a spatial anchor.
[0052] For example, the spatial anchor client in the spatial anchor producer 230 may communicate with the spatial anchor server 220 to create or update a spatial anchor. Alternatively, the spatial anchor consumer 210 and the spatial anchor producer 230 may be a VAL server which supports the spatial anchor.
[0053] As briefly mentioned above, metaverse applications are rapidly emerging as an essential technology in communication recently. The metaverse applications have already gained a lot of attention across various fields due to the potential in providing an immersive virtual space for users of the metaverse application. The term “metaverse” has been employed in diverse contexts to encapsulate the broader potential and implications of extended reality such as augmented reality (AR), virtual reality (VR) and mixed reality (MR).
[0054] As one of the key features of metaverse applications, the spatial anchor serves as an association relationship between a certain location in the real world or the virtual space and service information. The spatial anchor may be produced by a spatial anchor producer. The producer of a spatial anchor may determine the service information to be shared with the user via the spatial anchor and the location of the spatial anchor. The producer may also determine the target to be shared with the spatial anchor, for example, a user requesting the spatial anchor. Additionally, the producer may also determine other constraints and additional information especially including resources associated with the spatial anchor, e.g., AR media, mobile metaverse service to access, etc.
[0055] For the user of the metaverse application, spatial anchors offer a seamless and intuitive experience. The consumer of the spatial anchor may be able to recognize the relationship between spatial anchors and the corresponding locations of the spatial anchors and leverage them to retrieve the information associated with the spatial anchors.
[0056] Currently, the spatial anchors are widely used at different locations of various scenarios to provide specific service information. For example, a spatial anchor may be added at and associated with an entry or exit way of a building such that a user may find the entry orexit more efficiently with the assistance of the spatial anchor.
[0057] An example of using spatial anchors may relate to a scenario of presenting information about different products in a shop. In such scenarios, the user of the metaverse application may browse different products on a shelf or on a counter in the shop. The shop may be located in the real world and associated with a metaverse application that the user may interact with the shop therein with assistance of the information provided by the metaverse application. Alternatively, or additionally, the user of the metaverse application may interact with shop in the virtual space. When the user wants to check information related to a certain product, the user may be able to obtain the information associated with the spatial anchor.
[0058] For example, when the user wants to buy a product, the user may want to check the price or detailed information of the product (e.g., components of the product, the place of origin of the product, etc.). Under such conditions, the user may interact with the metaverse by performing an interaction at the spatial anchor (e.g., by focusing on the product, touching the area adjacent to the product, or by other implicit / explicit indication). In response to the interaction of the user at the spatial anchor, the metaverse application may provide the service information corresponding to the spatial anchor, for example, by a pop-up window or a notification indicating the service information.
[0059] Another example of using spatial anchors may relate to a scenario of a live concert. The metaverse application may provide services to the users to enable the users to join a live concert. The live concert may be an online digital concert in a virtual space. Alternatively, the live concert may be a virtual space presenting a streaming of a concert in the real world. The users may join the live concert with their avatars in the virtual space in order to have an immersive experience. In such scenarios, the spatial anchors may be provided to the users to enable the user to have additional information they may expect in the live concert. For example, the spatial anchors may be provided for presenting information about live chats and comments from other users in the live concert. Additionally, the spatial anchors may be provided for presenting subtitles and lyrics of the live concert.
[0060] As described above with respect to the example scenarios of using spatial anchors, the organizer of the live concert or the owner of the shop, or generally the organizer of an event in the virtual space of the metaverse, may create a plurality of spatial anchors. Once a spatial anchor is created, it will remain available until it is explicitly removed by the organizer of an authorized requestor (e.g. an authorized user). However, this will cause limitations on using spatial anchors in certain cases.
[0061]
[0062] For example, in a scenario related to a live concert, the organizer may create spatial anchors related to the event in advance to the live concert beginning. Therefore, the spatial anchors may not be valid till the event starts. Additionally, the spatial anchors related to the liver concert may be created by the organizer for a certain duration of time (e.g., time till the end of the live concert) to support the experience of the metaverse application. However, in some cases the spatial anchors may not be deleted by the organizer by chance. For example, the organizer may forget to delete the spatial anchors or the spatial anchors may not be deleted due to some mistakes. In such cases, the spatial anchors will remain present in the spatial anchor server unnecessarily and may provide invalid information to the spatial anchor consumer in future use of the metaverse application. Such invalid information may cause user experience degradation in the metaverse application.
[0063] For another example, in some cases, the requirement of specific spatial anchors may keep changing over time. For example, if the live concert is extended for a time period than it is initially scheduled, the spatial anchors related to the live concert may be required to extend at least the time period. For a further example, in some cases a spatial anchor may be activated or be valid according to a specific time pattern. For example, the spatial anchor may repeat over a period of time.
[0064] Furthermore, currently if a user discovers a spatial anchor, the application of the user will present the spatial anchor to the user even if the validity of the spatial anchor is expired. Such that the user may get invalid information which may cause degradation to the experience.
[0065] In general, currently the spatial anchors are not specified with a valid time duration to solve problems such as the examples described above. Therefore, there is a need for a method to manage (for example, create, update, discover, retrieve, remove, etc.) transient or time bound spatial anchors.
[0066] In accordance with some example embodiments of the present disclosure, there is provided a method for management of transient spatial anchors. In the present disclosure, a spatial anchor is created with time information associated with validity of the spatial anchor. For example, a spatial anchor producer of the spatial anchor may indicate the time information in a request to a spatial anchor server for creating the spatial anchor. If the spatial anchor is retrieved or discovered by a spatial anchor consumer, the spatial anchor server provides the time information to the spatial anchor consumer. Then, the spatial anchor consumer enables presentation of the spatial anchor based on the time information.
[0067] Accordingly, the spatial anchor may be managed based on the time information associated with its validity. An inactive or invalid spatial anchor would not be presented to auser, thus avoiding degradation of user experience. Therefore, the management of spatial anchors can provide the user of the metaverse application with a better immersive experience.
[0068] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0069] FIG. 3 illustrates a signaling flow 300 of an example procedure of creation and retrieval of transient spatial anchors in accordance with some example embodiments of the present disclosure. For the purposes of discussion without any limitation, FIG. 3 will be described with reference to FIG. 2 by using the spatial anchor consumer 210, the spatial anchor server 220 and the spatial anchor producer 230 in FIG. 2.
[0070] In the signaling flow 300, the spatial anchor producer 230 transmits (304) a creation request for a spatial anchor to the spatial anchor server 220. The creation request includes time information associated with validity of the spatial anchor. As used herein, the term “time information” may refer to any suitable information which is associated with the validity of the spatial anchor. The time information may be referred to as any other suitable term, for example, schedule information, validity information, etc. In some example embodiments, the time information may include a time period (which is also referred to as a valid time period) within which the spatial anchor is valid. For example, the time information may indicate a time period in terms of a time duration during which the spatial anchor is valid or applicable. The time information may include a start time and an expiry time, or may include a start time and a time length.
[0071] As an alternative or in addition, the time information may include a validity pattern indicating at least one activation time period for the spatial anchor and at least one deactivation time period for the spatial anchor. For example, the time information may include the validity pattern to indicate when the spatial anchor is activated and / or when the spatial anchor is deactivated. As an example without any limitation, the validity pattern may indicate that the spatial anchor is activated e.g. 9 - 11 am every day for a week or 4 - 8 pm on alternate days for a week.
[0072] In some example embodiments, the time information may be provided by a user associated with the spatial anchor producer 230. Alternatively, or additionally, the time information may be provided by an application client associated with the spatial anchor producer 230. For example, the user or the application client may provide the value of the time period to the SAn client or the VAL serve.
[0073] Alternatively, in some example embodiments, the spatial anchor producer 230 may determine (302) the time information based on information about one or more spatial anchorscreated historically. For example, if the user or application client has not provided the time period, then the SAn client (on UE) may determine the time period by analyzing the information about previously created spatial anchors (such as application, access control rules, service area, etc.). The SAn client may match the information with the new spatial anchor to be created and determines the validity time period and / or pattern based on the matching.
[0074] Correspondingly, the spatial anchor server 220 receives (306) the creation request from the spatial anchor producer 230. In response to receiving the creation request, the spatial anchor server 220 may create (308) the profile of the spatial anchor including the time information, for example, the time period or the validity pattern. For example, upon receiving the creation request, the spatial anchor server 220 may validate if the requestor is authorized for the request. If the requestor is authorized, the spatial anchor server 220 may create the spatial anchor, assign a spatial anchor identifier to the newly created spatial anchor. The spatial anchor server 220 may store the time information in the profile of the spatial anchor.
[0075] Additionally, in some example embodiments, the spatial anchor server 220 may start a timer upon starting of the valid time period. The timer may have a time length corresponding to the valid time period indicated in the time information. The spatial anchor server 220 may remove the profile of the spatial anchor upon expiry of the timer.
[0076] Continuing with the flow 300, in response to successful creation of the spatial anchor, the spatial anchor server 220 may transmit (312) a creation response to the spatial anchor producer 230. Correspondingly, the spatial anchor producer 230 may receive (314) the creation response from the spatial anchor server 220. The response may include an indication of success and a spatial anchor identifier of the newly created spatial anchor. An example procedure of the creation of the spatial anchor is described herein after with reference to FIG. 5.
[0077] Upon the creation of the spatial anchor, the spatial anchor server may store the time information about the spatial anchor in association with the spatial anchor. The profile of the spatial anchor may include the time information. In other words, the time period and / or the validity pattern may be stored in the profile of the spatial anchor. The spatial anchor is now created and available for discovery or retrieval by the spatial anchor consumer 210.
[0078] The spatial anchor consumer 210 transmits (316) a spatial anchor request for at least a spatial anchor to the spatial anchor server 220. In some example embodiments, the spatial anchor request may be used for one or more spatial anchors. For example, the spatial anchor request may request to discover spatial anchors within an area, or retrieve a spatial anchor.
[0079] Correspondingly, the spatial anchor server 220 receives (318) the spatial anchor request from the spatial anchor consumer 210. In response to receiving the spatial anchorrequest from the spatial anchor consumer 210, the spatial anchor server 220 determines (322) the time information associated with the validity of the spatial anchor. For example, the spatial anchor server 220 may read the time information from respective profiles of the one or more requested spatial anchors. As described above, the time information may include the time period within which the spatial anchor is valid or a validity pattern indicating at least one activation time period for the spatial anchor and at least one deactivation time period for the spatial anchor.
[0080] Then, the spatial anchor server 220 transmits (324) a spatial anchor response to the spatial anchor consumer 210. The spatial anchor response indicates the spatial anchor and includes the time information. In other words, the spatial anchor response may include schedule information or validity information associated with the validity of the spatial anchor.
[0081] In some example embodiments, the spatial anchor request may include a spatial anchor discovery request, and the spatial anchor response may include a spatial anchor discovery response. For each discovered spatial anchor, the spatial anchor response may include the time information for the discovered spatial anchor.
[0082] In some example embodiments, the discovery of one or more spatial anchors may be based on a time indication associated with the spatial anchor discovery request. The spatial anchor server 220 may compare the time information of a spatial anchor with the time indication associated with the spatial anchor discovery request. If the time information matches the time indication, the spatial anchor server 220 may transmit the spatial anchor discovery response to the spatial anchor consumer 210. In other words, the spatial anchor(s) of which the time information matches the time indication may be discovered by the spatial anchor consumer 210.
[0083] In some example embodiments, the time indication may be an explicit indication. For example, the spatial anchor discovery request may include a time requirement for the spatial anchor to be discovered. The time requirement may be associated with the validity of the spatial anchor. For example, the time requirement may indicate a specific time period or a specific validity pattern. The user or the application client may provide or generate the time requirement.
[0084] Alternatively, or additionally, the time indication may be an implicit indication. For example, the time indication may include a reception time of the spatial anchor discovery request by the spatial anchor server 220 or a transmission time of the spatial anchor discovery request by the spatial anchor consumer 210. For example, the spatial anchor server 220 may compare the reception time or transmission time to respective valid time periods of a plurality of spatial anchors. If one or more spatial anchors are valid after a certain time since the reception or transmission time, such one or more spatial anchors are discovered by the spatial anchor consumer 210. An example procedure of the discovery of the spatial anchor is describedherein after with reference to FIG. 6.
[0085] In some example embodiments, the spatial anchor request may include a spatial anchor retrieve request, and the spatial anchor retrieve request may include an identifier of the spatial anchor. Accordingly, the spatial anchor response may include a spatial anchor retrieve response. An example procedure of the discovery of the spatial anchor is described herein after with reference to FIG. 7.
[0086] Continuing with the flow 300, based on the time information received from the spatial anchor server 220, the spatial anchor consumer 210 enables (328) presentation of the spatial anchor based on the time information. For example, if a user triggers presentation of the spatial anchor at a time when the spatial anchor is valid or activated, the spatial anchor may be presented for example by a terminal device. If the user triggers presentation of the spatial anchor at a time when the spatial anchor is invalid or deactivated, the spatial anchor would not be presented. Depending on the content of the spatial anchor, presentation of the spatial anchor may include but not limited to displaying / projecting / rendering visual content, playing audio content, sound notification, etc.
[0087] In some example embodiments, the time information included in the spatial anchor response may indicate a time period within which the spatial anchor is valid. In such cases, the spatial anchor consumer 210 may start a timer upon / after starting of the time period indicated in the time information. The timer may have a time length corresponding to the time period. The spatial anchor consumer 210 may enable the presentation of the spatial anchor until expiry of the timer. I n some example embodiments, after the timer is expired, the spatial anchor consumer 210 may remove the spatial anchor from a set of available spatial anchors, for example, from a list of discovered spatial anchors.
[0088] In some example embodiments, the time information included in the spatial anchor response may indicate a validity pattern indicating at least one activation time period for the spatial anchor and / or at least one deactivation time period for the spatial anchor. In such cases, the spatial anchor consumer 210 may enable the presentation of the spatial anchor within the at least one activation time period and / or disable the presentation of the spatial anchor within the at least one deactivation time period.
[0089] In some example embodiments, the spatial anchor consumer 210 may remove (332) the spatial anchor from a set of discovered spatial anchors based on that the time information indicates the spatial anchor is invalid or expiry of the above mentioned timer.
[0090] For example, if the time information of the discovered or retrieved spatial anchor indicates a validity time period or a validity pattern, the spatial anchor consumer 210 mayprocess the parameters of the spatial anchor and start a corresponding timer. Once the timer expires, the spatial anchor which is expired is removed from the list of discovered spatial anchors and accordingly the user will not be able to have a visual on the expired spatial anchor. In a case that the validity pattern is applicable, the spatial anchor consumer 210 may activate and deactivate the spatial anchor for presentation to the user accordingly.
[0091] Continuing with the flow 300, in some example embodiments, the spatial anchor producer 230 may determine to update the time information of the created spatial anchor. Update to the time information may include for example extension of the valid time period, shortening of the valid time period, or a change of the validity pattern. For example, the end user or application client may provide the update to the spatial anchor client or VAL server. In response to determining an update to the time information, the spatial anchor producer 230 may transmit (334), to the spatial anchor server 220, an update request to update the time information. In other words, the spatial anchor producer 230 may transmit, to the spatial anchor server 220, an update request to update the schedule information or validity information associated with the validity of the spatial anchor.
[0092] Correspondingly, the spatial anchor server 220 may receive (336) the update request from the spatial anchor producer 230. Based on the update request, the spatial anchor server 220 may update (338) the time information in the profile of the spatial anchor.
[0093] Upon the update to the spatial anchor, the spatial anchor server 220 may transmit (342) the update to the time information to the spatial anchor consumer 210. Correspondingly, the spatial anchor consumer 210 may receive (344) the update from the spatial anchor server 220. After receiving the update from the spatial anchor server 220, the spatial anchor consumer 210 may enable the presentation of the spatial anchor based on the updated time information.
[0094] The example procedure for spatial anchor creation, discovery and retrieve is described with respect to FIG. 3. Now reference is made to FIG. 4. FIG. 4 illustrates a signaling flow 400 of an example procedure of maintenance of transient spatial anchors in accordance with some example embodiments of the present disclosure. For the purposes of discussion without any limitation, FIG. 4 will be described with reference to FIG. 2 by using the spatial anchor consumer 210, the spatial anchor server 220 and the spatial anchor producer 230 in FIG. 2.
[0095] The spatial anchor server 220 has created a spatial anchor with time information associated with validity of the spatial anchor, for example as described with the creation procedure described above or below with reference to FIG. 5. The time information may include the valid time period or the validity pattern.
[0096] In the signaling flow 400, the spatial anchor server 220 determines (410) that acondition related to expiry of a spatial anchor is met based on the time information associated with validity of the spatial anchor. For example, based on the schedule information or validity information associated with the validity of the spatial anchor, the spatial anchor server 220 may determine that the condition is met.
[0097] In some example embodiments, the condition may include that a time length before the expiry of the spatial anchor is below a threshold. In other words, the spatial anchor is about to expire. Alternatively, or additionally, in some example embodiments, the condition may include that the spatial anchor is expired. For example, the timer which starts upon starting of the valid time period is expired.
[0098] In response to determining that the condition is met, the spatial anchor server 220 may notify the expiry of the spatial anchor to at least one of the spatial anchor consumer 210 or the spatial anchor producer 230. The spatial anchor may be created as requested by the spatial anchor producer 230. Information of the spatial anchor may be provided to the spatial anchor consumer 210. For example, the spatial anchor consumer 210 may discover or retrieve the spatial anchor.
[0099] As shown in FIG. 4, in some example embodiments, if the spatial anchor is expired or a time length before the expiry of the spatial anchor is below a threshold, the spatial anchor server 220 may transmit (422), to the spatial anchor consumer 210, a notification about the expiry of the spatial anchor. Correspondingly, the spatial anchor consumer 210 may receive (424) the notification from the spatial anchor server 220.
[0100] In some example embodiments, the notification may be transmitted and received through a notification target address of the spatial anchor consumer 210. The notification target address may be at least one of a uniform resource location (URL), uniform resource identity (URI), IP address, etc. which indicates an address where the notification may be sent to.
[0101] In some example embodiments, the notification target address may be included in a spatial anchor discovery request. The spatial anchor discovery request is transmitted from the spatial anchor consumer 210 to the spatial anchor server 220 for discovering the spatial anchor. As such, the spatial anchor server 220 may notify spatial anchor consumer 210 about the expiry of the spatial anchor through the notification target address in the spatial anchor discovery request.
[0102] In some example embodiments, the notification target address may be included in a spatial anchor retrieve request. The spatial anchor retrieve request is transmitted from the spatial anchor consumer 210 to the spatial anchor server 220 for retrieving the spatial anchor. As such, the spatial anchor server 220 may notify the spatial anchor consumer 210 about theexpiry of the spatial anchor through the notification target address in the spatial anchor retrieve request.
[0103] In some example embodiments, the spatial anchor consumer 210 may subscribe to the spatial anchor server 220 for notifying about the expiry of the spatial anchor. As shown in FIG.4, the spatial anchor consumer 210 may transmit (406) to the spatial anchor server 220 a spatial anchor subscription request for subscribing to notification about the expiry of the spatial anchor. The spatial anchor subscription request may include the notification target address of the spatial anchor consumer 210. Correspondingly, the spatial anchor server 220 may receive (408) the spatial anchor subscription request from the spatial anchor consumer 210. As such, the spatial anchor server 220 may notify the spatial anchor consumer 210 about the expiry of the spatial anchor through the notification target address in the spatial anchor subscription request.
[0104] Based on the notification received from the spatial anchor server 220, the spatial anchor consumer 210 may disable (426) presentation of the spatial anchor. For example, the user is not allowed to trigger presentation of the spatial anchor or the spatial anchor would not be presented even if triggered by the user.
[0105] In some example embodiments, the spatial anchor consumer 210 may further remove the spatial anchor from a set of available spatial anchors, for example, from a list of discovered spatial anchors. As an example, if the spatial anchor consumer 210 determines that the spatial anchor has expired based on the notification, the spatial anchor may be removed.
[0106] Continuing with the flow 400, in some example embodiments, if the spatial anchor is expired or a time length before the expiry of the spatial anchor is below a threshold, the spatial anchor server 220 may transmit (414), to the spatial anchor producer 230, the notification about the expiry of the spatial anchor. Correspondingly, the spatial anchor producer 230 may receive (416) the notification from the spatial anchor server 220.
[0107] In some example embodiments, the notification may be transmitted and received through a notification target address of the spatial anchor producer 230. The notification target address may be at least one of a URL, URI, IP address, etc. which indicates an address where the notification may be sent to.
[0108] In some example embodiments, the notification target address may be included in a spatial anchor creation request. The spatial anchor creation request is transmitted from the spatial anchor producer 230 to the spatial anchor server 220 for creating the spatial anchor. As such, the spatial anchor server 220 may notify the spatial anchor producer 230 about the expiry of the spatial anchor through the notification target address in the spatial anchor creation request.
[0109] In some example embodiments, the spatial anchor producer 230 may subscribe to the spatial anchor server 220 for notifying about the expiry of the spatial anchor. As shown in FIG.4, the spatial anchor producer 230 may transmit (402) to the spatial anchor server 220 a spatial anchor subscription request for subscribing to notification about the expiry of the spatial anchor. The spatial anchor subscription request may include the notification target address of the spatial anchor producer 230. Correspondingly, the spatial anchor server 220 may receive (404) the spatial anchor subscription request from the spatial anchor producer 230. As such, the spatial anchor server 220 may notify the spatial anchor producer 230 about the expiry of the spatial anchor through the notification target address in the spatial anchor subscription request.
[0110] Reference is made back to the spatial anchor producer 230. After receiving the notification, the spatial anchor producer 230 may present the notification. For example, a notification message may be displayed or played to the user, for example a creator of the spatial anchor.
[0111] In some example embodiments, after notified with the expiry of the spatial anchor, the user may confirm the expiry of the spatial anchor. Accordingly, the spatial anchor producer 230 may receive a user input indicating confirmation on the expiry of the spatial anchor. Then, the spatial anchor producer 230 may remove the spatial anchor from a storage device associated with the spatial anchor producer 230. For example, the spatial anchor may be removed from a local memory of a UE.
[0112] In some example embodiments, after notified with the expiry of the spatial anchor, the user may expect some further operation to the spatial anchor. Accordingly, the spatial anchor producer 230 may receive a user input indicating a further operation on the spatial anchor. The further input may include but not limited to extension of a time period within which the spatial anchor is valid, or re-creation of the spatial anchor by the spatial anchor server 220. For example, the user may want to extend the valid time period or recreate the spatial anchor.
[0113] Accordingly, the spatial anchor producer 230 may transmit (428), to the spatial anchor server 220, a request comprising information indicating the further operation on the spatial anchor. For example, the spatial anchor producer 230 may request the spatial anchor server 220 to recreate the spatial anchor. For another example, the spatial anchor producer 230 may request the spatial anchor server 220 to extend the valid time period of the spatial anchor. Correspondingly, the spatial anchor server 220 may receive (432) the request from the spatial anchor producer 230 and perform (434) the further operation to update the spatial anchor.
[0114] In some example embodiments, if the valid time period of the spatial anchor is extended, the spatial anchor server 220 may transmit (436), to the spatial anchor consumer 210,an indication of the extended time period of the spatial anchor. The spatial anchor consumer 210 may receive (438) the indication of the extended time period from the spatial anchor server 220. Then, the spatial anchor consumer 210 may enable (442) the presentation of the spatial anchor based on the extended time period.
[0115] In some example embodiments, if the spatial anchor is re-created, the spatial anchor server 220 may transmit (444), to the spatial anchor consumer 210, further time information about expiry of a re-created spatial anchor. The spatial anchor consumer 210 may receive (446) the further time information from the spatial anchor server 220. The spatial anchor consumer 210 may enable (448) presentation of the re-created spatial anchor based on the further time information.
[0116] As briefly mentioned above, an example procedure of the creation of the spatial anchor is described below with reference to FIG. 5. FIG 5 illustrates a signaling flow 500 of an example procedure of creating the spatial anchor in accordance with some example embodiments of the present disclosure. For the purposes of discussion, FIG. 5 will be described with reference to FIG. 2, for example by using the spatial anchor server 220 and the spatial anchor producer 230 in FIG. 2.
[0117] In the signaling flow 500, it is assumed that the spatial anchor producer 230 has received information related to the spatial anchor server 220 for communication with the spatial anchor server 220. For example, the spatial anchor producer 230 may have received or configured with the URI or IP address related to the spatial anchor server 220. Additionally, the spatial anchor producer 230 may have received security credentials authorizing the spatial anchor producer 230 to communicate with the spatial anchor server 220. In some example embodiments that the spatial anchor producer 230 is a terminal device including a spatial anchor client, the spatial anchor producer 230 may receive the required information related to the spatial anchor server 220 from a VAL client of the terminal device over a spatial anchor-C interface.
[0118] The spatial anchor producer 230 may transmit (502) a spatial anchor create request to the spatial anchor server 220. Correspondingly, the spatial anchor server 220 may receive the request from the spatial anchor producer 230. The request may include an identity identifying the spatial anchor producer 230, security credentials, and list of spatial anchors to be created. The request may further include a position, a list of allowed entities defining which entities are permitted to discover and access the spatial anchor, and discoverability information (e.g., indicating whether the spatial anchor is discoverable by any user). If the request includes spatial anchor specific information, that information may remain opaque to the spatial anchor serverand may be stored with the spatial anchor. In some example embodiments, the request may indicate creating more than one spatial anchor.
[0119] The request may include time information of the spatial anchor. The time information may indicate a time period within which the spatial anchor is valid. For example, the time period may be in terms of a start time and an expiry time. Alternatively, the time period may be in terms of a start time and a certain time length. In the context of the present disclosure, the time period may be also referred to as a time duration.
[0120] Alternatively, or additionally, the time information may indicate a validity pattern. The validity pattern may indicate that till when the spatial anchor validity is activated. For example, the validity pattern may indicate that the spatial anchor is activated everyday morning or at a certain time each day. For another example, the validity pattern may indicate that the spatial anchor is activated during the weekend.
[0121] If the spatial anchor producer 230 has not subscribed to a spatial anchor related event, the creation request may also include a notification target address. The notification target address may be at least one of a uniform resource location (URL), uniform resource identity (URI), IP address, etc. indicates an address where the notification may be sent to.
[0122] The spatial anchor may be associated with spatial anchor specific information. For example, the spatial anchor specific information may contain application specific service information like a name, a URL, a media data, a type, a manufacturing company, a date, an expiry date, a ratings, and customer premise information (e.g. a residence, office or shop), a service schedule defining times when the spatial anchor(s) are active and inactive, etc. Such information may be stored in key-value pair and may be opaque to the spatial anchor server 220.
[0123] The spatial anchor create request may include at least information elements (lEs) listed below. It is noted that the lEs shown are examples without any limitation. The IE “duration” may correspond to the valid time period as described above. The IE “validity pattern” may correspond to the validity pattern as described above.Table 1: spatial anchor create requestInformation element Status DescriptionNotification Target Address O Notification target address (e.g. URL, URI, IP) where the notifications should be sent. > duration O Indicates start and end time till when the spatial anchor is valid.> validity pattern O Indicated till when the spatial anchorsvalidity duration is applicable.
[0124]
[0125] Upon receiving the create request from the spatial anchor producer 230, the spatial anchor server 220 may perform (506) request processing on the request. For example, if the anchor producer 230 is authorized, the anchor server 220 may create the spatial anchor according to the request and assign spatial anchor identity to the newly created spatial anchor and store the spatial anchor information. In some example embodiment, the spatial anchor producer 230 may request for creating more than one spatial anchor via the request and the spatial anchor server 220 may create more than one spatial anchor in response to the request.
[0126] If the time information indicates a time period, upon the creation of the spatial anchor the spatial anchor server 220 may activate the spatial anchor at the start time of time period and start a timer till the expiration time.
[0127] The spatial anchor server 220 may create a profile of the spatial anchor and store the time information in the profile. The profile may include at least lEs listed below. It is noted that the lEs shown are examples without any limitation. The IE “duration” may correspond to the valid time period as described above. The IE “validity pattern” may correspond to the validity pattern as described above.Table 2: spatial anchor profileInformation element Status Description> duration O Indicates start and end time till when the spatial anchor is valid.> validity pattern O Indicated till when the spatial anchorsvalidity duration is applicable.
[0128]
[0129] Upon the creation of the spatial anchor the spatial anchor server 220 may transmit (508) a spatial anchor create response to the spatial anchor producer 230. Correspondingly, the spatial anchor producer may receive (512) the spatial anchor create response from the spatial anchor server 220. If the spatial anchor server 220 has created the spatial anchor successfully, the response may include an indication indicating the success and the spatial anchor identity of the newly created spatial anchor. Otherwise, the response may include an indication of failure and may optionally include a reason for failure.
[0130] After a certain period of time, if the spatial anchor is expired and the spatial anchor producer 230 has been provided with the notification target address in the create request message, the spatial anchor server 220 may transmit (514) a notification to the spatial anchor producer 230. The notification may include a list of spatial anchors identities which are expired and no longer valid. Correspondingly, the spatial anchor producer 230 may receive (516) the notification from the spatial anchor server 220.
[0131]
[0132] In some example embodiments, the organizer may want to adjust (e.g., to increase or decrease) the validity of a spatial anchor that is already created. For example, in a scenario related to a live concert, the organizer may want to adjust the validity of the spatial anchor. In such cases, the spatial anchor producer 230 may update the already created spatial anchors by sending a spatial anchor update request to the spatial anchor server 220. The spatial anchor update request may include at least lEs listed below. It is noted that the lEs shown are examples without any limitation. The IE “duration” may correspond to the valid time period as described above. The IE “validity pattern” may correspond to the validity pattern as described above.Table 3: spatial anchor update requestInformation element Status Description> Notification Target O Notification target address (e.g. URL, URI, Address IP) where the notifications should be sent. > duration O Indicates start and end time till when the spatial anchor is valid.> validity pattern O Indicated till when the spatial anchorsvalidity duration is applicable.
[0133]
[0134] Based on the spatial anchor update request, the spatial anchor server 220 may update the time information in the profile.
[0135] As briefly mentioned above, a detailed procedure of the creation of the spatial anchor is described below with reference to FIG. 6. FIG 6 illustrates a signaling flow 600 of an example procedure of discovering the spatial anchor in accordance with some example embodiments of the present disclosure. For the purposes of discussion, FIG. 6 will be described with reference to FIG. 2, for example by using the spatial anchor consumer 210 and the spatial anchor server 220 in FIG. 2.
[0136] In the signaling flow 600, it is assumed that the spatial anchor consumer 210 has received information related to the spatial anchor server 220 for communication with the spatial anchor server 220. For example, the spatial anchor consumer 210 may have received or configured with the URI or IP address related to the spatial anchor server 220. Additionally, the spatial anchor consumer 210 may have received security credentials authorizing the spatial anchor consumer 210 to communicate with the spatial anchor server 220. In some example embodiments that the spatial anchor consumer 210 is a terminal device including a spatial anchor client, the spatial anchor producer 230 may receive the required information related to the spatial anchor server 220 from a VAL client of the terminal device over a spatial anchor-C interface.
[0137]
[0138] The spatial anchor consumer 210 may transmit (602) a spatial anchor discovery request to the spatial anchor server 220. Correspondingly, the spatial anchor server 220 may receive (604) the spatial anchor discovery request from the spatial anchor consumer 210. The spatial anchor discovery request may include time information associated with the validity of the spatial anchor.
[0139] For example, the spatial anchor consumer 210 may transmit a spatial anchor discovery request message to the spatial anchor server 220 to obtain information about spatial anchors of interest. The request may include an identity identifying the spatial anchor consumer 210, security credentials. Additionally, the request may further include spatial anchor discovery filters. If the spatial anchor discovery request was triggered by a VAL client on the spatial anchor consumer 210, the spatial anchor discovery request can additionally include a VAL client identity.
[0140] The spatial anchor discovery request may include at least information elements (lEs) listed below. It is noted that the lEs shown are examples without any limitation. The IE “duration” may correspond to the valid time period as described above.Table 4: spatial anchor discovery requestInformation element Status Description> duration O Indicates start and end time till when thespatial anchor is valid.
[0141]
[0142] Upon receiving the spatial anchor discovery request from the spatial anchor consumer 210, the spatial anchor server 220 may perform (606) request processing on the request. For example, upon receiving the request, the spatial anchor server 220 may validate if the spatial anchor consumer 210 is authorized for the request. If the spatial anchor consumer 210 is authorized, the spatial anchor server 220 may identify the spatial anchor(s) that satisfies the spatial anchor discovery filters. If the time information is indicated, the spatial anchor server 220 may compare the time information indicated in the spatial anchor discovery request with the time information available in the spatial anchor profiles. Additionally, the spatial anchor discovery request may further indicate a user preference in the spatial anchor discovery filters which may be used by the spatial anchor server 220 to be compared with the spatial anchor specific information.
[0143] For each matching spatial anchor, the spatial anchor server 220 may check whether the spatial anchor consumer 210 is authorized to obtain the spatial anchor based on the identity and location of the spatial anchor consumer 210, and based on an allowed entities list. To determine the location of interest of the spatial anchor consumer 210, the spatial anchor server 220 may use location information provided in the discovery request. If location information isnot provided in the discovery request, the spatial anchor server 220 may obtain location information by invoking location service directly or via a network exposure function, or by invoking the service enabler architecture layer (SEAL) location management application program interfaces (APIs).
[0144] Based on the discovery, the spatial anchor server 220 may transmit (608) a spatial anchor discovery response to the spatial anchor consumer 210. Correspondingly, the spatial anchor consumer 210 may receive (612) the spatial anchor discovery response from the spatial anchor server 220. The spatial anchor discovery response may include time information associated with the validity of the spatial anchor.
[0145] The spatial anchor server 220 may send a spatial anchor discovery response to the spatial anchor consumer 210. If the spatial anchor server 220 has successfully identified the spatial anchor(s), the discovery response may include an indication of success and the identified spatial anchor(s). Additionally, the discovery response may further include a list of recommended spatial anchor(s). The list of recommended spatial anchor(s) may be determined based on the discovery request or the user preference. Otherwise, if the discovery is failed, the discovery response may include an indication of failure and may optionally include a reason for failure.
[0146] The spatial anchor discovery response may include at least information elements (lEs) listed below. It is noted that the lEs shown are examples without any limitation. The IE “duration” may correspond to the valid time period as described above. The IE “validity pattern” may correspond to the validity pattern as described above.Table 5: spatial anchor discovery responseInformation element Status Description> duration O Indicates start and end time till when the spatial anchor is valid.> validity pattern O Indicated till when the spatial anchorsvalidity duration is applicable.
[0147]
[0148] Upon receiving the spatial anchor discovery response, the spatial anchor consumer 210 may determine (614) the validity of the spatial anchor. For example, upon receiving the spatial anchor discovery response indicating a success of the discovery, the spatial anchor consumer 210 may store the spatial anchor information in a spatial anchor cache. The spatial anchor consumer 210 may evaluate the validity conditions associated with the discovered spatial anchors prior to using the spatial anchor. If the spatial anchor consumer 210 is a terminal device including a spatial anchor client, the spatial anchor client may provide spatial anchor information to the VAL client(s) of the spatial anchor consumer 210. Upon receiving valid spatialanchor information, the VAL client(s) may be able to access the service(s) associated with each spatial anchor.
[0149] In some example embodiments, if the time information indicates a time period, the spatial anchors client (on the spatial anchor consumer 210) may process the parameters of the spatial anchors and starts a corresponding timer till when it can present the spatial anchors to the user according to the time period. Once / after the timer expires, the spatial anchors which are expired will be removed from the discovered spatial anchors list and accordingly the user will not be able to see the spatial anchors. Alternatively, or additionally, if the time information indicates a validity pattern, the spatial anchor consumer 210 may activate and deactivate the spatial anchor for presenting to the user accordingly.
[0150] As briefly mentioned above, a detailed procedure of the retrieval of the spatial anchor is described below with reference to FIG. 7. FIG 7 illustrates a signaling flow 700 of an example procedure of retrieving the spatial anchor in accordance with some example embodiments of the present disclosure. For the purposes of discussion, FIG. 7 will be described with reference to FIG. 2, for example by using the spatial anchor consumer 210 and the spatial anchor server 220 in FIG. 2.
[0151] In the signaling flow 700, it is assumed that the spatial anchor consumer 210 has received information related to the spatial anchor server 220 for communication with the spatial anchor server 220. For example, the spatial anchor consumer 210 may have received or configured with the URI or IP address related to the spatial anchor server 220. Additionally, the spatial anchor consumer 210 may have received security credentials authorizing the spatial anchor consumer 210 to communicate with the spatial anchor server 220. In some example embodiments that the spatial anchor consumer 210 is a terminal device including a spatial anchor client, the spatial anchor producer 230 may receive the required information related to the spatial anchor server 220 from a VAL client of the terminal device over a spatial anchor-C interface. In the signaling flow 700, it is assumed that the spatial anchor consumer 210 has discovered the list of spatial anchors as per the procedure of discovery described with respect to FIG. 6 above.
[0152] The spatial anchor consumer 210 may transmit (702) a spatial anchor retrieve request to the spatial anchor server 220. Correspondingly, the spatial anchor server 220 may receive (704) the spatial anchor retrieve request from the spatial anchor consumer 210. For example, the spatial anchor consumer 210 may transmit a spatial anchor retrieve request message to the spatial anchor server 220 to get information about specific spatial anchors of interest. The spatial anchor retrieve request may include an identity identifying the spatial anchor consumer210, security credentials, and an identity of the spatial anchor.
[0153] Based on the spatial anchor retrieve request, the spatial anchor server 220 may perform (706) the request processing on the request. For example, upon receiving the spatial anchor retrieve request, the spatial anchor server 220 may validate if the spatial anchor consumer 210 is authorized for the request. If the spatial anchor consumer 210 is authorized, the spatial anchor server 220 may identify whether the spatial anchor corresponding to the identity exists or not based on identity of the spatial anchor.
[0154] Based on the result of the retrieval, the spatial anchor server 220 may transmit (708) a spatial anchor retrieve response to the spatial anchor consumer 210. Correspondingly, the spatial anchor consumer 210 may receive the spatial anchor retrieve response from the spatial anchor server 220. For example, if the spatial anchor server 220 has identified the spatial anchor, the retrieve response may include an indication of success and the details about the retrieved spatial anchor. Otherwise, the response may include an indication of failure and may optionally include a reason for failure.
[0155] In some example embodiments, if the time information indicates the time period, the spatial anchors client (on the spatial anchor consumer 210) may process the parameters of the spatial anchor and start a corresponding timer till when the spatial anchor may be shown to the user. Once the timer expires, the spatial anchors which are expired will be removed from the discovered spatial anchors list and accordingly the user will not be able to see the spatial anchors. Alternatively, or additionally, if the time information indicates a validity pattern, the spatial anchor consumer 210 may activate and deactivate the spatial anchor for presenting to the user accordingly.
[0156] FIG. 8 shows a flowchart of an example method 800 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the first apparatus 110 in FIG. 1.
[0157] At block 810, the first apparatus 110 transmits, to a network entity, a spatial anchor request for at least a spatial anchor.
[0158] At block 820, the first apparatus 110 receives, from the network entity, a spatial anchor response indicating the spatial anchor, the spatial anchor response comprising time information associated with validity of the spatial anchor.
[0159] At block 830, the first apparatus 110 enables presentation of the spatial anchor based on the time information.
[0160]
[0161] In some example embodiments, the time information comprises at least one of: a time period within which the spatial anchor is valid, or a validity pattern indicating at least one activation time period for the spatial anchor and at least one deactivation time period for the spatial anchor.
[0162] In some example embodiments, the first apparatus is caused to enable the presentation of the spatial anchor based on the time information by: starting a timer upon starting of the time period, the timer having a time length corresponding to the time period; and enabling the presentation of the spatial anchor until expiry of the timer.
[0163] In some example embodiments, the first apparatus is caused to enable the presentation of the spatial anchor based on the time information by at least one of: enabling the presentation of the spatial anchor within the at least one activation time period, or disabling the presentation of the spatial anchor within the at least one deactivation time period.
[0164] In some example embodiments, the method 800 further comprises: removing the spatial anchor from a set of discovered spatial anchors based on at least one of: that the time information indicates the spatial anchor is invalid, or expiring of a timer that is started upon starting of a time period within which the spatial anchor is valid, the timer having a time length corresponding to the time period.
[0165] In some example embodiments, the method 800 further comprises: receiving, from the network entity, an update to the time information; and enabling the presentation of the spatial anchor based on the updated time information.
[0166] In some example embodiments, the spatial anchor request comprises a spatial anchor retrieve request, and the spatial anchor retrieve request comprises an identifier of the spatial anchor.
[0167] In some example embodiments, the spatial anchor request comprises a spatial anchor discovery request, and the time information in the spatial anchor response matches a time indication associated with the spatial anchor discovery request.
[0168] In some example embodiments, the time indication comprises at least one of: a time requirement comprised in the spatial anchor discovery request and associated with the validity of the spatial anchor, a reception time of the spatial anchor discovery request by the network entity, or a transmission time of the spatial anchor discovery request by the first apparatus.
[0169] In some example embodiments, the first apparatus comprises a spatial anchor client or a vertical application layer server, and the network entity comprises a spatial anchor server.
[0170] FIG. 9 shows a flowchart of an example method 900 implemented at a network entity in accordance with some example embodiments of the present disclosure. For the purpose ofdiscussion, the method 900 will be described from the perspective of the network entity 120 in FIG. 1.
[0171] At block 910, the network entity 120 receives, from a first apparatus, a spatial anchor request for at least a spatial anchor.
[0172] At block 920, the network entity 120 determines time information associated with validity of the spatial anchor based on a profile of the spatial anchor.
[0173] At block 930, the network entity 120 transmits a spatial anchor response indicating the spatial anchor to the first apparatus, the spatial anchor response comprising the time information.
[0174] In some example embodiments, the time information comprises at least one of: a time period within which the spatial anchor is valid, or a validity pattern indicating at least one activation time period for the spatial anchor and at least one deactivation time period for the spatial anchor.
[0175] In some example embodiments, the spatial anchor request comprises a spatial anchor retrieve request, and the spatial anchor retrieve request comprises an identifier of the spatial anchor.
[0176] In some example embodiments, the spatial anchor request comprises a spatial anchor discovery request, and the network entity is caused to transmit the spatial anchor response to the first apparatus by: comparing the time information with a time indication associated with the spatial anchor discovery request; and in response to determining that the time information matches the time indication, transmitting the spatial anchor response to the first apparatus.
[0177] In some example embodiments, the time indication comprises at least one of: a time requirement comprised in the spatial anchor discovery request and associated with the validity of the spatial anchor, a reception time of the spatial anchor discovery request by the network entity, or a transmission time of the spatial anchor discovery request by the first apparatus.
[0178] In some example embodiments, the method 900 further comprises: receiving, from a second apparatus, a creation request for the spatial anchor, the creation request comprising the time information; and creating, based on the creation request, the profile of the spatial anchor comprising the time information; and transmitting, to the second apparatus, a creation response indicating successful creation of the spatial anchor.
[0179] In some example embodiments, the method 900 further comprises: starting a timer upon starting of the time period, the timer having a time length corresponding to the time period; and removing the profile of the spatial anchor upon expiry of the timer.
[0180] In some example embodiments, the method 900 further comprises: receiving, from the second apparatus, an update request to update the time information; and updating the timeinformation in the profile of the spatial anchor based on the update request.
[0181] In some example embodiments, the method 900 further comprises: transmitting an update to the time information to the first apparatus.
[0182] FIG. 10 shows a flowchart of an example method 1000 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described from the perspective of the second apparatus 130 in FIG. 1.
[0183] At block 1010, the second apparatus 130 transmits, to a network entity, a creation request for a spatial anchor, the creation request comprising time information associated with validity of the spatial anchor.
[0184] At block 1020, the second apparatus 130 receives, from the network entity, a creation response indicating successful creation of the spatial anchor.
[0185] In some example embodiments, the time information is provided by at least one of: a user associated with the second apparatus, or an application client associated with the second apparatus.
[0186] In some example embodiments, the time information is determined based on information about one or more spatial anchors created historically.
[0187] In some example embodiments, the network entity is further caused to: in response to determining an update to the time information, transmitting to the network entity, an update request to update the time information.
[0188] In some example embodiments, a first apparatus capable of performing any of the method 800 (for example, the first apparatus 110 in FIG. 1) may comprise means for performing the respective operations of the method 800 and / or any of the described one or more example embodiments thereof. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.
[0189] In some example embodiments, a network entity capable of performing any of the method 900 (for example, the network entity 120 in FIG. 1) may comprise means for performing the respective operations of the method 900 and / or any of the described one or more example embodiments thereof. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The network entity may be implemented as or included in the network entity 120 in FIG. 1.
[0190] In some example embodiments, a second apparatus capable of performing any of the method 1000 (for example, the second apparatus 130 in FIG. 1) may comprise means forperforming the respective operations of the method 1000 and / or any of the described one or more example embodiments thereof. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 130 in FIG. 1.
[0191] FIG. 11 shows a flowchart of an example method 1100 implemented at a network entity in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1100 will be described from the perspective of the network entity 120 in FIG. 1.
[0192] At block 1110, the network entity 120 determines that a condition related to expiry of a spatial anchor is met based on time information associated with validity of the spatial anchor.
[0193] At block 1120, in response to determining that the condition is met, the network entity 120 transmits a notification about the expiry of the spatial anchor to at least one of a first apparatus or a second apparatus, wherein the spatial anchor is created as requested by the second apparatus, and information about the spatial anchor is provided to the first apparatus.
[0194] In some example embodiments, the condition comprises at least one of: that a time length before the expiry of the spatial anchor is below a threshold, or that the spatial anchor is expired.
[0195] In some example embodiments, the method 1100 further comprises: receiving, from the second apparatus, a spatial anchor creation request for creating the spatial anchor, wherein the notification is transmitted to the second apparatus through a notification target address comprised in the spatial anchor creation request.
[0196] In some example embodiments, the method 1100 further comprises: receiving, from the second apparatus, a spatial anchor subscription request for subscribing the expiry of the spatial anchor, and wherein the notification is transmitted to the second apparatus through a notification target address that is comprised in the spatial anchor subscription request.
[0197] In some example embodiments, the method 1100 further comprises: receiving, from the first apparatus, a spatial anchor discovery request for discovering the spatial anchor, wherein the notification is transmitted to the first apparatus through a notification target address comprised in the spatial anchor discovery request, or receiving, from the first apparatus, a spatial anchor retrieve request for retrieving the spatial anchor, wherein the notification is transmitted to the first apparatus through a notification target address comprised in the spatial anchor retrieve request.
[0198] In some example embodiments, the method 1100 further comprises: receiving, from the first apparatus, a spatial anchor subscription request for subscribing to the notification aboutthe expiry of the spatial anchor, and wherein the notification is transmitted to the first apparatus through a notification target address that is comprised in the spatial anchor subscription request.
[0199] In some example embodiments, the method 1100 further comprises: receiving, from the second apparatus, a request comprising information indicating a further operation associated with the spatial anchor; and performing the further operation to update the spatial anchor based on the information indicating the further operation associated with the spatial anchor.
[0200] In some example embodiments, the further operation comprises at least one of: extension of a time period within which the spatial anchor is valid, or re-creation of the spatial anchor with further time information about expiry of a re-created spatial anchor.
[0201] In some example embodiments, the method 1100 further comprises: transmitting, to the first apparatus, an indication of an extended time period of the spatial anchor.
[0202] In some example embodiments, the method 1100 further comprises: transmitting, to the first apparatus, the further time information about the expiry of the re-created spatial anchor.
[0203] FIG. 12 shows a flowchart of an example method 1200 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1200 will be described from the perspective of the first apparatus 110 in FIG. 1.
[0204] At block 1210, the first apparatus 110 receives, from a network entity, a notification associated with expiry of a spatial anchor, wherein information about the spatial anchor is provided to the first apparatus.
[0205] At block 1220, the first apparatus 110 disables presentation of the spatial anchor based on the notification.
[0206] In some example embodiments, the method 1200 further comprises: transmitting, to the network entity, a spatial anchor discovery request for discovering the spatial anchor, wherein the notification is received from the network entity through a notification target address that is comprised in the spatial anchor discovery request, or transmitting, to the network entity, a spatial anchor retrieve request for retrieving the spatial anchor, wherein the notification is received from the network entity through a notification target address that is comprised in the spatial anchor retrieve request.
[0207] In some example embodiments, the method 1200 further comprises: transmitting, to the network entity, a spatial anchor subscription request for subscribing the expiry of the spatial anchor, and wherein the notification is received from the network entity through a notification target address that is comprised in the spatial anchor subscription request.
[0208] In some example embodiments, the method 1200 further comprises: receiving, from the network entity, an indication of an extended time period of the spatial anchor; and enabling presentation of the spatial anchor based on the extended time period.
[0209] In some example embodiments, the method 1200 further comprises: receiving, from the network entity, further time information about expiry of a re-created spatial anchor; and enabling presentation of the re-created spatial anchor based on the further time information.
[0210] In some example embodiments, the method 1200 further comprises: removing the spatial anchor from a set of discovered spatial anchors.
[0211] FIG. 13 shows a flowchart of an example method 1300 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1300 will be described from the perspective of the second apparatus 130 in FIG. 1.
[0212] At block 1310, the second apparatus 130 receives, from a network entity, a notification about expiry of a spatial anchor, wherein the spatial anchor is created as requested by the second apparatus and with time information about validity of the spatial anchor.
[0213] At block 1320, the second apparatus 130 presents the notification.
[0214] In some example embodiments, the method 1300 further comprises: transmitting, to the network entity, a spatial anchor creation request for creating the spatial anchor, wherein the notification is received from the network entity through a notification target address that is comprised in the spatial anchor creation request.
[0215] In some example embodiments, the method 1300 further comprises: receiving, from the second apparatus, a spatial anchor subscription request for subscribing to notification about the expiry of the spatial anchor, and wherein the notification is received from the network entity through a notification target address that is comprised in the spatial anchor subscription request.
[0216] In some example embodiments, the method 1300 further comprises: receiving a user input indicating a further operation on the spatial anchor; and transmitting, to the network entity, a request comprising information indicating the further operation on the spatial anchor.
[0217] In some example embodiments, the further operation comprises at least one of: extension of a time period within which the spatial anchor is valid, or re-creation of the spatial anchor by the network entity.
[0218] In some example embodiments, the method 1300 further comprises: receiving a user input indicating confirmation on the expiry of the spatial anchor; and removing the spatial anchor from a storage device associated with the second apparatus.
[0219] In some example embodiments, a network entity capable of performing any of themethod 1100 (for example, the network entity 120 in FIG. 1 ) may comprise means for performing the respective operations of the method 1100 and / or any of the described one or more example embodiments thereof. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The network entity may be implemented as or included in the network entity 120 in FIG. 1.
[0220] In some example embodiments, a first apparatus capable of performing any of the method 1200 (for example, the first apparatus 110 in FIG. 1 ) may comprise means for performing the respective operations of the method 1200 and / or any of the described one or more example embodiments thereof. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.
[0221] In some example embodiments, a second apparatus capable of performing any of the method 1300 (for example, the second apparatus 130 in FIG. 1) may comprise means for performing the respective operations of the method 1300 and / or any of the described one or more example embodiments thereof. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 130 in FIG. 1.
[0222] FIG. 14 is a simplified block diagram of a device 1400 that is suitable for implementing example embodiments of the present disclosure. The device 1400 may be provided to implement a communication device, for example, the first apparatus 110 or the network entity 120 as shown in FIG. 1. As shown, the device 1400 includes one or more processors 1410, one or more memories 1420 coupled to the processor 1410, and one or more communication modules 1440 coupled to the processor 1410.
[0223] The communication module 1440 is for bidirectional communications. The communication module 1440 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 1440 may include at least one antenna.
[0224] The processor 1410 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1400 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0225] The memory 1420 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1424, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 1422 and other volatile memories that will not last in the power-down duration.
[0226] A computer program 1430 includes computer executable instructions that are executed by the associated processor 1410. The instructions of the program 1430 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 1430 may be stored in the memory, e.g., the ROM 1424. The processor 1410 may perform any suitable actions and processing by loading the program 1430 into the RAM 1422.
[0227] The example embodiments of the present disclosure may be implemented by means of the program 1430 so that the device 1400 may perform any process of the disclosure as discussed with reference to FIG. 3 to FIG. 13. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0228] In some example embodiments, the program 1430 may be tangibly contained in a computer readable medium which may be included in the device 1400 (such as in the memory 1420) or other storage devices that are accessible by the device 1400. The device 1400 may load the program 1430 from the computer readable medium to the RAM 1422 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).
[0229] FIG. 15 shows an example of the computer readable medium 1500 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1500 has the program 1430 stored thereon.
[0230] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and describedas block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0231] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computerexecutable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0232] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0233] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0234] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0235] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.
[0236] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
38Claims1. A first apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to:transmit, to a network entity, a spatial anchor request for at least a spatial anchor; receive, from the network entity, a spatial anchor response indicating the spatial anchor, the spatial anchor response comprising time information associated with validity of the spatial anchor; andenable presentation of the spatial anchor based on the time information.
2. The first apparatus of claim 1 , wherein the time information comprises at least one of: a time period within which the spatial anchor is valid, ora validity pattern indicating at least one activation time period for the spatial anchor and at least one deactivation time period for the spatial anchor.
3. The first apparatus of claim 2, wherein the first apparatus is caused to enable the presentation of the spatial anchor based on the time information by:starting a timer upon starting of the time period, the timer having a time length corresponding to the time period; andenabling the presentation of the spatial anchor until expiry of the timer.
4. The first apparatus of claim 2, wherein the first apparatus is caused to enable the presentation of the spatial anchor based on the time information by at least one of:enabling the presentation of the spatial anchor within the at least one activation time period, ordisabling the presentation of the spatial anchor within the at least one deactivation time period.
5. The first apparatus of any of claims 1 to 4, wherein the first apparatus is further caused to: remove the spatial anchor from a set of discovered spatial anchors based on at least one of: that the time information indicates the spatial anchor is invalid, orexpiry of a timer that is started upon starting of a time period within which the spatial anchor is valid, the timer having a time length corresponding to the time period.
396. The first apparatus of any of claims 1 to 5, wherein the first apparatus is further caused to: receive, from the network entity, an update to the time information; andenable the presentation of the spatial anchor based on the updated time information.
7. The first apparatus of any of claims 1 to 6, wherein the spatial anchor request comprises a spatial anchor retrieve request, and the spatial anchor retrieve request comprises an identifier of the spatial anchor.
8. The first apparatus of any of claims 1 to 6, wherein the spatial anchor request comprises a spatial anchor discovery request, and the time information in the spatial anchor response matches a time indication associated with the spatial anchor discovery request.
9. The first apparatus of claim 8, wherein the time indication comprises at least one of: a time requirement comprised in the spatial anchor discovery request and associated with the validity of the spatial anchor,a reception time of the spatial anchor discovery request by the network entity, or a transmission time of the spatial anchor discovery request by the first apparatus.
10. The first apparatus of any of claims 1 to 9, wherein the first apparatus comprises a spatial anchor client or a vertical application layer server, and the network entity comprises a spatial anchor server.
11. A network entity comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the network entity at least to:receive, from a first apparatus, a spatial anchor request for at least a spatial anchor; determine time information associated with validity of the spatial anchor based on a profile of the spatial anchor; andtransmit a spatial anchor response indicating the spatial anchor to the first apparatus, the spatial anchor response comprising the time information.4012. The network entity of claim 11 , wherein the time information comprises at least one of: a time period within which the spatial anchor is valid, ora validity pattern indicating at least one activation time period for the spatial anchor and at least one deactivation time period for the spatial anchor.
13. The network entity of any of claims 11-12, wherein the spatial anchor request comprises a spatial anchor retrieve request, and the spatial anchor retrieve request comprises an identifier of the spatial anchor.
14. The network entity of any of claims 11-12, wherein the spatial anchor request comprises a spatial anchor discovery request, and the network entity is caused to transmit the spatial anchor response to the first apparatus by:comparing the time information with a time indication associated with the spatial anchor discovery request; andin response to determining that the time information matches the time indication, transmitting the spatial anchor response to the first apparatus.
15. The network entity of claim 14, wherein the time indication comprises at least one of: a time requirement comprised in the spatial anchor discovery request and associated with the validity of the spatial anchor,a reception time of the spatial anchor discovery request by the network entity, or a transmission time of the spatial anchor discovery request by the first apparatus.
16. The network entity of any of claims 11 to 15, wherein the network entity is further caused to:receive, from a second apparatus, a creation request for the spatial anchor, the creation request comprising the time information; andcreate, based on the creation request, the profile of the spatial anchor comprising the time information; andtransmit, to the second apparatus, a creation response indicating successful creation of the spatial anchor.
17. The network entity of claim 12, wherein the network entity is further caused to: start a timer upon starting of the time period, the timer having a time length corresponding to the time period; andremove the profile of the spatial anchor upon expiry of the timer.
18. The network entity of any of claims 11 to 17, wherein the network entity is further caused to:receive, from the second apparatus, an update request to update the time information; and update the time information in the profile of the spatial anchor based on the update request.
19. The network entity of claim 18, wherein the network entity is further caused to: transmit an update to the time information to the first apparatus.
20. A second apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to:transmit, to a network entity, a creation request for a spatial anchor, the creation request comprising time information associated with validity of the spatial anchor; andreceive, from the network entity, a creation response indicating successful creation of the spatial anchor.
21. The second apparatus of claim 20, wherein the time information is provided by at least one of:a user associated with the second apparatus, oran application client associated with the second apparatus.
22. The second apparatus of claim 20, wherein the time information is determined based on information about one or more spatial anchors created historically.
23. The network entity of any of claims 20 to 22, wherein the network entity is further caused to:in response to determining an update to the time information, transmit, to the network entity, an update request to update the time information.
24. A method comprising:transmitting, to a network entity, a spatial anchor request for at least a spatial anchor; receiving, from the network entity, a spatial anchor response indicating the spatial anchor, the spatial anchor response comprising time information associated with validity of the spatial anchor; and enabling presentation of the spatial anchor based on the time information.
25. A method comprising:receiving, from a first apparatus, a spatial anchor request for at least a spatial anchor; determining time information associated with validity of the spatial anchor based on a profile of the spatial anchor; andtransmitting a spatial anchor response indicating the spatial anchor to the first apparatus, the spatial anchor response comprising the time information.
26. A method comprising:transmitting, to a network entity, a creation request for a spatial anchor, the creation request comprising time information associated with validity of the spatial anchor; andreceiving, from the network entity, a creation response indicating successful creation of the spatial anchor.
27. A first apparatus comprising:means for transmitting, to a network entity, a spatial anchor request for at least a spatial anchor; means for receiving, from the network entity, a spatial anchor response indicating the spatial anchor, the spatial anchor response comprising time information associated with validity of the spatial anchor; andmeans for enabling presentation of the spatial anchor based on the time information.
28. A network entity comprising:means for receiving, from a first apparatus, a spatial anchor request for at least a spatial anchor;means for determining time information associated with validity of the spatial anchor based on a profile of the spatial anchor; andmeans for transmitting a spatial anchor response indicating the spatial anchor to the first apparatus, the spatial anchor response comprising the time information.
29. A second apparatus comprising:means for transmitting, to a network entity, a creation request for a spatial anchor, the creation request comprising time information associated with validity of the spatial anchor; andmeans for receiving, from the network entity, a creation response indicating successful creation of the spatial anchor.
30. A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 24 or the method of claim 25 or the method of claim
