hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.1 Solution description | This solution maps to KI#4. This solution enhances SEAL LM service to provide spatial map management service. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.2 Architecture Impacts | This clause provides the architecture impacts of the solution. The solution provides enhancements to the SEAL LM functionalities for managing (i.e. produce, update, get, subscribe) spatial maps. To manage spatial maps between VAL server/SEAL LM client and SEAL LM server, reference points LM-S and LM-UU are used in this... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.3 Procedures | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.3.1 Producing spatial map | Figure 7.8.3.1-1 depicts the procedure for producing a spatial map. For the request from the spatial map requestor (VAL server or SEAL LM client), the service is provided by SEAL LM server. A spatial map can be structured in layers where each layer signifies a specific aspect of the spatial information (e.g. space, obj... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.3.2 Update spatial map | Figure 7.8.3.2-1 depicts the procedure to update the spatial map. For the request from the spatial map consumer (VAL server or SEAL LM client), SEAL LM server modifies or deletesthe spatial map as requested.
Figure 7.8.3.2-1: Update spatial map
1) The VAL server (or SEAL LM client) sends a request message to the SEAL L... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.3.3 Get spatial map | Figure 7.8.3.3-1 dipicts the procedure for the authorized spatial map consumer (VAL server or SEAL LM client) to get the spatial map. The service is provided by SEAL LM server.
Figure 7.8.3.3-1: Get spatial map
1) The VAL server (or SEAL LM client) sends a request message to the SEAL LM server to get the spatial map. T... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.3.4 Subscribe/unsubscribe spatial map | Figure 7.8.3.4-1 dipicts the procedure for the authorized spatial map consumer (VAL server or SEAL LM client) to subscribe the spatial map. The service is provided by SEAL LM server.
Figure 7.8.3.4-1: Subscribe/unsubscribe spatial map
1) The VAL server (or SEAL LM client) sends a request message to the SEAL LM server t... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.3.5 Spatial localization services | Figure 7.8.3.5-1 depicts the procedure for the authorized spatial map consumer (VAL server or SEAL LM client) to invoke spatial localization services. The service is provided by SEAL LM server.
Pre-condition:
1) Spatial map is created and the authorized consumer is aware of the spatial map identity.
Figure 7.8.3.5-1: S... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.3.6 Delete spatial map | Figure 7.8.3.6-1 depicts the procedure to delete the spatial map(s). For the request from the spatial map consumer (VAL server or SEAL LM client), SEAL LM server deletes the spatial map(s) as requested.
Figure 7.8.3.6-1: Delete spatial map procedure
1) The VAL server (or SEAL LM client) sends a request message to the S... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.4 Corresponding APIs | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.4.1 Produce spatial map | Table 7.8.4.1-1 shows the produce spatial map request sent by VAL server (or SEAL LM client) to SEAL LM server to produce a spatial map.
Table 7.8.4.1-1: Produce spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or SEAL LM client)
Requestor s... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.4.2 Update spatial map | Table 7.8.4.2-1 describes the information flow from VAL server (or SEAL LM client) to SEAL LM server for the update spatial map request.
Table 7.8.4.2-1: Update spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or SEAL LM client)
Requestor se... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.4.3 Get spatial map | Table 7.8.4.3-1 shows the get spatial map request sent by VAL server (or SEAL LM client) to SEAL LM server to get spatial maps.
Table 7.8.4.3-1: Get spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or SEAL LM client)
Requestor security crede... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.4.4 Subscribe/unsubscribe spatial map | Table 7.8.4.4-1 shows the subscribe spatial map request sent by VAL server (or SEAL LM client) to SEAL LM server to subscribe spatial maps.
Table 7.8.4.4-1: Subscribe spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or SEAL LM client)
Reques... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.4.5 Delete spatial map | Table 7.8.4.5-1 descibes the information flow from the VAL server (or SEAL LM client) to the SEAL LM server for the delete spatial map request.
Table 7.8.4.5-1: Delete spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or SEAL LM client)
Reque... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.8.5 Solution evaluation | This solution addresses KI#4. It provides spatial map management service procedures to publish, update/delete, get and subscribe to the spatial map. The solution is technically feasible for providing spatial map service. A new SEAL service and enhanced SEAL LM service are suitable architecture options to enable this so... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.9 Solution #9: Avatar discovery procedure | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.9.1 Solution description | This solution maps to KI#3 and KI#5. The solution provides a mechanism for discovering avatars.
Pre-conditions:
1) The VAL client has associated user or avatar profile information for an avatar which is authorized to discover.
Figure 7.9.1-1: Avatar discovery procedure
1. A VAL client triggers MMEC to search for a digi... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.9.2 Architecture Impacts | The architectural impact for this solution is described in clause 6.1, Option #1. The solution may be adapted to using a SEAL server. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.9.3 Corresponding APIs | Table 7.9.3-1 shows the avatar discovery request from the MMEC to the MMES.
Table 7.9.3-1: Avatar discovery request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
Requestor security credentials
M
The security credentials of the requestor.
Requesting avatar
M
The identifie... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.9.4 Solution evaluation | This solution maps to KI# 3. This solution is based on the Mobile Metaverse enablement layer architecture as specified in clause 6.1. The solution proposes to discover avatar based on query parameters.
This solution addresses Key Issues #3 and #5 by providing a mechanism for a VAL client to discover avatars, and their ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.10 Solution #10: Metaverse digital asset synchronization QoS control | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.10.1 Solution description | The following clauses specify procedures and information flows for Key Issue #3 and Key Issue #5 for QoS control for avatars as digital assets.
Preconditions:
1. A digital asset (e.g. avatar representation) has been created (e.g. as element in MDRB) and MMEL policies have been associated.
NOTE 1: This solution is descr... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.10.2 Architecture Impacts | This solution is described using a new Metaverse Enabler layer (MMES/MMEC entities as described in clause 6.1 and leveraging SEALDD functionality in the SEAL layer) for support of metaverse services. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.10.3 Corresponding APIs | Table 7.10.3-1 details digital asset synchronization session communication parameters received in steps 1- 2 at the SEALDD layer from the VAL Server (directly or via MMES).
Table 7.10.3-1: Digital asset synchronization session communication parameters
Information element
Status
Description
List of digital assets
M
A li... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.10.4 Solution evaluation | This solution enables MMEL to provide digital asset synchronization services to mobile metaverse VAL applications. The procedure allows for QoS coordination and is relevant to metaverse applications requiring synchronization of digital asset information.
The solution complements solution #11 by describing how SEALDD ca... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.11 Solution #11: Application QoS coordination for Mobile Metaverse Sessions | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.11.1 Solution description | This solution maps to KI# 5. This solution provides a mechanism for application session QoS coordination for mobile metaverse services (for use cases such as Mobile Metaverse Based Selective Multi-modal Feedback Service or Mobile Metaverse for 5G-enabled Traffic Flow Simulation and Situational Awareness as discussed in... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.11.2 Architecture Impacts | This solution requires a new Metaverse Enabler layer (MMES/MMEC entities) to support a new capability on QoS coordination for metaverse services. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.11.3 Corresponding APIs | This subclause provides a summary on the corresponding API for solution #x.
- MM-specific QoS management API (request / response model or subscribe/notify; API provider: MMES; known consumer: VAL UE, VAL server; corresponding to step 1).
- MM-specific QoS update notify API (command/ notify; API provider: MMES; known co... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.11.4 Solution evaluation | This solution provides a mechanism at MMES/MMEC for application session QoS coordination for mobile metaverse services, via compensating the possible downgrade in certain links (e.g., due to high latency in one or more links). This solution is only applicable to metaverse applications since the sessions are for both ph... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.12 Solution #12: Support device discovery to offload task for metaverse services | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.12.1 Solution description | This solution maps to KI#6. This solution proposes to enhance Application layer support for Personal IoT Network as defined in 3GPP TS 23.542 [12]. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.12.1.1 PIN client requests to discover another PIN element | Figure 7.12.1.1-1 illustrates procedure of PIN client requests to discover another PIN element, based on request/response model.
Pre-conditions:
1. The UE (PIN client) has already discovered PIN as specified in clause 8.5.7 of 3GPP TS 23.542 [12];
2. The UE (PIN client) has already joined the PIN as specified in clause... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.12.2 Architecture Impacts | This solution does not impact the existing architecture as defined in 3GPP TS 23.542 [12]. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.12.3 Corresponding APIs | Table 7.12.3-1 shows the request sent by a PIN client of a PIN element to a PEMC for the PIN element discovery request.
Table 7.12.3-1: PIN element discovery request
Information element
Status
Description
PIN ID
M
Identifier of the PIN that wants to join in.
Security credentials
M
Security credentials resulting from a ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.12.4 Solution evaluation | The solution resolves open issue 1) of KI #6. The solution provides a procedrue for a PIN element to discover another PIN elements to offload the computational task. The solution does not required any architecture update. The solution impacts PIN client and PIN management client. The solution is a feasible solution. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.13 Solution #13: Support for metaverse services requiring multiple devices | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.13.1 Solution description | This solution maps to KI# 7. A metaverse service (e.g. a game service) requires haptic device associated with the UE/user in order for user to consume the service (e.g. to play the game).
Consider a use case where a metaverse service (e.g. a game service) requires haptic device associated with the UE/user in order for ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.13.1.1 Enhancement to EAS profile | Following information element is added as an enhancements to EAS profile as defined in clause 8.2.4 of 3GPP TS 23.558 [13].
Table 7.13.1.1-1: Enhancement to EAS Profile
Information element
Status
Description
List of associated devices
O
List of associated devices (e.g. haptic device, joy stick) required along with UE i... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.13.1.2 Enhancement to EAS discovery request (between AC to EEC) | Following information element is added as an enhancements to EAS discovery request as defined in clause 8.14.3.8 of 3GPP TS 23.558 [13].
Table 7.13.1.2-1: Enhancement to EAS discovery request in clause 8.14.3.8 of 3GPP TS 23.558 [13]
Information element
Status
Description
List of associated devices
O
List of associated... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.13.1.3 Enhancement to EAS discovery procedure (between EEC to EES) | Following information element is added as an enhancements to EAS discovery request as defined in clause 8.5.3.2 of 3GPP TS 23.558 [13].
Table 7.13.1.3-1: Enhancement to EAS discovery request in clause 8.5.3.2 of 3GPP TS 23.558 [13]
Information element
Status
Description
List of associated devices
O
List of associated d... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.13.2 Architecture Impacts | This clause describes the architecture impacts to the EDGEAPP architecture as defined in 3GPP TS 23.558 [13]. Figure 7.13.2-1 illustrates the associated devices (e.g. tactile gloves or VR glasses) are connected with the application client of the UE.
Figure 7.13.2-1: Associated devices connected with AC of the UE
The as... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.13.3 Corresponding APIs | The enhancement to APIs as defined in 3GPP TS 23.558 [13] are specified in clause 7.13.1. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.13.4 Solution evaluation | Editor's Note: This clause provides an evaluation of the solution addressing KI#x.
This solution resolved open issue 1 of the KI 7. The architecture proposes to have application level connection between application client of the UE and other associated devices as shown in clause 7.13.2. The solution enhances existing E... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15 Solution #15: Support for VAL UEs in spatial map | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15.1 Solution description | This solution maps to KI#4. This solution enables to support the management of spatial map with VAL UEs information related to the VAL server and its VAL services. During create or update of the spatial map, based on request from the VAL server, this solution enhances spatial map with information related to the VAL UEs... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15.2 Architecture Impacts | The solution enhances the SEAL LM functionalities to manage the spatial map with VAL UEs information in the area related to the spatial map and that are related to the VAL server’s VAL services. For the spatial map management between the VAL server/SEAL LM client and SEAL LM server, reference points LM-S and LM-UU can ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15.3 Procedures | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15.3.1 Create spatial map augmented with VAL UE | Figure 7.x.3.1-1 illustrates the procedure to create a VAL UE augmented spatial map. The request is from VAL server or an SEAL LM client. The service is provided by SEAL LM server.
Editor’s note: This procedure is to provide the spatial map service with VAL UE, not spatial map. The terminologies will be reconsidered.
F... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15.3.2 Update spatial map augmented with VAL UEs | Figure 7.15.3.1-1 illustrates the procedure to updating a VAL UE augmented spatial map. The request is from VAL server or an SEAL LM client. The service is provided by SEAL LM server.
Pre-condition:
1. Spatial map is created and VAL server (or SEAL LM client) is aware of the spatial map identity.
2. The VAL server (or ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15.4 Corresponding APIs | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15.4.1 Overview | This clause provides summary of the corresponding APIs for the solution #15.
1. Produce spatial map with VAL UEs API (Request / Response, API Provider: SEAL LM server, Known consumers: VAL server/ SEAL LM client, corresponding to step 1 to 5 of clause 7.15.3.1)
2. Update spatial map with VAL UEs API (Request / Response... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15.4.2 Information Flows | Table 7.15.4.2-1 shows the information in the request sent by VAL Server/ SEAL LM client to SEAL LM server to produce VAL UE augmented spatial map with VAL UEs
Table 7.15.4.2-1: Produce VAL UE augmented spatial map request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.15.5 Solution evaluation | This solution addresses KI#4 by providing the VAL UE augmented spatial map create/update services. The procedures are based on the SEAL-LM architecture and functional model. The solution enhances the existing SEAL LM server by adding new functionalities to manage spatial maps augmented with VAL UE information. This sol... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16 Solution #16: Spatial mapping service exposure and discovery | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.1 Solution description | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.1.1 General | This solution is for KI#4 and addresses the open issue of how to produce, modify and expose a spatial map.
This solution is presented based on the Mobile Metaverse enablement layer architecture described in clause 6.1 (e.g., option #1); the solution is also applicable if introducing a new SEAL service reusing an existi... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.1.2 Exposing a spatial mapping service | This procedure allows an authorized VAL server to expose a spatial mapping service to authorized consumers.
Figure 7.16.1.2-1: Exposing a spatial mapping service
1. A VAL server providing a spatial mapping service sends a spatial mapping service exposure request to the MMES. The request includes a VAL server identifier... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.1.3 Discovering a spatial mapping service | This procedure allows a consumer application on a UE to discover a spatial mapping service according to provided requirements.
Pre-conditions:
1) A spatial mapping service is exposed via the MMES.
Figure 7.16.1.3-1: Discovering a spatial mapping service
1. A VAL client requires spatial mapping services for a specific l... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.1.4 Service exposure via CAPIF | The mobile metaverse services can support exposing the spatial mapping service offered by the VAL server via CAPIF as specified in 3GPP TS 23.222 [14] by deploying CAPIF core function within the MMES to support publish and discovery of the VAL server service APIs.
NOTE 1: The MMES supporting the exposure of the spatial... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.2 Architecture Impacts | This solution can be realized according to architectures described in clause 6.1 or clause 6.3 or using new SEAL Server. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.3 Corresponding APIs | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.3.1 Overview | This clause provides a summary of the corresponding APIs for solution #16.
- Spatial mapping service exposure API (request / response model; API provider: MMES; known consumers: VAL server; corresponding to step 1 and 3 of clause 7.16.1.2).
- Spatial mapping discovery API (request / response model; API provider: MMEC; ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.3.2 Information flows | Table 7.16.3.2-1 shows the request sent by a VAL server to a MMES for exposing a spatial mapping service.
Table 7.16.3.2-1: Spatial mapping service exposure request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server)
Requestor security credentials
M
The security ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.16.4 Solution evaluation | This solution is for KI#4 and addresses the open issue of how to produce, modify and expose a spatial map.
This solution can be realized according to architectures described in clause 6.1 or clause 6.3.This solution proposes that the mobile metaverse service provides capabilities for exposing a spatial mapping service ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17 Solution #17: Discovery of UEs consenting and capable of providing spatial mapping information | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17.1 Solution description | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17.1.1 General | This solution is for KI#4 and addresses the open issue of how to enable UE(s) to provide spatial mapping information for maintaining a spatial map.
This solution is presented based on the Mobile Metaverse enablement layer architecture described in clause 6.1 (e.g., option #1); the solution is also applicable if introdu... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17.1.2 Registering a spatial mapping information provider | This procedure allows a consenting VAL client (e.g., UE) that can provide spatial mapping information to register as a provider of spatial mapping information to be discoverable by authorized consumers.
NOTE: In this solution, the spatial mapping information provider is consenting since the provider initiates the regis... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17.1.3 Discovering and triggering a spatial mapping information provider | This procedure allows a spatial mapping service to discover and trigger a registered spatial mapping information provider for spatial mapping information.
Pre-conditions:
1) Spatial mapping information providers have registered with the MMES.
Figure 7.17.1.3-1: Spatial mapping information provider discovery and informa... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17.2 Architecture Impacts | Option #1 in clause 6.1, option #3 in clause 6.3 or a new SEAL client and server can be used to realize this solution. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17.3 Corresponding APIs | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17.3.1 Overview | This clause provides a summary of the corresponding APIs for solution #17.
- Spatial mapping information provider registration API (request / response model; API provider: MMES; known consumers: MMEC; corresponding to step 1 and 3 of clause 7.17.1.2).
- Spatial mapping information provider discovery API (request / resp... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17.3.2 Information flows | Table 7.17.3.2-1 shows the request sent by a MMEC to a MMES for registering a spatial mapping information provider.
Table 7.17.3.2-1: Spatial mapping information provider registration request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., MMEC, UE identifier)
Requestor ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.17.4 Solution evaluation | This solution is for KI#4 and addresses the open issue of how to enable UE(s) to provide spatial mapping information for maintaining a spatial map.
This solution can be realized according to architectures described in clause 6.1 or clause 6.3 or a new SEAL server and client. This solution proposes that the mobile metav... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.18 Solution #18: Discovery and requirements translation for 5G-enabled Traffic Flow Simulation and Situational Awareness | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.18.1 Solution description | In Mobile Metaverse for 5G-enabled Traffic Flow Simulation and Situational Awareness use case (as discussed in 3GPP TR 22.856 [3]), real-time information and data about the real objects can be delivered to the virtual objects of the road infrastructure and traffic participants including vulnerable road users can form a... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.18.2 Architecture Impacts | This solution requires an enhanced capability at the SEAL NRM for supporting the discovery and requirements translation for metaverse services. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.18.3 Corresponding APIs | This subclause provides a summary on the corresponding API for solution #x.
- MM-specific service requirements API (request / response model or subscribe/notify; API provider: SEAL NRM server; known consumer: MMSS, VAL server; corresponding to step 1).
- MM-specific provisioning policy API (command/ notify; API provide... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.18.4 Solution evaluation | This solution provides a mechanism for discovery and requirement translation for mobile metaverse services. This solution is only applicable to metaverse applications like “Mobile Metaverse for 5G-enabled Traffic Flow Simulation and Situational Awareness” as discussed in Stage 1 since the sessions are for both physical... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.19 Solution #x: Support for permission control of digital assets | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.19.1 Solution description | This solution maps to KI#9, achieves permission control on digital assets in the case of digital assets sharing. VAL user uses VAL server to upload a digital asset to A-DACM function. DAPM is to publish digital assets and provide subscription digital assets service. DACM and DAPM work together to achieve the permission... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.19.2 Architecture Impacts | The solution utilizes the architecture specified in clause 6.4, Option#4. In the architecture DAPM function exposes the APIs to the Vertical Application Layer for service providing. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.19.3 Procedures | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.19.3.1 Digital asset publishing | Since not all digital assets have publishing requirements, owners need to initiate and upload the digital asset information to DAPM, and make commission to DAPM to promote.
Figure 7.19.3.1-1 illustrates the high level flow for digital asset publishing procedure.
Figure 7.19.3.1-1: Procedure for digital asset publishing... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.19.3.2 Digital asset subscription | Figure 7.19.3.2-1 illustrates the high level flow for digital asset subscription procedure.
Precondition: The subscriber discovered the digital asset on DAPM and want to download.
Figure 7.19.3.2-1: Procedure for digital asset subscription
1. The consumer discovers the digital asset on the DAPM function and using VAL s... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 7.19.3.3 Digital asset download with subscription ( enhanced Avatar download procedure) | Figure 7.19.3.3-1 illustrates the high level flow for avatar download with subscription procedure. This procedure is an enhanced Avatar download procedure, in which the VAL Server/user has already subscribed the digital assets from DAPM.
Pre-condition: The consumer has subscribed the digital asset on DAPM and obtain th... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 8 Deployment scenarios | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 8.1 General | This clause describes different deployment models to provide metaverse services to the end user. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 8.2 Deployment model #1: Deployment of enabler for Metaverse Services as SEAL server(s) | Figure 8.2-1 illustrates deployment of the metaverse services as SEAL server(s) in a single PLMN operator domain and the VAL server(s) in the VAL service provider domain.
Figure 8.2.1-1: metaverse services as SEAL server(s)
The SEAL server(s) can be one or more SEAL services, providing enablement services to the metave... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 9 Business Relationships | The business relationship as specified in clause 5 of 3GPP TS 23.434 [8] is applicable for metaverse service eco system too, where VAL user is metaverse service user, VAL service provider is metaverse service provider and further, VAL service provider and SEAL service provider can be same organization. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10 Overall evaluation | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.1 Architecture evaluations | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.1.1 On-network mobile metaverse application layer architecture | The architecture is proposed as option #1 in clause 6.1. The architecture supports spatial anchors management (as specified in solution#1, solution #3, solution#4), avatar management (as specified in solution #6). The architecture proposes to create metaverse application enabler layer. The architecture option is a feas... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.1.2 SEAL architecture to support metaverse applications | The SEAL based architectures are proposed as option#2 in clause 6.2 and option#3 in clause 6.3.
For avatar and/or digital asset management,
- architecture option#2 is the basis for the solution#7 and proposes a new SEAL service; and
- architecture option#3 is the basis for the solution#5 and proposes to re-use SEAL CMS... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2 Key issue evaluations | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2.1 Key issue #1: Enabler support for managing spatial anchors | Solution #1, Solution #2 and Solution #3 addresses the key issue 1.
Solution #1 resolves open issue 2) and provides spatial anchors discovery procedure based on architecture option#1.
Solution #2 resolves open issue 1) and provides spatial anchors create, update, get and subscription procedures based on enhancing SEAL ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2.2 Key issue #2: Exposure of user sensitive information | Solution #X addresses key issue #2 by providing a mechanism for servers to avoid servicing requests for which user consent has not been granted for the information (e.g., the request body) provided by the client in such requests. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2.3 Key issue #3: Avatar and digital asset support | Solution #5, Solution #6, Solution #7 and Solution #9 addresses the key issue 3.
Solution #5 proposes to manage avatar profile by enhancing SEAL CM service. The solution proposes the create, update, get, delete avatar profile. The solution also proposes to subscribe for avatar profile.
Solution #6 proposes to manage av... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.