hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.3.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.3.3.1 Spatial anchor usage information request
|
Table 8.4.3.3.1-1 describes information elements for the spatial anchor usage information request from the consumer to the SAn server.
Table 8.4.3.3.1-1: Spatial anchor usage information request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server).
Security credentials
M
The security credentials of the requestor.
Spatial anchor filters
M
Indicates the spatial anchor filter for the information
> Spatial anchor identifiers
O
Indicates the spatial anchor identities
> Spatial anchor location information
O
Indicates the spatial anchor location information
> Area information
O
Indicates the area information (e.g., location information)
> Application service information
O
Indicates the application service information(e.g., application identifier)
NOTE: Spatial anchor filters IE must include at least one optional IE.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.3.3.2 Spatial anchor usage information response
|
Table 8.4.3.3.2-1 describes information elements for the spatial anchor usage information response from the SAn server to the consumer.
Table 8.4.3.3.2-1: Spatial anchor usage information response
Information element
Status
Description
Successful response
O
Indicates that the request was successful.
> Spatial anchor identifiers
M
Indicates the spatial anchor identities
> Spatial anchor usage information
M
Indicates spatial anchor usage information. It includes number of times spatial anchor discovered and accessed, spatial anchor services accessed information.
> Spatial anchor density per location
M
Indicates the density of the spatial anchor in the given area.
> User density per spatial anchor
M
Indicates the density of users within proximity to a specific spatial anchor.
Failure response
O
Indicates that the request has failed.
> Cause
O
The cause for the request failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.4 Spatial anchor usage reporting
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.4.1 General
|
Spatial anchor usage reporting enables a spatial anchor consumer (e.g., SAn client or VAL server) to report spatial anchor usage to the SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.4.2 Procedure
|
Figure 8.4.4.2-1 illustrates the spatial anchor usage reporting procedure.
Pre-conditions:
1. The SAn client or VAL server has received information (e.g. URI, IP address) related to the SAn server;
2. The SAn client or VAL server has received security credentials authorizing it to communicate with the SAn server.
Figure 8.4.4.2-1: Spatial anchor usage reporting
1. The requestor (e.g., SAn client or VAL server) sends a spatial anchor usage report request to the SAn server. The request includes a requestor identifier, security credentials, and spatial anchor usage information as described in clause 8.4.4.3.1.
2. Upon receiving the request, the SAn server validates if the requestor is authorized for the request. If the requestor is authorized, the SAn server updates the spatial anchor usage information. The SAn server uses the spatial anchor usage information when notifying subscribers(s) as specified in clause 8.4.2.2.
3. The SAn server sends a spatial anchor usage report response to the requestor. If the SAn server successfully stored the spatial anchor usage information, the response includes an indication of success. Otherwise, the response includes an indication of failure and can include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.4.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.4.3.1 Spatial anchor usage report request
|
Table 8.4.4.3.1-1 describes information elements for the spatial anchor usage report request from the SAn client or VAL server to the SAn server.
Table 8.4.4.3.1-1: Spatial anchor usage report request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL UE and VAL user).
Security credentials
M
The security credentials of the requestor.
List of spatial anchor usage information
M
List of usage information for spatial anchors.
> Spatial anchor ID
M
Identifier of the spatial anchor.
> Number of access
M
The number of times the spatial anchor was accessed.
> Report period
O
The time period for which the number of access applies. If omitted, the number of access is the number of access since the last spatial anchor usage report request.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.4.3.2 Spatial anchor usage report response
|
Table 8.4.4.3.2-1 describes information elements for the spatial anchor usage report response from the SAn server to the SAn client or VAL server.
Table 8.4.4.3.2-1: Spatial anchor usage report response
Information element
Status
Description
Successful response
O
Indicates that the spatial anchor usage report request was successful.
Failure response
O
Indicates that the spatial anchor usage report request has failed.
> Cause
O
The cause for the request failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5 SEAL APIs for spatial anchor management
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.1 General
|
Table 8.5.1-1 illustrates the SEAL APIs for spatial anchor management.
Table 8.5.1-1: List of SEAL APIs for spatial anchor management
API Name
API Operations
Known Consumer(s)
Communication Type
SS_SAnManagement
Create
VAL server, SAn client
Request/Response
Update
VAL server, SAn client
Delete
VAL server, SAn client
Get
VAL server, SAn client
Subscribe
VAL server, SAn client
Subscribe/Notify
Notify
VAL server, SAn client
UpdateSubscription
VAL server, SAn client
Unsubscribe
VAL server, SAn client
SS_SAnDiscovery
Request
SAn client, VAL server
Request/Response
SS_SAnUsageInfo
Request
VAL server
Request/Response
Subscribe
VAL server
Subscribe/Notify
Notify
VAL server
SS_SAnUsageReport
Request
VAL server, SAn client
Request/Response
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2 SS_SAnManagement API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2.1 General
|
Service description: This API enables a VAL server (or SAn client) to manage spatial anchors on SEAL SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2.2 Create operation
|
API operation name: SS_SAnManagement_Create
Description: The consumer requests to create spatial anchors.
Known Consumers: VAL server, SAn client.
Inputs: See Table 8.3.1.3.1-1.
Outputs: See Table 8.3.1.3.2-1.
See clause 8.3.1 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2.3 Update operation
|
API operation name: SS_SAMnanagement_Update
Description: The consumer requests to update spatial anchors.
Known Consumers: VAL server, SAn client.
Inputs: See Table 8.3.2.3.1-1.
Outputs: See Table 8.3.2.3.2-1.
See clause 8.3.2 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2.4 Delete operation
|
API operation name: SS_SAnManagement_Delete
Description: The consumer requests to delete spatial anchors.
Known Consumers: VAL server, SAn client.
Inputs: See Table 8.3.3.3.1-1.
Outputs: See Table 8.3.3.3.2-1.
See clause 8.3.3 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2.5 Retrieve operation
|
API operation name: SS_SAnManagement_Retrieve
Description: The consumer requests to get spatial anchor profile.
Known Consumers: VAL server, SAn client.
Inputs: See Table 8.3.6.3.1-1.
Outputs: See Table 8.3.6.3.2-1.
See clause 8.3.6 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2.6 Subscribe operation
|
API operation name: SS_SAnManagement_Subscribe
Description: The consumer subscribes for spatial anchors information.
Inputs: See clause 8.3.5.3.1.
Outputs: See clause 8.3.5.3.2.
See clause 8.3.5.2.1 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2.7 Notify operation
|
API operation name: SS_SAnManagement_Notify
Description: The consumer is notified with spatial anchors information.
Inputs: See clause 8.3.5.3.3.
Outputs: None.
See clause 8.3.5.2.2 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2.8 UpdateSubscription operation
|
API operation name: SS_SAnManagement_UpdateSubscription
Description: The consumer updates an existing subscription for spatial anchors information.
Inputs: See clause 8.3.5.3.4.
Outputs: See clause 8.3.5.3.5.
See clause 8.3.5.2.3 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.2.9 Unsubscribe operation
|
API operation name: SS_SAnManagement_Unsubscribe
Description: The consumer cancels an existing subscription for spatial anchors information.
Inputs: See clause 8.3.5.3.6.
Outputs: See clause 8.3.5.3.7.
See clause 8.3.5.2.4 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.3 SS_SAnDiscovery API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.3.1 General
|
Service description: This API enables a VAL server or SAn client to discover spatial anchors from SEAL SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.3.2 Request operation
|
API operation name: SS_SAnDiscovery_Request
Description: The consumer requests to discover spatial anchors.
Known Consumers: VAL server, SAn client.
Inputs: See Table 8.3.4.3.1-1.
Outputs: See Table 8.3.4.3.2-1.
See clause 8.3.4 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.4 SS_SAnUsageInfo API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.4.1 General
|
Service description: This API enables a VAL server to get spatial anchor usage information from the SEAL SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.4.2 Request operation
|
API operation name: SS_SAnUsageInfo_Request
Description: The consumer requests for spatial anchors usage information.
Inputs: See clause 8.4.3.3.1.
Outputs: See clause 8.4.3.3.2.
See clause 8.4.3 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.4.3 Subscribe operation
|
API operation name: SS_SAnUsageInfo_Subscribe
Description: The consumer subscribes for spatial anchors usage information.
Inputs: See clause 8.4.2.3.1.
Outputs: See clause 8.4.2.3.2.
See clause 8.4.2.2 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.4.4 Notify operation
|
API operation name: SS_SAnUsageInfo_Notify
Description: The consumer is notified with spatial anchors usage information.
Inputs: See clause 8.4.2.3.3.
Outputs: None.
See clause 8.4.2.2 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.5 SS_SAnUsageReport API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.5.1 General
|
Service description: This API enables a VAL server or SAn client to report spatial anchor usage information to the SEAL SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.5.5.2 Request operation
|
API operation name: SS_SAnUsageReport_Request
Description: The consumer provides spatial anchors usage information.
Inputs: See clause 8.4.4.3.1.
Outputs: See clause 8.4.4.3.2.
See clause 8.4.4 for details of usage of this operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9 Spatial Map (SM) management
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.1 General
|
The Spatial Map (SM) management is a SEAL service that offers the spatial map related capabilities to vertical application(s).
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2 Functional model for spatial map management
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.1 General
|
The functional model for the spatial map server is based on the generic functional model specified in clause 6 of 3GPP TS 23.434 [4]. It is organized into functional entities to describe a functional architecture which addresses the support for spatial map aspects for vertical applications.This clause provides architecture for spatial map (SM) service. The on-network functional model is specified in clause 9.2.2, and service based architecture is specified in clause 9.2.3.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2 On-network functional model description
|
Figure 9.2.2-1 illustrates an on-network functional model for spatial map (SM) service.
Figure 9.2.2-1: On-network spatial map functional model
The Spatial map management functional entities are grouped into the vertical application layer and the Service Enabler Architecture Layer (SEAL) layer. The Spatial map management offers the capabilities to manage spatial map to the vertical application layer. The Spatial map management functional model is based on SEAL layer as specified in 3GPP TS 23.434 [4].
The Spatial map functional entities on the UE and in the network are respectively the spatial map (SM) client and spatial map (SM) server. The VAL client and VAL server are application client and server respectively to provide an application service to the user. The SM client and SM server provides client and server side functionalities respectively for managing spatial map for the application. The SM client is a SEAL client providing spatial map service to VAL client. The SM server is a SEAL server providing spatial map service to VAL server and UE. The interface between SM Client and SM Server is SM-UU. The SM client interacts with the VAL client using a SM-C interface. The SM server interacts with the VAL server using a SM-S. The SM server communicates with the underlying 3GPP network system (either directly or via NEF) using 3GPP interfaces specified by the 3GPP network system (e.g. T8, N33). When SM server is deployed by PLMN operator, the SM server communicates with 3GPP network system by directly invoking the APIs from exposed by 3GPP core network functions.
The SM server interacts with SAn server over SEAL-X (AnM) reference point as specified in clause 8.2.2.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2.1 Functional Elements
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2.1.1 Spatial map (SM) server
|
The SM server acts as a SEAL server and it is used to provide services to create/update/delete/discover spatial map for the VAL application (i.e. metaverse application) and also provides spatial localization service. It can communicate with other SM server in the distributed SEAL deployments.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2.1.2 Spatial map (SM) client
|
The SM client acts as a SEAL client for spatial map function. It supports client side functionalities for creating/updating/deleting/discovering/retrieving spatial map for VAL application (i.e. metaverse application) and also provides spatial localization service. The SM client receives the request from VAL client to perform specific functionality.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2.1.3 VAL server
|
The VAL server is specified in clause 6.4.2.3 of 3GPP TS 23.434 [4]. The VAL server provides the server side functionalities corresponding to the vertical applications (i.e. metaverse applications) to the client of a VAL user based on a service contract.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2.1.4 VAL client
|
The VAL client is specified in clause 6.4.2.2 of 3GPP TS 23.434 [4]. The VAL client provides a metaverse services to the user. It uses the SM client to manage spatial maps for the application.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2.2 Reference Points
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2.2.1 SM-UU
|
SM-UU reference point enables interactions between a SM client and SM server. It is used to create/update/delete/discover/retrieve spatial map for the VAL applications (i.e. metaverse applications).
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2.2.2 SM-S
|
SM-S reference point enables interactions between a SM server and VAL servers (i.e. metaverse application servers). It can be used to create/update/delete/get/retrieve spatial map for the VAL applications (i.e. metaverse applications).
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.2.2.3 SM-C
|
SM-C reference point enables interactions between a SM client and VAL clients (i.e. metaverse application clients). It is used by the VAL client to share information regarding spatial maps related information to the SM client and also to get spatial maps related information from the SM client.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.2.3 Service based architecture
|
Figure 9.2.3-1 illustrates the service-based SEAL architecture to support spatial map services.
Figure 9.2.3-1: Service based architecture for spatial map
The SM server exposes the APIs over the Ssm interface to the VAL server and SM client. The VAL servers consume the services by interacting on the Ssm interface of the SM server. The CAPIF can be used by VAL functions to discover the services of the SM server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3 Spatial map management procedures
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.1 Create spatial map
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.1.1 General
|
The create spatial map procedure enables the consumers to request the SEAL SM Server to create spatial map of the area of interest.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.1.2 Procedure
|
Figure 9.3.1.2-1 depicts the procedure for creating a spatial map. For the request from VAL server or SEAL SM client, as a spatial map consumer, SEAL SM server creates a spatial map. A spatial map can be structured in layers where each layer signifies a specific aspect of the spatial information (e.g. three dimensional space of area of interest, objects).
Figure 9.3.1.2-1: Create spatial map procedure
1) The requestor (e.g., VAL server or SEAL SM client) sends a request message to the SEAL SM server to create a spatial map. The request includes requestor ID, security credentials, three-dimensional area of interest, information to be included in the spatial map such as allowed entities list defining which entities are permitted to discover and access the spatial map. The request may include spatial map layering information parameters and may also include augmented layer information that can be requested with the spatial map.
NOTE: SEAL SM server can obtain augmented layer information and can provide the obtained augmented layer information to the requestor in the response message.
2) The SEAL SM server authorizes the requestor, and validates the request. The SEAL SM server produces a requested spatial map using layering information and processed sensor data.
a) If the augmented layer information indicates to include VAL UE information, the SEAL SM server fetches the list of VAL UEs in the area of interest from LM server using clause 9.3.10 of 3GPP TS 23.434 [4] and/or from NEF as specified in 3GPP TS 23.502 [5].
b) If the augmented layer information indicates to include spatial anchors information within area of interest, the SEAL SM server fetches the list of spatial anchors in the area of interest as specified in clause 8.3.4.
NOTE: For the current release, the processed sensor data is stored at VAL layer (e.g., in database at VAL layer) and the SEAL SM server gets access to such database to create a spatial map via application specific way which is out of scope.
3) The SEAL SM server sends response message to the requestor with a indication of success, in-progress or fail. If the requested spatial map has been created sussesfully, the response message includes assigned spatial map ID and information which includes three-dimensional space defined by the spatial map and can include a list of spatial map layers with their corresponding layer ID, objects belong to the layer, etc.. If the response indicates "in-progress", an assigned spatial map ID is included in the message. Further, if the response indicates "in-progress" and the requestor has not provided a notification target address, then the requestor subscribes for spatial map event to receive notification when the spatial map is created. Otherwise, the response includes an indication of failure and may include a reason for the failure.
4) If the response indicates "in-progress", the SM server detects when the SEAL SM server has sufficient information to map all the objects related to area of interest and the spatial map is ready to provide service (e.g. employed for localization). If the requestor has provided a notification target address in the request or has subscribed for spatial map events, the SEAL SM server notifies the requestor with the spatial map ready notification message. The notification includes parameters as specifed in Table 9.3.6.3.3-1.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.1.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.1.3.1 Create spatial map request
|
Table 9.3.1.3.1-1 descibes the information elements from VAL server (or SEAL SM client) to SM server for create spatial map request.
Table 9.3.1.3.1-1: Create spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or VAL User or VAL UE)
Requestor security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Area of interest
M
Three-dimensional area information to produce the spatial map
Notification Target Address
O
Notification target address (e.g. URL, URI, IP) where the notifications should be sent.
Information to include
O
Information to be included in the spatial map
> Allowed entities list
O
Identity of entities (e.g. VAL client, VAL server or VAL service identity) which are permitted to discover and access the spatial map
> List of spatial map layers
O
List of spatial map layer information. Each element includes the information described below.
>> Spatial map layer information
O
Information to specify the corresponding spatial map layer specific information
> Augmented layer information
O
List of required augmented layer information. This IE can contain multiple values. Possible values are:
- VAL_USERS;
- SPATIAL_ANCHORS.
NOTE 1: For the current release, the spatial map layer information is implementation specific and out of scope.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.1.3.2 Create spatial map response
|
Table 9.3.1.3.2-1 descibes the information elements for create spatial map response from SM server to VAL server or SM client.
Table 9.3.1.3.2-1: Create spatial map response
Information element
Status
Description
Application service ID
O
ID of the requesting VAL application service
Success response
O
(NOTE)
Information on the created spatial map. It contains information as specified in Table 7.3.3.1-1.
> Spatial map information
M
The information about the created spatial map as described in Table 7.3.3.1-1.
> Augmented layer information
O
Augmented layer information provided by SM server
Failure response
O
(NOTE)
Indicates failed create spatial map
> Cause
O
Cause of the failure
NOTE: At least one of the information elements shall be provided.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.2 Discover spatial map
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.2.1 General
|
The discover spatial map procedure enables the consumers to request the SEAL SM Server to discover either spatial maps or SMAS of the area of interest.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.2.2 Procedure
|
Figure 9.3.2.2-1 depicts the procedure for an authorized spatial map consumer (VAL server or SEAL SM client) to discover either spatial map(s) or SMAS. The service is provided by SEAL SM server.
Figure 9.3.2.2-1: Discover spatial map procedure
1) The requestor (e.g.,VAL server or SEAL SM client) sends a request message to the SEAL SM server to discover spatial map(s). The request includes requestor ID, security credentials, three-dimensional area of interest or localization information to discover spatial maps in the area, optional discovery filters, i.e., a set of characteristics (e.g., a list of specific spatial map layers) to search the matching spatial maps when multiple spatial maps are allowed in the area of interest.
NOTE 1: How the requestor identifies the three-dimensional area of interest is implementation specific.
2) The SEAL SM server authorizes the requestor, and validates the request. If the request is authorized, the SEAL SM server determines the spatial map(s) available with it according to the requested filtering criteria. If no spatial map determined for the requeted area of interest, the SEAL SM server determines the SMAS registered with the SEAL SM server according to the requested filtering criteria.
3) The SEAL SM server sends the discover spatial map response message to the requestor. If the request was succesful, the response includes an indication of success and the determined spatial map information or SMAS profile(s), otherwise the response includes an indication of failure and may include a failure reason.
NOTE 2: The requestor can discover APIs associated with SMAS(s) via CAPIF as specified in 3GPP TS 23.222 [7].
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.2.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.2.3.1 Discover spatial map request
|
Table 9.3.2.3.1-1 descibes the information elements from VAL server (or SEAL SM client) to SEAL SM server for discover spatial map request.
Table 9.3.2.3.1-1: Discover spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or VAL User or VAL UE)
Requestor security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Filtering criteria
M
Criteria to get spatial map(s)
> Area of interest
O
(NOTE)
Three-dimensional area information to discover spatial maps
> Location information
O
(NOTE)
Location, orientation and pose information that is used to identify relevant spatial maps.
> Optional discovery filters
O
A set of characteristics to search the matching spatial maps
>> List of spatial map layers
O
The list of spatial map layers to discover spatial map(s) with matching layers. Each element includes the information described below.
>>> Spatial map layer information
O
Information to specify the corresponding spatial map layer specific information.
NOTE: At least one of the information elements shall be provided.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.2.3.2 Discover spatial map response
|
Table 9.3.2.3.2-1 descibes the information elements for Discover spatial map response from SEAL SM server to VAL server or SEAL SM client.
Table 9.3.2.3.2-1: Discover spatial map response
Information element
Status
Description
Application service ID
O
ID of the requesting VAL application service
Success response
O
(NOTE 1)
Indicates successful discovery
> List of discovered spatial maps
O
(NOTE 2)
List of ID(s) of the discovered spatial map(s). Each element includes the information described below
>> Spatial map ID
M
ID of a spatial map discovered
> List of SMAS profiles
O
(NOTE 2)
The list of SMAS profiles as described in Table 9.6.2.3.1-2.
Failure response
O
(NOTE 1)
Indicates failed discovery
> Cause
O
Cause of the failure
NOTE 1: At least one of the information elements shall be provided.
NOTE 2: At least one of the information elements shall be provided.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.3 Get spatial map information
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.3.1 General
|
The get spatial map procedure enables the consumers to request the SEAL SM Server to get all details about the specific spatial map.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.3.2 Procedure
|
Figure 9.3.3.2-1 depicts the procedure for an authorized spatial map consumer (VAL server or SEAL SM client) to get the spatial map. The service is provided by SEAL SM server.
Figure 9.3.3.2-1: Get spatial map information procedure
1) The requestor (e.g., VAL server or SEAL SM client) sends a request message to the SEAL SM server to get the spatial map information. The request includes requestor ID, security credentials, spatial map ID.
2) The SEAL SM server authorizes the requestor, and validates the request. If the request is authorized, the SEAL SM server determines information about the requested spatial map information.
3) The SEAL SM server sends the get spatial map information response message to the requestor. If the request is successful, the response includes spatial map information, otherwise the response indicates a failure and may include a failurereason.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.3.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.3.3.1 Get spatial map information request
|
Table 9.3.3.3.1-1 descibes the information elements for get spatial map request from the VAL server or SEAL SM client to the SEAL SM server.
Table 9.3.3.3.1-1: Get spatial map information request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or VAL User or VAL UE)
Requestor security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Spatial map ID
M
ID of the spatial map to get information on it
> List of spatial map layers
O
A list of spatial map layers for which information is requested.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.3.3.2 Get spatial map information response
|
Table 9.3.3.3.2-1 descibes the information elements for get spatial map response from the SEAL SM server to the VAL server or SEAL SM client.
Table 9.3.3.3.2-1: Get spatial map information response
Information element
Status
Description
Spatial map ID
M
ID of the requested spatial map to get information
Application service ID
O
ID of the requesting VAL application service
Success response
O
(NOTE)
Indicates successful get information
> Spatial map information
M
Information about the requested spatial map as specified in Table 7.3.3.1-1.
Failure response
O
(NOTE)
Indicates failed get information
> Cause
O
Cause of the failure
NOTE: At least one of the information elements shall be provided.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.4 Update spatial map
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.4.1 General
|
The update spatial map procedure enables the consumers to request the SEAL SM Server to update a spatial map.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.4.2 Procedure
|
Figure 9.3.4.2-1 depicts the procedure to update the spatial map. For the request from the spatial map consumer (VAL server or SEAL SM client), SEAL SM server updates the spatial map as requested.
Figure 9.3.4.2-1: Update spatial map procedure
1) The requestor (e.g., VAL server or SEAL SM client) sends a request message to the SEAL SM server to update a spatial map. The request includes requestor ID, security credentials, spatial map ID, information on what to update such as updated spatial map layering information and updated spatial map coverage area. As a part of update, the request may include augmented layer information (e.g., VAL users, spatial anchors).
2) The SEAL SM server authorizes the requestor and validates the request. The SEAL SM server updates the spatial map as requested.
3) The SEAL SM server sends response message to the requestor with result of the request and updated spatial map information with the spatial map ID. SEAL SM server may include the requested augmented layer information in the response message.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.4.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.4.3.1 Update spatial map request
|
Table 9.3.4.3.1-1 descibes the information elements for update spatial map request from VAL server or SEAL SM client to SEAL SM server.
Table 9.3.4.3.1-1: Update spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or VAL User or VAL UE)
Requestor security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Spatial map ID
M
ID of the spatial map to update
Spatial map update information
M
The spatial map Information to update as described in described in Table 7.3.3.1-1. Only IEs which need to be updated are included.
> Augmented layer information
O
List of required augmented layer information. This IE can contain multiple values. Possible values are:
- VAL_UE;
- SPATIAL_ANCHORS.
NOTE: At least one of the information elements shall be provided.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.4.3.2 Update spatial map response
|
Table 9.3.4.3.2-1 descibes the information elements for update spatial map response from the SEAL SM server to the VAL server or SEAL SM client.
Table 9.3.4.3.2-1: Update spatial map response
Information element
Status
Description
Spatial map ID
M
ID of the requested spatial map to get information
Application service ID
O
ID of the requesting VAL application service
Success response
O
(NOTE)
Indicates successful update
> Spatial map information
M
Updated spatial map information. It contains information as specified in Table 7.3.3.1-1.
> Augmented layer information
O
Augmented layer information
Failure response
O
(NOTE)
Indicates failed update
> Cause
O
Cause of failure
NOTE: At least one of the information elements shall be provided.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.5 Delete spatial map
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.5.1 General
|
The delete spatial map procedure enables the consumers to request the SEAL SM Server to delete a spatial map.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.5.2 Procedure
|
Figure 9.3.5.2-1 depicts the procedure to delete the spatial map. For the request from the spatial map consumer (VAL server or SEAL SM client), SEAL SM server deletes the spatial map as requested.
Figure 9.3.5.2-1: Delete spatial map procedure
1) The requestor (e.g., VAL server or SEAL SM client) sends a request message to the SEAL SM server to delete the spatial map. The request includes requestor ID, security credentials, a spatial map ID.
2) The SEAL SM server authorizes the requestor and validates the request. The SEAL SM server deletes the spatial map as requested.
3) The SEAL SM server sends response message to the requestor with the result of success or failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.5.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.5.3.1 Delete spatial map request
|
Table 9.3.5.3.1-1 descibes the information elements for delete spatial map request from VAL server or SEAL SM client to SEAL SM server.
Table 9.3.5.3.1-1: Delete spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or VAL User or VAL UE)
Requestor security credentials
M
The security credentials of the requestor.
Spatial map ID
M
Spatial map ID to delete
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.5.3.2 Delete spatial map response
|
Table 9.3.5.3.2-1 descibes the information elements for delete spatial map response from SEAL SM server to VAL server or SEAL SM client.
Table 9.3.5.3.2-1: Delete spatial map response
Information element
Status
Description
Success response
O
(NOTE)
Indicates successful delete
Failure response
O
(NOTE)
Indicates failed delete
> Cause
O
Cause of failure
NOTE: At least one of the information elements shall be provided.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6 Spatial map subscription
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.1 General
|
This clause provides subscription related procedures to spatial map specific events.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.2 Procedures
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.2.1 Subscribe spatial map event
|
Figure 9.3.6.2.1-1 depicts the procedure for the authorized spatial map consumer (VAL server or SEAL SM client) to subscribe the spatial map event. The service is provided by SEAL SM server. Spatial map consumer can get notification information when the the SM server detects subscribed event.
Figure 9.3.6.2.1-1: Subscribe spatial map event procedure
1) The VAL server (or SEAL SM client) sends a request message to the SEAL SM server to subscribe spatial map event. The request includes requestor ID, security credentials, a notification endpoint, a spatial map ID, event to subscribe which triggers the notification. The request message may also include a list of spatial map layers with its corresponding layer IDs to subscribe spatial map layering information related events. The requestor (VAL server or SEAL SM client) may subscribe to one or more of the following events:
a) "changes of objects" events to indicate the SM server to notify the requestor when changes of the objects are detected. The notification triggering criteria for "changes of objects" event may include added or removed objects, position or direction changes of the spatial map objects.
b) "layers modification" events to indicate the SM server to notify the requestor when any layer in the spatial map is added or updated or removed.
c) "spatial map ready" events to indicate the SM server to notify the requestor when the SEAL SM server has sufficient information to map all the objects related to area of interest the spatial map and the spatial map is ready to provide service (e.g. employed for localization). This event is used when the result IE in the Create spatial map response indicates "in-progress".
Editor's Note: Objects are limited to UEs and objects other than UE is FFS.
2) The SEAL SM server authorizes VAL server (or SEAL SM client), and validates the request. Then server add the requestor into the subscriber list of the event. SM server starts monitoring the events.
3) The SEAL SM server sends response message with the result. For the successful subscribe request, a subscription ID is included in the message. Otherwise, the response message includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.2.2 Notify spatial map event
|
Figure 9.3.6.2.2-1 depicts the notify spatial map event operation between the authorized spatial map consumer (VAL server or SEAL LM client) and SEAL SM server.
Figure 9.3.6.2.2-1: Notify spatial map event
1) The SEAL SM server detects an event that triggers the notification to the subscribers for the corresponding event.
a) If the subscribed event is "changes of objects", the SM server detects any changes of the spatial map objects.
b) If the subscribed event is "Layers modification", the SM server detects any changes of the spatial map layers information.
a) If the subscribed event is "spatial map ready", the SM server detects when the SEAL SM server has sufficient information to map all the objects related to area of interest the spatial map and the spatial map is ready to provide service (e.g. employed for localization).
SM server determines whether the detected event matchs triggering criteria and notifies subscribers accordingly.
2) The SEAL SM server notifies the VAL servers (or SEAL SM clients) which subscribed the corresponding event. The notification includes a subscription ID and event-specific information. If the event is "changes of objects", spatial map notification message includes the information on the detected triggering event, e.g. added or removed objects, position or direction changes of the objects in the spatial map etc. If the event is "Layer modification", the notification message includes the list of all layers for the spatial map.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.2.3 Unsubscribe spatial map
|
Figure 9.3.6.2.3-1 depicts the procedure for the authorized spatial map consumer (VAL server or SEAL CM client) to unsubscribe from the spatial map event. The service is provided by SEAL SM server.
Figure 9.3.6.2.3-1: Unsubscribe spatial map procedure
1) The VAL server (or SEAL SM client) sends a request message to the SEAL SM server to unsubscribe from spatial map event. The request includes requestor ID, security credentials and the subscription ID for the event.
2) The SEAL SM server authorizes VAL server (or SEAL SM client), and validates the request. Then SM server removes the requestor's subscription ID from the subscriber list for the spatial map event.
3) The SEAL SM server sends unsubscribe spatial map event response message with the result. If successful, the response includes an indication of success. Otherwise, the response includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.3.1 Subscribe spatial map request
|
Table 9.3.6.3.1-1 shows the subscribe spatial map event request sent by VAL server (or SEAL SM client) to SEAL SM server to subscribe for spatial map event(s).
Table 9.3.6.3.1-1: Subscribe spatial map event request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or VAL user)
Security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Expiry time
O
Proposed subscription expiry time
Target spatial map(s)
M
Spatial map(s) to subscribe
> List of spatial map IDs
O
ID(s) of the spatial map(s) to subscribe
> Area of interest
O
Three-dimensional area information to discover spatial map(s) to subscribe
List of events
M
Events to subscribe. Each element includes the information described below.
> Event type
O
List of events to subscribed. Possible values are:
- Change of objects
- Layers modification
- spatial map ready
> specified objects
O
List of specified objects for "change of objects" event
> Triggering criteria
O
Specifies the condition to determine whether the event is occurred, e.g. Spatial map is employed and ready for localization service.
>> Changes in objects
O
(NOTE)
Triggers notification if any or specified (or specified type of) objects are added, removed, etc.
>> Layer IDs
O
(NOTE)
List of layers. Triggers notification if any or specified spatial map layer change is detected
> Notification intervals
O
Specifies when to notify the detected event,
Possible values are:
- Event based (e.g., promptly); Or
- Periodically (with minimum time between consecutive notifications)
- intervals (i.e. minimum time between consecutive notifications)
> interval time
O
Time between consecutive notifications (applicable only if notification intervals is set to intervals.
NOTE: At least one of the sub-elements shall be provided.
Editor's Note: Details about "layers" event is FFS.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.3.2 Subscribe spatial map response
|
Table 9.3.6.3.2-1 shows the subscribe spatial map event response sent by SEAL SM server to VAL server (or SEAL SM client) as the response to the subscribe spatial map event request.
Table 9.3.6.3.2-1: Subscribe spatial map event response
Information element
Status
Description
Result
M
Result of the subscribe spatial map event request
Subscription Id (NOTE)
O
Identity of the subscription
Expire time
O
Subscription expire time
Failure cause
O
Indicates reason for the failure.
NOTE: This IE is mandatory when Result IE indicates success.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.3.3 Notify spatial map event
|
Table 9.3.6.3.3-1 shows the spatial map notification sent by SEAL SM server to VAL server (or SEAL SM client) to notify about spatial map event(s).
Table 9.3.6.3.3-1: Spatial map event notification
Information element
Status
Description
Subscription ID
M
Subscription ID for the event
Notification information
M
Specifies what matches the triggering notification condition, including related information
> Spatial map ID
M
ID of the spatial map for which the event is detected
> Event type
M
Type of event detected. One of the event as specified in Table 9.3.6.3.1-1.
>> Changed object
O
(NOTE)
Information on the object which triggered the notification
>>> Object ID
O
ID of the changed object
>>> Type of change
O
Specifies the detected type of change for the object (e.g., added, removed, or changed position or direction)
>>> Changed object information
O
A container to carry the changed object specific information
>> list of layers (NOTE 2)
O
Information about layers for the spatial map.
NOTE 1: This IE is applicable for "Change of objects" event type.
NOTE 2: This IE is applicable for "Layer modification" event type.
Editor's Note: Details on "Changed object information" is FFS.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.3.4 Unsubscribe spatial map request
|
Table 9.3.6.3.4-1 shows the unsubscribe spatial map event request sent by VAL server (or SEAL SM client) to SEAL SM server to subscribe for spatial map event(s).
Table 9.3.6.3.4-1: Unsubscribe spatial map event request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or VAL user)
Security credentials
M
The security credentials of the requestor.
Subscription ID
M
Subscription ID for the event
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.3.6.3.5 Unsubscribe spatial map response
|
Table 9.3.6.3.5-1 shows the unsubscribe spatial map event response sent by SEAL SM server to VAL server (or SEAL SM client) as the response to the unsubscribe spatial map event request.
Table 9.3.6.3.5-1: Unsubscribe spatial map event response
Information element
Status
Description
Result
M
Result of the subscribe spatial map event request
Failure cause
O
Indicates reason for the failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.4 Spatial localization services
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.4.1 General
|
This spatial localization services enables consumer to request SEAL SM Server for localization of a VAL user or VAL UE.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.4.2 Procedure
|
Figure 9.4.2-1 depicts the procedure for the authorized spatial map consumer (VAL server or SEAL SM client) to invoke spatial localization services. The service is provided by SEAL SM server.
Pre-condition:
1) Spatial map is created and the authorized consumer is aware of the spatial map identity.
Figure 9.4.2-1: Spatial localization services
1) The VAL server (or SEAL SM client) sends request to perform localization service in the spatial map to the SEAL SM server. The request includes identity of the map on which the action is to be performed. The request may include list of users (or UEs) to localize.
2) The SEAL SM server authorizes the requestor (e.g. VAL server or SEAL SM client). If the requestor is not authorized then the SEAL SM server sends failure response. If the request is authorized: the SEAL SM server, identifies all users/UEs along with their three dimensional location in the spatial map. If area of interest IE is present then the SEAL SM server identifies the target users/UEs within the area of interest only, otherwise, the SEAL SM server identifies the target users for whole map (according to the area associated with spatial map identifier).
3) The SEAL SM server sends response to the VAL server (or SEAL SM client). The response includes the object localization and identity.
NOTE: In this release, the localization of UE is considered. Localization of all objects will be considered in future release.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.4.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.4.3.1 Spatial localization service request
|
Table 9.4.3.1-1 describes information elements for the spatial localization service request from the SM client or VAL server to the SM server.
Table 9.4.3.1-1: Spatial localization service request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL User or VAL UE, VAL server)
Requestor security credentials
M
The security credentials of the requestor.
Spatial Map Id
M
Identity of the spatial map
Area of interest
O
Contains three dimensional area within spatial map
Target identities
O
List of identity of the users or objects to localize
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.4.3.2 Spatial localization service response
|
Table 9.4.3.2-1 describes information elements for the spatial localization service response from the SM server to the SM client or VAL server.
Table 9.4.3.2-1: Spatial localization service response
Information element
Status
Description
Result
M
Indicates success or failure of the action
Object details (NOTE)
O
A list of objects or users
>> UE id
O
Identity of the UE
>> localization
O
3D position and pose of the VAL UE
NOTE: This IE should be added in case of successful response.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5 SM data source
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.1 General
|
This clause provides registration related procedures for SM data source.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.2 SM data source registration
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.2.1 General
|
The SM data source registration procedure registers the authorized SM information data source with SEAL SM server.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.