Digital asset identifier

Description

The digital asset identifier (DAI) is a concept introduced in 3GPP Release 19 to uniquely identify digital assets across different mobile metaverse services. A digital asset can be any virtual object, such as a 3D model, texture, audio file, or avatar, that is used within metaverse applications. The DAI ensures that the same asset can be referenced consistently across multiple services, platforms, and operators, facilitating interoperability and a unified user experience. This is particularly important as the metaverse ecosystem is expected to span various providers, and users may want to access their assets seamlessly regardless of the underlying network or service.

The DAI is defined in 3GPP specifications 23.438 (Study on supporting identity management and authentication for mobile metaverse services), 23.700 (Study on architecture enhancements for 5G system to support metaverse services), and 33.721 (Study on security aspects of supporting identity management and authentication for mobile metaverse services). These specifications outline the requirements, architecture, and security mechanisms for mobile metaverse services, including the need for a standardized identifier for digital assets. The DAI is typically a globally unique string or numeric value, possibly based on a URI (Uniform Resource Identifier) or a UUID (Universally Unique Identifier), that is assigned to an asset when it is created or registered. It may include information about the asset's origin, owner, and version, but the primary purpose is uniqueness and resolvability.

In the architecture, the DAI is used by metaverse service providers, content delivery networks, and user equipment to locate, retrieve, and manage digital assets. For example, when a user enters a virtual room, the client may request a list of DAIs for the assets needed to render the environment. The client then resolves these DAIs to actual asset data, possibly through a distributed hash table (DHT), a centralized registry, or a content delivery network. The DAI also enables access control and digital rights management (DRM), as the identifier can be linked to ownership and licensing information. Security is paramount: the DAI must be resistant to spoofing and tampering, and mechanisms such as digital signatures and blockchain may be used to ensure integrity and provenance.

The introduction of the DAI in Release 19 reflects the growing convergence of telecommunications and the metaverse. 3GPP recognizes that mobile networks will play a critical role in delivering metaverse experiences, and that standardized identifiers are essential for scaling and interoperability. The DAI is part of a broader effort to define identity management for metaverse services, including user identities, device identities, and asset identities. By providing a common identifier, 3GPP aims to avoid fragmentation and enable a vibrant ecosystem of metaverse applications that can work across different operators and vendors.

In Release 20, the definition of DAI was slightly reworded for clarity, but the technical meaning remained the same. The DAI continues to be a key enabler for mobile metaverse services, ensuring that digital assets can be uniquely identified and managed across diverse environments. As the metaverse evolves, the DAI may be extended to support new asset types and interactions, but its core purpose of unique identification will remain.

Purpose & Motivation

The digital asset identifier exists to solve the problem of asset fragmentation in the emerging metaverse ecosystem. In a world where metaverse services are provided by multiple vendors and operators, digital assets (such as 3D models, avatars, and textures) need to be referenced consistently across different platforms. Without a standardized identifier, each service would use its own naming scheme, leading to duplication, incompatibility, and a poor user experience. The DAI provides a unique, globally resolvable identifier that enables interoperability, allowing users to access their assets seamlessly regardless of which service they are using.

Prior to the DAI, metaverse applications often relied on proprietary identifiers or URLs, which were not portable across services. This created silos and hindered the growth of a unified metaverse. The DAI addresses this by defining a common format and resolution mechanism, backed by 3GPP specifications. It also enables new business models, such as asset marketplaces and cross-service licensing, by providing a clear way to track ownership and usage. Security is a key motivation: the DAI can be cryptographically bound to its owner, preventing unauthorized use and ensuring trust.

The DAI was introduced in Release 19 as part of 3GPP's study on metaverse services. It reflects the recognition that mobile networks will be the backbone of the metaverse, and that standardization is crucial for scalability. By defining the DAI, 3GPP provides a foundation for identity management in the metaverse, which will be essential for mass adoption. The slight rewording in Release 20 indicates ongoing refinement, but the core concept remains unchanged.