hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
6.5 Service-based interface
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
7 Identities and commonly used information
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
7.1 General
|
This clause specifies details about the identifiers and common values used for digital asset service.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
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, Get, 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
O
List of accessories (e.g. Hat, watch, shoes) which are 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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
7.3 Digital asset collection profile
|
One or more digital assets can be used together as a digital asset collection. When a digital asset collection profile is used to access metaverse application, all digital assets within the digital asset collection profile are allowed to be used while using the metaverse application service. Table 7.3-1 shows the information elements for the digital asset collection profile.
Table 7.3-1: Digital asset collection profile
Information element
Status
Description
Digital asset collection profile ID
M
Identifier of the digital asset collection profile
List of owners
M
(NOTE)
List of identity of the owner(s) who created the digital asset collection profile.
> Owner information
O
Application-level information related to the owner of the digital asset collection.
allowed application list
O
List of application IDs which are allowed to use this digital asset profile
List of digital asset profile(s)
M
One or more digital asset profile(s) as shown in Table 7.2-1
NOTE: The digital asset collection can be created for organizing digital assets belonging to a single owner.
NOTE: IEs from individual digital asset profile takes precedence over IEs from digital asset collection profiles.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
7.4 Identities
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
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
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
7.4.2 Identities related to digital asset
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
7.4.2.1 Digital asset identifier (Digital asset ID)
|
A unique identifier to identify digital asset. It is assigned by SEAL DA server. The identity is globally unique.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
7.4.2.2 Digital asset collection profile identifier (Digital asset collection profile ID)
|
A unique identifier to identify digital asset collection profile. It is assigned by SEAL DA server. The identity is globally unique.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8 Procedures and information flows
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.1 General
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.2 Digital asset profile management
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.2.1 General
|
The following clauses specify procedures, information flows, and APIs for digital asset profile management.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.2.2 Procedures
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.2.3 Information flows
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
List of Metaverse 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, Get, 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
O
List of accessories (e.g. Hat, watch, shoes) which are purchased for this digital asset profile
expiry time
O
Time until this digital asset profile is valid
Digital asset media information
O
Information related to digital asset media (e.g. URI where the media is stored)
Editor's Note: The association of a subscriber/user identifier for the digital asset is FFS.
Editor's Note: Additional parameters (communication parameters, experience requirements) are FFS,
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.2.4 APIs
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
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
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.2.4.2 SS_DAProfileManagement API
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.3 Digital asset discovery
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.3.1 General
|
The following clauses specify procedures, information flows, and APIs for digital asset discovery.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.3.3 Information flows
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
Requesting digital asset identifier
M
The identifier of the digital asset of the requestor.
Digital asset discovery filters
M
Set of characteristics to determine matching digital asset (e.g., Digital asset identifier, Digital asset name, Digital asset description, location, VAL client type, Digital asset type, Digital asset owner , Allowed user, Digital asset profile).
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
>Discovered digital asset profile identifier
O
(NOTE)
Profile identifier 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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.3.4 APIs
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.3.4.1 General
|
Service description: This API enables a DA client to discover digital assets from a DA server.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.4 Digital asset media management
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.4.1 General
|
The following clauses specify procedures, information flows, and APIs for digital asset media management.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.4.2 Procedures
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
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 a 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. If the digital asset identifier corresponds to a digital asset collection, then a list of digital assets is included in the request.
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 a upload digital asset media response to the requestor. The response includes information listed in Table 8.4.3.2-1.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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. If the digital asset identifier corresponds to a digital asset collection, multiple digital asset media objects are provided in the response.
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.4.3 Information flows
| |
b978cebfe2ef2ab93e2d7fe6e166a051
|
23.438
|
8.4.3.1 Upload digital asset media request
|
Table 8.4.3.1-1 describes the information elements for a 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.
List of digital assets
M
List of digital assets to be uploaded
> Digital asset profile identifier
M
Identifier of the digital asset profile
> 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
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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
O
If digital asset is a collection, then this identifies the digital asset collection.
List of digital assets
M
List of digital asset media objects included
> Digital asset profile identifier
M
An identifier for the digital asset.
> 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
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
List of digital assets
M
List of digital assets to be updated
> Digital asset profile identifier
M
Identifier of the digital asset profile
> 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
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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.
List of digital assets
M
List of digital assets to be deleted
> Digital asset profile identifier
M
Identifier of the digital asset profile
|
b978cebfe2ef2ab93e2d7fe6e166a051
|
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. 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
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
1 Scope
|
The present document specifies the procedures and information flows necessary for AIML Enablement SEAL Service.
|
8e3606cbebf5d984a580195cd59a0ad0
|
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”.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
3 Definitions of terms, symbols and abbreviations
| |
8e3606cbebf5d984a580195cd59a0ad0
|
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].
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 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.
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.
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.
AIMLE service: An AIMLE service is an AIMLE capability which aims assisting in performing or enabling one or more AIML operations.
AIMLE client set identifier: an identifier of the set of selected AIMLE clients.
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 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 server: An FL member which generates global ML model by aggregating local model information from FL clients.
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.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
8e3606cbebf5d984a580195cd59a0ad0
|
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
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
4 Architectural requirements
| |
8e3606cbebf5d984a580195cd59a0ad0
|
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.
|
8e3606cbebf5d984a580195cd59a0ad0
|
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.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5 Application architecture for enabling AI/ML services
| |
8e3606cbebf5d984a580195cd59a0ad0
|
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.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2 Application enablement architecture
| |
8e3606cbebf5d984a580195cd59a0ad0
|
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.
|
8e3606cbebf5d984a580195cd59a0ad0
|
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.
|
8e3606cbebf5d984a580195cd59a0ad0
|
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]).
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.3 Functional Entities Description
| |
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.3.1 General
|
Each subclause is a description of a functional entity and does not imply a physical entity.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.3.2 AIMLE client
|
The AIMLE client functional entity acts as the application client supporting AIMLE services. It interacts with the AIMLE server.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.3.3 AIMLE server
|
The AIMLE server functional entity provides AIMLE services supported within the vertical application layer. It interacts with the AIMLE client, the 3GPP network, other SEAL services, and VAL server.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.3.4 ML repository
|
The ML repository is a logical entity that serves both as a registry for ML/FL members and as a repository for application layer ML model related information. It can be accessed by the AIMLE server.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.4 Reference Points Description
| |
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.4.1 General
|
The reference points for the functional model related to AIMLE are described in the following subclauses.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.4.2 AIML-UU
|
The interactions related to AIML enablement functions between the AIMLE client and AIMLE server are supported by AIML-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [7] and 3GPP TS 23.501 [6].
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.4.3 AIML-S
|
The interactions related to AIML enablement functions between the VAL server(s) and the AIMLE server are supported by AIML-S reference point.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.4.4 AIML-C
|
The interactions related to AIML enablement functions between the VAL client(s) and the AIMLE client within a VAL UE are supported by AIML-C reference point.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.4.5 AIML-R
|
The interactions related to AIML enablement functions between the AIMLE server, and the ML repository are supported by AIML-R reference point.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.4.6 AIML-E
|
The interactions related to AIML enablement functions between AIMLE servers (e.g., central and edge AIMLE servers).
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
5.2.4.7 AIML-PC5
|
The interactions related to AIML enablement functions between AIMLE clients in off-network deployments.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6 AIMLE Functional Description
| |
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6.1 Support for ML model retrieval
|
This functionality covers the retrieval of ML models by an AIMLE client or a VAL server via the AIMLE server. The AIMLE server provides the functionality required to retrieve ML models stored in a ML repository based on a filtering criteria. The functionality is provided to the ML model consumer via an API following a request/response model or a subscribe/notify model.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6.2 Support for ML model training
|
This functionality enables the AIMLE server to support ML model training based on requests from a VAL server. The AIMLE server provides the functionality to train a specific ML model or assist the ML model training at VAL server/client(s).
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6.3 Support for FL member registration
|
This functionality covers the registration and registration update of the candidate FL member to the ML repository which is keeping the FL member registrations. Such candidate member can be a VAL server functionality or an enabler layer functionality (e.g. AIMLE server) which is registering to the ML repository/registry to act as FL member for a given application event (analytics event or event triggered by a VAL layer application server).
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6.4 Support for FL events subscription and notification
|
This functionality enables a consumer (who can be the AIMLE server or a VAL server e.g. acting as FL server) to subscribe for FL related events and getting notified on changes on the availability of the FL members which are to be used for the FL-related task (e.g., training). This capability at the ML repository acting as an AIML service registry supports the subscription for events related to FL members and the notification to the consumer in case of changes. This feature assumes that such FL members (AIMLE or VAL server or AIMLE clients) have previously registered to this registry their availability and capabilities.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6.5 Support AI/ML task transfer
|
This functionality covers the AIMLE support for ML task transfer, which is applicable to scenarios where an AI/ML member cannot finish the assigned AI/ML task during the performing process. In this scenario, the AIMLE server assists the source AI/ML member by support transferring the intermediate AI/ML information (e.g., the intermediate AI/ML operation status and results) to another AI/ML member (target AI/ML member) for further operations to complete the AI/ML task.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6.6 Support for AIMLE client registration
|
This functionality allows an AIMLE client (e.g., AI/ML capable UEs) to register with an AIMLE server. The AIMLE server stores the client information for future interactions. This functionality is crucial for enabling the AIMLE client to participate in AI/ML operations.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6.7 Support for AIMLE client discovery
|
This functionality enables the VAL server to discover available AIMLE clients for AI/ML operations, such as training or inference. The AIMLE server provides the functionality to select suitable AIMLE clients that fulfill the discovery criteria.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6.8 Support for AIMLE client selection
|
This functionality enables the selection of AIMLE clients to participate in AI/ML operations. There are two modes for client selection: VAL server selection and AIMLE server selection. In VAL server selection, the functionality is provided by the AIMLE Server selecting candidate AIMLE clients from the client list provided by the VAL Server. In AIMLE server selection, the functionality is provided by the AIMLE Server selecting candidate AIMLE clients based on the client selection criteria provided by the VAL Server from the AIMLE clients in the ML repository.
|
8e3606cbebf5d984a580195cd59a0ad0
|
23.482
|
6.9 Support for AIMLE client participation
|
This functionality enables the AIMLE server to verify and manage the participation of AIMLE clients in AI/ML operations. The AIMLE client responds with its willingness to perform AI/ML operations based on the information provided by the AIMLE server.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.