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 serv... |
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... |
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
Notificatio... |
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)
S... |
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
Subscrip... |
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).
... |
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
Indi... |
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 ... |
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)
... |
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 successfu... |
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 c... |
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 ... |
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
Id... |
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 ... |
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 crede... |
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
> E... |
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. ... |
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
... |
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 respo... |
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
Upd... |
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 ope... |
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 operat... |
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... |
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 operati... |
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 a... |
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.
-... |
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. ... |
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 ... |
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 di... |
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 ... |
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 c... |
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 ... |
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 supp... |
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 (B... |
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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.