hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.6.2.6 Retrieve Spatial anchors of group operation
| API operation name: SS_SAnGroupManagement_Retrieve_SpatialAnchors
Description: The consumer requests to retrieve the profiles of the spatial anchors of groups.
Known Consumers: VAL server, SAn client.
Inputs: See Table 8.3.7.3.9-1.
Outputs: See Table 8.3.7.3.10-1.
See clause 8.3.7.2.5 for details of usage of this operation.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9 Spatial Map (SM) management
| |
26e140d21b097a2c000610e4bd7ffb34 | 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).
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.2 Functional model for spatial map management
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.2.2.1 Functional Elements
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.2.2.2 Reference Points
| |
26e140d21b097a2c000610e4bd7ffb34 | 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).
|
26e140d21b097a2c000610e4bd7ffb34 | 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).
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3 Spatial map management procedures
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.1 Create spatial map
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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. The request may include a required media format for 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. If the required quality information is present, the SEAL SM server checks the feasilibty of the spatial map as per the parameters included in the request message. If processed/available sensor data to match the required quality information (e.g. resolution) is available, the SEAL SM server produces a requested spatial map using layering information and processed sensor data, according to the requested spatial map media format. The SEAL SM server does not create a spatial map if the requested spatial map media format is not supported and can create a spatial map based on local configuration if no spatial map media format is included in the request.
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 successfully, 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 and indication of supported spatial map media formats if the failure is related to an unsupported spatial map media format.
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 specified in Table 9.3.6.3.3-1.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.1.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.1.3.1 Create spatial map request
| Table 9.3.1.3.1-1 describes 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 identifier
M
The identifier of the requestor (e.g., VAL server or VAL User or VAL UE)
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.
Spatial map media format
O
The media format requested for the spatial map.
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.
Required quality information
O
(NOTE)
Includes required quality of the map
> Resolution
O
Required resolution of the map (e.g. HD resolution)
NOTE: When this IE is not present, the requestor is open for any available quality of the map.
NOTE 1: For the current release, the spatial map layer information is implementation specific and out of scope.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.1.3.2 Create spatial map response
| Table 9.3.1.3.2-1 describes 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 1)
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
In-progress response
O
(NOTE 1)
Indicates that creation of the requested spatial map is in-progress.
> Spatial map ID
O
Identifier of the spatial map which is in-progress state.
Available quality Info
O
(NOTE 1)
Includes available quality of the map
> Resolution
O
available resolution of the map (e.g. HD resolution)
Failure response
O
(NOTE 1)
Indicates failed create spatial map
> Cause
O
Cause of the failure
> List of supported spatial map media format
O
(NOTE 2)
The list of media format(s) supported by the SM server.
NOTE 1: One of the information elements shall be provided.
NOTE 2: Only included if the failure is unsupported spatial map media format.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.2 Discover spatial map
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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. The request may include a required media format for the discovered spatial map(s).
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].
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.2.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.2.3.1 Discover spatial map request
| Table 9.3.2.3.1-1 describes 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 identifier
M
The identifier of the requestor (e.g., VAL server or VAL User or VAL UE)
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.
> Spatial map media format
O
The media format that is used to identify relevant spatial map(s).
> 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.2.3.2 Discover spatial map response
| Table 9.3.2.3.2-1 describes 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.3 Get spatial map information
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 and may include a list of requested spatial map layers and augmented layer information.
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 and may include augmented layer information, otherwise the response indicates a failure and may include a failure reason.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.3.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.3.3.1 Get spatial map information request
| Table 9.3.3.3.1-1 describes 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 identifier
M
The identifier of the requestor (e.g., VAL server or VAL User or VAL UE)
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.
> Augmented layer information
O
List of requested augmented layer information. This IE can contain multiple values. Possible values are:
- VAL_USERS;
- SPATIAL_ANCHORS.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.3.3.2 Get spatial map information response
| Table 9.3.3.3.2-1 describes 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.
> Augmented layer information
O
Augmented layer information provided by SM server.
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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.4 Update spatial map
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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). The request may include a list of UE-object association information for the SEAL SM server to identify associations between UEs and objects in a spatial map.
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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.4.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.4.3.1 Update spatial map request
| Table 9.3.4.3.1-1 describes 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 identifier
M
The identifier of the requestor (e.g., VAL server or VAL User or VAL UE)
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.
List of UE-object association information
O
List of UE-object association information to identify associations between UEs and objects in a spatial map as described in Table 7.3.3.x-1.
NOTE: At least one of the information elements shall be provided.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.4.3.2 Update spatial map response
| Table 9.3.4.3.2-1 describes 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.5 Delete spatial map
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.5.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.5.3.1 Delete spatial map request
| Table 9.3.5.3.1-1 describes 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 identifier
M
The identifier of the requestor (e.g., VAL server or VAL User or VAL UE)
Security credentials
M
The security credentials of the requestor.
Spatial map ID
M
Spatial map ID to delete
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.5.3.2 Delete spatial map response
| Table 9.3.5.3.2-1 describes 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.6 Spatial map subscription
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.6.1 General
| This clause provides subscription related procedures to spatial map specific events.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.6.2 Procedures
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 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, target spatial map(s), notification intervals and duration for which events are notified, 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, velocity 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".
NOTE: In this release, objects are limited to UEs.
2) The SEAL SM server authorizes VAL server (or SEAL SM client), and validates the request. If authorized, the SEAL SM server determines the target spatial map(s) using spatial map ID(s), area of interest, and/or location information provided in the request. Then the SEAL SM server adds the requestor into the subscriber list of the event. The SEAL SM server starts monitoring for events. For the "changes of objects" events, SM server can obtain the position, direction and velocity information of trackable objects from 5GS or SEAL Location Management service.
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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 DM 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. For the tracking objects, based on the data analytics for position, direction and velocity, the SM server can do trackable object mobility prediction and estimate the duration for which they stay in the spatial map. If UE-object association information has been provided, the SEAL SM server can use this information to determine if a detected spatial map object is associated with a UE.
NOTE: How to do trackable object mobility prediction and estimate the duration of object tracking is implementation specific and out of scope.
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, UE-object association, etc. If the event is "Layer modification", the notification message includes the list of all layers for the spatial map.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 SM 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.3.6.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 identifier
M
The identifier 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
Notification endpoint
M
Indicates the address (e.g., IP address, FQDN, URI) where the notifications should be sent.
Target spatial map(s)
M
Spatial map(s) to subscribe
> List of spatial map IDs
O
(NOTE 1)
ID(s) of the spatial map(s) to subscribe
> Area of interest
O
(NOTE 1)
Three-dimensional area information to discover spatial map(s) to subscribe
> Location information
O
(NOTE 1)
Location, orientation and pose information that is used to identify relevant spatial maps 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
- UE-object association
> 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 2)
Triggers notification if any or specified (or specified type of) objects are added, removed, changed in position, direction, velocity, UE-object association, etc.
>> Layer IDs
O
(NOTE 2)
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.
Tracking end condition
O
Specifies the condition until when events for the tracking objects are notified (e.g. as long as tracking objects stay in the spatial map, etc.)
NOTE 1: At least one of the sub-elements shall be provided.
NOTE 2: At least one of the sub-elements shall be provided.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 1)
Information on the object which triggered the notification
>>> Object ID
O
(NOTE 3)
ID of the changed object
>>> Association ID
O
(NOTE 3)
Identifier of the UE-object association.
>>> UE ID
O
(NOTE 3)
Identifier of the UE with an associated object.
>>> Type of change
O
Specifies the detected type of change for the object (e.g., added, removed, or changed position, direction, velocity, or UE-object association)
>>> Estimated duration of tracking
O
Estimated duration for which the object being tracked stays in the spatial map. Applicable for tracking objects.
>>> Object mobility prediction
O
Information predicting the mobility of the object being tracked. Applicable for tracking objects.
>>> 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.
NOTE 3: This IE is applicable for "UE-object association" event type.
NOTE: For the current release, the object specific information is implementation specific and out of scope.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 identifier
M
The identifier 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
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.4 Spatial localization services
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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(s) to the SEAL SM server. The request includes a requestor identifier, security credentials, and identity of the map(s) on which the action is to be performed. The request may include list of users (or UEs, objects) to localize. The request may include a list of UE-object association information for the SEAL SM server to identify associations between UEs and objects in a spatial map.
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 localization along with their three dimensional location and pose 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). If UE-object association information has been provided, the SEAL SM server can use this information to determine if a spatial map object is associated with a UE. If a UE-object association is determined, the SEAL SM server can use localization information of the associated object to determine user/UE localization in the spatial map, or use localization information of the associated UE to determine object localization in the spatial map.
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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.4.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 identifier
M
The identifier of the requestor (e.g., VAL User or VAL UE, VAL server)
Security credentials
M
The security credentials of the requestor.
Spatial Map list
List of spatial maps to be used for spatial localization
> 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
List of UE-object association information
O
List of UE-object association information to identify associations between UEs and objects in a spatial map.
Reference point
O
Reference point from where the object is localized within spatial map
|
26e140d21b097a2c000610e4bd7ffb34 | 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 (or associated UE)
>> Object ID
O
Identifier of the object (or associated object)
>> localization
O
3D position and pose of the VAL UE or object
NOTE: This IE should be added in case of successful response.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5 SM data source
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.1 General
| This clause provides registration related procedures for SM data source.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.2 SM data source registration
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.2.1 General
| The SM data source registration procedure registers the authorized SM information data source with SEAL SM server.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.2.2 Procedure
| Figure 9.5.2.2-1 depicts the procedure for an authorized VAL client, via a SEAL SM client, to register as a SM data source with the SEAL SM server.
Pre-conditions:
1. The SEAL SM client has received information (e.g. URI, IP address) related to the SEAL SM server;
2. The SEAL SM client has received security credentials authorizing it to communicate with the SEAL SM server.
Figure 9.5.2.2-1: SM data source registration procedure
1. The SEAL SM client sends a SM data source registration request to the SEAL SM server. The request includes a requestor ID, security credentials, SEAL SM client notification endpoint and a SM data source profile including SM information details (e.g., provider identifier, type, position, state). The request may include UE identifier, VAL client identifier, Proposed expiration time. The SM data source profile may also include data source update interval information to support the different needs for frequency of the data source and the mobility information (like fixed or low or high mobility). When real-time data is needed (such as autonomous driving, drones, etc.) a different update interval can be used than for the fixed cases (e.g., in industrial setting).
2. Upon receiving the request, the SEAL SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SEAL SM server assigns a unique identifier for the registration and stores the SM data source profile provided in the request.
3. The SEAL SM server sends a SM data source registration response to the SEAL SM client. If the SEAL SM server successfully stored the SM data source profile, the response includes an indication of success, the registration identifier and may include an expiration time for the registration. Otherwise, the response includes an indication of failure and may include a reason for failure.
NOTE: In this release, SM specific data source procedures are used. If and when generic data source related procedures are available, usage of generic procedures will be considered.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.2.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.2.3.1 SM data source registration request
| Table 9.5.2.3.1-1 describes information elements in the SM data source registration request from the SEAL SM client to the SEAL SM server.
Table 9.5.2.3.1-1: SM data source registration request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL User or VAL UE)
Security credentials
M
The security credentials of the requestor
Proposed expiration time
O
Proposed expiration time for the registration
UE ID
O
The identifier of the hosting UE (i.e., GPSI)
VAL client ID
O
The identifier of the VAL client
Notification endpoint
M
The endpoint for notifying the SM data source about a SM information request.
SM data source profile
M
The SM data source profile of the registering SM data source as described in Table 7.3.3.2-1.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.2.3.2 SM data source registration response
| Table 9.5.2.3.2-1 describes information elements in the SM data source registration response from the SEAL SM server to the SEAL SM client.
Table 9.5.2.3.2-1: SM data source registration response
Information element
Status
Description
Successful response
O
Indicates that the registration request was successful
> Registration ID
M
Identifier of the registration
> Expiration time
O
Indicates the expiration time of the registration. To maintain an active registration status, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the registration never expires.
Failure response
O
Indicates that the registration request failed
> Cause
O
Indicates the cause of registration request failure
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.3 SM data source registration update
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.3.1 General
| The SM data source registration update procedure updates registration status of the authorized SM information data source to the SEAL SM server.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.3.2 Procedure
| Figure 9.5.3.2-1 depicts the procedure for an authorized VAL client, via a SEAL SM client, to update a registered SM data source information.
Pre-conditions:
1. The SEAL SM client has successfully registered the SM data source with the SEAL SM server.
Figure 9.5.3.2-1: SM data source registration update procedure
1. The SEAL SM client sends a SM data source registration update request to the SEAL SM server. The request includes a requestor ID, security credentials, a registration ID, and may include an updated SM data source profile and a proposed expiration time for the updated registration.
2. Upon receiving the request, the SEAL SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SEAL SM server updates the SM data source profile based on the request information.
3. The SEAL SM server sends the SM data source registration update response to the SEAL SM client. If the SEAL SM server successfully updated the SM data source profile, the response includes an indication of success. Otherwise, the response includes an indication of failure and may include a reason for failure.
NOTE: In this release, SM specific data source procedures are used. If and when generic data source related procedures are available, usage of generic procedures will be considered.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.3.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.3.3.1 SM data source registration update request
| Table 9.5.3.3.1-1 describes information elements in the SM data source registration update request from the SEAL SM client to the SEAL SM server.
Table 9.5.3.3.1-1: SM data source registration update request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL User or VAL UE)
Security credentials
M
The security credentials of the requestor
Registration ID
M
Identifier of the registration
Proposed expiration time (NOTE)
O
Proposed expiration time for the registration
Updated SM data source profile (NOTE)
O
The SM data source profile, as described in Table 7.3.3.2-1, with updated SM information details. Included only if there is an update in SM information details.
NOTE: At least one of the IEs is included.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.3.3.2 SM data source registration update response
| Table 9.5.3.3.2-1 describes information elements in the SM data source registration update response from the SEAL SM server to the SEAL SM client.
Table 9.5.3.3.2-1: SM data source registration update response
Information element
Status
Description
Successful response
O
Indicates that the registration update request was successful
> Expiration time
O
Indicates the expiration time of the updated registration. To maintain an active registration status, a registration update is required before the expiration time. If the Expiration time IE is not included, it indicates that the updated registration never expires.
Failure response
O
Indicates that the request failed
> Cause
O
Indicates the cause of the failure
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.4 SM data source deregistration
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.4.1 General
| The SM data source deregistration procedure deregisters the authorized SM information data source from the SEAL SM server.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.4.2 Procedure
| Figure 9.5.4.2-1 depicts the procedure for an authorized SEAL SM client to deregister a SM data source.
Pre-conditions:
1. The SEAL SM client has already registered the SM data source with the SEAL SM server.
Figure 9.5.4.2-1: SM data source deregistration procedure
1. The SEAL SM client sends a SM data source deregistration request to the SEAL SM server. The request includes a requestor ID, security credentials, and a registration ID.
2. Upon receiving the request, the SEAL SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SEAL SM server ends the SM data source registration and removes the stored SM data source profile.
3. The SEAL SM server sends the SM data source deregistration response to the SEAL SM client. If the SEAL SM server successfully deregistered the SEAL SM client, the response includes an indication of success. Otherwise, the response includes an indication of failure and may include a reason for failure.
NOTE: In this release, SM specific data source procedures are used. If and when generic data source related procedures are available, usage of generic procedures will be considered.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.4.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.4.3.1 SM data source deregistration request
| Table 9.5.4.3.1-1 describes information elements in the SM data source deregistration request from the SEAL SM client to the SEAL SM server.
Table 9.5.4.3.1-1: SM data source deregistration request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL User or VAL UE)
Security credentials
M
The security credentials of the requestor
Registration ID
M
Identifier of the registration
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.4.3.2 SM data source deregistration response
| Table 9.5.4.3.2-1 describes information elements in the SM data source deregistration response from the SEAL SM server to the SEAL SM client.
Table 9.5.4.3.2-1: SM data source deregistration response
Information element
Status
Description
Successful response
O
Indicates that the deregistration request was successful
Failure response
O
Indicates that the request failed
> Cause
O
Indicates the cause of the failure
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.5 SM data source discovery
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.5.1 General
| The SM data source discovery procedure allows VAL server to discover the authorized SM information data sources from the SEAL SM server.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.5.2 Procedure
| Figure 9.5.5.2-1 depicts the procedure for an authorized VAL server to discover SM data source(s).
Pre-conditions:
1. The VAL server has received information (e.g. URI, IP address) related to the SEAL SM server;
2. The VAL server has received security credentials authorizing it to communicate with the SEAL SM server.
Figure 9.5.5.2-1: SM data source discovery procedure
1. The requestor (e.g, VAL server or SEAL server) sends a SM data source discovery request to the SEAL SM server. The request includes a requestor ID, security credentials, and may include discovery filters, endpoint information for receiving spatial mapping information from discovered SM data sources, and a triggered reporting indication. Discovery filters include the area of interest (e.g., three-dimensional area, localization information and requirements on spatial mapping information (e.g., availability, data source update interval, mobility information) as defined in clause 9.5.5.3.1.
NOTE 1: How the requestor determines the requested 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 one or more registered SM data source(s) according to the discovery filters.
The SEAL SM server evaluates if the SM data source location is in accordance with the area of interest included in the discovery request to determine the SM data source(s). The SEAL SM server can obtain UE location information and velocity information from the 3GPP core network by invoking the 3GPP Core Network Location Services exposed by the NEF as described in 3GPP TS 23.273 [6] and 3GPP TS 23.502 [5], or by invoking the SEAL Location Management APIs as described in 3GPP TS 23.434 [4]. If the SM data source discovery request includes a triggered reporting indication, the SEAL SM server allocates and stores a triggered reporting identifier, and associates the determined SM data sources and information included in the request with the triggered reporting identifier.
3. The SEAL SM server sends a SM data source notification to trigger the determined SEAL SM client(s) to send spatial mapping information. The notification includes details about the requested spatial mapping information and endpoint information for sending the spatial mapping information to the requestor. The SEAL SM client provides the information included in the notification to the VAL client that will send the spatial mapping information. If the SM data source discovery request includes a triggered reporting identifier, the SM server does not send the SM data source notification and procedure described in clause 9.5.7 applies.
4. The SEAL SM server sends a SM data source discovery response to the requestor. The response includes information about SM data source(s) when at least one SM data source has been determined. If no SM information provided was determined, the SEAL SM server sends a failure indication with a reason for failure. If the SEAL server allocated a triggered reporting identifier, the response includes the triggered reporting identifier and procedure described in clause 9.5.7 applies.
NOTE: In this release, SM specific data source procedures are used. If and when generic data source related procedures are available, usage of generic procedures will be considered.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.5.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.5.3.1 SM data source discovery request
| Table 9.5.5.3.1-1 describes information elements in the SM data source discovery request from the VAL server to the SEAL SM server.
Table 9.5.5.3.1-1: SM data source discovery 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
SM data reporting endpoint
O
The endpoint information where the triggered spatial mapping data source sends the SM data.
Triggered reporting indication
O
An indication that SM data reporting will be triggered.
Discovery filters
O
Set of characteristics to determine SM data source(s) in the area of interest
> Area of interest
O
Three-dimensional area of interest or localization information to discover SM data source(s) in the area
> SM information details
O
The SM information details to match
>> SM data identifier
O
The identifier of SM information
>> SM data type (NOTE)
O
The type of SM information (e.g., LiDAR camera, RGB-D camera, high-resolution cameras, etc.) that is provided by the application layer.
>> SM data format
O
The format of a SM information (e.g., raw, processed, etc.)
>> Position information
O
Indicates the Three dimensional area of interest or location information of the SM data source
>> Availability State information
O
Indicates the time period availability information of the SM data source.
>> Data source update interval information
O
Indicates the rate at which data source updates or generates the data. It describes how often the new data is captured or collected. e.g., every x milliseconds generates data.
>> Mobility information
O
Indicates the mobility information of the SM data source.e.g., fixed, low or high mobility
NOTE: The definition of SM data types is application specific (e.g., VAL client) for the current release.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.5.3.2 SM data source discovery response
| Table 9.5.5.3.2-1 describes information elements in the SM data source discovery response from the SEAL SM server to the SM data source consumer (e.g., VAL server or SEAL server).
Table 9.5.5.3.2-1: SM data source discovery response
Information element
Status
Description
Successful response
O
Indicates that the discovery request was successful
> SM data source profiles
O
The list of SM data source profiles as described in Table 7.3.3.2-1.
> Triggered reporting ID
O
(NOTE)
The identifier of a triggered SM data reporting.
Failure response
O
Indicates that the request failed
> Cause
O
Indicates the cause of the failure
NOTE: The IE shall be present if triggered SM data reporting is requested
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.5.3.3 SM data source notification
| Table 9.5.5.3.3-1 shows the notification sent by a SEAL SM server to a SEAL SM client for triggering a spatial mapping information session from a SM data source.
Table 9.5.5.3.3-1: SM data source notification
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., SEAL SM server, VAL server).
Security credentials
M
The security credentials of the requestor.
SM data source ID
M
The identifier of the SM data source.
SM information reporting session
M
The characteristics of SM information reporting session.
> SM data identifier
M
The identifier of spatial SM data to report.
> SM data type (NOTE)
O
The type of SM information data to report. (e.g., LiDAR camera, RGB-D camera, high-resolution cameras, etc.) that is provided by the application layer.
> SM data format
O
The format of a SM information data to report. (e.g., raw, processed, etc.).
> SM duration
O
The duration for which the SM data is reported.
> SM frequency
O
The frequency at which the SM data is reported.
> SM endpoint
M
The endpoint where to report the SM data.
NOTE: The definition of SM data types is application specific (e.g., VAL client) for the current release.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6 SM data source subscription
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.1 General
| SM data source subscription enables VAL server or SEAL server to subscribe to the SM server to get the updates related to changes in SM data sources and data source profiles.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.2 Procedures
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.2.1 Subscribe SM data source
| Figure 9.5.6.2.1-1 depicts the procedure for the authorized VAL server or SEAL server to subscribe to the SM server for the the SM data source specific event. VAL server or SEAL server can get notification information when the the SM server detects subscribed event.
Pre-conditions:
1. The VAL server or SEAL server has received information (e.g. URI, IP address) related to the SEAL SM server;
2. The VAL server or SEAL server has received security credentials authorizing it to communicate with the SEAL SM server.
3. The VAL server or SEAL server has already discovered the SM data sources and obtained the SM data source information.
Figure 9.5.6.2.1-1: SM data source subscription
1. The requestor (e.g., VAL server or SEAL server) sends a SM data source subscription request to the SM server. The request includes requestor ID, security credentials, a notification endpoint, event to subscribe which triggers the notification etc as specified in Table 9.5.6.3.1-1.
2. Upon receiving the request from the requestor, the SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SM server creates the subscription and stores the subscription information.
a. If the subscribed event is for "changes in SM data source(s) profiles", the SM server monitors for updates to the elements of SM data source profile(s) described in Table 7.3.3.2-1 that are associated with the target SM data source(s) provided in the subscription request. The SM server also monitors for the creation of SM data source profile(s) and deletion of SM data source profiles by SM data source(s) registration or deregistration in the area of interest provided in the subscription request. The SM server also subscribes to the SEAL Location Management Server services in 3GPP TS 23.434 or NEF services specified in 3GPP TS 23.502 to monitor the location of the SM data source. The SM server also monitors updates to the SM data source profile done via the procedure defined in clause 9.5.3.
3. The SM server sends a SM data source subscription response to the requestor with the indication of success or failure as specified in Table 9.5.6.3.2-1.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.2.2 Notify SM data source event
| Figure 9.5.6.2.2-1 depicts the notify spatial map event operation between the authorized SM data source consumer (VAL server or SEAL server) and SEAL SM server.
Figure 9.5.6.2.2-1: SM data source notification
1. The SEAL SM server detects an event that triggers the notification to the subscribers for the corresponding event. SM server determines whether the detected event matches triggering criteria and notifies subscribers accordingly.The SM server detects changes to the SM data source like changes in to the SM data source profile, SM data type, SM data format, SM data area, changes in location, availability state, data source update interval and also detects the creation or deletion of SM data source profiles based on the registration and deregistration of SM data sources in the provided area of interest .
2. The SEAL SM server notifies the VAL servers or SEAL servers which subscribed the corresponding event. The notification includes a subscription ID and event-specific information. The notification message includes the list of all SM data sources identifiers that are updated and the updated elements (e.g. changes in SM data type, SM data format, SM data area, location, availability state, data source update interval).
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.2.3 SM data source update subscription
| Figure 9.5.6.2.3-1 depicts the procedure for the authorized VAL server or SEAL server to update the SM data source subscription with the SM server.
Pre-conditions:
1. The VAL server or SEAL server subscribed for SM data source related events with the SM server.
Figure 9.5.6.2.3-1: SM data source subscription update
1. The requestor (e.g., VAL server or SEAL server) sends a SM data source subscription update request to the SM server. The request includes the requestor identifier, security credentials and the subscription identifier and may include subscribed event information and expiration time.
2. Upon receiving the request from the requestor, the SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SM server updates the subscription information and starts monitoring for the updated events and triggering criteria if received in the subscription update request.
3. The SM server sends a SM data source subscription update response to the requestor. If the SM server has updated the subscription, the response includes an indication of success and may include an expiration time. To maintain the subscription, the requestor shall send a subscription update request before the expiration time; otherwise, the SM data source subscription expires. If the SM server has not updated the subscription, the response includes an indication of failure and may include a reason for failure.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.2.4 SM data source unsubscribe
| Figure 9.5.6.2.4-1 depicts the procedure for the authorized VAL server or SEAL server to remove the SM data source subscription with the SM server.
Pre-conditions:
1. The VAL server or SEAL server subscribed for SM data source related events with the SM server.
Figure 9.5.6.2.4-1: SM data source unsubscribe
1. The requestor (e.g., VAL server or SEAL server) sends a SM data source unsubscribe request to the SM server. The request includes the requestor identifier, security credentials and the subscription identifier.
2. Upon receiving the request from the requestor, the SM server validates if the requestor is authorized for the request. If the requestor is authorized, the SM server cancels the SM data source subscription associated with the subscription identifier.
3. The SM server sends a SM data source unsubscribe response to the requestor. If the SM server has canceled the subscription, the response includes an indication of success. If the SM server has not canceled the subscription, the response includes an indication of failure and may include a reason for failure.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.3 Information flows
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.