hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.35.5 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing services, entities and interfaces. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.36 Solution #36: Device ID(s) for AIoT Devices | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.36.1 Description | This solution addresses device ID aspect of Key Issue #2
In 5GS, there are the following identifiers which are described in TS 23.501 [4]:
- Subscription Permanent Identifier (SUPI).
- Subscription Concealed Identifier (SUCI).
- Permanent Equipment Identifier (PEI).
- 5G Globally Unique Temporary Identifier (5G-GUTI).
... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.36.2 Procedures | The device IDs for AIoT devices are used in an equivalent way as current ones for UEs. No new procedures introduced due to AIoT device IDs. They are used in the inventory, command, (and also other) procedures for AIoT devices:
- SUCI like device ID is sent from AIoT devices to network to identify the device when unauth... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.36.3 Impacts on services, entities and interfaces | The logic of current 5GS usage of identifiers is re-used with the following differences or clarifications:
- AIOTF applies similar functionality as an AMF for handling, e.g. SUCI.
- Entities, e.g. AIoT Device, UDM that conceal and reveal SUCI to handle new SUPI type format.
- Entities handling SUPI may need to handle n... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.37 Solution #37: Multiple Temporary Reusable Identities for AIoT Devices | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.37.1 Description | This solution addresses KI#2 and tackles the problem of efficiently and securely identifying an AIoT device while preserving the limited AIoT device computing resources. This is accomplished by providing the AIoT device with a set of temporary identifiers, which can be revoked and reallocated as explained below. Unique... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.37.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.37.2.1 Temporary Reusable ID Allocation | Figure 6.37.2.1-1: Procedure to support allocation of multiple temporary identities to AIoT devices
The procedure in Figure 6.37.2-1 to support allocation of multiple temporary identities to AIoT devices is described step by step below. The temporary ID allocation is assumed to be performed in a secure manner.
0. An AI... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.37.2.2 Temporary Reusable ID Revocation and Re-Allocation | The temporary reusable IDs may be revoked and re-allocated as described below:
- One or more temporary IDs can be revoked from the AIoT device and re-allocated to another device e.g. in case of a pre-determined period of inactivity after which the device is assumed to have left the network. A revocation notification ma... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.37.2.3 Temporary Reusable ID Conflict Detection and Resolution | If a device from which the ID had been previously revoked attempts to communicate again with the network by responding to the paging from the network, the following conflict detection and resolution mechanisms are performed:
- When the returning device responds to paging from the network using the temporary ID and the ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.37.3 Impacts on services, entities and interfaces | Impacts on existing entities:
CN NF (AMF or AIoT NF):
- Support handling and allocation of multiple temporary reusable identifiers for AIoT devices.
- Support revocation and conflict detection and resolution for temporary reusable IDs for AIoT devices.
AIoT device:
- Support for multiple temporary identifiers capabilit... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.38 Solution #38: AIoT device tracking for inventory | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.38.1 Description | This solution addresses KI#3.
The solution introduces a new role, "AIoT Device Companion UE", which is a normal UE and moves with the AIoT devices. A Companion UE is able to perform mobility/location update and support LCS procedures with the 5GC. Therefore, a Companion UE's accurate location may be known in the 5GC. W... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.38.2 Procedures | Figure 6.38.2-1: AIoT inventory procedure using Companion UE
1. Multiple AIoT devices move with a Companion UE. The Companion UE obtains a list of AIoT device IDs or group device IDs that move with it, either through preconfiguration or collecting via the radio interface. The UE reports its role of Companion UE and the... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.38.3 Impacts on services, entities and interfaces | UE:
- Support the role of Companion UE (obtaining AIoT device IDs, report their roles to the network).
AMF/AIoT Function:
- Receive and store Companion UE-AIoT device(s) ID association in the UDM.
- Select Reader based on Companion UE location.
- Forward inventory request to Reader.
UDM:
- Store Companion UE-AIoT devic... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.39 Solution #39: Configuration of Ambient IoT device frequency | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.39.1 Description | This solution addresses Key Issue #2 by providing simplified connection management for Ambient IoT devices. Based on the assumptions in clause 4.1 of the present document, there is no cell selection/re-selection like feature for Ambient IoT devices. Hence, it is unclear how the Ambient IoT devices is going to work with... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.39.2 Procedures | This clause describes procedures to enable and disable communication for an Ambient IoT device in licensed spectrum. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.39.2.1 Enable Ambient IoT device(s) communication in operator network | Figure 6.39.2.1-1: Enablement of communication in operator network
0. One or several Ambient IoT device(s) powers on and operates in a default frequency. The Ambient IoT device(s) operates in a default frequency. The default frequency is unlicensed. The Ambient IoT device(s) is preconfigured with Ambient IoT group ID a... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.39.2.2 Disable Ambient IoT device(s) communication in operator network | Figure 6.39.2.2-1: Disablement of communication in operator network
0. The Ambient IoT device and reader can communicate in licensed spectrum owned by the serving network.
1. Optional, the AF can send a Removal request to the NEF. The reason can be the AF is planning to move Ambient IoT devices from one serving network... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.39.3 Impacts on services, entities and interfaces | AF:
- Support requesting onboarding and removal of Ambient IoT devices from a serving network.
NEF:
- Supports signalling for onboarding and removal of Ambient IoT devices in the serving network.
AMF with AIoT functionality / AIoTF:
- Support index frequency configuration for Ambient IoT e.g. steer to licensed spectrum... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.40 Solution #40: Reader dependent Inventory Response | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.40.1 Description | This solution address aspects of Key Issue #3 and specifically relates to inventory and "how to support information transfer for Ambient IoT services and related system functionality, including the information transfer for an Ambient IoT device and for a group of Ambient IoT Devices".
In some scenarios, it may not be p... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.40.2 Procedures | Figure 6.40.2-1: Inventory Procedure where the AIoT Device Checks Reader Permissions before Responding
1. The AIoT Device is configured with reader(s) identities and permissions.
The reader(s) identities and permissions can be either pre-configured in the AIoT Device or sent to the AIoT Device by the network. The confi... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.40.3 Impacts on services, entities and interfaces | Reader:
- Supports sending the request to AIoT devices with Reader Identity, AIoT Device ID and Service/Application ID.
AIoT Device:
- Supports per-reader configuration information.
- Uses the per-reader configuration to determine how to respond to an inventory request (e.g. whether to include application data or to on... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.41 Solution #41: Simple AIoT device and AIoT solution in the certain deployment | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.41.1 Description | One typical AIoT use case is inventory in the warehouse, where the environment is closed and controllable by the warehouse owner (as the 3rd party/AF) and the AIoT network operator.
For the AIoT device with very limited capabilities and power can access to the network, the AIoT device operation including security and p... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.41.2 Procedures | In this solution, the AIoT device does not need to have security or privacy capabilities internally. For the AIoT device having security or privacy capabilities, either the warehouse owner or the network operator configures the AIoT device without security or privacy enabled in this case. From the AIoT network and 3rd ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.41.3 Impacts on services, entities and interfaces | AF:
- It indicates the 3rd party's preference with No security and privacy operation allowed indication to AIoT network.
AIoT device Management:
- A core network function manages the AIoT device including the indication that this AIoT device can be operated without security and privacy requirements.
AIoT controller:
- ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.42 Solution #42: AIoT data forwarding over UE reader in topology 2 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.42.1 Description | This solution address aspects of key issue #3 on Support of Ambient IoT Services.
This solution can be applied for only Topology 2.
There are multiple methods that a UE reader forward data received from the AIoT devices to the network.
1. Over user plane.
2. Over control plane where the UE reader in RRC CONNECT state (... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.42.2 Procedures | Figure 6.42.2-1: Information Flow for AIoT communication optimization
1. When a UE registers with the 5GC, it provides its capability, indicating which AIoT data forwarding (UL) methods (e.g. UP, UL NAS and/or CIoT optimisation) it supports.
2. An AF sends an AIoT service (e.g. inventory or command) request message to ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.42.3 Impacts on services, entities and interfaces | Entity in 5GC, responsible for AIoT service handling (e.g. AIoTF):
- Supports selecting the AIoT data forwarding methods or providing the relevant information to the gNB.
AIoT UE reader:
- Supports indicating its capability for AIoT data forwarding methods
RAN node:
- Supports selecting the AIoT data forwarding methods... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43 Solution #43: Harmonized RAN-CN solution using AIOTF for Topology 2 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.1 Description | This solution proposes a complementary solution to Solution #8. It enables the support of Ambient IoT devices for topology 2 with harmonized RAN-CN architecture, which addresses KI#1, KI#2 and KI#3. Together with Solution #8 which focus on Topology 1, the solutions can support AIoT devices for both Topologies.
In this ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.1.1 Reference Architecture | The Figure 6.43.1.1-1 illustrates the architecture for harmonized RAN-CN solution using AIOTF for topology 2:
Figure 6.43.1.1-1: System Architecture of harmonized RAN-CN solution using AIOTF for Topology 2
This solution focuses on Topology 2, which works together with Solution #8 addressing Topology 1.
The functional e... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.1.2 Protocol Stack | The Figure 6.43.1.2-1 illustrates the protocol stack:
Figure 6.43.1.2-1: Protocol Stack for harmonized RAN-CN solution using AIOTF for Topology 2
As solution #8, within the protocol stack:
- AIOT device NAS layer: The NAS protocol between AIOTF and AIoT devices.
- AIOT AS layer: The AS protocol layers between UE reader... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.2 Procedures | NOTE: The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.2.1 NG Setup | The NG-RAN triggers NG Setup procedure not only towards the AMF, but also towards the AIOTF. Via the NG connection, the AIOTF delivers AIoT device NAS messages towards the NG-RAN, as well as receives AIoT device NAS messages from the NG-RAN. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.2.2 AIoT Service Authorization for Intermediate UE | The procedures for AIoT service authorization for Intermediate UEs are the same as described in clause 6.30.2.1 in solution #30.
The Registration procedure for UE is performed as defined in clause 4.2.2.2 of TS 23.502 [5] with the following additions:
- UE includes the AIoT Intermediate node capability as part of "5GMM... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.2.3 AIOTF Keep Track of Intermediate UE | The procedures to enable AIOTF to keep track of Intermediate UEs are the same as described in clause 6.30.2.2 in solution #30.
For authorized Intermediate UEs (Those Ambient IoT Capable UEs which have been authorized by the AMF as described in clause 6.43.2.2), in Initial Registration procedure as defined in clause 4.2... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.2.4 Application Inventory | The Inventory procedure can be initiated by the AF to discover one or more AIoT devices in a specific area via Intermediate UEs.
Figure 6.43.2.4-1: Inventory Procedure
1. AF sends Inventory Request to the AIOTF, which is the same as step 1 - 4 in Figure 6.8.2.1-1 in Solution #8.
2. The AIOTF may generate the candidate ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.2.5 Periodic Inventory Procedure | The periodic inventory may be requested by the AF, so that network can trigger the inventory periodically without the request from the AF directly.
Considering the movement of the Intermediate UEs which are not fixed, and the inventory is based on area information, the periodic inventory should be initiated by the CN (... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.2.6 Command Procedure | The command procedure is initiated by the AF to request one or more specific AIoT devices or a group of AIoT devices in an area to execute the command. The command can be read, write, enable, disable, or execution request from the AF. The command result from the devices may or may not be required.
Figure 6.43.2.6-1: Co... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.43.3 Impacts on services, entities and interfaces | The following NFs are impacted on top of the impacts of solution #8:
- NG-RAN:
- NGAP association with AIOTF.
- Determine radio resources between Intermediate UE and AIoT devices.
- Receive request from AIOTF, (optional) determine Intermediate UEs, forward to Intermediate UEs.
- Receive response from Intermediate UEs a... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 7 Overall Evaluation | Editor's note: This clause will provide a general evaluation and comparison of the solutions per Key Issue #<X>. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8 Conclusions | NOTE: The cconclusions in this clause regarding Topology 2 (i.e. mainly in clause 8.1.3) have not been updated since v1.2.0 and will not be further updated considering that the Topology 2 is not pursued in Rel-19 normative phase as per RAN WI in RP-243326. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1 Conclusion on Key Issue #1 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.1 General | Key issue #1 includes the following aspects:
- System architecture identified along with the solutions for KI#2 and KI#3.
Key issue#2 aspect on "Ambient IoT Device subscription management" and key issue#3 aspect on "Ambient IoT service exposure" is considered in this clause.
In this Release, normative work will take pl... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.2 Architecture to Support Topology 1 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.2.1 General | The principles and aspects in this clause are agreed to support Topology 1:
- The new core network function (AIOTF) is introduced to support Ambient IoT functionality, described in clause 8.1.1, with the following features for topology 1:
- Send requests that trigger BS Reader(s) (via AIoT RAN) to perform AIoT operatio... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.2.2 AIOT RAN and the AIOTF communicate directly | When a AIOT RAN and the AIOTF communicate directly:
- The AIOTF communicates with a AIOT RAN via a direct interface reference point Nx.
- Figure 8.1.2.2-1 below shows the aspects related to Topology 1 (direct path) architecture in reference point representation architecture with other NFs removed.
Figure 8.1.2.2-1: Non... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.2.3 AIOT RAN and the AIOTF communicate indirectly via an AMF | When AIOT RAN and the AIoTF communicate indirectly via an AMF:
- The AIoTF connects with AIOT RAN via an AMF. NGAP over the N2 reference point between the AIOT RAN and AMF supports Ambient IoT services including delivery of inventory/command messages.
NOTE 1: If network isolation is required an AMF instance is deployed... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.3 Architecture to Support Topology 2 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.3.1 General | The following principles apply:
- Architecture: Two architecture options will be specified for Topology 2:
- User-plane option as defined in clause 8.1.3.2.
- RRC-based option as defined in clause 8.1.3.3.
- Subscription aspects:
- The UE subscription in the UDM will be extended with UE Reader subscription information,... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.3.2 User-plane option | The following additional principles apply:
- As depicted in Figure 8.1.3.2-1, the UE Reader connects to the AIoTF based on the AIoT Application Protocol (AIoT-AP) using an IP PDU Session between the UE and the UPF as transport. The related protocol stack is shown in Figure 8.1.3.2-2. The AIoT AP protocol will support p... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.3.3 RRC option | The following principles apply:
- Messages between the UE Reader and the AIoTF are delivered using RRC between UE and RRC and NGAP between gNB and AMF, and using an SBI interface between AMF and AIoTF. The related protocol stack is shown in Figure 8.1.3.3-1.
Editor's note: How addressing works for UL for Option B is FF... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.1.3.4 Interim Conclusion for authorization | The following interim conclusion are agreed for the UE Reader authorization in Topology 2:
- The subscription data of UE Reader includes the indication that whether the UE is allowed to act as an AIoT Reader.
- The AMF provides the UE Reader authorization indication to the NG-RAN serving the UE Reader.
Editor's note: H... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.2 Conclusion on Key Issue #2 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.2.1 Identifier and Identification Management | The following aspects and principles are considered and agreed for the interim conclusion on Identifier and Identification Management.
The following principles are agreed for Identifier and Identification Management:
- An Ambient IoT Device is configured with a permanent Ambient IoT Device Identifier which can be assig... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.2.2 Subscription Management | The AIoT device may or may not have operator’s subscription data in the network. If the AIoT device doesn’t have the operator’s subscription data in the network, the corresponding related data (e.g. Device ID or credentials) is stored in the AAA server external to the network.
Subscription data for an Ambient IoT Devic... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.3 Conclusion on Key Issue #3 | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.3.1 General | The clause concludes the following aspects:
- Study how to support information transfer for Ambient IoT services and related system functionality, including the information transfer for an Ambient IoT device and for a group of Ambient IoT Devices.
NOTE: The above aspect includes studying whether there is a need to supp... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.3.2 AIoT services supported by the 5GC | The following Ambient IoT services are agreed to be supported by the 5GC, which apply to both topology 1 and topology 2:
- Inventory: Request to perform an inventory operation.
- Read: Request to read information from an AIoT Device.
- Write: Request to write information to an AIoT Device.
- Disable: Request that an AI... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.3.3 NEF exposure | NEF supports to expose Ambient IoT service towards the AF.
- New NEF services (e.g. Nnef_AIoT) to support the AIoT services including Service Operations of Inventory, Read, Write, and Permanent Disable will be defined. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.3.4 Principles on the procedures to support AIoT services | To support the services provided by 5GC and the NEF exposure of those AIoT services, the following procedures are supported:
- Inventory Procedure.
- Command Procedure, to e.g. transfer AF AIoT Data to/from AIoT Device(s) as AIoT specific NAS messages.
There are requests that are used from the AIOTF towards the Reader ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 8.3.5 Information provided by the AF | The AF provides one or some of the following information: - Information about AIoT services: - Service type indicating e.g. inventory or command (e.g. read or write). - Information to be used for AIoT reader selection: - At least one of the UE reader ID or the target area information. - Optionally, Information about th... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 1 Scope | The present document is a technical report capturing the study on application enablement architecture for mobile metaverse services over 3GPP networks. The aspects of the study include defining key issues and their related solutions to identify architecture requirements, application layer functional model (either by de... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 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.
- Fo... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 3 Definitions of terms, symbols and abbreviations | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 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].
Avatar profile: It is avatar specific configuration and parameters (e.g. allowed locations... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 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].
A-DACM Application - Digital Asset Container Management
DAPM Digi... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4 Key issues | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.1 Key issue #1: Enabler support for managing spatial anchors | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.1.1 Description | SA1 in 3GPP TS 22.156 [2] defines spatial anchors as "an association between a location in space (three dimensions) and service information that can be used to identify and access services, e.g. information to access AR media content".
Application providers can use spatial anchors to associate application content and s... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.1.2 Open issues | SA6 defined enablers as of now do not support operations required for managing spatial anchors. The open issues are:
1) How to enhance existing appliction enabler (either adding new capability in existing server or defining new capability server) to support CRUD operations for spatial anchors (association between locat... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.2 Key Issue #2: Exposure of user sensitive information | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.2.1 Description | Ensuring appropriate user consent has been obtained is a critical aspect when handling sensitive information relating to or collected from a user, their devices or the applications installed at their devices. This is highlighted at stage 1 where many of the requirements captured in 3GPP TS 22.156 [2] are subject to ope... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.2.2 Open issues | SA6 defined enablers as of now do not consider usage of user consent in the context of supporting localized mobile metaverse services. The open issues are:
- How to ensure appropriate usage of user consent at the enabler layer to support localized mobile metaverse services in 3GPP specified networks? Appropriate usage ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.3.1 Description | In addition to new 5GS performance requirements, support for Metaverse services have introduced new use cases and requirements related to optimal support for multi-user, highly performant applications. These use cases led to new CN functionality supporting richer digital representations of physical entities (e.g. user ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.3.2 Open issues | This key issue will study:
- What SA6-defined information is required to expose the SA2-defined, SA4-defined and SA3-defined avatar information to support allowed application configuration, location-based avatar contextual information?
- Whether and how application enablement layer manages and exposes information about... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.4.1 Description | In clause 5.2.1 "Localized mobile metaverse service" of 3GPP TS 22.156 [2],
Localized mobile metaverse services are immersive and integrated into a user's ordinary experiences. Such service experiences are location-related and can include presentation of AR, MR media.
Users' localization is important in order to discov... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.4.2 Open issues | SA6 defined enablers as of now do not support operations required for spatial mapping. The open issues are:
1) How to produce or modify a spatial map by the consumer (e.g. UE, VAL server)?
2) How to expose a spatial map to authorized third parties? |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.5 Key issue #5: Support for avatar discovery and QoS control | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.5.1 Description | Mobile Metaverse brings a new dimension to XR/VR services (since meta is about a persistent large-scale virtual interactive experience, where the digital assets are owned or deployed by the end users); and requires enhancements to 3GPP systems to ensure connectivity /performance and provide support.
Two relevant use ca... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.5.2 Open issues | This Key Issue aims to study:
- How to support the discovery and grouping of digital/avatar and physical UEs so as to interact via the mobile network?
- How to monitor and configure the application QoS parameters for the multimodal sessions within meta service?
NOTE 1: Coordination with FS_XRApp may be required for the... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.6 Key issue #6: Support device discovery to offload task for metaverse services | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.6.1 Description | SA1 studied use cases to support metaverse services in 3GPP TR 22.856 [3]. However, many of the devices may not be equiped with sufficient capacity to process the data. And so, they need support from other devices to process data as much near as possible.
In order to provide immersive interactive location agnostic serv... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.6.2 Open issues | In this key issue, SA6 will study following open issues:
1) Whether and how the existing SA6 defined enabler (e.g. PINAPP) is sufficient to support metaverse applications or any enhancements are required (e.g. to discover device from anothter device to offload task)? |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.7 Key issue #7: Support for metaverse services requiring multiple devices | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.7.1 Description | SA1 studied use cases to support metaverse services in 3GPP TR 22.856 [3]. In many of the use case, metaverse applications are defined at edge to provide law latency, and further, a user needs multiple devices inorder to work with metaverse services.
For example, consider a scenario where a metaverse service (e.g. a ga... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.7.2 Open issues | In this key issue, open issues are:
1) To study whether and how to enhance architecture and procedures (e.g. EDGEAPP) to support metaverse service requiring multiple devices? |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.8 Key issue #8: Enabler support for spatial anchors based services | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.8.1 Description | SA1 in 3GPP TS 22.156 [2] defines spatial anchors as "an association between a location in space (three dimensions) and service information that can be used to identify and access services, e.g. information to access AR media content".
Application providers can use spatial anchors to associate application content and s... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.8.2 Open issues | The open issues are:
1) How to combine one or more mobile metaverse services associated with spatial anchors?
2) How to provide the exposure of the spatial anchor analytics to the consumers? |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.9 Key issue #9: Support for permission control of digital assets | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.9.1 Description | Digital asset is defined in 3GPP TS 22.156 [2] as "digitally stored information that is uniquely identifiable and can be used to realize value according to their licensing conditions and applicable regulations. Examples of digital assets include digital representation (avatar), software licenses, gift certificates, tok... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 4.9.2 Open issue | This key issue is going to study:
Whether and how to manage the permission control for digital asset, including in across multiple metaverses use case.
NOTE: Operations include access, download, modification and deletion of digital assets. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.