hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.3.1 Subscribe SM data source request
| Table 9.5.6.3.1-1 shows the subscribe SM data source request sent by VAL server or SEAL server to SEAL SM server to subscribe for SM data source event(s).
Table 9.5.6.3.1-1: Subscribe SM data source request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or SEAL server)
Security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Notification Target Address
O
Notification target address (e.g. URL) where the notifications should be sent.
Expiry time
O
Proposed subscription expiry time
List of SM data source IDs
O
(NOTE)
ID(s) of the SM data source(s) to subscribe
Area of interest
O
(NOTE)
Three-dimensional area information to discover SM data source(s) to subscribe
Triggering criteria
M
Specifies the condition to determine whether the event is occurred and to notify the requestor
> Changes in SM data source profiles
O
Triggers notification if any or specified element described in Table 7.3.3.2-1 change is detected or if SM data source profile(s) created or deleted based on the registration and deregistration of SM data source(s).
> Notification intervals
O
Specifies when to notify the detected event,
Possible values are:
- Event based (e.g., promptly); Or
- Periodically (with minimum time between consecutive notifications)
- intervals (i.e. minimum time between consecutive notifications)
> interval time
O
Time between consecutive notifications (applicable only if notification intervals is set to intervals.
NOTE: At least one of these elements shall be provided.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.3.2 Subscribe SM data source response
| Table 9.5.6.3.2-1 shows the subscribe SM data source response sent by SEAL SM server to VAL server or SEAL server.
Table 9.5.6.3.2-1: Subscribe SM data source response
Information element
Status
Description
Result
M
Result of the subscribe SM data source 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.5.6.3.3 Notify SM data source event
| Table 9.5.6.3.3-1 shows the SM data source notification sent by SEAL SM server to VAL server or SEAL server to notify about SM data source event(s).
Table 9.5.6.3.3-1: SM data source event notification
Information element
Status
Description
Subscription ID
M
Identifier of the subscription request
Notification information
M
Specifies what matches the triggering notification condition, including related information
Event type
M
Type of event detected (i.e SM data source profile(s) created , updated or deleted.
SM data source(s) profile list
M
Indicates list of SM data source ID and information about changes in the SM data source.
> SM data source ID
M
Identifier of the SM data source
> SM Data source profile
O
(NOTE)
Updated or created data source profile of the SM data source as specified in clause 7.3.3.2.
NOTE: This IE shall be present if the event type is created or updated.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.3.4 SM data source subscription update request
| Table 9.5.6.3.4-1 shows the SM data source subscription update request sent by VAL server or SEAL server to SEAL SM server.
Table 9.5.6.3.4-1: SM data source subscription update request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or SEAL server)
Security credentials
M
The security credentials of the requestor.
Subscription ID
M
Subscription identifier corresponding to the subscription to be updated.
Notification Target Address
O
Notification target address (e.g. URL) where the notifications should be sent.
Expiry time
O
Proposed subscription expiry time
Target SM data source(s)
O
SM data source(s) to subscribe
> List of SM data source IDs
O
ID(s) of the SM data source(s) to subscribe
> Area of interest
O
Three-dimensional area information to discover SM data source(s) to subscribe
List of events
O
Events to subscribe. Each element includes the information described below.
> Event type
O
List of events to subscribed. Possible values are:
- Change of SM Data source(s)
> Triggering criteria
O
Specifies the condition to determine whether the event is occurred and to notify the requestor
>> Changes in SM data source profiles
O
Triggers notification if any or specified element described in Table 7.3.3.2-1 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.3.5 SM data source subscription update response
| Table 9.5.6.3.5-1 shows the subscribe SM data source subscription update response sent by SEAL SM server to VAL server or SEAL server.
Table 9.5.6.3.5-1: SM data source subscription update response
Information element
Status
Description
Result
M
Result of the SM data source subscription update 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.5.6.3.6 SM data source unsubscribe request
| Table 9.5.6.3.6-1 describes information elements for the SM data source unsubscribe request from the SEAL server or VAL server to the SM server.
Table 9.5.6.3.6-1: SM data source unsubscribe request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server).
Security credentials
M
Security credentials of the requestor
Subscription ID
M
Subscription identifier corresponding to the subscription to be unsubscribed
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.6.3.7 SM data source unsubscribe response
| Table 9.5.6.3.7-1 describes information elements for the SM data source unsubscribe response sent by the SM server.
Table 9.5.6.3.7-1: SM data source unsubscribe response
Information element
Status
Description
Successful response
O
Indicates that the unsubscribe request was successful.
Failure response
O
Indicates that the unsubscribe request failed.
> Cause
O
Indicates the cause of unsubscribe request failure
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.7 SM data source triggering
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.7.1 General
| The SM data source triggering procedure allows an SM data source consumer (e.g., VAL server or SEAL server) to trigger SM data source reporting.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.7.2 Procedure
| Figure 9.5.7.2-1 depicts the procedure for an authorized SM data source consumer to trigger SM data reporting.
Pre-conditions:
1. The SM data source consumer has received information (e.g. URI, IP address) related to the SEAL SM server;
2. The SM data source consumer has received security credentials authorizing it to communicate with the SEAL SM server.
3. The SM data source consumer has performed SM data source discovery as described in clause 9.5.5.2 and has obtained a triggered reporting identifier.
Figure 9.5.7.2-1: SM data source triggering procedure
1. The requestor (e.g, VAL server or SEAL server) sends a SM data source triggering request to the SEAL SM server. The request includes a requestor ID, security credentials, and a triggered reporting identifier.
2. The SEAL SM server authorizes the requestor and validates the request. If the request is authorized, the SEAL SM server retrieves the SM data source(s) associated with the triggered reporting identifier included in the request and sends a SM data source notification to the retrieved SM data source(s) as described in step 3 of clause 9.5.5.2.
3. The SEAL SM server sends a SM data source triggering response to the requestor. The response includes an indication of success if the triggered reporting identifier is valid. Otherwise, the SEAL SM server sends a failure indication and may include a cause for failure.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.7.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.7.3.1 SM data source triggering request
| Table 9.5.7.3.1-1 describes information elements in the SM data source triggering request from the SM data source consumer to the SEAL SM server.
Table 9.5.7.3.1-1: SM data source triggering 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
Triggered reporting ID
M
The identifier of a triggered reporting.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.5.7.3.2 SM data source triggering response
| Table 9.5.7.3.2-1 describes information elements in the SM data source triggering response from the SEAL SM server to the SM data source consumer.
Table 9.5.7.3.2-1: SM data source triggering response
Information element
Status
Description
Successful response
O
Indicates that the triggering request was successful
Failure response
O
Indicates that the request failed
> Cause
O
Indicates the cause of the failure
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6 SM service capable application server (SMAS)
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6.2 SMAS registration
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6.2.1 General
| The SMAS registration procedure registers the authorized VAL server with SM capability with SEAL SM server.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6.2.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 identifier
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
|
26e140d21b097a2c000610e4bd7ffb34 | 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
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6.3 SMAS registration update
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6.3.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 identifier
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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6.4 SMAS deregistration
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6.4.1 General
| The SMAS deregistration procedure deregisters the authorized VAL server with SM capability from the SEAL SM server.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6.4.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 identifier
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
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.6.4.3.2 SMAS deregistration response
| 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
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7 SEAL APIs for spatial map management
| |
26e140d21b097a2c000610e4bd7ffb34 | 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_SmDataSourceSubscription
Subscribe
VAL server
Subscribe/Notify
Notify
VAL server
Update
VAL server
Unsubscribe
VAL server
SS_SmSmasRegistration
Request
VAL server
Request/Response
Update
VAL server
Deregister
VAL server
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.2 SS_SmManagement API
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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: Refer Table 9.3.6.3.3-1
Outputs: None
See clause 9.3.6.2.2 for the details of usage of this API operation.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.3 SS_SmDiscovery API
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.4 SS_SmLocalization API
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.5 SS_SmDataSourceRegistration API
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.6 SS_SmDataSourceDiscovery API
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.7 SS_SmSmasRegistration API
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.8 SS_SmDataSourceSubscription API
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.8.1 General
| Service description: This API enables the VAL server to subscribe to the SEAL SM server to get the updates related to changes in SM data source profiles.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.8.2 Subscribe operation
| API operation name: SS_SmDataSource_Subscribe
Description: Subscription to get the updates related to SM data source profiles.
Known Consumers: VAL server.
Inputs: Refer Table 9.5.6.3.1-1
Outputs: Refer Table 9.5.6.3.2-1
See clause 9.5.6.2.1 for the details of usage of this API operation.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.8.3 Notify operation
| API operation name: SS_SmDataSource_Notify
Description: Notifies the subscribers of the changes to the SM data source profiles.
Known Consumers: VAL server.
Inputs: Refer Table 9.5.6.3.3-1
Outputs: None
See clause 9.5.6.2.2 for the details of usage of this API operation.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 9.7.8.4 UpdateSubscription operation
| API operation name: SS_ SmDataSource _UpdateSubscription
Description: The consumer updates an existing subscription for SM data source profiles.
Inputs: Refer Table 9.5.6.3.4-1.
Outputs: Refer Table 9.5.6.3.5-1.
See clause 9.5.6.2.x for details of usage of this operation.
9.7.x.5 Unsubscribe operation
API operation name: SS_ SmDataSource_Unsubscribe
Description: The consumer cancels an existing subscription for SM data source profiles.
Inputs: See clause 9.5.6.3.6-1.
Outputs: See clause 9.5.6.3.7-1.
See clause 9.5.6.2.4 for details of usage of this 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
2025-06
SA#108
SP-250610
0017
2
F
Fix for spatial anchor usage information (Sub-Notify)
19.2.0
2025-06
SA#108
SP-250610
0023
1
F
Removing ENs in Spatial map subscription
19.2.0
2025-06
SA#108
SP-250610
0024
1
F
Enhancement to spatial localization services procedure text
19.2.0
2025-06
SA#108
SP-250610
0027
1
F
Corrections to Clause 8
19.2.0
2025-06
SA#108
SP-250610
0028
1
F
Updates to the spatial anchor profile
19.2.0
2025-06
SA#108
SP-250610
0030
1
F
Corrections to spatial anchor specific information
19.2.0
2025-06
SA#108
SP-250610
0031
F
Retrieving spatial map augmented layer information
19.2.0
2025-06
SA#108
SP-250610
0034
1
F
EN resolution on changed objects event
19.2.0
2025-06
SA#108
SP-250610
0041
F
Corrections to the Create spatial map response and Subscribe spatial map event request IEs
19.2.0
2025-06
SA#108
SP-250610
0042
F
Correction for spatial map subscription
19.2.0
2025-06
SA#108
SP-250611
0021
3
B
Spatial map layer link
20.0.0
2025-06
SA#108
SP-250611
0029
2
B
Spatial anchor group management operations
20.0.0
2025-06
SA#108
SP-250611
0035
1
B
Support for spatial map media format
20.0.0
2025-06
SA#108
SP-250611
0036
2
B
Enhancements to SM data source services
20.0.0
2025-06
SA#108
SP-250611
0039
2
B
Enhancement to exposure of object(s) tracking
20.0.0
2025-06
SA#108
SP-250611
0040
2
B
Enhancement to support spatial anchor on trackable objects
20.0.0
2025-06
SA#108
SP-250611
0044
3
B
Management operation of spatial anchor group
20.0.0
2025-06
SA#108
SP-250611
0045
2
B
Supporting localization of users/UEs by multiple spatial maps
20.0.0
2025-06
SA#108
SP-250611
0046
1
B
Spatial anchor group management operations
20.0.0
2025-06
SA#108
SP-250611
0047
2
B
Corrections to spatial anchor information and handling
20.0.0
2025-09
SA#109
SP-251062
0025
4
B
Spatial anchor distance compute service
20.1.0
2025-09
SA#109
SP-251062
0037
5
B
Enhancements to SM data source events
20.1.0
2025-09
SA#109
SP-251062
0050
1
B
Spatial map UE to object association
20.1.0
2025-09
SA#109
SP-251061
0052
1
A
Fix for clause 9.3
20.1.0
2025-09
SA#109
SP-251061
0054
A
Fix for clause 9.4
20.1.0
2025-09
SA#109
SP-251061
0056
A
Fix for clause 9.5
20.1.0
2025-09
SA#109
SP-251062
0060
2
B
Spatial anchor group management – update procedure
20.1.0
2026-01
SA#110
SP-251486
0063
2
F
Fix for clause 9.5.5.2
20.2.0
2026-01
SA#110
SP-251485
0065
A
Fix for clause 9.6
20.2.0
2026-01
SA#110
SP-251486
0070
2
B
SM data source triggering
20.2.0
2026-01
SA#110
SP-251486
0071
1
F
Removing ENs related to request object tracking
20.2.0
2026-01
SA#110
SP-251485
0073
1
A
Add reference to Pose definition
20.2.0
2026-01
SA#110
SP-251486
0075
2
B
Required Spatial map information
20.2.0
2026-01
SA#110
SP-251486
0076
1
F
Handling Editor’s Notes
20.2.0
2026-01
SA#110
SP-251486
0077
1
F
Spatial Anchor Group Management APIs
20.2.0
2026-01
SA#110
SP-251486
0078
1
F
SM data source subscription APIs
20.2.0
2026-01
SA#110
SP-251486
0079
2
B
Spatial Anchor Group Retrieve operation
20.2.0
2026-01
SA#110
SP-251486
0080
B
Updates to SM Data Source subscription procedures
20.2.0
2026-01
SA#110
SP-251486
0083
Corrections to TS 23.437 SAn clauses (mirror)
20.2.0
2026-01
SA#110
SP-251485
0086
1
A
Corrections to TS 23.437 SM and common clauses (mirror)
20.2.0
2026-01
SA#110
SP-251485
0092
1
A
Fix for clause 8.3.6
20.2.0
2026-01
SA#110
SP-251486
0096
2
C
Updates to the SM data source subscription
20.2.0
|
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 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".
[5] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 3 Definitions of terms, symbols and abbreviations
| |
676d3698b25fe18441c7058a012cf0fe | 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
digital asset
|
676d3698b25fe18441c7058a012cf0fe | 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
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 4 Overview
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 4.1 General
| This clause provides an overview of the features supported by digital asset service. The digital asset service is supported for both IMS and non-IMS communication. In this specification, the digital asset is implemented as a combination of digital asset profile along with associated media to represent the asset. The digital asset service supports the following features:
- Management of digital assets profile
- Management of digital asset media
- Discovery of digital assets
|
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 5 Architectural requirements
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 5.1 General
| This clause specifies the architectural requirements for digital asset service.
|
676d3698b25fe18441c7058a012cf0fe | 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] Void
[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.
|
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 6 Architecture
| |
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 6.3 Functional elements
| |
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 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.
NOTE: The DA server as specified in this specification supports the Base Avatar Repository (BAR) (related to avatar communications) as specified in 3GPP TS 23.228 [5].
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 6.4 Reference points
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 6.4.1 DA-C
| This reference point supports the interactions between VAL client(s) and DA client.
|
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 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.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 6.5 Service-based interface
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 6.5.1 Sda
| This interface supports the interactions between VAL function (VAL servers) and DA server. The VAL function consumes the digital asset service as specified in clause 6.3.2.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 7 Identities and commonly used information
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 7.1 General
| This clause specifies details about the identifiers and common values used for digital asset service.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 7.2 Digital asset profile
| The digital asset profile includes the information elements about the attributes of a single digital asset. Table 7.2-1 shows the information elements for the digital asset profile.
NOTE 1: In this release, the digital asset profile is specified considering Avatar as a digital asset of the user.
Table 7.2-1: Digital asset profile
Information element
Status
Description
Digital asset ID
M
Identifier of the digital asset profile
Digital asset type
M
Type of the digital asset. (For this release, it contains "Avatar").
List of owners
M
List of identity of the owner user(s) who created the digital asset.
List of service provider identifiers
O
List of service providers for the digital asset.
Digital asset name
O
The name of the digital asset
Digital asset description
O
The description on the digital asset
access control list
O
List of tuples indicating the requestors allowed to perform operations with this digital asset and the allowed operation types.
> allowed user list
O
List of users allowed to access this digital asset
>> allowed operations
O
List of operations allowed by this user. Possible operations are (one or more of) : Discovery, Retrieve, Update, Delete
>> list of predictive models
O
For each allowed user, list of one or more predictive model for the user, in order to predict user's behaviour.
current status
O
Current status (in use or not) of the profile
spatial conditions
O
List of spatial conditions (e.g. locations) where this digital asset profile is allowed to be accessed
> current location
O
Current location where the profile is being used
allowed application list
O
List of application IDs which are allowed to use this digital asset profile
associated accessories identifiers
O
List of digital asset identifiers which are accessories (e.g. Hat, watch, shoes) purchased for this digital asset profile
expiry time
O
Time until this digital asset profile is valid
History information
O
Usage history for this digital asset profile
> list of locations
O
List of locations where the digital asset profile is used.
> time of use
O
Time information when the digital asset profile is used
> list of applications
O
List of the application IDs which used this digital asset profile.
List of digital asset media information
O
List of digital asset media
> Media URI
O
(NOTE 1)
URI where the media is stored
> Media object
O
(NOTE 1)
Media object (e.g. JPG file)
Digital signature
O
The digital signature of this digital asset, signed by the DA server
NOTE 1: One of the IE shall be included
NOTE 2: The provisioning of the certificate of the DA server and generation and usage of the digital signature at DA server are left for implementation.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.