hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
200a67263e13f9f0a665c785e9573ee5
|
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, UE identifier, VAL client identifier, SEAL SM client notification endpoint and a SM data source profile including SM information details (e.g., provider identifier, type, position, state). The SM data source profile may also include data source update interval information, to support the different needs for frequency of the data source. 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 a proposed 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.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.2.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
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 ID
M
The identity of the requestor (e.g., VAL User or VAL UE)
Requestor 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.
|
200a67263e13f9f0a665c785e9573ee5
|
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
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.3 SM data source registration update
| |
200a67263e13f9f0a665c785e9573ee5
|
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.
|
200a67263e13f9f0a665c785e9573ee5
|
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.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.3.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
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 ID
M
The identity of the requestor (e.g., VAL User or VAL UE)
Requestor 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.
|
200a67263e13f9f0a665c785e9573ee5
|
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
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.4 SM data source deregistration
| |
200a67263e13f9f0a665c785e9573ee5
|
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.
|
200a67263e13f9f0a665c785e9573ee5
|
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.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.4.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
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 ID
M
The identity of the requestor (e.g., VAL User or VAL UE)
Requestor security credentials
M
The security credentials of the requestor
Registration ID
M
Identifier of the registration
|
200a67263e13f9f0a665c785e9573ee5
|
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
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.5 SM data source discovery
| |
200a67263e13f9f0a665c785e9573ee5
|
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.
|
200a67263e13f9f0a665c785e9573ee5
|
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, discovery filters and endpoint information for receiving spatial mapping information from discovered SM data sources. Discovery filters inlcude the area of interest (e.g., three-dimensional area, localization information) and requirements on spatial mapping 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 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].
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.
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.
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.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.5.5.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
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 ID
M
The identifier of the requestor (e.g., VAL server)
Requestor security credentials
M
The security credentials of the requestor
Area of interest
M
Three-dimensional area of interest or localization information to discover SM data source(s) in the area
SM data reporting endpoint
O
The endpoint information where the triggered spatial mapping data source sends the SM data.
Discovery filters
O
Set of characteristics to determine SM data source(s) in the area of interest
> 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 availabaility 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.
NOTE: The definition of SM data types is application specific (e.g., VAL client) for the current release.
|
200a67263e13f9f0a665c785e9573ee5
|
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.
Failure response
O
Indicates that the request failed
> Cause
O
Indicates the cause of the failure
|
200a67263e13f9f0a665c785e9573ee5
|
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 ID
M
The identifier of the requestor (e.g., SEAL SM server, VAL server).
Requestor 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.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6 SM service capable application server (SMAS)
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.1 General
|
This clause enables VAL server with SM capability to register with SEAL SM server in order to provide SM services.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.2 SMAS registration
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.2.1 General
|
The SMAS registration procedure registers the authorized VAL server with SM capability with SEAL SM server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.2.2 Procedure
|
Figure 9.6.2.2-1 depicts the procedure for an authorized VAL server with SM capabilities to register a SMAS with the SEAL SM server.
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.6.2.2-1: SMAS registration procedure
1. The VAL server sends a SMAS registration request to the SEAL SM server. The request includes a requestor ID, security credentials, and a SMAS profile including SM service information (e.g., endpoint, availability period, availability location) and spatial map information (e.g., identifier, coverage area, civic address, latest update time).
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 SMAS profile that was provided in the request.
3. The SEAL SM server sends a SMAS registration response to the VAL server. If the SEAL SM server successfully stored the SMAS profile, the response includes an indication of success, the registration identifier and may include a proposed expiration time for the registration. Otherwise, the response includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.2.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.2.3.1 SMAS registration request
|
Table 9.6.2.3.1-1 describes information elements in the SMAS registration request from the VAL server to the SEAL SM server.
Table 9.6.2.3.1-1: SMAS registration request
Information element
Status
Description
Requestor ID
M
The identifier of the requestor (e.g., VAL server)
Security credentials
M
The security credentials of the requestor
Proposed expiration time
O
Proposed expiration time for the registration
SMAS profile
O
The SMAS profile as described in Table 9.6.2.3.1-2.
Table 9.6.2.3.1-2 describes information elements in the SMAS profile.
Table 9.6.2.3.1-2: SMAS profile
Information element
Status
Description
SMAS information
M
The information about the SM service; each element includes the information described below.
> Endpoint
O
The endpoint information (e.g. URI, FQDN, IP address) used to communicate with the SM Service.
> Availability period
O
The time period when a service consumer can access the SM service.
> Availability location
O
The location where a service consumer can access the service from.
List of spatial map information
M
The information about spatial map(s) available at the SM service; each spatial map of the list includes the information described below.
> Identifier
M
The identifier of a spatial map
> Coverage area
M
The spatial coverage area of a spatial map
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.2.3.2 SMAS registration response
|
Table 9.6.2.3.2-1 describes information elements in the SMAS registration response from the SEAL SM server to the VAL server.
Table 9.6.2.3.2-1: SMAS 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 request failed
> Cause
O
Indicates the cause of the failure
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.3 SMAS registration update
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.3.1 General
|
The SMAS registration update procedure updates registration status of the authorized VAL server with SM capability to the SEAL SM server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.3.2 Procedure
|
Figure 9.6.3.2-1 depicts the procedure for an authorized VAL server to update SMAS information.
Pre-conditions:
1. The VAL server has already registered the SM service with the SEAL SM server.
Figure 9.6.3.2-1: SMAS registration update procedure
1. The VAL server sends a SMAS registration update request to the SEAL SM server. The request includes a requestor ID, security credentials, a registration ID, and may include an updated SMAS profile and 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 SMAS profile based on the request information.
3. The SEAL SM server sends the SMAS registration update response to the VAL server. If the SEAL SM server successfully updated the SMAS profile, the response includes an indication of success and may include a proposed expiration time for the registration. Otherwise, the response includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.3.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.3.3.1 SMAS registration update request
|
Table 9.6.3.3.1-1 describes information elements in the SMAS registration update request from the VAL server to the SEAL SM server.
Table 9.6.3.3.1-1: SMAS registration update request
Information element
Status
Description
Requestor ID
M
The identifier of the requestor (e.g., VAL server)
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
SMAS profile (NOTE)
O
The SMAS profile as described in Table 9.6.2.3.1-2.
NOTE: At least one of the IEs is included.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.3.3.2 SMAS registration update response
|
Table 9.6.3.3.2-1 describes information elements in the SMAS registration update response from the SEAL SM server to the VAL server.
Table 9.6.3.3.2-1: SMAS 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
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.4 SMAS deregistration
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.4.1 General
|
The SMAS deregistration procedure deregisters the authorized VAL server with SM capability from the SEAL SM server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.4.2 Procedure
|
Figure 9.6.4.2-1 depicts the procedure for an authorized VAL server to deregister a SMAS.
Pre-conditions:
1. The VAL server has already registered the SM service with the SEAL SM server.
Figure 9.6.4.2-1: SMAS deregistration procedure
1. The VAL server sends a SMAS 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 SMAS registration and removes the stored SMAS profile.
3. The SEAL SM server sends the SMAS deregistration response to the VAL server. If the SEAL SM server successfully deregistered the SMAS, 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.6.4.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.4.3.1 SMAS deregistration request
|
Table 9.6.4.3.1-1 describes information elements in the SMAS deregistration request from the VAL server to the SEAL SM server.
Table 9.6.4.3.1-1: SMAS deregistration request
Information element
Status
Description
Requestor ID
M
The identifier of the requestor (e.g., VAL server)
Requestor security credentials
M
The security credentials of the requestor
Registration ID
M
Identifier of the registration
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.4.3.2 SMAS deregistration request
|
Table 9.6.4.3.2-2 describes information elements in the SMAS deregistration response sent from the SEAL SM server to the VAL server.
Table 9.6.4.3.2-2: SMAS 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
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.6.5 SMAS discovery
|
SMAS registered with a SEAL SM server are discovered via the spatial map discovery procedure described in clause 9.3.2.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7 SEAL APIs for spatial map management
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.1 General
|
Table 9.7.1-1 illustrates the SEAL APIs for spatial map management.
Table 9.7.1-1: List of SEAL APIs for spatial map management
API Name
API Operations
Known Consumer(s)
Communication Type
SS_SmManagement
Create
VAL server, SEAL SM client
Request/Response
Get
VAL server, SEAL SM client
Update
VAL server, SEAL SM client
Delete
VAL server, SEAL SM client
Subscribe
VAL server, SEAL SM client
Subscribe/Notify
Notify
VAL server, SEAL SM client
Unsubscribe
VAL server, SEAL SM client
SS_SmDiscovery
Request
SEAL SM client, VAL server
Request/Response
SS_SmLocalization
Request
VAL server, SEAL SM client
Request/Response
SS_SmDataSourceRegistration
Request
SEAL SM client
Request/Response
Update
SEAL SM client
Deregister
SEAL SM client
SS_SmDataSourceDiscovery
Request
VAL server
Request/Response
Notify
SEAL SM client
Notify
SS_SmSmasRegistration
Request
VAL server
Request/Response
Update
VAL server
Deregister
VAL server
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.2 SS_SmManagement API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.2.1 General
|
Service description: This API enables the VAL server or SEAL SM client to manage spatial maps on SEAL SM server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.2.2 Create operation
|
API operation name: SS_SmManagement_Create
Description: Create a spatial map in the given three-dimensional area of interest.
Known Consumers: VAL server, SEAL SM client.
Inputs: Refer Table 9.3.1.3.1-1
Outputs: Refer Table 9.3.1.3.2-1
See clause 9.3.1 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.2.3 Get operation
|
API operation name: SS_SmManagement_Get
Description: Provide requested spatial map information to the authorized consumers.
Known Consumers: VAL server, SEAL SM client.
Inputs: Refer Table 9.3.3.3.1-1
Outputs: Refer Table 9.3.3.3.2-1
See clause 9.3.3 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.2.4 Update operation
|
API operation name: SS_SmManagement_Update
Description: Update the information on a spatial map as requested.
Known Consumers: VAL server, SEAL SM client.
Inputs: Refer Table 9.3.4.3.1-1
Outputs: Refer Table 9.3.4.3.2-1
See clause 9.3.4 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.2.5 Delete operation
|
API operation name: SS_SmManagement_Delete
Description: Delete spatial map.
Known Consumers: VAL server, SEAL SM client.
Inputs: Refer Table 9.3.5.3.1-1
Outputs: Refer Table 9.3.5.3.2-1
See clause 9.3.5 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.2.6 Subscribe operation
|
API operation name: SS_SmManagement_Subscribe
Description: Process the authorized consumer's subscription to the spatial map events.
Known Consumers: VAL server, SEAL SM client.
Inputs: Refer Table 9.3.6.3.1-1
Outputs: Refer Table 9.3.6.3.2-1
See clause 9.3.6.2.1 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.2.7 Notify operation
|
API operation name: SS_SmManagement_Notify
Description: Notify the information on the detected triggering events to which the authorized consumers are subscribed.
Known Consumers: VAL server, SEAL SM client.
Inputs: None
Outputs: Refer Table 9.3.6.3.3-1
See clause 9.3.6.2.2 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.2.8 Unsubscribe operation
|
API operation name: SS_SmManagement_Unsubscribe
Description: Revoke the authorized consumer's subscription to the spatial map events.
Known Consumers: VAL server, SEAL SM client.
Inputs: Refer Table 9.3.6.3.4-1
Outputs: Refer Table 9.3.6.3.5-1
See clause 9.3.6.2.3 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.3 SS_SmDiscovery API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.3.1 General
|
Service description: This API enables the VAL server or SEAL SM client to discover spatial maps and SMAS from the SEAL SM server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.3.2 Request operation
|
API operation name: SS_SmDiscovery_Request
Description: Discover spatial maps or SMAS in the given three-dimensional area of interest.
Known Consumers: VAL server, SEAL SM client.
Inputs: Refer Table 9.3.2.3.1-1
Outputs: Refer Table 9.3.2.3.2-1
See clause 9.3.2 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.4 SS_SmLocalization API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.4.1 General
|
Service description: This API enables the VAL server or SEAL SM client to get localization information from the spatial maps.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.4.2 Request operation
|
API operation name: SS_SmLocalization_Request
Description: Get localization information of the requested object from the spatial map.
Known Consumers: VAL server, SEAL SM client.
Inputs: Refer Table 9.4.3.1-1
Outputs: Refer Table 9.4.3.2-1
See clause 9.4.2 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.5 SS_SmDataSourceRegistration API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.5.1 General
|
Service description: This API enables the SM data source to register, update register or deregister with SEAL SM server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.5.2 Request operation
|
API operation name: SS_SmDataSourceRegistration_Request
Description: registers the SM data source to the SEAL SM server.
Known Consumers: SEAL SM client.
Inputs: Refer Table 9.5.2.3.1-1
Outputs: Refer Table 9.5.2.3.2-1
See clause 9.5.2.2 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.5.3 Update operation
|
API operation name: SS_SmDataSourceRegistration_Update
Description: Updates existing registration of the SM data source to the SEAL SM server.
Known Consumers: SEAL SM client.
Inputs: Refer Table 9.5.3.3.1-1
Outputs: Refer Table 9.5.3.3.2-1
See clause 9.5.3.2 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.5.4 Deregister operation
|
API operation name: SS_SmDataSourceRegistration_Deregister
Description: Deregisters the existing registration of the SM data source to the SEAL SM server.
Known Consumers: SEAL SM client.
Inputs: Refer Table 9.5.4.3.1-1
Outputs: Refer Table 9.5.4.3.2-1
See clause 9.5.4.2 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.6 SS_SmDataSourceDiscovery API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.6.1 General
|
Service description: This API enables the VAL server to discover SM data sources from the SEAL SM server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.6.2 Request operation
|
API operation name: SS_SmDataSourceDiscovery_Request
Description: discovers the SM data sources from the SEAL SM server.
Known Consumers: VAL server.
Inputs: Refer Table 9.5.5.3.1-1
Outputs: Refer Table 9.5.5.3.2-1
See clause 9.5.5.2 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.6.3 Notify operation
|
API operation name: SS_SmDataSourceDiscovery_Notify
Description: Notify a SM data source to trigger a spatial mapping information session.
Known Consumers: SEAL SM client.
Inputs: Refer Table 9.5.5.3.3-1
Outputs: None
See clause 9.5.5 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.7 SS_SmSmasRegistration API
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.7.1 General
|
Service description: This API enables the VAL server with SM capabilities to register, update register or deregister with the SEAL SM server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.7.2 Request operation
|
API operation name: SS_SmSmasRegistration_Request
Description: registers the VAL server with SM capabilities to the SEAL SM server.
Known Consumers: VAL server.
Inputs: Refer Table 9.6.2.3.1-1
Outputs: Refer Table 9.6.2.3.2-1
See clause 9.6.2.2 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.7.3 Update operation
|
API operation name: SS_SmSmasRegistration_Update
Description: Updates existing registration of the VAL server with SM capabilities to the SEAL SM server.
Known Consumers: VAL server.
Inputs: Refer Table 9.6.3.3.1-1
Outputs: Refer Table 9.6.3.3.2-1
See clause 9.6.3.2 for the details of usage of this API operation.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
9.7.7.4 Deregister operation
|
API operation name: SS_SmSmasRegistration_Deregister Description: Deregisters the existing registration of the VAL server with SM capabilities to the SEAL SM server. Known Consumers: VAL server. Inputs: Refer Table 9.6.4.3.1-1 Outputs: Refer Table 9.6.4.3.2-1 See clause 9.6.4.2 for the details of usage of this API operation. Annex A (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2024-07 SA6#62-AE S6a240151 Skeleton 0.1.0 2024-08 SA6#62 S6-243614 Introduction and Scope of the TS 0.2.0 2024-08 SA6#62 S6-243661 Spatial Anchors Management Architecture 0.2.0 2024-08 SA6#62 S6-243669 Spatial Anchor Management and Discovery 0.2.0 2024-08 SA6#62 S6-243670 Spatial Anchor Subscription 0.2.0 2024-08 SA6#62 S6-243671 Spatial Map Management Architecture 0.2.0 2024-08 SA6#62 S6-243703 New text for clause 9 Spatial Map (SM) management 0.2.0 2024-10 SA6#63 S6-244187 Pseudo-CR on Terms and Abbreviations 0.3.0 2024-10 SA6#63 S6-244563 Pseudo-CR on business relation and functional model 0.3.0 2024-10 SA6#63 S6-244564 Spatial anchor update 0.3.0 2024-10 SA6#63 S6-244686 Spatial Anchor Analytics Information 0.3.0 2024-10 SA6#63 S6-244687 Pseudo-CR on enhancements to spatial anchor subscription procedure 0.3.0 2024-10 SA6#63 S6-244689 Pseudo-CR on enhancements to spatial map subscription procedures 0.3.0 2024-10 SA6#63 S6-244690 Pseudo-CR on Support for spatial mapping data sources 0.3.0 2024-10 SA6#63 S6-244700 Pseudo-CR on Support for spatial mapping service exposure 0.3.0 2024-10 SA6#63 S6-244711 Pseudo-CR on localization service 0.3.0 2024-10 SA6#63 S6-244712 Spatial map procedure updates and Information Flows 0.3.0 2024-11 SA6#64 S6-245517 TS clean up and restructuring 0.4.0 2024-11 SA6#64 S6-245518 Updates to Terms 0.4.0 2024-11 SA6#64 S6-245519 Pseudo-CR on Spatial map management requirements 0.4.0 2024-11 SA6#64 S6-245520 Pseudo-CR on architectural requirements 0.4.0 2024-11 SA6#64 S6-245676 Pseudo-CR on Identities and commonly used values 0.4.0 2024-11 SA6#64 S6-245114 Pseudo-CR on general clauses 0.4.0 2024-11 SA6#64 S6-245735 Pseudo-CR on spatial anchor usage information update 0.4.0 2024-11 SA6#64 S6-245523 Pseudo-CR on Spatial anchor usage analytics reporting 0.4.0 2024-11 SA6#64 S6-245636 Spatial Anchor Usage Analytics API clause 0.4.0 2024-11 SA6#64 S6-245699 Spatial Anchor association with Spatial Map 0.4.0 2024-11 SA6#64 S6-245120 Pseudo-CR on correction to SM service procedure 0.4.0 2024-11 SA6#64 S6-245700 Pseudo-CR on implicit subscription for spatial map ready event 0.4.0 2024-11 SA6#64 S6-245506 Pseudo-CR on APIs for Spatial anchors and Spatial map services 0.4.0 2024-12 SA#106 SP-241702 Submitted to SA#106 for information and approval 1.0.0 2024-12 SA#106 SP-241702 MCC Editorial update for publication after TSG SA approval (SA#106) 19.0.0 2025-03 SA#107 SP-250214 0001 1 F Correction for clause 8.4 19.1.0 2025-03 SA#107 SP-250214 0005 1 B Remove EN on access control rules 19.1.0 2025-03 SA#107 SP-250214 0006 B Removing EN on additional events 19.1.0 2025-03 SA#107 SP-250214 0007 1 B Removing EN on Get operation 19.1.0 2025-03 SA#107 SP-250214 0009 4 F Update to requestor identity in information flows 19.1.0 2025-03 SA#107 SP-250214 0010 1 B SMAS discovery procedure 19.1.0 2025-03 SA#107 SP-250214 0011 2 B Spatial anchor usage reporting 19.1.0 2025-03 SA#107 SP-250214 0016 1 B Enhancements to SM data source services 19.1.0
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
1 Scope
|
The present document specifies the application layer architecture, procedures and information flows necessary for digital asset service to support mobile metaverse services. It includes architectural requirements, application layer architecture fulfilling the architecture requirements and procedures to manage digital assets.
The normative work in the present document is based on the requirements as defined in 3GPP TS 22.156 [2].
NOTE: In the current release of this specification, the digital asset type is limited to digital avatar. Other types of digital asset are for the consideration of future release.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.156: "Mobile Metaverse Services".
[3] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs".
[4] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
3 Definitions of terms, symbols and abbreviations
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
3.1 Terms
|
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Digital asset profile: It is a digital asset specific configuration and parameters (e.g. allowed locations) applicable to one or more application(s). The digital asset profile may be associated with one or more VAL user(s). In this release, avatar is considered as a digital asset.
Digital asset identifier: A digital asset identifier is used to uniquely identify a digital asset across different mobile metaverse services.
For the purposes of the present document, the following terms given in 3GPP TS 22.156 [2] apply:
Avatar
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
CAPIF Common API Framework for 3GPP northbound APIs
DA Digital Asset
SEAL Service Enabler Architecture Layer for verticals
VAL Vertical Application Layer
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
4 Overview
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
4.1 General
|
This clause provides an overview of the features supported by digital asset service.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
4.2 Digital asset profile management
|
The digital asset profile management feature is specified in clause 8.2. It enables a consumer (VAL server or DA client) of digital asset service to be able to manage (CRUD) a digital asset profile. This is a necessary feature to make a digital asset exposure via the digital asset service.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
4.3 Digital asset discovery
|
The digital asset profile discovery feature is specified in clause 8.3. It enables a DA client to discover digital assets available in the digital asset service.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
4.4 Digital asset media management
|
The digital asset media management feature is specified in clause 8.4. It enables a consumer (VAL server or DA client) of digital asset service to manage the media related to digital asset profile.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
5 Architectural requirements
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
5.1 General
|
This clause specifies the architectural requirements for digital asset service.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
5.2 Digital asset profile management requirements
|
This clause specifies the requirements for digital asset profile management.
[AR-5.2-a] The digital asset service shall provide mechanisms to support management (CRUD) of digital assets profiles.
[AR-5.2-b] The digital asset service shall provide mechanisms to support management (CRUD) of digital assets collection.
[AR-5.2-c] The digital asset service shall provide mechanisms to control access to digital assets by one or more users other than the owner of the digital asset.
[AR-5.2-d] The digital asset service shall provide mechanisms to control access to digital assets by one or more applications.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
5.3 Digital asset discovery requirements
|
This clause specifies the requirements for digital asset discovery.
[AR-5.3-a] The digital asset service shall provide mechanisms to support discovery of digital assets.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
5.4 Digital asset media management requirements
|
This clause specifies the requirements for digital asset media management.
[AR-5.4-a] The digital asset service shall provide mechanisms to upload/store the digital asset media corresponding to a digital asset profile.
[AR-5.4-b] The digital asset service shall provide mechanisms to download the digital asset media corresponding to authorized users of the digital asset.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6 Architecture
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.1 General
|
The digital asset service architecture enables the digital asset service capabilities and resources to be offered as APIs to be consumed by the VAL services deployed in the network and to be consumed by the VAL services and DA clients deployed on the UE. The different architecture representations are specified in this clause.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.2 Architecture description
|
Figure 6.2-1 illustrates the digital asset service architecture to support Metaverse services using SEAL architecture specified in 3GPP TS 23.434 [4].
Figure 6.2-1: Digital asset service architecture to support Metaverse services using SEAL architecture
The SEAL architecture includes DA client and server which supports the VAL layer. The DA server interacts with the VAL server(s) over the DA-S reference point. The DA client interacts with the VAL client(s) over the DA-C reference point. The interactions between DA client and DA server is over the DA-UU reference point. The DA server may utilize the 5GC services over N33 reference point. The DA client may be located within the VAL client(s) in which case the DA-C reference point will be internal to VAL client(s). The service APIs offered by DA server on DA-UU and DA-S to the VAL layer functions (via DA client) follow the service-based architecture as shown in the figure 6.2-3.
Figure 6.2-2 illustrates the service-based SEAL architecture for digital asset service to support Metaverse services.
Figure 6.2-2: Service-based SEAL architecture for digital asset service to support Metaverse services
The DA server exposes the APIs over the Sda interface to the VAL layer. The VAL functions (VAL clients and servers) and the DA client (serving a VAL client) consume the services by interacting on the Sda interface of the DA server. The CAPIF as specified in 3GPP TS 23.222 [3] can be used by VAL functions to discover the services of the DA server.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.3 Functional elements
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.3.1 DA client
|
The following capabilities are supported by the DA client:
- Supports the client-side functionalities for digital asset profile create, update, retrieve and delete operations.
- Supports the client-side functionalities for digital asset discovery.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.3.2 DA server
|
The following capabilities are supported by the DA server:
- Supports the functionalities for digital asset profile create, update, retrieve and delete operations.
- Supports the functionalities for digital asset discovery.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.4 Reference points
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.4.1 DA-C
|
This reference point supports the interactions between VAL client(s) and DA client.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.4.2 DA-UU
|
This reference point supports the interactions between DA client(s) and DA server. The DA client can consume the digital asset services supported by the DA server as specified in clause 6.3.2.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.4.3 DA-S
|
This reference point supports the interactions between VAL server(s) and DA server. The VAL server consumes the digital asset services supported by the DA server as specified in clause 6.3.2.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.