hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 7.3 Void
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 7.4 Identities
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 7.4.1 General
| Following identifies as defined in clause 7 of 3GPP TS 23.434 [4] are applicable for this specification too.
- User ID
- VAL user ID
- VAL UE ID
- VAL service ID
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 7.4.2 Identities related to digital asset
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 7.4.2.1 Digital asset identifier (Digital asset ID)
| A unique identifier to identify digital asset. A digital asset has only one digital asset profile, the digital asset identifier is also used to uniquely identify the digital asset profile of the digital asset. It is assigned by SEAL DA server. The identity is globally unique.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 7.4.2.2 Void
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8 Procedures and information flows
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.1 General
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2 Digital asset profile management
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.1 General
| The following clauses specify procedures, information flows, and APIs for digital asset profile management.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.2 Procedures
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.2.1 Digital asset profile create
|
Figure 8.2.2.1-1: Digital asset profile create
1. A requestor (e.g. DA client) sends a digital asset create request to the DA server. The request includes information listed in Table 8.2.3.1-1.
2. The DA server authenticates and authorizes the request. If authorized, the DA server creates the digital asset profile (as per clause 7.2), assigns globally unique digital asset identifier and stores the information about the digital asset profile in a local repository.
3. The DA server generates and sends a response to the requestor. The response includes information listed in Table 8.2.3.2-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.2.2 Digital asset profile retrieve
| The digital asset retrieve procedure obtains information about the digital asset and is different from digital asset discovery.
Figure 8.2.2.2-1: Digital asset profile retrieve
1. A requestor (e.g. DA client) sends a digital asset retrieve request to the DA server. The request includes information listed in Table 8.2.3.3-1.
2. The DA server authenticates and authorizes the request. If authorized, the DA server retrieves the digital asset from the local repository.
3. The DA server generates and sends a response to the requestor. The response includes information listed in Table 8.2.3.4-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.2.3 Digital asset profile update
|
Figure 8.2.2.3-1: Digital asset profile update
1. A requestor (e.g. DA client) sends a digital asset update request to the DA server. The request includes information listed in Table 8.2.3.5-1.
2. The DA server authenticates and authorizes the request. If authorized, the DA server updates information about the digital asset in the local repository.
3. The DA server generates and sends a response to the requestor. The response includes information listed in Table 8.2.3.6-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.2.4 Digital asset profile delete
|
Figure 8.2.2.4-1: Digital asset profile delete
1. A requestor (e.g. DA client) sends a digital asset delete request to the DA server. The request includes information listed in Table 8.2.3.7-1.
2. The DA server authenticates and authorizes the request. If authorized, the DA server deletes the digital asset from the local repository.
3. The DA server generates and sends a response to the requestor. The response includes information listed in Table 8.2.3.8-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.3 Information flows
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.3.1 Digital asset profile create request
| Table 8.2.3.1-1 describes the information elements for a digital asset profile create request sent from a requestor (e.g. DA client) to a DA server.
Table 8.2.3.1-1: Digital asset profile create request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Security credentials
M
Security credentials to authenticate and authorize the requestor.
Digital asset profile parameters
M
Parameters to create digital asset profile
Table 8.2.3.1-2: Parameters for digital asset profile
Information element
Status
Description
Digital asset owner identifier(s)
M
A list of identifier(s) for the digital asset owner.
Digital asset type
M
The type of digital asset, e.g. avatar, wallet, etc.
Digital asset name
O
The name of the digital asset
Digital asset description
O
The description on the digital asset
List of service provider identifiers
O
List of service providers for 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.
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
Editor's Note: The association of a subscriber/user identifier for the digital asset is FFS.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.3.2 Digital asset profile create response
| Table 8.2.3.2-1 describes the information elements for the digital asset profile create response sent from a DA server to a requestor (e.g. DA client).
Table 8.2.3.2-1: Digital asset profile create response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure code may be provided.
Digital asset identifier
M
An identifier for the digital asset.
Digital asset media upload endpoint
M
The end point provided by DA server at which digital asset media is to be uploaded.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.3.3 Digital asset profile retrieve request
| Table 8.2.3.3-1 describes the information elements for the digital asset profile retrieve request sent from a requestor (e.g. DA client) to a DA server.
Table 8.2.3.3-1: Digital asset profile retrieve request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Security credentials
M
Security credentials to authenticate and authorize the requestor.
Digital asset identifier
M
An identifier for the digital asset.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.3.4 Digital asset profile retrieve response
| Table 8.2.3.4-1 describes the information elements for the digital asset profile retrieve response sent from a DA server to a requestor (e.g. DA client).
Table 8.2.3.4-1: Digital asset profile retrieve response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure code may be provided.
Digital asset profile
M
The digital asset profile as specified in clause 7.2.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.3.5 Digital asset profile update request
| Table 8.2.3.5-1 describes the information elements for the digital asset profile update request sent from a requestor (e.g. DA client) to a DA server.
Table 8.2.3.5-1: Digital asset profile update request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Security credentials
M
Security credentials to authenticate and authorize the requestor.
Digital asset identifier
M
An identifier for the digital asset.
Digital asset profile parameters
M
The digital asset profile parameters as specified in Table 8.2.3.1-2.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.3.6 Digital asset profile update response
| Table 8.2.3.6-1 describes the information elements for the digital asset profile update response sent from a DA server to a requestor (e.g. DA client).
Table 8.2.3.6-1: Digital asset profile update response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure code may be provided.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.3.7 Digital asset profile delete request
| Table 8.2.3.7-1 describes the information elements for the digital asset profile delete request sent from a requestor (e.g. DA client) to a DA server.
Table 8.2.3.7-1: Digital asset profile delete request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Security credentials
M
Security credentials to authenticate and authorize the requestor.
Digital asset identifier
M
An identifier for the digital asset.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.3.8 Digital asset profile delete response
| Table 8.2.3.8-1 describes the information elements for the digital asset profile delete response sent from a DA server to a requestor (e.g. DA client).
Table 8.2.3.8-1: Digital asset profile delete response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure code may be provided.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.4 APIs
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.4.1 General
| Table 8.2.4.1-1 illustrates the SEAL APIs for digital asset profile management.
Table 8.2.4.1-1: List of SEAL APIs for digital asset profile management
API Name
API Operations
Known Consumer(s)
Communication Type
SS_DAProfileManagement
Create
DA client, VAL server
Request/Response
Retrieve
DA client, VAL server
Update
DA client, VAL server
Delete
DA client, VAL server
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.4.2 SS_DAProfileManagement API
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.4.2.1 General
| Service description: This API enables a VAL server (or DA client) to manage digital asset profile on a DA server.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.4.2.2 Create operation
| API operation name: SS_DAProfileManagement_Create
Description: The consumer requests to create digital asset profiles.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.2.3.1-1.
Outputs: See Table 8.2.3.2-1.
See clause 8.2.2.1 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.4.2.3 Retrieve operation
| API operation name: SS_DAProfileManagement_Retrieve
Description: The consumer requests to retrieve digital asset profiles.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.2.3.3-1.
Outputs: See Table 8.2.3.4-1.
See clause 8.2.2.2 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.4.2.4 Update operation
| API operation name: SS_DAProfileManagement_Update
Description: The consumer requests to update digital asset profiles.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.2.3.5-1.
Outputs: See Table 8.2.3.6-1.
See clause 8.2.2.3 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.2.4.2.5 Delete operation
| API operation name: SS_DAProfileManagement_Delete
Description: The consumer requests to delete digital asset profiles.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.2.3.7-1.
Outputs: See Table 8.2.3.8-1.
See clause 8.2.2.4 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.3 Digital asset discovery
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.3.1 General
| The following clauses specify procedures, information flows, and APIs for digital asset discovery.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.3.2 Procedure
|
Figure 8.3.2.1-1: Digital asset discovery
1. A DA client sends a digital asset discovery request to the DA server. The request includes information listed in Table 8.3.3.1-1.
2. The DA server authenticates and authorizes the request. If authorized, the DA server applies the discovery criteria to discover digital assets from the local repository.
3. The DA server generates and sends a response to the requestor. The response includes information listed in Table 8.3.3.2-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.3.3 Information flows
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.3.3.1 Digital asset discovery request
| Table 8.3.3.1-1 describes the information elements for a digital asset discovery request sent from a requestor (e.g. DA client or VAL server) to a DA server.
Table 8.3.3.1-1: Digital asset discovery request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Security credentials
M
Security credentials to authenticate and authorize the requestor.
Digital asset identifier
O
(NOTE)
The identifier of the digital asset.
Digital asset discovery filters
O
(NOTE)
Set of characteristics to determine matching digital asset (e.g., Digital asset name, Digital asset description, location, Digital asset type, Digital asset owner, Allowed user, Digital asset profile).
NOTE: At least one of the information elements shall be present
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.3.3.2 Digital asset discovery response
| Table 8.3.3.2-1 describes the information elements for the digital asset discovery response sent from a DA server to a requestor (e.g. DA client or VAL server).
Table 8.3.3.2-1: Digital asset discovery response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure code may be provided.
Discovery results
M
List of discovery results matching the discovery criteria.
>Digital asset identifier
O
(NOTE)
Identifier of the digital asset matching the discovery criteria.
>Digital asset name
O
(NOTE)
Name of the digital asset matching the discovery criteria.
>URL
O
A URL of the service provider the digital asset is associated with.
>Digital asset status
M
Status of the digital asset.
>Digital asset descriptions
O
Description of the digital asset.
NOTE: At least one of the information elements must be present.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.3.4 APIs
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.3.4.1 General
| Service description: This API enables a DA client to discover digital assets from a DA server.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.3.4.2 Discovery operation
| API operation name: SS_DADiscovery
Description: The consumer requests to discover digital assets.
Known Consumers: DA client.
Inputs: See Table 8.3.3.1-1.
Outputs: See Table 8.3.3.2-1.
See clause 8.3.2 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4 Digital asset media management
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.1 General
| The following clauses specify procedures, information flows, and APIs for digital asset media management.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.2 Procedures
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.2.1 Upload digital asset media
|
Figure 8.4.2.1-1: Upload digital asset media
1. A requestor (e.g. DA client) sends an upload digital asset media request to the DA server (at the digital asset media upload endpoint). The request includes information listed in Table 8.4.3.1-1.
2. The DA server authenticates and authorizes the request and verifies the digital asset identifier. If authorized, the DA server receives the media object or media URI corresponding to the digital asset profile, stores the media or the information about the digital asset media.
3. The DA server sends an upload digital asset media response to the requestor. The response includes information listed in Table 8.4.3.2-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.2.2 Download digital asset media
|
Figure 8.4.2.2-1: Download digital asset media
1. A requestor (e.g. DA client) sends a download digital asset media request to the DA server. The request includes information listed in Table 8.4.3.3-1.
2. The DA server authenticates and authorizes the request and verifies the digital asset identifier. If authorized, the DA server determines the digital asset media as per the information provided in step 1.
3. The DA server sends a download digital asset media response to the requestor. The response includes information listed in Table 8.4.3.4-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.2.3 Update digital asset media
|
Figure 8.4.2.3-1: Update digital asset media
1. A requestor (e.g. DA client) sends an update digital asset media request to the DA server. The request includes information listed in Table 8.4.3.5-1.
2. The DA server authenticates and authorizes the request and verifies the digital asset identifier. If authorized, the DA server receives the media object or media URI corresponding to the digital asset profile, updates the existing media or the information about the digital asset media corresponding to the digital asset identifier.
3. The DA server sends an update digital asset media response to the requestor. The response includes information listed in Table 8.4.3.6-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.2.4 Delete digital asset media
|
Figure 8.4.2.4-1: Delete digital asset media
1. A requestor (e.g. DA client) sends a delete digital asset media request to the DA server. The request includes information listed in Table 8.4.3.7-1.
2. The DA server authenticates and authorizes the request and verifies the digital asset identifier. If authorized, the DA server deletes the existing media or the information about the digital asset media corresponding to the digital asset identifier.
3. The DA server sends a delete digital asset media response to the requestor. The response includes information listed in Table 8.4.3.8-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.3 Information flows
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.3.1 Upload digital asset media request
| Table 8.4.3.1-1 describes the information elements for an upload digital asset media request sent from a requestor (e.g. DA client) to a DA server.
Table 8.4.3.1-1: Upload digital asset media request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Security credentials
M
Security credentials to authenticate and authorize the requestor.
Digital asset identifier
M
Identifier of the digital asset profile
List of digital asset media
M
List of digital asset media to be uploaded
> Media URI (NOTE)
O
URI where the media is stored
> Media object (NOTE)
O
Media object (e.g. JPG file)
NOTE: One of the IE shall be included
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.3.2 Upload digital asset media response
| Table 8.4.3.2-1 describes the information elements for the upload digital asset media response sent from a DA server to a requestor (e.g. DA client).
Table 8.4.3.2-1: Upload digital asset media response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure cause is provided.
Digital asset identifier
M
An identifier for the digital asset.
Cause
O
The cause information when the status is fail.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.3.3 Download digital asset media request
| Table 8.4.3.3-1 describes the information elements for the download digital asset media request sent from a requestor (e.g. DA client) to a DA server.
Table 8.4.3.3-1: Download digital asset media request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Security credentials
M
Security credentials to authenticate and authorize the requestor.
Digital asset identifier
M
An identifier for the digital asset.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.3.4 Download digital asset media response
| Table 8.4.3.4-1 describes the information elements for the download digital asset media response sent from a DA server to a requestor (e.g. DA client).
Table 8.4.3.4-1: Download digital asset media response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure cause is provided.
Digital asset identifier
M
An identifier for the digital asset.
List of digital asset media
M
List of digital asset media to be downloaded
> Media URI (NOTE)
O
URI where the media is stored
> Media object (NOTE)
O
Media object (e.g. JPG file)
NOTE: One of the IE shall be included
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.3.5 Update digital asset media request
| Table 8.4.3.5-1 describes the information elements for an update digital asset media request sent from a requestor (e.g. DA client) to a DA server.
Table 8.4.3.5-1: Update digital asset media request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Security credentials
M
Security credentials to authenticate and authorize the requestor.
Digital asset identifier
M
Identifier of the digital asset profile
List of digital asset media
M
List of digital asset media to be updated
> Media URI (NOTE)
O
URI where the media is stored
> Media object (NOTE)
O
Media object (e.g. JPG file)
NOTE: One of the IE shall be included
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.3.6 Update digital asset media response
| Table 8.4.3.6-1 describes the information elements for the update digital asset media response sent from a DA server to a requestor (e.g. DA client).
Table 8.4.3.6-1: Update digital asset media response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure cause is provided.
Digital asset identifier
M
An identifier for the digital asset.
Cause
O
The cause information when the status is fail.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.3.7 Delete digital asset media request
| Table 8.4.3.7-1 describes the information elements for a delete digital asset media request sent from a requestor (e.g. DA client) to a DA server.
Table 8.4.3.7-1: Delete digital asset media request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Security credentials
M
Security credentials to authenticate and authorize the requestor.
Digital asset identifier
M
Identifier of the digital asset profile
List of digital asset media
M
List of digital asset media to be deleted
> Media URI
O
(NOTE)
URI where the media is stored
> Media object
O
(NOTE)
Media object (e.g. JPG file)
NOTE: One of the IE shall be included
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.3.8 Delete digital asset media response
| Table 8.4.3.6-1 describes the information elements for the delete digital asset media response sent from a DA server to a requestor (e.g. DA client).
Table 8.4.3.8-1: Delete digital asset media response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure cause is provided.
Digital asset identifier
M
An identifier for the digital asset.
Cause
O
The cause information when the status is fail.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.4 APIs
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.4.1 General
| Table 8.4.4.1-1 illustrates the APIs for managing media related to digital asset profile.
Table 8.4.4.1-1: List of APIs for media management for digital asset
API Name
API Operations
Known Consumer(s)
Communication Type
SS_DAMediaManagement
Upload
DA client, VAL server
Request/Response
Download
DA client, VAL server
Update
DA client, VAL server
Delete
DA client, VAL server
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.4.2 SS_DAMediaManagement API
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.4.2.1 General
| Service description: This API enables a VAL server (or DA client) to manage media related to digital asset profile on a DA server.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.4.2.2 Upload operation
| API operation name: SS_DAMediaManagement_Upload
Description: The consumer requests to upload media related to digital asset.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.4.3.1-1.
Outputs: See Table 8.4.3.2-1.
See clause 8.4.2.1 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.4.2.3 Download operation
| API operation name: SS_DAMediaManagement_Download
Description: The consumer requests to retrieve media related to digital asset.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.4.3.3-1.
Outputs: See Table 8.4.3.4-1.
See clause 8.4.2.2 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.4.2.4 Update operation
| API operation name: SS_DAMediaManagement_Update
Description: The consumer requests to update media related to digital asset.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.4.3.5-1.
Outputs: See Table 8.4.3.6-1.
See clause 8.4.2.3 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.4.4.2.5 Delete operation
| API operation name: SS_DAMediaManagement_Delete
Description: The consumer requests to delete media related to digital asset.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.4.3.7-1.
Outputs: See Table 8.4.3.8-1.
See clause 8.4.2.4 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5 Digital asset usage report
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.1 General
| The following clauses specify procedures, information flows, and APIs for digital asset usage report.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.2 Procedures
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.2.1 Digital asset usage report (Request-Response)
|
Figure 8.5.2.1-1: Digital asset usage report (Rquest-Response)
1. The requestor (e.g. DA client or VAL server) sends a digital assets usage report request to the DA server to get the digital assets usage information report and the request contains the information elements listed in Table 8.5.3.1-1.
2. The DA server authenticates and authorizes the request. If authorized, the DA server prepares the digital assets usage report based on the requested information received in step 1.
3. The DA server provides the digital assets usage report response to the requestor. The response message includes the information as specified in Table 8.5.3.2-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.2.2 Digital asset usage report (Subscribe-Notify)
|
Figure 8.5.2.2-1: Digital asset usage report (Subscribe-Notify)
1. The requestor (e.g. DA client or VAL server) sends a Digital assets usage report subscription request to the DA server. The request includes the information as specified in Table 8.5.3.3-1.
2. Upon receiving the request, the DA server checks whether the requestor is authorized to subscribe for the digital assets usage report.
3. If authorized, DA server sends the Digital assets usage information subscription response as specified in Table 8.5.3.4-1 with status as success otherwise failure if not authorized.
4. The DA server creates the report related to digital assets usage based on the filters provided in the step 1 and provides notification to the requestor as per the reporting interval. The notification message includes the information as specified in Table 8.5.3.5-1.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.3 Information flows
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.3.1 Digital asset usage report request
| Table 8.5.3.1-1 describes the information elements for digital asset usage report request sent from a requestor (e.g. DA client) to a DA server.
Table 8.5.3.1-1: Digital asset usage report 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.
Digital assets filters
M
Indicates the digital assets filter for the report as specified in Table 8.5.3.1-2
Table 8.5.3.1-2: Digital asset usage report filters
Information element
Status
Description
Digital assets identifiers
O
(NOTE)
Indicates the digital assets identities
Location information
O
(NOTE)
Indicates the location information of a particular geographical area for identifying the digital assets usage in that area
Application service information
O
(NOTE)
Indicates the digital assets usage of a particular application (e.g., application identifier)
Identities of the consumers
O
(NOTE)
Identifiers of the users (e.g. VAL user ID, VAL Server identity) of whose digital assets usage information/report required.
Unutilized digital assets
O
(NOTE)
Indication to include the list of digital assets identities which are discovered but not accessed/downloaded
Undiscovered digital assets
O
(NOTE)
Indication to include the list of digital assets identities which are not discovered by the consumers
NOTE: At least one of these information elements shall be present.
Editor's Note: Whether permission or consent is required from the consumers if digital assets usage report is requested for a list of consumers.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.3.2 Digital asset usage report response
| Table 8.5.3.2-1 describes the information elements for digital asset usage report response sent from DA server to requestor (e.g. DA client).
Table 8.5.3.2-1: Digital asset usage report response
Information element
Status
Description
Successful response
O
Indicates that the request was successful.
Digital assets usage report
M
Details of the digital assets usage report
> List of digital asset (NOTE)
O
Identifies the list of digital assets
>> Digital asset identifier
M
Identity of the digital asset
>>> List of consumers
M
Indicates the list of consumer identifiers (VAL user Id, VAL server ID) accessed the digital assets
>>> Location information
O
Indicates the geographical area where the digital asset is accessed frequently
> Location information (NOTE)
O
Indicates the geographical area for which digital assets usage report is generated
>> List of Digital asset identifiers
M
Identifies the digital assets being used/accessed in the given geographical area
>>> Number of access
M
Indicates the no of times a particular digital asset is accessed/used in the given geographical area. This helps to identify the frequently or less frequently used digital assets in a given geographical area
> List of Identifiers of the consumers (NOTE)
O
Indicates the list of consumer identifiers (VAL user Id, VAL server ID) accessed the digital assets
>> List of Digital asset identifiers
M
Identifies the digital assets being used/accessed by the consumer
> Unutilized digital assets
O
Indicates the list of digital assets identities which are discovered but not accessed/downloaded
> Undiscovered digital assets
O
Indicates the list of digital assets identities which are not discovered by the consumers
Failure response
O
Indicates that the request was failure
> Reason code
M
Reason for the failure
NOTE: Success response shall include at least one of these information elements..
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.3.3 Digital asset usage subscription request
| Table 8.5.3.3-1 describes the information elements for digital asset usage subscription request sent from requestor (e.g. DA client) to DA server.
Table 8.5.3.3-1: Digital asset usage subscription 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.
Digital assets filters
M
Indicates the digital assets filter for the report as specified in Table 8.5.3.1-2.
Reporting interval
O
Indicates the periodic reporting interval of information
Notification endpoint
O
Indicates the endpoint(e.g., IP address, FQDN, URI) to send the information notification
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.3.4 Digital asset usage subscription response
| Table 8.5.3.4-1 describes the information elements for digital asset usage subscription response sent from DA server to requestor (e.g. DA client).
Table 8.5.3.4-1: Digital asset usage subscription response
Information element
Status
Description
Successful response
O
Indicates that the subscription request was successful.
> Digital asset usage information subscription ID
M
Identity for the digital asset usage information subscription
Failure response
O
Indicates that the subscription request has failed.
> Cause
O
The cause for the request failure.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.3.5 Digital asset usage report notification
| Table 8.5.3.5-1 describes the information elements for digital asset usage report notification sent from DA server to requestor (e.g. DA client).
Table 8.5.3.5-1: Digital asset usage report notification
Information element
Status
Description
> Digital asset usage information subscription ID
M
Identity for the digital asset usage information subscription
Digital assets usage report
M
Details of the digital assets usage report
> List of digital asset
O
(NOTE)
Identifies the list of digital assets
>> Digital asset identifier
M
Identity of the digital asset
>>> List of consumers
M
Indicates the list of consumer identifiers (VAL user Id, VAL server ID) accessed the digital assets
>>> Location information
O
Indicates the geographical area where the digital asset is accessed frequently
> Location information
O
(NOTE)
Indicates the geographical area for which digital assets usage report is generated
>> List of Digital asset identifiers
M
Identifies the digital assets being used/accessed in the given geographical area
>>> Number of access
M
Indicates the no of times a particular digital asset is accessed/used in the given geographical area. This helps to identify the frequently or less frequently used digital assets in a given geographical area
> List of Identifiers of the consumers
O
(NOTE)
Indicates the list of consumer identifiers (VAL user Id, VAL server ID) accessed the digital assets
>> List of Digital asset identifiers
M
Identifies the digital assets being used/accessed by the consumer
> Unutilized digital assets
O
Indicates the list of digital assets identities which are discovered but not accessed/downloaded
> Undiscovered digital assets
O
Indicates the list of digital assets identities which are not discovered by the consumers
NOTE: Digital assets usage report must include at least one optional IE.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.4 APIs
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.4.1 General
| Table 8.5.4.1-1 illustrates the APIs to get digital assets usage report from the DA server.
Table 8.5.4.1-1: List of APIs for digital assets usage report
API Name
API Operations
Known Consumer(s)
Communication Type
SS_DAUsageReport
Request
DA client, VAL server
Request/Response
Subscribe
DA client, VAL server
Subscribe/Notify
Notify
DA client, VAL server
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.4.2 SS_DAUsageReport API
| |
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.4.2.1 General
| Service description: This API enables a VAL server (or DA client) to the usage report of digital assets from DA server.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.4.2.2 Request operation
| API operation name: SS_DAUsageReport_Request
Description: The consumer requests to get the usage report of digital assets.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.5.3.1-1.
Outputs: See Table 8.5.3.2-1.
See clause 8.5.2.1 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.4.2.3 Subscribe operation
| API operation name: SS_DAUsageReport_Subscribe
Description: The consumer subscribes for the digital assets usage report.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.5.3.3-1.
Outputs: See Table 8.5.3.4-1.
See clause 8.5.2.2 for details of usage of this operation.
|
676d3698b25fe18441c7058a012cf0fe | 23.438 | 8.5.4.2.4 Notify operation
| API operation name: SS_DAUsageReport_Notify
Description: The consumer is notified with digital assets usage report.
Known Consumers: VAL server, DA client.
Inputs: See Table 8.5.3.5-1.
Outputs: See Table 8.5.3.6-1.
See clause 8.5.2.3 for details of usage of this operation.
Annex A (informative):
Deployment models
The digital assets service can support the requirements of the SEAL service deployment models specified in clause 4.2 of 3GPP TS 23.434 [4].
The architecture of digital asset service is based on the SEAL functional model. The digital assets service can support the SEAL service deployment models specified in clause 8 of 3GPP TS 23.434 [4].
Annex B (informative):
Business relationships
The digital assets service can be hosted by a SEAL provider and the business relationships specified in clause 5 of 3GPP TS 23.434 [4] can apply to the hosting of digital assets service. The SEAL provider agreement between VAL service provider and SEAL providers can include the context of lawful interactions related to digital assets.
Annex C (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2024-10
SA6#63
TS skeleton (S6-244146)
0.0.0
2024-10
SA6#63
Implemented the following approved pCRs:
S6-244574, S6-244575, S6-244577, S6-244579, S6-244691, S6‑244721
0.1.0
2024-11
SA6#64
Implemented the following approved pCRs:
S6-245275, S6-245530, S6-245531, S6-245542
0.2.0
2024-12
SA#106
SP-241696
Submitted to SA#106 for information
1.0.0
2025-02
SA6#65
Implemented the following approved pCRs:
S6-250036, S6-250411, S6-250412, S6-250413, S6-250414, S6-250415, S6-250416, S6-250257, S6-250263
1.1.0
2025-03
SA#107
SP-250195
Submitted to SA#107 for approval
2.0.0
2025-03
SA#107
SP-250195
MCC Editorial update for publication after TSG SA approval
19.0.0
2025-06
SA#108
SP-250610
0001
1
F
Fix for Digital asset media management
19.1.0
2025-06
SA#108
SP-250610
0002
F
Clarification on digital asset
19.1.0
2025-06
SA#108
SP-250610
0003
1
F
Fix for clause 3.1 & 7.4.2.1
19.1.0
2025-06
SA#108
SP-250610
0005
F
Fix for clause 7.2
19.1.0
2025-06
SA#108
SP-250610
0006
F
Fix for clause 8.3.3.2
19.1.0
2025-06
SA#108
SP-250610
0007
F
Remove for clause 7.3 & 7.4.2.2
19.1.0
2025-06
SA#108
SP-250610
0008
1
F
Fix for Upload digital asset media
19.1.0
2025-06
SA#108
SP-250610
0009
1
F
Fix for Download digital asset media
19.1.0
2025-06
SA#108
SP-250610
0010
1
F
Fix for Update digital asset media
19.1.0
2025-06
SA#108
SP-250610
0011
2
F
Fix for Delete digital asset media
19.1.0
2025-06
SA#108
SP-250610
0013
1
F
Clarification on digital assets
19.1.0
2025-09
SA#109
SP-251061
0016
F
Adding APIs for Digital Asset Media Management
19.2.0
2025-09
SA#109
SP-251061
0017
F
Correction in DA Profile
19.2.0
2025-09
SA#109
SP-251062
0018
1
B
Procedures to support digital assets usage report
20.0.0
2026-01
SA#110
SP-251485
0024
1
A
CR on digital asset discovery request message
20.1.0
2026-01
SA#110
SP-251485
0025
1
A
CR on digital asset media
20.1.0
2026-01
SA#110
SP-251485
0026
A
CR on digital asset profile
20.1.0
2026-01
SA#110
SP-251485
0027
A
CR on the description of IE allowed operations
20.1.0
2026-01
SA#110
SP-251485
0029
1
A
Resolving ENs
20.1.0
2026-01
SA#110
SP-251486
0030
F
Digital Assets usage report APIs
20.1.0
2026-01
SA#110
SP-251485
0032
2
A
CR on digital assets authentication
20.1.0
2026-01
SA#110
SP-251485
0034
1
A
Remove digital assets collection requirement
20.1.0
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 1 Scope
| The present document specifies the procedures and information flows necessary for AIML Enablement SEAL Service.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 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 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[3] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics".
[4] 3GPP TS 23.436: "Functional architecture and information flows for Application Data Analytics Enablement Service".
[5] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[6] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[7] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[8] 3GPP TS 28.105: "Management and orchestration; Artificial Intelligence/ Machine Learning (AI/ML) management".
[9] 3GPP TS 23.502: "Procedures for the 5G System (5GS)".
[10] 3GPP TS 22.261: "Service requirements for the 5G system".
[11] 3GPP TS 26.531: "Data Collection and Reporting; General Description and Architecture".
[12] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
[13] 3GPP TS 23.273:"5G System (5GS) Location Services (LCS); Stage 2".
[14] 3GPP TS 33.434: "Security aspects of Service Enabler Architecture Layer (SEAL) for verticals".
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 3 Definitions of terms, symbols and abbreviations
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 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].
AIMLE client set identifier: an identifier of the set of selected AIMLE clients.
AI/ML intermediate model: For federated learning, members need to train models for multiple rounds, intermediate models indicate the model which do not meet the required training rounds and/or meet the requirements of the federation training.
AI/ML operation: also known as AI/ML task, it refers to the specific execution step in AI/ML lifecycle, it can include data management, model training etc.
AIMLE service: An AIMLE service is an AIMLE capability which aims assisting in performing or enabling one or more AIML operations.
FL client: An FL member which locally trains the ML model as requested by the FL server. Such FL client functionality can be at the network (e.g. AIMLE server with FL client capability) or at the device side (e.g. AIMLE client with FL client capability).
FL member: An FL member or participant is an entity which has a role in the FL process. An FL member can be an FL client performing ML model training, or an FL server performing aggregation/collaboration for the FL process.
FL server: An FL member which generates global ML model by aggregating local model information from FL clients.
ML model: According to 3GPP TS 28.105 [8], mathematical algorithm that can be "trained" by data and human expert input as examples to replicate a decision an expert would make when provided that same information.
ML model inference: According to 3GPP TS 28.105 [8], ML model inference includes capabilities of an ML model inference function that employs an ML model and/or AI decision entity to conduct inference.
ML model lifecycle: The lifecycle of an ML model aka ML model operational workflow consists of a sequence of ML operations for a given ML task / job (such job can be an analytics task or a VAL automation task). This definition is aligned with the 3GPP definition on ML model lifecycle according to 3GPP TS 28.105 [8].
ML model training: According to 3GPP TS 28.105 [8], ML model training includes capabilities of an ML training function or service to take data, run it through an ML model, derive the associated loss and adjust the parameterization of that ML model based on the computed loss.
Split AI/ML operation pipeline: A Split AI/ML operation pipeline is a workflow for ML model inference in which AI/ML endpoints are organized and collaborate to process ML models in sequential stages, where processing at each stage involves ML model inference on the output of the previous stage.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 3.3 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].
ADAES Application Data Analytics Enablement Server
AIMLE AI/ML enablement
ASP Application Service Provider
FL Federated Learning
NEF Network Exposure Function
NWDAF Network Data Analytics Function
OAM Operation, Administration and Maintenance
SEAL Service Enabler Architecture Layer
SEALDD SEAL Data Delivery
VAL Vertical Application Layer
VFL Vertical FL
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 4 Architectural requirements
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 4.1 General requirements
| [AR-4.1-a] The AIML enablement layer shall be able to support one or more VAL applications.
[AR-4.1-b] Supported AIML enablement capabilities shall be offered as APIs to the VAL applications.
[AR-4.1-c] The AIML enablement layer shall support interaction with 3GPP network system to consume network and AI/ML support services.
[AR-4.1-d] The AIMLE client shall be capable to communicate with one or more AIMLE servers of the same AIMLE service provider.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 4.2 AIML capability related requirements
| [AR-4.2-a] The AIMLE server shall be capable of provisioning and exposing ML client information.
[AR-4.2-b] The AIMLE server shall be capable of supporting the registration, discovery, and selection of AIMLE clients which participate as ML members in AIML service lifecycle.
[AR-4.2-c] The AIMLE layer shall be capable of supporting ML service lifecycle operations (e.g., ML model training).
[AR-4.2-d] The AIMLE server shall be capable of supporting discovery and provisioning of AIML models.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5 Application architecture for enabling AI/ML services
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.1 General
| The functional architecture enhancements for the AIML enablement service are based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [5]. The architecture enhancements are organized into functional entities to describe a functional architecture enhancement which addresses the support for AIML enablement aspects for vertical applications.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2 Application enablement architecture
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.1 On-Network AIML Enablement (AIMLE) Functional Architecture
|
Figure 5.2.1-1: On-network AIMLE functional model
Figure 5.2.1-1 illustrates the on-network functional model of AIMLE. In the vertical application layer, the VAL client communicates with the VAL server over VAL-UU reference point. VAL-UU supports both unicast and multicast delivery modes. The AIMLE functional entities on the UE and the server are grouped into AIMLE client(s) and AIMLE server(s) respectively.
The AIMLE includes of a common set of services for comprehensive enablement of AIML functionality, including federated and distributed learning (e.g., FL client registration management, FL client discovery and selection), and reference points. The AIMLE services are offered to the vertical application layer (VAL).
The AIMLE client communicates with the AIMLE server(s) over the AIML-UU reference points. The AIMLE client provides functionality to the VAL client(s) over AIML-C reference point. The VAL server(s) communicate with the AIMLE server(s) over AIML-S reference points. The AIMLE servers communicate with the underlying 3GPP network systems using the respective 3GPP interfaces specified by the 3GPP network system. AIML-E reference point enables interactions between two AIMLE servers (e.g. central and edge AIMLE servers).
The AIMLE server interacts with the ML repository which serves as repository for ML model and ML participants over AIML-R.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.1.1 Service-based AIMLE architecture representation
| Figure 5.2.1.1-1 exhibits the service-based interfaces for providing and consuming AIMLE services. The AIMLE server could provide service to VAL server and AIMLE client through interface SAiml.
Figure 5.2.1.1-1: Architecture for AIML enablement – Service based representation.
Figure 5.2.1.1-2 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in 3GPP TS 23.501 [6].
Figure 5.2.1.1-2: Architecture for AIMLE utilizing the 5GS network services based on the 5GS SBA – Service based representation,
The AIMLE server as well as ADAES is deployed as a SEAL server; hence enhancements to SEAL architecture (as specified in 3GPP TS 23.434 [5]) are needed to incorporate the AIMLE service. Figure 5.2.1.1-3 illustrates the service-based representation including AIMLE server as part of the SEAL framework.
Figure 5.2.1.1-3: SEAL functional model representation using service-based interfaces and including AIMLE function.
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.2 Off-Network AIMLE Functional Architecture
|
Figure 5.2.2-1: Off-network AIMLE functional model
Figure 5.2.2-1 illustrates the off-network (UE-to-UE) functional model of AIML enablement. In the vertical application layer, the VAL client communicates with a further VAL client over VAL-PC5 reference point. VAL-PC5 supports both unicast and multicast delivery modes. The UE1, if connected to the network via Uu reference point, can also act as a UE-to-network relay, to enable UE2 to access the VAL server(s) over the VAL-UU reference point.
The AIMLE client communicates with a further AIMLE client(s) over the AIML-PC5 reference points. The AIMLE client provides functionality to the VAL client(s) over AIML-C reference point. Such communication is performed for supporting local ML operations (training, distribution, inference) in a coordinated manner.
The off network functional architecture is similar to SEAL off-network architecture (as specified in 3GPP TS 23.434 [5]).
|
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.3 Functional Entities Description
| |
29cb23e409b7480fb8bd6cba8e348433 | 23.482 | 5.2.3.1 General
| Each subclause is a description of a functional entity and does not imply a physical entity.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.