hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 5 Application enablement architecture requirements | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 5.1 General requirements | Following general requirements are identified:
[AR-5.1-a] The application enabler service shall support management of spatial anchors.
[AR-5.1-b] The application enabler service shall support management of digital avatars including create, read, update, delete avatar profiles and uploading and downloading the avatar me... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 5.2 Spatial anchors management service requirements | [AR-5.2-a] The spatial anchor management service shall provide mechanism to create, update, get/discover spatial anchors.
[AR-5.2-b] The spatial anchor management service shall provide mechanism to subscribe for spatial anchor related information including usage information, UEs within certain range. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 5.3 Spatial map management service requirements | [AR-5.3-a] The spatial map management service shall provide mechanisms to create, update/delete, get and subscribe spatial maps.
[AR-5.3-b] The spatial map management service shall provide mechanisms to expose spatial map information to authorized third parties.
5.4 Digital asset and avatar management service requireme... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6 Application enablement architecture for metaverse services | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1 Option #1: On-network mobile metaverse application layer architecture | This clause proposes a mobile metaverse enablement layer as a possible architecture. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1.1 Application enablement architecture | Figure 6.1.1-1 illustrates the detailed on-network mobile metaverse application layer functional model.
Figure 6.1.1-1: On-network mobile metaverse application layer functional model
The mobile metaverse application layer functional entities are grouped into the vertical application layer and the mobile metaverse appli... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1.2 Functional Elements | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1.2.1 Mobile Metaverse Enablement Server | A Mobile Metaverse Enablement Server (MMES) provides metaverse application enablement services used by Metaverse VAL servers and Mobile Metaverse Enablement Clients (MMEC). |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1.2.2 Mobile Metaverse Enablement Client | A Mobile Metaverse Enablement Client provides metaverse application enablement services to VAL clients. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1.3 Reference Points | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1.3.1 MM-UU | MM-UU reference point enables interactions between a MMES and MMEC. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1.3.2 MM-S | MM-S reference point enables interactions between a MMES and Metaverse VAL servers. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1.3.3 MM-E | MM-E reference point enables interactions between MMES instances. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.1.3.4 MM-C | MM-C reference point enables interactions between a MMEC and Metaverse VAL clients. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.2 Option #2: A-DACM architecture to support Metaverse services | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.2.1 Application enablement architecture | Figure 6.2.1-1 illustrates the A-DACM architecture to support Metaverse services using SEAL architecture specified in 3GPP TS 23.434 [8].
Figure 6.2.1-1: A-DACM architecture to support Metaverse services using SEAL architecture
The SEAL architecture includes A-DACM client and server which supports the VAL layer. The A-... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.2.2 Functional Elements | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.2.2.1 A-DACM function | The A-DACM function expose the services/APIs to the VAL layer services over Sdacm interface for the following avatar management capabilities:
- Avatar profile creation;
- Avatar upload;
- Avatar linking to user/subscriber;
- Avatar download;
- Avatar update/modification;
- Avatar delete; |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.2.3 Reference Points | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.2.3.1 SEAL-S | This reference point supports the interactions between VAL server(s) and A-DACM function. The VAL server consumes the avatar management services supported by the A-DACM function as specified in clause 6.2.2.1. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.2.4 Service-based interface | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.2.4.1 Sdacm | This interface supports the interactions between VAL function (VAL servers) and A-DACM function. The VAL function consumes the avatar management services supported by the A-DACM function as specified in clause 6.2.2.1. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.3 Option #3: Reuse existing SEAL architecture for metaverse services | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.3.1 Application enablement architecture | The SEAL architecture as defined in 3GPP TS 23.434 [8] is reused to enhance to support metaverse services, e.g. SEAL LM enhancement to support spatial anchor management and spatial map management, SEAL CM enhancement to support avatar profile(s) management. The SEAL clients are enhanced to provide client side functiona... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4 Option #4: Architecture to support Metaverse services with permission control | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.1 Application enablement architecture | There are many types of digital assets. Some digital assets may not contain sensitive information. After being created, they are expected to be widely used. Although the management of API through CAPIF realizes the management of resource usage rights. The current structure does not consider some special scenarios relat... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.2 Functional Elements | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.2.1 DAPM function | The DAPM function provides the services to VAL layer for the permission management of digital assets. The main capabilities as following:
- Publish the digital asset;
- Create, store and search subscription records of digital assets;
- Verify the authenticity and validity of the subscription records; |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.2.2 UE DAPM function | UE DAPM function provides client service of digital asset permission management. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.3 Reference Points | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.3.1 PM-V | PM-V reference point enables interactions between VAL server(s) and DAPM function. The VAL server consumes the services supported by the DAPM function as specified in clause 6.2.2.1. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.3.2 CM-PM | CM-PM reference point enables interactions between DAPM function and A-DACM function. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.3.3 PM-C | PM-C reference point enables interactions between DAPM function and UE DAPM function. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.4 Service-based interface | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.4.1 Sdapm | This interface supports the interactions between VAL function (VAL servers) and DAPM function. The VAL function consumes the services supported by the A-DAPM function as specified in clause 6.4.2.1. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.5 Services | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 6.4.5.1 DAPM services | The services provided by DAPM function are as following:
- obtain owner’s permission to publish and promote the digital asset;
- create, store, search, validate the subscription records of digital asset. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7 Solutions | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.0 Mapping of solutions to key issues | Table 7.0-1: Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
KI #5
KI #6
KI #7
KI #8
KI #9
Sol #1
X
Sol #2
X
Sol #3
X
Sol #4
X
X
Sol #5
X
Sol #6
X
Sol #7
X
Sol #8
X
Sol #9
X
X
Sol #10
X
X
Sol #11
X
Sol #12
X
Sol #13
X
Sol #14
X
Sol #15
X
Sol #16
X
Sol #17
X
Sol #18
X |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1 Solution #1: Spatial anchor discovery | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.1 Solution description | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.1.1 General | This solution is for KI#1 and addresses the open issue of spatial anchor discovery by the consumer.
This solution is based on the Mobile Metaverse enablement layer architecture.
In this solution, the mobile metaverse application enablement layer provides capabilities to discover and determine the validity of spatial an... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.1.2 Procedure | Pre-conditions:
1) Spatial anchors have been provisioned in the mobile metaverse enabler server
2) A VAL client (e.g., an AR application) needs to display enriched localized content to a user
3) The spatial anchor specific information (e.g. the description or label of spatial anchor) has been provisioned in the mobile ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.1.3 Creating spatial anchor group | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.1.3.1 General | Consider a scenario where the user wearing the headset is in the supermarket or mall. The mall could have many shops(like clothes, vintage items), restaurants, etc. The VAL server can create a group of spatial anchors within the shop and represent the shop with a grouped spatial anchor. Similarly it can create a group ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.1.3.2 Procedure | Figure 7.1.1.3.2-1 depicts the procedure for creating the group of spatial anchor services linked to each other. The service is provided by MMES and consumed by VAL server or MMEC.
Figure 7.1.1.3.2-1: Create spatial anchor group
1) The VAL server (or MMEC) sends a request message to the MMES server to create a group of... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.2 Architecture Impacts | Option #1 in clause 6.1 is the basis for this solution. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.3 Corresponding APIs | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.3.1 Overview | This clause provides a summary of the corresponding APIs for solution #1.
- Spatial anchor discovery request API (request / response model; API provider: MMES; known consumers: MMEC; corresponding to step 1 to 3 of clause 7.1.1.2).
- Spatial anchor discovery response API (request / response model; API provider: MMES; k... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.3.2 Information flows | Table 7.1.3.2-1 shows the request sent by a MMEC to a MMES for the discovery of spatial anchor(s).
Table 7.1.3.2-1: Spatial anchor discovery request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., MMEC, UE, VAL server)
Requestor security credentials
M
The security creden... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.1.4 Solution evaluation | This solution is for KI#1 and addresses the open issue of spatial anchor discovery by the consumer. This solution is based on the Mobile Metaverse enablement layer architecture as specified in clause 6.1. The solution proposes MMEC to send discovery request with appropriate discovery filters. The MMES discovers the spa... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.2 Solution #2: Support for spatial anchor management | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.2.1 Solution description | This solution maps to KI# 1. This solution enhances Service Enabler Architecture Layer (SEAL) Location Management (LM) service to provide spatial anchor management service to the VAL server or the UE. The architecture impacts are captured in clause 7.2.2 while procedures to manage spatial anchors are captured in clause... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.2.2 Architecture Impacts | This clause provided architecture enhancements to the SEAL LM architecture as defined in 3GPP TS 23.434 [8]. The SEAL LM client is enhanced to provide client side functionalities for managing (i.e. create, read, update and delete) spatial anchors for metaverse application. The SEAL LM server is enhanced to provide serv... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.2.3 Procedures | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.2.3.1 Creating spatial anchor | Consider a supermarket example, where a user with a headset discovers multiple spatial anchor(s). Some spatial anchor providers can mark their spatial anchors visibility level as discoverable for all users during creation process. During the discovery process, the user also discovers spatial anchors provided by differe... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.2.3.2 Updating spatial anchor | Figure 7.2.3.2-1 depicts the procedure for updating spatial anchor association for metaverse applications. The update operation includes modifying existing spatial anchor or deleting the spatial anchor. The service is provided by SEAL LM server and consumed by VAL server or SEAL LM client.
Figure 7.2.3.2-1: Update spat... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.2.3.3 Get spatial anchor | Figure 7.2.3.3-1 depicts the procedure for getting spatial anchor details for metaverse applications. The service is provided by SEAL LM server and consumed by VAL server or SEAL LM client.
Figure 7.2.3.3-1: Get spatial anchor
1) The VAL server (or SEAL LM client) sends a request message to the SEAL LM server to get th... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.2.3.4 Spatial anchor information subscription | Figure 7.2.3.3-1 depicts the procedure for subscribing to receive spatial anchor details for metaverse applications. The service is provided by SEAL LM server and consumed by VAL server or SEAL LM client.
Figure 7.2.3.4-1: Spatial anchor information subscription
1) The VAL server (or SEAL LM client) sends a subscriptio... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.2.4 Solution evaluation | This solution maps to KI# 1. This solution enhances Service Enabler Architecture Layer (SEAL) Location Management (LM) service by enhancing SEAL LM client and SEAL LM server functionalities as specified in clause 7.2.2. The solution proposes to create, update and get spatial anchors. The solution also proposes to subsc... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3 Solution #3: Spatial anchor subscription | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3.1 Solution description | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3.1.1 General | This solution is for KI#1 and addresses the open issue of how to detect UE(s) within a certain range of a spatial anchor and detect spatial anchors within a certain range of a UE.
This solution is based on the Mobile Metaverse enablement layer architecture.
A first procedure is proposed to allow a VAL server to subscri... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3.1.2 VAL server subscription procedure for information about UE with spatial anchor interest | This procedure goes beyond capabilities defined in SEAL LMS for providing UEs within range of a target location described in 3GPP TS 23.434 [8]. SEAL LMS provides information about UE(s) within range of a location, which may be the location of a spatial anchor, regardless of the interest of such UE(s) for spatial ancho... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3.1.3 VAL client subscription procedure for spatial anchors in range | Pre-conditions:
1) Spatial anchors have been provisioned in the mobile metaverse enabler server
2) A VAL client requires information about spatial anchors of interest
Figure 7.3.1.3-1: Spatial anchor of interest subscription/notification procedure
1. A metaverse VAL client subscribes for spatial anchor of interest info... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3.2 Architecture Impacts | Option #1 in clause 6.1 is the basis for this solution. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3.3 Corresponding APIs | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3.3.1 Overview | This clause provides a summary of the corresponding APIs for solution #3.
- Discover UE with Spatial Anchor interest API (subscribe / notify model; API provider: MMES; known consumers: VAL server; corresponding to step 1 to 5 of clause 7.3.1.2).
- Discover Spatial Anchor API (subscribe / notify model; API provider: MME... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3.3.2 Information flows | Table 7.3.3,2-1 shows the request sent by a MMEC to a MMES for the UE with SA interest subscription request.
Table 7.3.3.2-1: UE with Spatial Anchor interest subscription request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., MMEC, UE, VAL server)
Requestor security cre... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.3.4 Solution evaluation | This solution addresses Key Issue #1 by providing spatial anchor subscribe/notify procedures; a first procedure allows the VAL server to subscribe for information about UEs with spatial anchor interest, and a second procdure allows for a consumer UE to subscribe for information about spatial anchors of interest.
The so... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.4 Solution #4: Support for spatial anchor analytics information | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.4.1 Solution description | This solution maps to KI# 8. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.4.2 Procedures | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.4.2.1 Spatial anchor analytics information (subscription-notify) | Figure 7.4.2.1-1 depicts the procedure for subscribing to receive spatial anchor analytics information for metaverse applications. The service is provided by MMES server and consumed by VAL server.
Figure 7.4.2.1-1: Spatial anchor analytics information subscription
1. A metaverse VAL server sends a spatial anchor analy... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.4.3 Architecture Impacts | Option #1 in clause 6.1 is the basis for this solution. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.4.4 Corresponding APIs | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.4.4.1 Overview | This clause provides a summary of the corresponding APIs for solution #4.
- Spatial anchor analytics information subscription request API (subscribe / notify model; API provider: MMES; known consumers: VAL server; corresponding to step 1 to 3 of clause 7.4.2.1).
- Spatial anchor analytics information notification API (... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.4.5 Solution evaluation | This solution addresses Key Issue #8(open issue# 2) by providing spatial anchor analytics information procedures based on MMES. This solution enables the VAL server to request the analytics related to the spatial anchor. The solution has no additional requirement to the core network. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5 Solution #5: Support for digital avatars | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5.1 Solution description | Metaverse is considered as a digital world which is a replica of a real world. Most of the Metaverse application needs avatar for the user to interact with the application. And for each application, user may required to create, modify, get and delete avatars. For each avatar (regardless of application) will have some c... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5.2 Architecture Impacts | This clause provided architecture enhancements to the SEAL CM architecture as defined in 3GPP TS 23.434 [8]. The SEAL CM client is enhanced to provide client side functionalities for managing (i.e. create, read, update and delete) application specific avatar profile(s) for metaverse application. The application specifi... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5.3 Procedures | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5.3.1 Create application specific avatar profile | The procedure for creating avatar profile is illustrated in figure 7.5.3.1-1. The configuration management server exposes the API for the consumer to create the avatar profile(s). The application specific avatar profile(s) may be created based on user’s request via configuration management client or based on request fr... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5.3.2 Update application specific avatar profile | The procedure for updating avatar profile is illustrated in figure 7.5.3.2-1. The configuration management server exposes the API for the consumer to update the avatar profile. The application specific avatar profile(s) may be updated based on user’s request via configuration management client or based on request from ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5.3.3 Get application specific avatar profile | The procedure to get avatar profile is illustrated in figure 7.5.3.3-1. The configuration management server exposes the API for the consumer to get the avatar profile.
Pre-conditions:
- The VAL UE has the secure access to the configuration management server.
Figure 7.5.3.3-1: Get application specific avatar profile
1. ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5.3.4 Delete application specific avatar profile | The procedure to delete avatar profile is illustrated in figure 7.5.3.4-1. The configuration management server exposes the API for the consumer to delete the avatar profile.
Pre-conditions:
- The VAL UE has the secure access to the configuration management server.
Figure 7.5.3.4-1: Delete application specific avatar pr... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5.3.5 Application specific avatar profile(s) subscription | Figure 7.5.3.5-1 depicts the procedure for application specific avatar profile(s) subscription. The service is provided by SEAL CM server and consumed by VAL server or SEAL CM client.
Figure 7.5.3.1-1: Application specific avatar profile(s) subscription
1) The VAL server (or SEAL CM client) sends a subscription request... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.5.4 Solution evaluation | This solution maps to KI# 3. This solution enhances Service Enabler Architecture Layer (SEAL) Configuration Management (CM) service by enhancing SEAL CM client and SEAL CM server functionalities as specified in clause 7.5.2. The solution proposes to create, update, get and delete avatar profile. The solution also propo... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7 Solution #7: Digital avatar support by A-DACM | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7.1 Solution description | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7.1.1 General | This solution maps to KI#3. This solution is based on A-DACM function to support the following avatar management services offered to VAL layer (VAL server):
- Avatar profile creation;
- Avatar upload;
- Avatar linking to user/subscriber;
- Avatar download;
- Avatar update/modification;
- Avatar delete;
Editor's Note: H... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7.1.2 Avatar profile creation | Figure 7.7.1.2-1 illustrates the high level flow for avatar profile creation procedure.
Figure 7.7.1.2-1: Procedure for Avatar profile creation
1. VAL server sends the Create Avatar Profile Request to A-DACM function with the details such as Avatar ID (optional), Avatar properties (e.g. name), Avatar usage policies (e.... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7.1.3 Avatar profile upload | Figure 7.7.1.3-1 illustrates the high level flow for avatar upload procedure.
Pre-conditions:
1. Avatar ID is available as per the procedure in clause 7.7.1.2
Figure 7.7.1.3-1: Procedure for Avatar upload
1. The VAL server sends the Upload Avatar Request to the A-DACM function with the Avatar ID and Avatar object/media... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7.1.4 Avatar linking to user/subscriber | Figure 7.7.1.4-1 illustrates the high level flow for avatar linking to user/subscriber procedure.
Figure 7.7.1.4-1: Procedure for Avatar linking to user/subscriber
1. The VAL server sends a Link Avatar Request to the A-DACM function with Avatar ID and GPSI/External identifier of the UE.
2. The A-DACM function checks th... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7.1.5 Avatar download | Figure 7.x.1.5-1 illustrates the high level flow for avatar download procedure.
Figure 7.7.1.5-1: Procedure for Avatar download
1. The VAL server sends a Download Avatar Request to the A-DACM function with the Avatar ID, GPSI/External ID of the UE, Filter/Adaptation information (e.g. VAL information, media adaptations)... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7.2 Architecture Impacts | The solution utilizes the architecture specified in clause 6.2, Option #2. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7.3 Corresponding APIs | Editor's Note: This clause provides the corresponding APIs for supporting the solution. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.7.4 Solution evaluation | This clause provides an evaluation of the solution addressing KI#3. The A-DACM function can support the avatar management services towards the VAL layer.
NOTE: The security mechanisms for this solution is the responsibility of SA3. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8 Solution #8: Support for spatial map management |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.