First network node, second network node and methods performed therein for handling services related to spatial anchors in a communication network

Abstract

Embodiments herein relate to a method performed by a first network node (15), such as a SEAL LM client, a MMEC, a VAL server, for handling a service in a communication network (1). The first network node transmits a request to a second network node (16), wherein the request is related to one or more spatial anchors of a service. The first network node (15) receives a response from the second network node (16), wherein the response is related to the request transmitted.

Description

[0001] FIRST NETWORK NODE, SECOND NETWORK NODE AND METHODS PERFORMED THEREIN FOR HANDLING SERVICES RELATED TO SPATIAL ANCHORS IN A COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a first network node, a second network node, and methods performed therein regarding communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling a service in a communication network.

[0004] BACKGROUND

[0005] In a typical communication network, User Equipments (UE), also known as wireless communication devices, mobile stations, stations (ST A) and / or wireless devices, communicate via an Access Network (AN), such as a radio access network (RAN), with one or more core networks (CN). A RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.

[0006] A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate e.g. enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

[0007] Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and coming 3GPP releases, such as New Radio (NR) and 6 generation (6G), are worked on. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an essentially non-hierarchical architecture comprising radio network nodes connected directly to one or more core networks.

[0008] With the emerging 5G technologies such as NR, the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. NR is connected to a 5G Core Network (5GC) which comprises a number of Network Functions (NF) such as User Plane Function (UPF), Session Management Function (SMF), Access Management Function (AMF), Authentication Service Function (AUSF), Policy Control Function (PCF), Unified Data Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF), just to mention some. In the 5GC, NFs can discover other NFs by using a discovery service provided by the Network Repository Function (NRF).

[0009] Augmented Reality (AR) may be defined as an interactive experience that combines the real world and computer-generated content. The content can span multiple sensory modalities, including visual, auditory, haptic, somatosensory and olfactory. AR can be defined as a system that incorporates three basic features: a combination of real and virtual worlds, real-time interaction, and accurate three-dimensional (3D) registration of virtual and real objects.

[0010] In addition to the “AR” term the industry uses two other related terms. Mixed reality (MR) is an advanced form of AR where some virtual elements are inserted into the physical scene with the intent to provide the illusion that these elements are part of the real scene. Extended reality (XR) refers to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. It includes representative forms such as AR, MR and virtual reality (VR) and the areas interpolated among them. The levels of virtuality range from partially sensory inputs to fully immersive VR. A key aspect of XR is the extension of human experiences especially relating to the senses of existence, represented by VR, and the acquisition of cognition, represented by AR. While it is herein mostly used the “AR” term in the description but “MR” and “XR” may equally be applied to embodiments herein.

[0011] Applications and services for smart phones, automotive, XR and smart manufacturing etc. are moving to the cloud, with 5G as the connectivity solution. Access needs to be optimized to guarantee a rich experience for consumers of an application or consumers of content. The optimization may involve the deployment of applications / content at edge cloud sites which are close to or even collocated with the mobile operator’s network. Typically, these edge empowered applications consist of an edge application client, running on the UE, which is connected via the mobile network, and an Edge Application Server (EAS), running in the edge hosting environment at the edge cloud site(s) to provide an edge service for the edge application client. When considering the cloud based XR gaming as an example, on the terminal device, the lightweight client function provides a minimum set of capabilities like rendering the VR / AR experience. It communicates with the cloud-based AR / VR services, like video coding, remote rendering, the gaming engine etc. which are deployed at edge cloud sites to fulfill for example low latency requirements. The server components of such edge applications could be deployed in the distributed edge cloud sites.

[0012] Since 3GPP Release 16, Service Enablement Architecture Layer for Verticals (SEAL) has been introduced to support vertical applications such as vehicle to everything (V2X) applications. 3GPP TS 23.434 v.18.5.0 specifies application plane and signalling plane entities for application-enabling services, e.g., group management, configuration management, location management, identity / key management, network resource management, that can be reused across vertical applications. SEAL also specifies the northbound application programming interfaces (API) for its individual services to enable flexible integration with vertical applications.

[0013] Fig. 1 illustrates the generic on-network functional model of SEAL:

[0014] In the Vertical Application Layer (VAL), the VAL client communicates with the VAL server over VAL-UU reference point. VAL-UU supports both unicast and multicast delivery modes. The SEAL functional entities on the UE and the server are grouped into SEAL client(s) and SEAL server(s) respectively. The SEAL consists of a common set of services, e.g., group management, location management, and reference points. The SEAL offers its services to the VAL.

[0015] The SEAL client(s) communicates with the SEAL server(s) over the SEAL-UU reference points. SEAL-UU supports both unicast and multicast delivery modes. The SEAL client(s) provides the service enabler layer support functions to the VAL client(s) over SEAL-C reference points. The VAL server(s) communicate with the SEAL server(s) over the SEAL-S reference points. The SEAL server(s) may communicate with the underlying 3GPP network systems using the respective 3GPP interfaces specified by the 3GPP network system.

[0016] SA1 in 3GPP TS 22.156 defines spatial anchors as "an association between a location in space (three dimensions) and service information that can be used to identify and access services, e.g. information to access AR media content".

[0017] Application providers can use spatial anchors to associate application content and services with location information which can be managed by the 3GPP system. In turn, spatial anchors can be used by application clients to discover and access application content and services in a location aware fashion.

[0018] Clause 5.4 "Use Case on Spatial Anchor Enabler" of 3GPP TR 22.856 provides detailed use case for spatial anchor enabler. The use case defines mainly two entities:

[0019] 1) Spatial anchor producer: It creates the spatial anchor along with its place and / or location in the 3D space. It determines what to share and its location, and any constraints, e.g. who to share the spatial anchor with, and additional information.

[0020] 2) Spatial anchor consumer: It recognizes anchors associated with locations in 3D space, and use the spatial anchor to obtain the associated information.

[0021] In order to create spatial anchor, the producer captures the location of the product and associates a new spatial anchor with this location and product information. The producer can adjust and / or update the spatial anchors for its location or service information or remove it completely. The consumer can retrieve information about spatial anchors.

[0022] SUMMARY

[0023] As part of developing embodiments herein one or more problems have been identified. 1 . The spatial anchors can provide access to information or content services like multimedia content (video or audio or haptic), interactive content (like games) to the users accessing the spatial anchor. Therefore, it is necessary to provide the desired quality of service and quality of experience to the user while accessing the spatial anchor services. Currently it does not provide the exposure for the application provider to indicate the Quality of Service (QoS) and Quality of Experience (QoE) of the services like associated with the spatial anchor(s).

[0024] 2. There are use cases like collaborative virtual meeting rooms consisting of whiteboards, erasers, markers, etc. which can have more than one spatial anchors. This creates the need to group or link the spatial anchor(s) associated with each other. Also in the collaborative environment, the information associated with the one or more than one spatial anchor may change dynamically, like the addition / removal / modification of a spatial anchor in a group. Currently there is no way to provide the linkage of spatial anchors.

[0025] 3. Certain spatial anchors need to be prioritized like emergency spatial anchors, medical services spatial anchors, etc. A large number of users accessing a spatial anchor and its services during peak time may lead to heavy load and bottleneck in the network and this can impact the delivery of services associated with other spatial anchors like medical services spatial anchor. This leads to the need to have spatial anchor service differentiation and delivery based on the priority information to provide or ensure the required QoS / QoE. Currently we cannot provide prioritization of spatial anchor and its services.

[0026] 4. Consider an example, in a mall, there can be various spatial anchors deployed by different application providers. Some spatial anchors like restrooms, fire exit, medical services, emergency exit, food court, etc. are common and domain-specific, i.e. applicable only to mall. Similarly, on road, there are common spatial anchors like gas station, hospital, etc. Such common spatial anchor(s) are universal spatial anchor. It might happen that certain spatial anchors could not be discovered and accessed by certain users due to lack of business agreement or SLA with the user and application provider. But for the universal spatial anchors, it shall be accessed and discovered by any user irrespective of SLA between the user and application provider. In the existing solution, we cannot provision universal spatial anchors and its context like applicable domain.

[0027] 5. The consumers created the spatial anchor may require analytics for various reasons like user engagement, spatial planning, spatial anchor improvement, etc. The existing solution cannot provide the analytics. An object herein is to provide a mechanism to provide a service in a communication network in an efficient manner.

[0028] According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a first network node, such as an SEAL LM client, a MMEC, a VAL server or a client node, for handling a service in a communication network. The first network node transmits a request to a second network node, wherein the request is related to one or more spatial anchors of a service; and receives a response from the second network node, wherein the response is related to the request transmitted.

[0029] According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a first network node, for handling services related to spatial anchors in a communication network. The first network node transmits a request to a second network node. The request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information, e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association, receives a response from the second network node, wherein the response is related to the request transmitted. The first network node then receives a response from the second network node, wherein the response is related to the request transmitted.

[0030] According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a second network node, such as a SEAL LM server, a MMES or a server node, for handling a service in a communication network. The second network node receives a request from a first network node, wherein the request is related to one or more spatial anchors of a service. The second network node further transmits a response to the first network node, wherein the response is related to the request received.

[0031] According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a second network node, for handling services related to spatial anchors in a communication network. The second network node receives a request from a first network node. The request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association,

[0032] The second network node then transmits a response to the first network node, wherein the response is related to the request received.

[0033] It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method herein, as performed by the first and second network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method herein, as performed by the first and second network node, respectively.

[0034] According to another aspect the object is achieved by providing a first network node and a second network node configured to perform the methods herein, respectively.

[0035] According to another aspect of embodiments herein, the object is achieved by providing a first network node, for handling services related to spatial anchors in a communication network. The first network node is configured to:

[0036] - Transmit a request to a second network node. The request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information, e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association. - Receive a response from the second network node, wherein the response is related to the request transmitted.

[0037] According to another aspect of embodiments herein, the object is achieved by providing a second network node for handling services related to spatial anchors in a communication network. The second network node is configured to:

[0038] - Receive a request from a first network node. The request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association.

[0039] - Transmit a response to the first network node, wherein the response is related to the request received.

[0040] Embodiments herein propose, e.g., provides, one or more of the following:

[0041] 1 . Create spatial anchor procedure. a. We propose, e.g., it is provided herein, the Linked spatial anchor to create a group of spatial anchors linked with each other and a linked group identifier to identify the group. This is e.g. related to embodiment b. We propose, e.g., it is provided herein, the indication of QoS of services associated with spatial anchor, priority requirements of the spatial anchor(s), spatial anchor context. The spatial anchor context includes spatial anchor visibility level like universal or non-universal, spatial anchor applicable domain information.

[0042] 2. Get Spatial anchor procedure, Spatial anchor information subscription procedure and Spatial anchor discovery procedure a. We propose, e.g., it is provided herein, the request for a recommended list of spatial anchor to get the recommendation of spatial anchor based on the discovery filter and stored spatial anchor list. b. We propose, e.g., it is provided herein, the retrieval of linked spatial anchors and details of each spatial anchor in the group in the response c. The response includes the prioritization information of the spatial anchor d. The response provides the list of spatial anchors whose visibility level is universal spatial anchor.

[0043] 3. Spatial anchor analytics information(request-response), spatial anchor analytics information(subscription-notify) a. We propose, e.g., it is provided herein, the analytics information request which includes analytics filter like the position of the user, location information, proximity distance, and application service identifier to filter the analytics information. b. The response message includes spatial anchor ID, number of times accessed, spatial anchor density per location, user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, spatial anchor services session time per user.

[0044] Embodiments herein provide one or more of the following advantages:

[0045] 1. Consumers can manage their linked spatial anchors, retrieve the grouped spatial anchors in one request, which saves multiple round trip to fetch each spatial anchor linked with each other. This improves the QoE of the users as all the linked spatial anchors can be rendered at once.

[0046] 2. The linked spatial anchor provides robustness for tracking the location as many markers are available for the group.

[0047] 3. The prioritization of the spatial anchor and its services enables the service differentiation even if the network serving is overloaded and maintain the desired QoS and QoE to the users.

[0048] 4. The universal spatial anchors like emergency exits, medical services etc. which may not be available to some users, can be available using the universal visibility of the spatial anchor context. This enables any user to access the common spatial anchor without any SLA or business relationships between application providers and users.

[0049] 5. The spatial anchor analytics information helps the consumers to plan their space, manage the spatial anchors, check user engagement, spatial planning, spatial anchor improvement, etc.

[0050] This will thus result in an improved performance of the communication network handling a service in the communication network. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

[0052] Fig. 1 shows a schematic architecture according to prior art;

[0053] Fig. 2 shows an overview depicting a communication network according to embodiments herein;

[0054] Fig. 3 shows a signalling scheme according to some embodiments herein;

[0055] Fig. 4 shows a signalling scheme according to some embodiments herein;

[0056] Fig. 5 shows a signalling scheme according to some embodiments herein;

[0057] Fig. 6 shows a signalling scheme according to some embodiments herein;

[0058] Fig. 7 shows a signalling scheme according to some embodiments herein;

[0059] Fig. 8 shows a signalling scheme according to some embodiments herein;

[0060] Fig. 9 shows a signalling scheme according to some embodiments herein;

[0061] Fig. 10 shows a signalling scheme according to some embodiments herein;

[0062] Fig. 11 shows a flowchart illustrating a method performed by a first network node according to embodiments herein;

[0063] Fig. 12 shows a flowchart illustrating a method performed by a second network node according to embodiments herein;

[0064] Fig. 13 shows a block diagram depicting a first network node according to embodiments herein;

[0065] Fig. 14 shows a block diagram depicting a second network node according to embodiments herein;

[0066] Fig. 15 schematically illustrates embodiments of a communication system,

[0067] Fig. 16 is a generalized block diagram of embodiments of a UE,

[0068] Fig. 17 is a generalized block diagram of embodiments of a network node, and

[0069] Fig. 18 is a generalized block diagram of embodiments of a virtualization environment.

[0070] DETAILED DESCRIPTION

[0071] Embodiments herein relate to communication networks in general. Fig. 2 is a schematic overview depicting a communication network 1. The communication network 1 comprises one or more RANs and one or more CNs. The communication network 1 may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further development of existing wireless communications systems such as e.g. Wi-Fi, LTE or Wideband Code Division Multiple Access (WCDMA).

[0072] In the communication network 1 , a user equipment (UE) 10, also referred to as a user, exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (ST A), a STA and / or a wireless terminal, is comprised communicating via e.g. one or more Access Networks (AN), e.g. radio access network (RAN), to one or more core networks (CN). It should be understood by the skilled in the art that “UE” is a nonlimiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB-loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.

[0073] The communication network 1 comprises a first radio network node 12 or just radio network node, providing radio coverage over a geographical area, a first service area 11 or first cell, of a first radio access technology (RAT), such as NR, LTE, or similar. The radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the first radio network node depending e.g. on the first radio access technology and terminology used. The first radio network node may be referred to as a serving radio network node wherein the service area may be referred to as a serving cell, and the serving network node communicates with the wireless device in form of DL transmissions to the wireless device and UL transmissions from the wireless device. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.

[0074] The communication network 1 comprises a second radio network node 13 or just radio network node, providing radio coverage over a geographical area, a second service area 14 or second cell, of a second radio access technology (RAT), such as NR, LTE, or similar. The radio network node may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP ST A), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the first radio network node depending e.g. on the first radio access technology and terminology used.

[0075] The communication network 1 may comprise a network comprising one or more network nodes. For example, a first network node 15 such as a vertical application layer (VAL) server or a SEAL client, SEAL location management (LM) client or a mobile metaverse enabler client (MMEC), and a second network node 16 such as a Service enabler architecture layer for verticals (SEAL) LM server, or a mobile metaverse enabler server (MMES). The different network nodes may have different tasks. Functions may be for LTE and / or NR.

[0076] The respective network node may be a standalone server, a cloud-implemented server, a distributed server or processing resources in a server farm or same node. Embodiments herein may be implemented as physical bare metal, virtual or cloud native such as Kubernetes environment in, e.g., hyper-cloud networks.

[0077] Embodiments herein propose, e.g. provide, that the first network node 15 transmits a request to the second network node 16 that responds with a response. The proposed embodiments cover one or more of the following:

[0078] 1 . Create spatial anchor procedure a. We propose, e.g. it is provided, the Linked spatial anchor to create a group of spatial anchors linked with each other and a linked group identifier to identify the group b. We propose, e.g. it is provided, the indication of QoS of services associated with spatial anchor, priority requirements of the spatial anchor(s), spatial anchor context. The spatial anchor context includes spatial anchor visibility level like universal or non-universal, spatial anchor applicable domain information

[0079] 2. Get Spatial anchor procedure, Spatial anchor information subscription procedure and Spatial anchor discovery procedure a. We propose, e.g. it is provided, the request for a recommended list of spatial anchors to get the recommendation of spatial anchor based on the discovery filter and stored spatial anchor list. b. We propose, e.g. it is provided, the retrieval of linked spatial anchors and details of each spatial anchor in the group in the response c. The response includes the prioritization information of the spatial anchor d. The response provides the list of spatial anchors whose visibility level is universal spatial anchor.

[0080] 3. Spatial anchor analytics information(request-response), spatial anchor analytics information(subscription-notify) a. We propose, e.g. it is provided, the analytics information request which includes analytics filter like the position of the user, location information, proximity distance, and application service identifier to filter the analytics information. b. The response message includes spatial anchor ID, number of times accessed, spatial anchor density per location, user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, spatial anchor services session time per user

[0081] Embodiments herein provide one or more of the following advantages:

[0082] 1. Consumers can manage their linked spatial anchors, retrieve the grouped spatial anchors in one request, which saves multiple round trip to fetch each spatial anchor linked with each other. This improves the QoE of the users as all the linked spatial anchors can be rendered at once.

[0083] 2. The linked spatial anchor provides robustness for tracking the location as many markers are available for the group.

[0084] 3. The prioritization of the spatial anchor and its services enables the service differentiation even if the network serving is overloaded and maintain the desired QoS and QoE to the users.

[0085] 4. The universal spatial anchors like emergency exits, medical services etc. which may not be available to some users, can be available using the universal visibility of the spatial anchor context. This enables any user to access the common spatial anchor without any SLA or business relationships between application providers and users.

[0086] 5. The spatial anchor analytics information helps the consumers to plan their space, manage the spatial anchors, check user engagement, spatial planning, spatial anchor improvement, etc. It should be noted that the word analytics when used herein includes both usage and prediction.

[0087] It should further be noted that a spatial anchor filter when used herein may be analytics filter or discovery filter.

[0088] Fig. 3 is an example of a combined flowchart and signaling scheme according to some embodiments herein.

[0089] Action 301. The first network node 15 transmits the request to the second network node 16, wherein the request is related to one or more spatial anchors of a service.

[0090] Action 302. The second network node 16 may handle the request.

[0091] Action 303. The second network node 16 further transmits a response to the first network node 15, wherein the response is related to the request received.

[0092] Embodiments cover one or more of the following, e.g. referred to as embodiments a) to f):

[0093] Title: Update to create spatial anchor solution

[0094] Spec: 3GPP TR 23.700-xx v0.2.0

[0095] Agenda item: 8.x

[0096] Document for: Approval

[0097] 1. Introduction

[0098] This pCR proposes a solution to KI#1

[0099] 2. Reason for Change

[0100] The spatial anchors can provide access to information or content services like multimedia content(video or audio or haptic), interactive content(like games) to the users accessing the spatial anchor. Therefore, it is necessary to provide the desired quality of service and quality of experience to the user while accessing the spatial anchor services. For example, in a museum, a spatial anchor can have multiple services like video, and haptic associated with it. Some users can choose only video services, others can select haptic services or a combination of all services simultaneously while accessing the spatial anchor at the same time. This creates the need for the enabler layer to provide the QoS / QoE to the users as per the services accessed. Moreover, certain spatial anchors need to be prioritized like emergency spatial anchors, medical services spatial anchors, etc. A large number of users accessing a spatial anchor and its services during peak time may lead to heavy load and bottleneck in the network and this can impact the delivery of services associated with other spatial anchors like medical services spatial anchor. This leads to the need to have spatial anchor service differentiation and delivery based on the priority information to provide or ensure the required QoS / QoE. There are use cases like collaborative virtual meeting rooms consisting of whiteboards, erasers, markers, etc. which can have more than one spatial anchors. This creates the need to group or link the spatial anchor(s) associated with each other. Also in the collaborative environment, the information associated with the one or more than one spatial anchor may change dynamically, like the addition / removal / modification of a spatial anchor in a group The group based operation of spatial anchor provides an easy management interface to the application providers like tracking of the spatial anchor as a group and not each spatial anchor.

[0101] Consider a example, in a mall, there can be various spatial anchors deployed by different application providers. Some spatial anchors like restrooms, fire exit, medical services, emergency exit, food court, etc. are common and domain-specific (i.e. applicable only to mall). Similarly, on road, there are common spatial anchors like gas station, hospital, etc.

[0102] Such common spatial anchor(s) are universal spatial anchor. It might happen that certain spatial anchors could not be discovered and accessed by certain users due to lack of business agreement or SLA with the user and application provider. But for the universal spatial anchors, it shall be accessed and discovered by any user irrespective of SLA between the user and application provider.

[0103] 3. Conclusions cConclusion part (optional)>

[0104] 4. Proposal

[0105] It is proposed to agree the following changes to 3GPP TR 23.700-82 v0.2.0.

[0106] Embodiment a).

[0107] First change

[0108] 7.2.3. 1 Creating spatial anchor

[0109] Figure 7.2.3.1-1 depicts the procedure for creating association of spatial anchor with location for metaverse applications. The service is provided by SEAL LM server and consumed by VAL server or SEAL LM client.

[0110] This is referred to as embodiment a) and is depicted in Figure 4 (7.2.3.1 -1 ): Create spatial anchor

[0111] 1) The VAL server (or SEAL LM client or MMEC) sends a request message to the SEAL LM server(or MMES) to create association of the spatial anchor with the location. The request includes VAL server identity, one or more than one position of the anchor and application service identifier, security credentials, spatial anchor service area. The request may include service information of the product to associate it with the spatial anchor, access control rules defining which entities are permitted to discover and access the spatial anchor. The request also includes the linked spatial anchor indicator to indicate the requested spatial anchors are linked with each other. The request also indicates the QoS, priority requirements of the spatial anchor(s), spatial anchor context. The spatial anchor context includes spatial anchor visibility level like universal or non-universal, spatial anchor applicable domain information.

[0112] 2) The SEAL LM server or MMES authorizes VAL server (or SEAL LM client). If the requestor is authorized, then the SEAL LM server creates the association between spatial anchor and the location, and stores the information as received in the request message. The server creates identity for the spatial anchor. If the request includes a linked spatial anchor indicator then the server creates the group of spatial anchors and provides a single identity for the spatial anchor group. The SEAL LM server or MMES sends the response back to the VAL server (or SEAL LM client or MMEC) including identity for the spatial anchor for a successful case. NOTE: The MMES or SEAL LM server may use the SEAL GM service for spatial anchor group management.

[0113] Title: Update to get solution

[0114] Spec: 3GPP TR 23.700-xx v0.2.0

[0115] Agenda item: 8.x

[0116] Document for: Approval

[0117] 1. Introduction

[0118] This pCR proposes solution to KI#1

[0119] 2. Reason for Change

[0120] The existing solution does not provide the prioritized list of spatial anchors and linked spatial anchors indicated by group of spatial anchors. Such information is necessary to provide the required QoE at the user end or client side. The group of spatial anchors reduces the client's round trip in fetching each spatial anchor which is helpful in the QoE for the users. Also, it provides the information to the client that the spatial anchors are linked to each other, which helps the client to render it correctly for the user perception. Consider the use case of supermarket metaverse, based on the purchase of item(s)(item is identified with a spatial anchor in the metaverse), the supermarket application can provide the list of recommended items for purchase to the user. This creates the need to provide the recommended list of other spatial anchors.

[0121] 3. Conclusions cConclusion part (optional)>

[0122] 4. Proposal

[0123] It is proposed to agree the following changes to 3GPP TR 23.700-82 v0.2.0.

[0124] Embodiment b).

[0125] First change:

[0126] 7.2.3.3 Get spatial anchor

[0127] Figure 7.x.3.3-1 depicts the procedure for getting spatial anchor details for metaverse applications. The service is provided by SEAL LM server and consumed by VAL server or SEAL LM client.

[0128] This is referred to as embodiment b) and is depicted in Figure 5 (7.2.3.3-1): Get spatial anchor

[0129] 1) The VAL server (or SEAL LM client or MMEC) sends a request message to the SEAL LM server or MMES to get the spatial anchor details. The request includes discovery filters like the position of the user and application service identifier. If the request to get specific spatial anchor, the request may include application specific information (e.g type of service). The request also includes recommended spatial anchors list indication.

[0130] 2) The SEAL LM server or MMES authorizes VAL server (or SEAL LM client or MMEC). If the requestor is authorized, then the SEAL LM server or MMES determines all spatial anchors from the repository based on the discovery filters provided in the request message. The SEAL LM server sends the response back to the VAL server (or SEAL LM client or MMEC) including a prioritized list of spatial anchor details for successful case. It also provides the linked id for grouped spatial anchor and details of each associated spatial anchor within the group. If the request provides the recommended spatial anchors list, then the SEAL LM server or MMES provides the recommended list of spatial anchor details based on the requested spatial anchor type of service information and the stored spatial anchor(s). The response also provides the list of spatial anchors whose visibility level is universal spatial anchor.

[0131] NOTE: The logic to provide a recommended list of spatial anchor details is implementationspecific and out of scope.

[0132] Embodiment c).

[0133] Next change

[0134] 7.2.3.4Spatial anchor information subscription

[0135] Figure 7.2.3.3-1 depicts the procedure for subscribing to receive spatial anchor details for metaverse applications. The service is provided by SEAL LM server and consumed by VAL server or SEAL LM client.

[0136] This is referred to as embodiment c) and is depicted in Figure 6. (7.2.3.4-1): Spatial anchor information subscription

[0137] 1) The VAL server (or SEAL LM client) sends a subscription request to the SEAL LM server to get notifications about the spatial anchor details. The request includes discovery filters like the position and application service identifier. If the request to subscribe to specific spatial anchor, the request may include application specific information (e.g type of service). The request also includes recommended spatial anchors list indication.

[0138] 2) The SEAL LM server authorizes VAL server (or SEAL LM client). If the requestor is authorized, then the SEAL LM server sends successful response along with subscription identity.

[0139] NOTE 1 : The SEAL LM server starts monitoring the location of the user if it is not already monitoring.

[0140] 3-4) Upon occurrence of the event (e.g. spatial anchor added or removed or updated), the SEAL LM server determines all spatial anchors from the repository which are matched with the discovery filters provided in the request. The SEAL LM server sends the notification to the VAL server (or SEAL LM client) including list of spatial anchor details and prioritization information of spatial anchors. It also provides the linked id for grouped spatial anchor and details of each associated spatial anchor within the group. If the request includes the recommended spatial anchors list, then the SEAL LM server or MMES provides the recommended list of spatial anchor details based on the requested spatial anchor (e.g. type of service information) and the stored spatial anchor(s). The response also provides the list of spatial anchors whose visibility level is universal spatial anchor.

[0141] NOTE: The logic to provide a recommended list of spatial anchor details is implementationspecific and out of scop

[0142] Title: New solution on spatial anchor analytics. Spec: 3GPP TR 23.700-xx v0.2.0

[0143] Agenda item: 8.x

[0144] Document for: Approval

[0145] 1. Introduction

[0146] This pCR proposes solution to KI#1

[0147] 2. Reason for Change

[0148] The consumers created the spatial anchor may require analytics for various reasons like user engagement, spatial planning, spatial anchor improvement, etc. The enabler layer can provide the analytics related to the spatial anchor to the consumers.

[0149] 3. Conclusions cConclusion part (optional)>

[0150] 4. Proposal

[0151] It is proposed to agree the following changes to 3GPP TR 23.700-82 v0.2.0.

[0152] First change

[0153] Embodiment di.

[0154] 7.x Solution #x: Support for spatial anchor analytics information

[0155] 7.x.1 Solution description

[0156] This solution maps to KI# 1.

[0157] 7.x.2 Procedures

[0158] 7.x.2.1 Spatial anchor analytics (Request-Response)

[0159] Figure 7.x.2.2-1 depicts the procedure for getting spatial anchor analytics for metaverse applications. The service is provided by Metaverse enabler server and consumed by VAL server.

[0160] This is referred to as embodiment d) and is depicted in Figure 7 (7.2.3.3-1) Spatial anchor analytics

[0161] 1) The VAL server sends a request message to the MMES to get the spatial anchor analytics information. The request includes analytics fdters like the position of the user, location information, proximity distance, application service identifier to fdter the analytics information, and e.g., discovery fdters.

[0162] 2) The MMES authorizes VAL server. If the requestor is authorized, then the SEAL LM server or MMES determines all spatial anchors from the repository based on the discovery fdters provided in the request message. The MMES sends the response back to the VAL server. The response message includes spatial anchor ID, number of times accessed, spatial anchor density per location, user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, spatial anchor services session time per user.

[0163] Next change

[0164] Embodiment e). 7.y.2.1 Spatial anchor analytics information (subscription-notify)

[0165] Figure 7. y.2.1-1 depicts the procedure for subscribing to receive spatial anchor analytics information for metaverse applications. The service is provided by MMES server and consumed by VAL server.

[0166] This is referred to as embodiment e) and is depicted in Figure 8 (7.2.3.4-1): Spatial anchor information subscription

[0167] 1) The VAL server sends a subscription request to the MMES server to get notifications about the spatial anchor analytics information. The request includes analtyics filters like the position of the user, location information, proximity distance, and application service identifier to filter the analytics information. It also includes the periodicity of notification, and analytics sampling interval.

[0168] 2) The MMES server authorizes VAL server. If the requestor is authorized, then the MMES sends a successful response along with the subscription identity.

[0169] 3) Based on the analytics sampling interval, the MMES generates the analytics based on the analytics filer. As per the periodicity of notification, the MMES sends the notification to the VAL server providing the spatial anchor analytics details. The response message includes spatial anchor ID, number of times accessed, spatial anchor density per location, user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, spatial anchor services session time per user

[0170] Update to discovery solution

[0171] Spec: 3GPP TR 23.700-xx v0.2.0

[0172] Agenda item: 8.x

[0173] Document for: Approval

[0174] >

[0175] 1. Introduction

[0176] This pCR proposes a solution to KI#1

[0177] 2. Reason for Change

[0178] The existing solution does not provide the prioritized list of spatial anchors, a universal list of spatial anchors to cater to common spatial anchors, and linked spatial anchors indicated by a group of spatial anchors. Such information is necessary to provide the required QoE at the user end or client side. The group of spatial anchors reduces the client's round trip in fetching each spatial anchor which is helpful in the QoE for the users. Also, it provides the information to the client that the spatial anchors are linked to each other, which helps the client render it correctly for the user perception.

[0179] Consider the use case of supermarket metaverse, based on the purchase of item(s)(item is identified with a spatial anchor in the metaverse), the supermarket application can provide the list of recommended items for purchase to the user. This creates the need to provide the recommended list of other spatial anchors.

[0180] 3. Conclusions cConclusion part (optional)>

[0181] 4. Proposal It is proposed to agree the following changes to 3GPP TR 23.700-82 v0.2.0.

[0182] First change Embodiment f).

[0183] 7.1.1.2 Procedure

[0184] Pre-conditions:

[0185] 1) Spatial anchors have been provisioned in the mobile metaverse enabler server

[0186] 2) A VAL client (e.g., an AR application) needs to display enriched localized content to a user

[0187] This is referred to as embodiment f) and is depicted in Figure 9 ( 7.1.1.2-1): Spatial anchor discovery procedure

[0188] 0. A metaverse VAL client discover s spatial anchors. The VAL client performs spatial anchor discovery using the mobile metaverse enabler client (MMEC) of the UE.

[0189] Editor’s Note: It is FFS whether and what spatial anchor requirements may be provided by a VAL client for spatial anchor discovery.

[0190] 1. The MMEC sends a spatial anchor discovery request to the mobile metaverse enabler server (MMES). The request includes information elements defined in Table 7.1.3-1.

[0191] 2. Upon receiving the request, the MMES validates if the requestor is authorized to discover spatial anchors. If the requestor is authorized, the MMES uses the information included the spatial anchor discovery request to determine spatial anchors to include in the discovery response.

[0192] If spatial anchor discovery filters are provided in the request, the MMES determines any spatial anchors matching the discovery filters. For each determined spatial anchor, the MMES checks whether the requestor is authorized to discover the spatial anchor based on the identity and location of the requestor and the access controls and service area characteristics of the spatial anchor. To determine a location of interest to the requestor, the MMES may use location information in the request, if available, or obtain location information by invoking the 3GPP Core Network Location Services exposed by the NEF as described in TS 23.273 [7] and TS 23.502 [9], or by invoking the SEAL Location Management APIs as described in TS 23.434 [8], Additionally, the MMES may obtain and consider data analytics, such as UE mobility prediction, during spatial anchor determination. The MMES may obtain data analytics by invoking NEF APIs as described in TS 23.288

[0010] and TS 23.502 [9], 3. The MMES sends a spatial anchor discovery response to the MMEC. If the MMES has successfully determined spatial anchors, the response may include a success indication, a list of the determined spatial anchors as defined in Table 7.1.3-2. If the MMES has not determined any spatial anchor, the response may include a failure indication and a cause of failure. The discovery response includes the prioritization information of the spatial anchor. If the recommended spatial anchor indication is provided in the request then the MMES uses the discovery filter information and stored spatial anchor information to provide the recommended list of spatial anchor in the discovery response. Also for linked spatial anchors, it provides the linked spatial anchor ID and details of each spatial anchor within the group. It also provides the universal spatial anchor details.

[0193] NOTE: The logic to generate the recommended list of spatial anchor is out of scope and implementation-specific.

[0194] 4. Upon receiving the discovery response, if the response indicates success, the MMEC may store the received spatial anchor information in a spatial anchor cache. The MMEC evaluates the validity conditions of discovered spatial anchors. 5. The MMEC provides the valid spatial anchor information to the VAL client(s) based on VAL client requirement(s). Upon receiving valid spatial anchor information, the VAL client can access the service(s) associated with each spatial anchor.

[0195] NOTE: This procedure may be adapted to allow a VAL server to discover spatial anchor(s). 7.1.2 Architecture Impacts

[0196] Option #1 in clause 6.1 is the basis for this solution.

[0197] 7.1.3 Corresponding APIs

[0198] Table 7. 1.3-1 shows the request sent by a MMEC to a MMES for the discovery of spatial anchor(s). Table 7.1.3-1: Spatial anchor discovery request

[0199] Table 7. 1.3-2 shows the response sent by the MetaApp server to the requester for a spatial anchor discovery request.

[0200] Table 7.1.3-2: Spatial anchor discovery response

[0201] Table 7.1.3-2-1 : Spatial anchor information Update to update solution

[0202] Spec: 3GPP TR 23.700-xx v0.2.0

[0203] Agenda item: 8.x

[0204] Document for: Approval

[0205] >

[0206] 1. Introduction

[0207] This pCR proposes solution to KI#1

[0208] 2. Reason for Change

[0209] The existing solution does not support the update of linked spatial anchor. The VAL server can modify the existing linked spatial anchor, delink the existing spatial anchor, and update the prioritization of the spatial anchor.

[0210] 3. Conclusions cConclusion part (optional)>

[0211] 4. Proposal

[0212] It is proposed to agree the following changes to 3GPP TR 23.700-82 v0.2.0.

[0213] First change

[0214] Embodiment a)

[0215] 7.2.3.2 Updating spatial anchor

[0216] Figure 7.2.3.2-1 depicts the procedure for updating spatial anchor association for metaverse applications. The update operation includes modifying existing spatial anchor or deleting the spatial anchor. The service is provided by SEAL LM server and consumed by VAL server or SEAL LM client.

[0217] This is referred to as embodiment g) and is depicted in Figure 10 (7.2.3.2-1): Update spatial anchor

[0218] 1) The VAL server (or SEAL LM client or MMEC) sends a request message to the SEAL LM server or MMES to update the existing spatial anchor association. The request is used to modify or delete the spatial anchor. The request message includes the identity of the spatial anchor and the application service identifier. To modify the spatial anchor, the request may include service information of the product to associate it with the spatial anchor. The request may include the modify linked spatial anchor indicator identity to update the existing group of spatial anchor with new spatial anchor information and delinked spatial anchor indicator to ungroup the spatial anchor. The request also includes the updated priority of the spatial anchor(s).

[0219] 2) The SEAL LM server or MMES authorizes VAL server (or SEAL LM client or MMEC). If the requestor is authorized, then the SEAL LM server or MMES checks whether the spatial anchor as identified by the identity of the spatial anchor exists or not. If the spatial anchor does not exists then the SEAL LM server sends failure response. Otherwise, the SEAL LM server updates the spatial anchor details (for update request) or deletes the spatial anchor details (for delete request). The SEAL LM server sends the response back to the VAL server (or SEAL LM client) including reason for failure for failure case., the MMES or SEAL server updates the existing group of spatial anchor(s) as per the modify linked spatial indicator and performs ungrouping of existing spatial anchor group as per the delink spatial anchor indicator. It also updates the priority of the spatial anchors as per the priority indicated in the request message.

[0220] The method actions performed by the first network node 15, such as an SEAL LM client, a MMEC, or a VAL server, for handling a service in the communication network 1 , for example, handling services related to spatial anchors, according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 11. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0221] Action 1101. The first network node 15 transmits a request to the second network node 16, wherein the request is related to one or more spatial anchors of a service.

[0222] Action 1102. The first network node 15 further receives a response from the second network node 16, wherein the response is related to the request transmitted.

[0223] Some further embodiments of Actions 1101 and 1102 will now be described.

[0224] Action 1101. The first network node 15 transmits a request to the second network node 16. The request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information, e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association.

[0225] In some embodiments of d) the first network node comprises a VAL server. In these embodiments, the request message to get the spatial anchor analytics information includes any one or more out of:

[0226] A filter (e.g. Discovery filters, and / or analytics filters) comprising the position of a user, location information, proximity distance, and an application service identifier to filter the analytics information such as e.g. spatial anchor usage information and / or predictive information. It should be noted that the wording filter, discovery filters, and analytics filters are deemed to be equal or similar and can be used interchangeably herein. In some embodiments of a) the request message to create association of the spatial anchor with the location includes a VAL server identity, one or more than one position of the anchor and application service identifier, security credentials, spatial anchor service area.

[0227] In some embodiments of b) the request message to get the spatial anchor details includes discovery filters comprising a position of the user and / or an application service identifier.

[0228] In some embodiments of c) the subscription request to get notifications about the spatial anchor details includes discovery filters like a position and application service identifier.

[0229] In some embodiments of e) the subscription request to get notifications about the spatial anchor analytics information includes analytics filters comprising a position of the user, and / or location information, and / or proximity distance, and / or application service identifier to filter the analytics information and / or the periodicity of notification, and / or analytics sampling interval.

[0230] In some embodiments of f) the spatial anchor discovery request includes information elements comprising a requestor identity and / or requestor security credentials and / or location of interest and / or spatial anchor discovery filters and / or recommended spatial anchor indication.

[0231] In some embodiments of g) the request message to update the existing spatial anchor association includes the identity of the spatial anchor and the application service identifier.

[0232] Action 1102. The first network node 15 receives a response from the second network node 16, wherein the response is related to the request transmitted.

[0233] In some embodiments of d): the response includes any one or more out of the following: a spatial anchor Identity, ID, number of times accessed, spatial anchor density per location, a user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, and spatial anchor services session time per user.

[0234] In some embodiments of d): the response is based on spatial anchors determined from a repository based on discovery filters provided in the request.

[0235] In some of these embodiments of d): the response is based on spatial anchors determined from a repository obtained data such as e.g. stored spatial anchor data, based on filters such as e.g. discovery filters provided in the request. The filter may be a discovery or analytics filter.

[0236] In some embodiments the first network node 15 comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, client, a Mobile Metaverse Enabler Client, MMEC, or a Vertical Application Layer, VAL, server. In some embodiments the second network node 16 comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, server, or a Mobile Metaverse Enabler Server, MMES.

[0237] The method actions performed by the second network node 16, such as a SEAL LM server or a MMES, for handling a service in the communication network 1 , for example, handling services related to spatial anchors, according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 12. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0238] Action 1201. The second network node 16 receives a request from the first network node 15, wherein the request is related to one or more spatial anchors of a service.

[0239] Action 1202. The second network node 16 further transmits a response to the first network node 15, wherein the response is related to the request received.

[0240] Some further embodiments of Actions 1201 and 1202 will now be described.

[0241] Action 1201. The second network node 16 receives a request from a first network node 15. The request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association. In some embodiments of d) the request message to get the spatial anchor analytics information includes any one or more out of:

[0242] Discovery filters, analytics filters comprising the position of a user, location information, proximity distance, and an application service identifier to filter the analytics information.

[0243] In some embodiments of d) the first network node 15 comprises a VAL server. In these embodiments, the second network node 16 further handles the request by: authorizing the VAL server, and if authorized, determining all spatial anchors from a repository based on discovery filters provided in the request message.

[0244] In some embodiments of a) the request message to create association of the spatial anchor with the location includes a VAL server identity, one or more than one position of the anchor and application service identifier, security credentials, spatial anchor service area.

[0245] In some embodiments of b) the request message to get the spatial anchor details includes discovery filters comprising a position of the user and / or an application service identifier.

[0246] In some embodiments of c) the subscription request to get notifications about the spatial anchor details includes discovery filters like a position and application service identifier.

[0247] In some embodiments of e) the subscription request to get notifications about the spatial anchor analytics information includes analytics filters comprising a position of the user, and / or location information, and / or proximity distance, and / or application service identifier to filter the analytics information and / or the periodicity of notification, and / or analytics sampling interval.

[0248] In some embodiments of f) the spatial anchor discovery request includes information elements comprising a requestor identity and / or requestor security credentials and / or location of interest and / or spatial anchor discovery filters and / or recommended spatial anchor indication.

[0249] In some embodiments of g) the request message to update the existing spatial anchor association includes the identity of the spatial anchor and the application service identifier.

[0250] Action 1202. The second network node 16 transmits a response to the first network node 15. The response is related to the request received.

[0251] In some embodiments of d) the first network node comprises a VAL server. In these embodiments the response includes any one or more out of: a spatial anchor Identity, ID, number of times accessed, spatial anchor density per location, a user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, and spatial anchor services session time per user.

[0252] In some embodiments the first network node 15 comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, client, a Mobile Metaverse Enabler Client, MMEC, or a Vertical Application Layer, VAL, server. In some embodiments the second network node 16 comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, server, or a Mobile Metaverse Enabler Server, MMES.

[0253] Fig. 13 shows a block diagram depicting the first network node 15 for handling a service in the communication network 1 , for example, handling service related to spatial anchors, according to embodiments herein.

[0254] The first network node 15 may comprise processing circuitry 1301 , e.g. one or more processors, configured to perform the methods herein.

[0255] The first network node 15 and / or processing circuitry 1301 is configured to transmit the request to the second network node 16, wherein the request is related to one or more spatial anchors of a service.

[0256] The first network node 15 and / or processing circuitry 1301 is further configured to transmit a request to a second network node 16. The request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information, e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association.

[0257] The first network node 15 and / or processing circuitry 1301 is configured to receive the response from the second network node 16, wherein the response is related to the request transmitted. In some embodiments of d), the first network node 15 comprises a VAL server. In these embodiments, the request message to get the spatial anchor analytics information includes any one or more out of:

[0258] Discovery filters, and / or analytics filters comprising the position of a user, location information, proximity distance, and an application service identifier to filter the analytics information.

[0259] In some embodiments of d): the response includes any one or more out of the following:

[0260] A spatial anchor Identity, ID, number of times accessed, spatial anchor density per location, a user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, and spatial anchor services session time per user.

[0261] In some embodiments of d): the response is based on spatial anchors determined from a repository based on discovery filters provided in the request.

[0262] In some embodiments of a) the request message to create association of the spatial anchor with the location includes a VAL server identity, one or more than one position of the anchor and application service identifier, security credentials, spatial anchor service area.

[0263] In some embodiments of b) the request message to get the spatial anchor details includes discovery filters comprising a position of the user and / or an application service identifier.

[0264] In some embodiments of c) the subscription request to get notifications about the spatial anchor details includes discovery filters like a position and application service identifier.

[0265] In some embodiments of e) the subscription request to get notifications about the spatial anchor analytics information includes analytics filters comprising a position of the user, and / or location information, and / or proximity distance, and / or application service identifier to filter the analytics information and / or the periodicity of notification, and / or analytics sampling interval.

[0266] In some embodiments of f) the spatial anchor discovery request includes information elements comprising a requestor identity and / or requestor security credentials and / or location of interest and / or spatial anchor discovery filters and / or recommended spatial anchor indication. In some embodiments of g) the request message to update the existing spatial anchor association includes the identity of the spatial anchor and the application service identifier.

[0267] In some embodiments the first network node comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, client, a Mobile Metaverse Enabler Client, MMEC, or a Vertical Application Layer, VAL, server.

[0268] In some embodiments the second network node comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, server, or a Mobile Metaverse Enabler Server, MMES.

[0269] The first network node 15 may comprise a memory 1303. The memory 1303 comprises one or more units to be used to store data on, such as spatial anchors information, service information, configuration, capabilities, indications, services, IDs, messages, thresholds, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the first network node 15 may comprise a communication interface 1304 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0270] The methods according to the embodiments described herein for the first network node 15 are respectively implemented by means of e.g. a computer program product 1305 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first network node 15. The computer program product 1305 may be stored on a computer-readable storage medium 1306, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1306, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first network node 15. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose the first network node 15 for handling communication in a communication network, wherein the first network node 15 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said first network node 15 is operative to perform any of the methods herein. Fig. 14 shows a block diagram depicting the second network node 16 for handling a service in the communication network 1 , for example, handling service related to spatial anchors, according to embodiments herein.

[0271] The second network node 16 may comprise processing circuitry 1401 , e.g. one or more processors, configured to perform the methods herein.

[0272] The second network node 16 and / or processing circuitry 1401 is configured to received the request from the first network node 15, wherein the request is related to one or more spatial anchors of a service.

[0273] The second network node 16 and / or processing circuitry 1401 is configured to transmit the response to the first network node, wherein the response is related to the request received.

[0274] The second network node 16 and / or processing circuitry 1401 is further configured to receive a request from a first network node. The request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association.

[0275] The second network node 16 and / or processing circuitry 1401 is further configured to transmit a response to the first network node 15, wherein the response is related to the request received.

[0276] In some embodiments of d) the request message to get the spatial anchor analytics information includes any one or more out of: discovery filters, analytics filters comprising the position of a user, location information, proximity distance, and an application service identifier to filter the analytics information.

[0277] In some embodiments of d) the first network node 15 comprises a VAL server. In these embodiments the second network node 16 is further being configured to: handle the request by: authorizing the VAL server, and if authorized, determining all spatial anchors from a repository based on discovery filters provided in the request message. In some embodiments of d) the first network node 15 comprises a VAL server. In these embodiments the response includes any one or more out of: a spatial anchor Identity, ID, number of times accessed, spatial anchor density per location, a user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, and spatial anchor services session time per user.

[0278] In some embodiments of a) the request message to create association of the spatial anchor with the location includes a VAL server identity, one or more than one position of the anchor and application service identifier, security credentials, spatial anchor service area.

[0279] In some embodiments of b) the request message to get the spatial anchor details includes discovery filters comprising a position of the user and / or an application service identifier.

[0280] In some embodiments of c) the subscription request to get notifications about the spatial anchor details includes discovery filters like a position and application service identifier.

[0281] In some embodiments of e) the subscription request to get notifications about the spatial anchor analytics information includes analytics filters comprising a position of the user, and / or location information, and / or proximity distance, and / or application service identifier to filter the analytics information and / or the periodicity of notification, and / or analytics sampling interval.

[0282] In some embodiments of f) the spatial anchor discovery request includes information elements comprising a requestor identity and / or requestor security credentials and / or location of interest and / or spatial anchor discovery filters and / or recommended spatial anchor indication.

[0283] In some embodiments of g) the request message to update the existing spatial anchor association includes the identity of the spatial anchor and the application service identifier.

[0284] In some embodiments the first network node comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, client, a Mobile Metaverse Enabler Client, MMEC, or a Vertical Application Layer, VAL, server.

[0285] In some embodiments the second network node comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, server, or a Mobile Metaverse Enabler Server, MMES. The second network node 16 may comprise a memory 1403. The memory 1403 comprises one or more units to be used to store data on, such as spatial anchors information, service information, configuration, capabilities, indications, services, IDs, messages, thresholds, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the second network node 16 may comprise a communication interface 1404 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0286] The methods according to the embodiments described herein for the second network node 16 are respectively implemented by means of e.g. a computer program product 1405 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second network node 16. The computer program product 1405 may be stored on a computer-readable storage medium 1406, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1406, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second network node 16. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose the second network node 16 for handling communication in a communication network, wherein the second network node 16 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said second network node 16 is operative to perform any of the methods herein.

[0287] In some embodiments a more general term “network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a UE and / or with another network node.

[0288] In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating .with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), loT capable device, machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc. Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and / or transmit signals (e.g. data) e.g. NR, Wi-Fi, LTE, LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0289] As will be readily understood by those familiar with communications design, that functions means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

[0290] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and / or program or application data. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0291] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0292] Fig. 15 shows an example of a communication system QQ100 in accordance with some embodiments.

[0293] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0294] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0295] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0296] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQUO and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0297] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more host computing systems, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0298] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ 102. The host QQ 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0299] As a whole, the communication system QQ100 of Figure 15 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0300] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0301] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0302] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0303] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0304] Fig. 16 shows a UE QQ200 in accordance with some embodiments. The UE QQ200 presents additional details of some embodiments of the UE QQ112 of Figure 15. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehiclemounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0305] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0306] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 16. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0307] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0308] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied. The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0309] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0310] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0311] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0312] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0313] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0314] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Fig. 16.

[0315] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0316] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0317] Fig. 17 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O- RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0318] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0319] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0320] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0321] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0322] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0323] The communication interface QQ306 is used in wired or wireless communication of signalling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0324] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0325] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0326] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0327] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0328] Embodiments of the network node QQ300 may include additional components beyond those shown in Fig. 17 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300. In some embodiments providing a core network node, such as core network node 108 of Fig. 15, some components, such as the radio front-end circuitry QQ318 and the RF transceiver circuitry QQ312 may be omitted.

[0329] Fig. 18 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0330] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0331] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0332] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0333] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0334] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signalling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0335] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0336] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0337] In some embodiments a more general term “network node” is used and it can correspond to any type of radio network node or any network node, which communicates with a wireless device and / or with another network node. Examples of network nodes are NodeB, Master eNB, Secondary eNB, a network node belonging to Master cell group (MCG) or Secondary Cell Group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node e.g. Mobility Switching Centre (MSC), Mobile Management Entity (MME) etc., Operation and Maintenance (O&M), Operation Support System (OSS), SelfOrganizing Network (SON), positioning node e.g. Evolved Serving Mobile Location Centre (E-SMLC), Minimizing Drive Test (MDT), etc.

[0338] In some embodiments, the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device-to-device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

[0339] The embodiments are described for 5G. However the embodiments are applicable to any RAT or multi-RAT systems, where the UE receives and / or transmit signals (e.g. data) e.g. LTE, LTE FDD / TDD, WCDMA / HSPA, GSM / GERAN, Wi Fi, WLAN, CDMA2000 etc.As will be readily understood by those familiar with communications design, functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

[0340] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0341] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

CLAIMS1 . A method performed by a first network node (15), for handling services related to spatial anchors in a communication network (1), the method comprising: transmitting (301 , 1101) a request to a second network node (16), wherein the request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information, e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association, and receiving (303, 1102) a response from the second network node (16), wherein the response is related to the request transmitted.

2. The method according to claim 1 , wherein the first network node (15) comprises a VAL server, and wherein d): the request message to get the spatial anchor analytics information includes any one or more out of: discovery filters, and / or analytics filters comprising the position of a user, location information, proximity distance, and an application service identifier to filter the analytics information.

3. The method according to any of the claims 1-2, wherein d): the response includes any one or more out of the following,: a spatial anchor Identity, ID, number of times accessed, spatial anchor density per location, a user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, and spatial anchor services session time per user.

4. The method according to claim 3, wherein d): the response is based on spatial anchors determined from a repository based on discovery filters provided in the request.

5. The method according to any of the claims 1-4, wherein any one or more out of: a) the request message to create association of the spatial anchor with the location includes a VAL server identity, one or more than one position of the anchor and application service identifier, security credentials, spatial anchor service area, b) the request message to get the spatial anchor details includes discovery filters comprising a position of the user and / or an application service identifier, c) the subscription request to get notifications about the spatial anchor details includes discovery filters like a position and application service identifier.

6. The method according to any of the claims 1-5, wherein any one or more out of: e) the subscription request to get notifications about the spatial anchor analytics information includes analytics filters comprising a position of the user, and / or location information, and / or proximity distance, and / or application service identifier to filter the analytics information and / or the periodicity of notification, and / or analytics sampling interval, f) the spatial anchor discovery request includes information elements comprising a requestor identity and / or requestor security credentials and / or location of interest and / or spatial anchor discovery filters and / or recommended spatial anchor indication. g) the request message to update the existing spatial anchor association includes the identity of the spatial anchor and the application service identifier.

7. The method according to any of the claims 1-6, wherein any one or more out of: the first network node (15) comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, client, aMobile Metaverse Enabler Client, MMEC, or a Vertical Application Layer, VAL, server, and the second network node (16) comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, server, a Mobile Metaverse Enabler Server, MMES.

8. The method according to claim 1 , wherein b): the response message provides a list of spatial anchors whose visibility level is universal spatial anchor.

9. The method according to claim 1 , wherein f): the response message provides a recommended list of spatial anchor in the discovery response.

10. A method performed by a second network node (16), for handling services related to spatial anchors in a communication network (1), the method comprising: receiving (301 , 1201) a request from a first network node (15), wherein the request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association, and transmitting (303, 1202) a response to the first network node (15), wherein the response is related to the request received.

11. The method according to claim 10, wherein d):the request message to get the spatial anchor analytics information includes any one or more out of: discovery filters, analytics filters comprising the position of a user, location information, proximity distance, and an application service identifier to filter the analytics information.

12. The method according to any of the claims 10-11 , wherein the first network node (15) comprises a VAL server, the method further comprising d): handling (302) the request by: authorizing the VAL server, and if authorized, determining all spatial anchors from a repository based on discovery filters provided in the request message.

13. The method according to any of the claims 10-12, wherein the first network node (15) comprises a VAL server, and wherein d): the response includes any one or more out of: a spatial anchor Identity, ID, number of times accessed, spatial anchor density per location, a user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, and spatial anchor services session time per user.

14. The method according to any of the claims 10-13, wherein any one or more out of: a) the request message to create association of the spatial anchor with the location includes a VAL server identity, one or more than one position of the anchor and application service identifier, security credentials, spatial anchor service area, b) the request message to get the spatial anchor details includes discovery filters comprising a position of the user and / or an application service identifier. c) the subscription request to get notifications about the spatial anchor details includes discovery filters like a position and application service identifier.

15. The method according to any of the claims 10-14, wherein any one or more out of:e) the subscription request to get notifications about the spatial anchor analytics information includes analytics filters comprising a position of the user, and / or location information, and / or proximity distance, and / or application service identifier to filter the analytics information and / or the periodicity of notification, and / or analytics sampling interval, f) the spatial anchor discovery request includes information elements comprising a requestor identity and / or requestor security credentials and / or location of interest and / or spatial anchor discovery filters and / or recommended spatial anchor indication, g) the request message to update the existing spatial anchor association includes the identity of the spatial anchor and the application service identifier.

16. The method according to any of the claims 10-15, wherein any one or more out of: the first network node (15) comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, client, a Mobile Metaverse Enabler Client, MMEC, or a Vertical Application Layer, VAL, server, and the second network node (16) comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, server, a Mobile Metaverse Enabler Server, MMES.

17. The method according to claim 10, wherein b): the response message provides a list of spatial anchors whose visibility level is universal spatial anchor.

18. The method according to claim 10, wherein f): the response message provides a recommended list of spatial anchor in the discovery response.

19. A first network node (15), for handling services related to spatial anchors in a communication network (1), wherein the first network node (15) is configured to:transmit a request to a second network node (16), wherein the request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information, e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association, and receive a response from the second network node (16), wherein the response is related to the request transmitted.

20. The first network node (15) according to claim 19, wherein the first network node (15) comprises a VAL server, and wherein d): the request message to get the spatial anchor analytics information includes any one or more out of: discovery filters, and / or analytics filters comprising the position of a user, location information, proximity distance, and an application service identifier to filter the analytics information.

21. The first network node (15) according to any of the claims 19-20, wherein d): the response includes any one or more out of the following: a spatial anchor Identity, ID, number of times accessed, spatial anchor density per location, a user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, and spatial anchor services session time per user.

22. The first network node (15) according to claim 21 , wherein d): the response is based on spatial anchors determined from a repository based on discovery filters provided in the request.

23. The first network node (15) according to any of the claims 19-22, wherein any one or more out of: a) the request message to create association of the spatial anchor with the location includes a VAL server identity, one or more than one position of the anchor and application service identifier, security credentials, spatial anchor service area, b) the request message to get the spatial anchor details includes discovery filters comprising a position of the user and / or an application service identifier, c) the subscription request to get notifications about the spatial anchor details includes discovery filters like a position and application service identifier.

24. The first network node (15) according to any of the claims 19-23, wherein any one or more out of: e) the subscription request to get notifications about the spatial anchor analytics information includes analytics filters comprising a position of the user, and / or location information, and / or proximity distance, and / or application service identifier to filter the analytics information and / or the periodicity of notification, and / or analytics sampling interval, f) the spatial anchor discovery request includes information elements comprising a requestor identity and / or requestor security credentials and / or location of interest and / or spatial anchor discovery filters and / or recommended spatial anchor indication, g) the request message to update the existing spatial anchor association includes the identity of the spatial anchor and the application service identifier.

25. The first network node (15) according to any of the claims 19-24 wherein any one or more out of: the first network node (15) comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, client, a Mobile Metaverse Enabler Client, MMEC, or a Vertical Application Layer, VAL, server, and the second network node (16) comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, server, a Mobile Metaverse Enabler Server, MMES.

26. The first network node (15) according to claim 19, wherein b): the response message provides a list of spatial anchors whose visibility level is universal spatial anchor.

27. The first network node (15) according to claim 19, wherein f): the response message provides a recommended list of spatial anchor in the discovery response.

28. A second network node (16), for handling services related to spatial anchors in a communication network (1), wherein the second network node (16) is configured to: receive a request from a first network node (15), wherein the request is related to one or more spatial anchors of a service comprising one or more of the following: a) a request message to create association of the spatial anchor with a location, b) a request message to get spatial anchor details, c) a subscription request to get notifications about spatial anchor details, d) a request message to get spatial anchor analytics information e) a subscription request to get notifications about the spatial anchor analytics information, f) a spatial anchor discovery request, g) a request message to update the existing spatial anchor association, and transmit a response to the first network node (15), wherein the response is related to the request received.

29. The second network node (16) according to claim 28, wherein d): the request message to get the spatial anchor analytics information includes any one or more out of: discovery filters, analytics filters comprising the position of a user, location information, proximity distance, and an application service identifier to filter the analytics information.

30. The second network node (16) according to any of the claims 28-29, wherein the first network node (15) comprises a VAL server, the second network node further being configured to d): handle the request by: authorizing the VAL server, and if authorized, determining all spatial anchors from a repository and based on discovery filters provided in the request message.

31. The second network node (16) according to any of the claims 28-30, wherein the first network node (15) comprises a VAL server, and wherein d): the response includes any one or more out of: a spatial anchor Identity, ID, number of times accessed, spatial anchor density per location, a user density per spatial anchor, number of users accessed per spatial anchor, spatial anchor services accessed information, and spatial anchor services session time per user.

32. The second network node (16) according to any of the claims 28-31 , wherein any one or more out of: a) the request message to create association of the spatial anchor with the location includes a VAL server identity, one or more than one position of the anchor and application service identifier, security credentials, spatial anchor service area, b) the request message to get the spatial anchor details includes discovery filters comprising a position of the user and / or an application service identifier. c) the subscription request to get notifications about the spatial anchor details includes discovery filters like a position and application service identifier.

33. The second network node (16) according to any of the claims 28-32, wherein any one or more out of: e) the subscription request to get notifications about the spatial anchor analytics information includes analytics filters comprising a position of the user, and / or location information, and / or proximity distance, and / or application service identifier to filter the analytics information and / or the periodicity of notification, and / or analytics sampling interval,,f) the spatial anchor discovery request includes information elements comprising a requestor identity and / or requestor security credentials and / or location of interest and / or spatial anchor discovery filters and / or recommended spatial anchor indication, g) the request message to update the existing spatial anchor association includes the identity of the spatial anchor and the application service identifier.

34. The second network node (16) according to any of the claims 28-33, wherein any one or more out of: the first network node (15) comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, client, a Mobile Metaverse Enabler Client, MMEC, or a Vertical Application Layer, VAL, server, and the second network node (16) comprises any one out of a Service Enablement Architecture Layer for Verticals Location Management, SEAL LM, server, a Mobile Metaverse Enabler Server, MMES.

35. The second network node (16) according to claim 28, wherein b): the response message provides a list of spatial anchors whose visibility level is universal spatial anchor.

36. The second network node (16) according to claim 28, wherein f): the response message provides a recommended list of spatial anchor in the discovery response.

37. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-18, as performed by the first network node (15) and the second network node (16), respectively.

38. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-18, as performed by the first network node (15) and the second network node (16), respectively.

Images