hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.9.1.1 General
| This solution addresses the KI#2. Just as the example described in the KI#2, a 3rd-party retail App-server (i.e., VAL server) may issue periodic or event-triggered inventory service requests to check the changed volume of some specific types of AIoT devices in a certain area. When the number of the available AIoT devic... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.9.1.2 Procedure of AIoT inventory service requests
| Figure 7.9.1.2-1 illustrates the high-level procedures of periodic and event-triggered inventory service request triggered by the VAL server(s).
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related operations and services. For the functio... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.9.2 Architecture Impacts
| This solution proposes a new architecture (i.e., new AIoT enabler) to support AIoT services.
For the new architecture, please check the Sol#1for KI#1 for more details.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.9.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.9.4 Solution evaluation
| This solution addresses the KI#2 to support the periodic and the event-triggered AIoT inventory service requests from the VAL servers.
This solution assumes there is a new application enabler (i.e. AIoT enabler) in the application enablement layer to support the AIoT services. The new AIoT enabler supports enriching ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.10 Solution #10: Support of querying history data for AIoT devices
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.10.1 Solution description
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.10.1.1 General
| This solution addresses the KI#2. Some application servers (e.g., a super market) may need to check the history data for some specific type of AIoT devices (e.g., check the sales volume of umbrellas from last year) to predict the trends for this year and beyond. So it’s necessary for application servers to query the hi... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.10.1.2 Procedure of querying history data for AIoT devices
| Figure 7.10.1.2-1 illustrates the high-level procedure of querying history data for AIoT devices.
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related operations and services.
- The AIoT enabler support to store the history data for req... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.10.2 Architecture Impacts
| This solution proposes a new architecture (i.e., new AIoT enabler) to support AIoT services.
For the new architecture, please check the Sol#1for KI#1 for more details.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.10.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.10.4 Solution evaluation
| This solution addresses the KI#2 to support the AIoT devices history information query request from the VAL server.
This solution assumes there is a new application enabler (i.e. AIoT enabler) in the application enablement layer to support the AIoT services. And the AIoT enabler supports to store the history data for ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11 Solution #11: Provision and monitor AIoT device presence
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.1 Solution Architecture
| This solution is based on an independent architecture that is newly defined in the Sol#2. In the architecture, an AIoTApp application enabler is defined and acts as a SEAL layer function entity. This function entity can be deployed and implemented by integrating with other related service enabler functions for the supp... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.2 Solution description
| For the AIoT service operation requests defined in 3GPP TS 23.369 [3], i.e., Inventory and Command, there exist certain scenarios for which the AIoT application enabler can enhance the operations.
For example, a 3rd-party application server (e.g., VAL server) may collect the AIoT device information (e.g., location inf... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.3 Procedure
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.3.1 Provision and monitor AIoT device presence
| Figure 7.11.3.1-1 illustrates the procedure for the AIoT application enabler to interact with the 5GS for the support of the Ambient IoT App service that leverages the corresponding 5GC NF services and APIs as specified in the TS 23.369 [3]. The VAL server sends the ‘location information request’ indication to AIoTApp,... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.3.2 Information flows
| NOTE: The Information flows can be further updated during the normative phase.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.3.2.1 AIoT App Service request
| Table 7.11.3.2.1-1 describes the information flow from the VAL server to the AIoTApp enabler for the support of the AIoT App service.
Table 7.11.3.2.1-1: AIoT App service request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
AIo... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.3.2.2 AIoT App service response
| Table 7.11.3.2.2-1 describes the information flow from the AIoTApp enabler to the VAL server to respond to the AIoT App service request.
Table 7.11.3.2.2-1: AIoT App service response
Information element
Status
Description
Result
M
Success or failure.
Cause
O
(see NOTE)
Indicates the reason for the failure, e... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.3.2.3 AIoT App service notification
| Table 7.11.3.2.3-1 describes the information flow from the AIoTApp enabler to the VAL server to notify the events related to the AIoT App service.
Table 7.11.3.2.3-1: AIoT App service notification
Information element
Status
Description
Event ID
O
(see NOTE)
Identifies event of the AIoTApp enabler interaction st... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.4 Corresponding APIs
| The APIs for supporting the solution can reference the following information:
- Table 7.11.3.2.1-1 on AIoT App service request
- Table 7.11.3.2.2-1 on AIoT App service response
- Table 7.11.3.2.3-1 on AIoT App service notification
Details of APIs will be further discussed in the normative phase.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.11.5 Solution evaluation
| This solution addresses the KI#3 for provisioning and monitoring AIoT device presence. It covers the following open issues:
- How to provision information about AIoT devices requiring monitoring in the application enablement layer.
- How concurrent AIoT device monitoring operations can be managed in the application ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.12 Solution #12: Support of monitoring requests for AIoT devices
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.12.1 Solution description
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.12.1.1 General
| This solution addresses the KI#2 and KI#3. Some application servers (e.g. a logistics company) may need to regularly track the location of the AIoT devices (e.g. the goods in the truck) and identify the trajectory or the direction for the AIoT devices depending on their locations, and then send warnings to the AIoT dev... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.12.1.2 Procedure of Monitoring requests for AIoT devices
| Figure 7.12.1.2-1 illustrates the high-level procedure of monitoring requests for AIoT devices.
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related operations and services.
Figure 7.12.1.2-1: Procedure of Monitoring requests for AI... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.12.2 Architecture Impacts
| This solution proposes a new architecture (i.e., new AIoT enabler) to support AIoT services.
For the new architecture, please check the Sol#1 for KI#1 for more details.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.12.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.12.4 Solution evaluation
| This solution addresses the KI#2 and KI#3 to support the monitoring the location information for the AIoT devices.
This solution assumes there is a new application enabler (i.e. AIoT enabler) in the application enablement layer to support the AIoT services. The AIoT enabler enables to obtain the location information ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.13 Solution #13: AIoT Data Processing management
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.13.1 Solution description
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.13.1.1 General
| This solution address key issue#2, and #4 to introduce a solution for AIoT data processing of the network exposured AIoT inventory/command result.
The inventory results in the notification from 3GPP network is further processed and transformed into the application layer interested service events using the provisioned ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.13.1.2 Procedures
| The figure 7.13.1.2-1 shows the high-level procedure of AIoT data processing management and event notification.
Pre-conditions:
1. The AIoT task initiate service has been invoked by the AIoT application layer consumer, and the AIoT enabler has initiated the AIoT service request to the 3GPP core network as described i... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.13.1.3 Information flows
| Table 7.13.1.3-1 describes the information flow of the AIoT service event notification service (from AIoT enable server to AIoT application layer consumer.
Table 7.13.1.3-1: AIoT service event notification
Information element
Status
Description
VAL service ID
O
Identity of the VAL service.
Interested AIoT ser... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.13.2 Architecture Impacts
| This solution introduces AIoT service event notification capability to the AIoT enabler server.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.13.3 Corresponding APIs
| The AIoT service event notification service is introduced.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.13.4 Solution evaluation
| This solution addresses key issues #2 and #4 based on the new functional model, featuring an AIoT enabler server function entity and the information provided in Sol#6.
In this solution, the enabler server processes network-exposed AIoT result data and generates application-layer events and data for each AIoT service ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.14 Solution #14: New functional model for AIoT services
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.14.1 Solution description
| This solution addresses the KI#1. The following procedures introduce the on-network functional model for AIoT services capturing the relevant functional entities and reference points. This solution aligns with the network architecture for AIoT services which specified in clause 4.2 of 3GPP TS 23.369 [3].
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.14.1.1 On-network Functional model for AIoT services
| Figure 7.14.1.1-1 illustrates the generic on-network functional model for AIoT service.
Figure 7.14.1.1-1: On-network functional model for AIoT services
The AIoTE server, acting as an AF, could obtain AIoT data information from the 3GPP core network via NEF (over N33 reference point) which is defined in clause 4.5.... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.14.1.2 Functional entities description
| AIoTE server (AIoT Enabler Server): Functionalities offered by the AIoTE server are similar to AMS entity described in clause 7.1.1.2.
AIoTE client (AIoT Enabler Client): This entity is similar to AMC entity described in clause 7.1.1.2.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.14.2 Architecture Impacts
| This solution proposes a new architecture and functional mode for AIoT services.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.14.3 Corresponding APIs
| None.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.14.4 Solution evaluation
| This solution addresses the KI#1 to provide a new architecture and functional model to support AIoT service in the application enablement layer since these services are specific AIoT vertical applications. Specifically, this solution introduces the on-network functional model, the relevant functional entities and the r... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.1 Solution description
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.1.1 Introduction
| This solution address key issue#3 to introduce a solution for AIoT information provisioning for the application enablement layer AIoT service.
An AIoT service consumer needs to provision information (application AIoT device profile) in the AIoT Enablement Server (AIOTES), before consuming AIoT services from the AIOTES... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.1.2 AIoT information provisioning
| The figure 7.15.1.2-1 describes the procedure for provisioning application AIoT device information in the AIOTES.
Figure 7.15.1.2-1: AIoT information provisioning
1. The requestor (e.g., VAL server or AIOTEC) sends an AIoT information provisioning request to the AIOTES. The request includes the requestor identifie... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.1.3 AIoT information provisioning update
| The figure 7.15.1.3-1 describes the procedure for updating application AIoT device profiles in the AIOTES.
Figure 7.15.1.3-1: AIoT information provisioning update
1. The requestor (e.g., VAL server or AIOTEC) sends an AIoT information provisioning update request to the AIOTES. The request includes the requestor ide... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.2 Architecture Impacts
| This solution proposes a functional entity, as an AIoT Enablement Server (AIOTES), is supported in the application enablement layer as described in Solution #1 and Solution #2.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.3 Corresponding APIs
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.3.1 AIoT Information Provisioning request
| Table 7.15.3.1-1 describes the AIoT information provisioning request.
Table 7.15.3.1-1: AIoT Information Provisioning request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
List of application AIoT device profiles
M
The list of application AIoT device profile to... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.3.2 AIoT Information Provisioning response
| Table 7.15.3.2-1 describes the AIoT information provisioning response.
Table 7.15.3.2-1: AIoT Information Provisioning response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> List of device identifiers
M
The list of device identifiers (ap... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.3.3 AIoT Information Provisioning Update request
| Table 7.15.3.3-1 describes the AIoT information provisioning update request.
Table 7.15.3.3-1: AIoT Information Provisioning Update request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
List of application AIoT device profiles
M
The list of application AIoT dev... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.3.4 AIoT Information Provisioning Update response
| Table 7.15.3.4-1 describes the AIoT information provisioning update response.
Table 7.15.3.4-1: AIoT Information Provisioning Update response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> List of device identifiers
M
The list of device i... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.3.5 AIoT Information Provisioning Delete request
| Table 7.15.3.5-1 describes the AIoT information provisioning delete request.
Table 7.15.3.5-1: AIoT Information Provisioning Delete request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
List of device identifiers
M
The list of device identifiers (application AI... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.3.6 AIoT Information Provisioning Delete response
| Table 7.15.3.6-1 describes the AIoT information provisioning delete response.
Table 7.15.3.6-1: AIoT Information Provisioning Delete response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> List of device identifiers
M
The list of device i... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.15.4 Solution evaluation
| This solution addresses Key Issue #3 on provisioning and managing application AIoT device profiles provided by the VAL layer. The solution allows the VAL layer to provision and manage application AIoT device profiles with the AIoT enablement service (e.g., AIOTES) to enable AIoT operations with the network.
The provis... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 8 Overall evaluation
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 8.1 General
| Various solutions proposed in the present document are introduced to support the different capabilities for AIoT services in application enablement layer. This clause provides a summary overall evaluation of the key issues and corresponding solutions.
All of the key issues and their corresponding solutions specified ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 8.2 Overall evaluation of key issue #1
| The KI#1 mainly studies the following open issue:
- Whether and how to enhance the application enablement architecture /functional model or new application enabler to support the Ambient IoT services (i.e. AIoT inventory and command services).
To address the open issues aforementioned, there are 4 solutions proposed ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 8.3 Overall evaluation of key issue #2
| The KI#2 mainly studies the following open issue:
1. How to enrich the processing (e.g. filtering, categorization, consolidation) of AIoT service requests and the collected Ambient IoT device data;
2. How to utilize the exposure from other working group (e.g. SA2) and provide the value-added AIoT devices information ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 8.4 Overall evaluation of key issue #3
| The open issues studied in the Key Issue #3 are as follows:
1. How to provision information about AIoT devices requiring monitoring in the application enablement layer.
2. How concurrent AIoT device monitoring operations can be managed in the application enablement layer considering existing CN AIoT exposure capabili... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 8.5 Overall evaluation of key issue #4
| Sol#3, Sol#5, Sol#6, Sol#7, Sol#13 address the key issue #4.
Sol#3 provides a high-level work flow description of the AIoT application layer utilizing the services provided by the AIoT enabler layer to achieve its whole service business. And one of the important operations at the enabler layer is to further process th... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 9 Conclusions
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 9.1 General conclusions
| This technical report fulfils the objectives of the study on application enablement for Ambient IoT Services.
The report includes the following contents:
1. Definition of terms and abbreviations used in the study (clause 3);
2. Architectural assumption and requirements (clause 4);
3. Key issues identified by the st... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 9.2 Conclusions of key issue #1
| Sol #1, Sol #2, Sol#3 and Sol#14 addressing the KI#1 and the following principles can be considered for the conclusion for KI#1.
- There is a new architecture and on-network functional model in the application enablement layer to support the AIoT services which includes the AIoT enablement server and AIoT enablement c... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 9.3 Conclusions of key issue #2
| 9 solutions addressing the KI#2 and the following solutions can be considered for normative work.
For Open Issue 1, the solution #5, #7, #8, #9 can be considered for normative work to support different functionalities.
For Open Issue 2, the solution #5, #8, #9, #10, #12, #13 can be considered for normative work to s... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 9.4 Conclusions of key issue #3
| The following solution considerations will be considered for the normative work for KI #3:
- Solution #3 can be considered for normative work to illustrate the high-level workflow for AIoT solutions.
- Solution #4 can be considered for normative work to support presence reporting configuration for AIoT device presenc... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 9.5 Conclusions of key issue #4
| Sol #3, Sol #5, Sol #6, Sol #7 and Sol#14 address the KI#4 and the following principles can be considered for the conclusion for KI#4:
The enabler server should process the network exposed AIoT result data and generate the application layer events/data per requirements from the ASP.
The Sol#3 is considered for normat... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 1 Scope
| The present document is a technical report which analyses and proposes solutions for the application user (app-user) consent.
The study work is performed in a phased approach. In the first phase, the study identifies and analyse the use cases, it clarifies the related terminology, analyses related industry solutions (... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 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.
-... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 3 Definitions of terms, symbols and abbreviations
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 3.1 Terms
| For the purposes of the present document, the terms given in 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 TR 21.905 [1].
Application user consent: The agreement of a user/subscriber provided to the API Provider, to allow... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 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 TR 21.905 [1].
AEF API Exposing Function
APCOT APplication user COnsenT management
AS... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4 Use Cases
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.1 General
| This clause describes relevant use cases where different aspects of app-user consent need to be considered.
It is assumed in all cases that an exposure platform provider is aware of the regulation, and therefore it has internal knowledge (via internal policies, provisioning, etc) which applications and possibly also ... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.2 Use Case #1: End-to-end basic scenario
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.2.1 Use Case Description
| Preconditions:
- The API provider (PLMN A) is the owner and manager of Alice’s subscription in the API Provider (PLMN A) domain.
- Alice is an app-user (e.g., for Netflix).
- The API provider (PLMN A) has a service agreement with the provider B of the Exposure Platform.
- Netflix application has an agreement with... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.2.2 Use Case Analysis
| As the Exposure platform and the Consent management entity belong to different domains, the interactions for the app-user consent check between the Exposure platform and the Consent management entity require an interoperable, standard interaction.
The app-user consent enabler needs to expose the capability to perform ... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.3 Use Case #2: Add app-user consent
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.3.1 Use Case Description
| Preconditions:
- The API provider (PLMN A) is the owner and manager of Alice’s subscription in the API Provider (PLMN A) domain.
- Alice is an app-user for several applications.
- The API provider (PLMN A) has a service agreement with the provider B of the Exposure Platform.
- The ASPs for the applications used b... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.3.2 Use Case Analysis
| The Consent Management entity has to have the capability to receive for each app-user, their app-user consent data per application, and additional app-user consent context data such as purpose and the user data that is allowed to be exposed to the application.
Consent Management entity has the capability to persist e... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.4 Use Case #3: Update app-user consent (includes revoke)
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.4.1 Use Case Description
| Preconditions:
- The API provider (PLMN A) is the owner and manager of Alice’s subscription in the API Provider (PLMN A) domain.
- Alice is an app-user for several applications.
- The API provider (PLMN A) has a service agreement with the provider B of the Exposure Platform.
- The ASP for the applications used by... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.4.2 Use Case Analysis
| The Consent Management enabler has to be able to receive updates of the app-user consent data at any time, whenever the app-user decides to change their current consent data for an application.
The application user consent capture is defined under the “Consent Capture” term in GSMA PRD OPG.02 [2] and is not the subje... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.5 Use Case #4: App-user consent handled by exposure platform
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.5.1 General
| This section describes use case where the applications require app-user consent and the app-user consent is handled by exposure platform.
|
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.5.2 Use Case Description
| This use case illustrates the case of app-user consent data delegated to service providers like exposure platforms. When the API provider is responsible for the user data shared via the exposed APIs, the API provider can delegate the app-user consent capture and management to trusted exposure platforms. The exposure pl... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 4.5.3 Use Case Analysis
| Study the gaps, where multiple consent information are required for exposure to applications (e.g., EDGEAPP case) and how this can be addressed with one or both of CAPIF RNAA (using RO authorization for EDGEAPP) and/or with the application user consent management, consent in UDM.
NOTE: The consent in UDM is subject fo... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 5 Business Relationships
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 5.1 General
| The business relationships between main exposure actors’ impact on the approach and solutions for handling the application user consent (app-user consent) is not determined. Typical business relationships models used by service and capabilities providers that are considered in the app-user consent analysis are:
- Fede... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 5.2 Business relationship: Federation model
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 5.2.1 Description
| The federation business model enables different service and capabilities providers to efficiently leverage exposure platforms from other service and capabilities providers (API providers), establishing an exposure ecosystem partnership.
In the federated model described in GSMA PRD OPG.02 [2], an exposure platform (suc... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 5.3 Business relationship: Aggregator model
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 5.3.1 Description
| ASPs target simplification not only at API level, but also in eliminating the need to implement variations and customizations to multiple exposure platform (e.g., Operator Platform (OP)) providers and to API providers, as well as to establishing many individual business relationships.
To simplify their business relat... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 6 Terminology
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 6.1 Background
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 6.2 Related industry specifications
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.