hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11 Solution #11: Provision and monitor AIoT device presence
| |
a4787e77ad46014e6b67fb22e3452dda | 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... |
a4787e77ad46014e6b67fb22e3452dda | 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... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.3 Procedure
| |
a4787e77ad46014e6b67fb22e3452dda | 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,... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.3.2 Information flows
| Editor’s Note: The details of Information flows are FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 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... |
a4787e77ad46014e6b67fb22e3452dda | 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... |
a4787e77ad46014e6b67fb22e3452dda | 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... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.4 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.5 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12 Solution #12: Support of monitoring requests for AIoT devices
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12.1 Solution description
| |
a4787e77ad46014e6b67fb22e3452dda | 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... |
a4787e77ad46014e6b67fb22e3452dda | 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... |
a4787e77ad46014e6b67fb22e3452dda | 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.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13 Solution #13: AIoT Data Processing management
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13.1 Solution description
| 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 ... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13.2 Architecture Impacts
| This solution introduces AIoT service event notification capability to the AIoT enabler server.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13.3 Corresponding APIs
| The AIoT service event notification service is introduced.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13.4 Solution evaluation
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 8 Overall evaluation
| This clause will provide evaluation of different solutions.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 9 Conclusions
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 9.1 General conclusions
| This clause will provide general conclusions for the study.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 9.2 Conclusions of key issue #x
| This clause will provide conclusions for the specific key issue.
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA6#68
Skeleton
0.0.0
2025-08
SA6#68
Implementation of the following pCRs approved by SA6:
S6-253714... |
263d42674c1a3a0559086815e5da4aa3 | 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 (... |
263d42674c1a3a0559086815e5da4aa3 | 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.
-... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 3 Definitions of terms, symbols and abbreviations
| |
263d42674c1a3a0559086815e5da4aa3 | 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... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
263d42674c1a3a0559086815e5da4aa3 | 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
ASP Application Service Provider
CSP Communi... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 4 Use Cases
| |
263d42674c1a3a0559086815e5da4aa3 | 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 ... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 4.2 Use Case #1: End-to-end basic scenario
| |
263d42674c1a3a0559086815e5da4aa3 | 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... |
263d42674c1a3a0559086815e5da4aa3 | 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 ... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 4.3 Use Case #2: Add app-user consent
| |
263d42674c1a3a0559086815e5da4aa3 | 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... |
263d42674c1a3a0559086815e5da4aa3 | 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... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 4.4 Use Case #3: Update app-user consent (includes revoke)
| |
263d42674c1a3a0559086815e5da4aa3 | 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... |
263d42674c1a3a0559086815e5da4aa3 | 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... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 4.5 Use Case #4: App-user consent handled by exposure platform
| |
263d42674c1a3a0559086815e5da4aa3 | 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.
|
263d42674c1a3a0559086815e5da4aa3 | 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... |
263d42674c1a3a0559086815e5da4aa3 | 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.
Editor's Note: The consent in UDM is s... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 5 Business Relationships
| |
263d42674c1a3a0559086815e5da4aa3 | 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:
- Feder... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 5.2 Business relationship: Federation model
| |
263d42674c1a3a0559086815e5da4aa3 | 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... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 5.3 Business relationship: Aggregator model
| |
263d42674c1a3a0559086815e5da4aa3 | 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... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 6 Terminology
| |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 6.1 Background
| |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 6.2 Related industry specifications
| |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 6.2.1 General
| Various specifications tackling the consent obtained or provided by a subscriber have used specific terminology to refer to the subscriber consent, provided to a network service provider. This clause collects the different terms used and studies the differences in meaning, with the goal to clarify what the terms refer ... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 6.3 Analysis
| There are some differences in the terminology used in GSMA PRD OPG.02 [2] captured in clause 6.2.2, CAMARA [3] captured in clause 6.2.3 and in 3GPP captured in clause 6.2.4, and the assumptions used.
While in 3GPP the user consent and RO authorization are considered forms of user authorization, in GSMA OPG and CAMARA... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 7 Key issues
| 7.1 Key issue #1: Application user consent management
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 7.1.1 Description
| This KI brings up the gap of the missing architecture for the application user consent management. Based on the use cases and business relationships studied in the present document, there are certain aspects that need to be studied to fulfil an architecture for the application user consent.
According to different regi... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 7.1.2 Open issues
| The architecture for application user consent management needs to be studied, considering aspects derived from the use cases and business relationships. These include gaps and open issues indicated in the use case analysis in clauses 4.2.2, 4.3.2 and 4.4.2.
7.2 Key issue #2: E2E clarification of the consent needed fo... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 7.2.1 Description
| This KI proposes to study the end to end flow that clarifies what user consent is needed for applications.
Based on the use case in clause 4.2 "Use Case #1: End-to-end basic scenario", for an application to be able to access the application user’s data from the API Provider (e.g. PLMN operator), a check on the applic... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 7.2.2 Open issues
| Clarifications of the end to end aspects related to what application user consent and user consent checks are needed throughout E2E flow for exposure to applications, such as:
- Whether and how to fulfil the application authorization flow with application user consent check, and how it is enforced upon service invoca... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8 Solutions
| |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.1 Mapping of solutions to key issues
| Table 6.1-1 Mapping of solutions to key issues
KI #1
KI #2
…
Sol #1
x
Sol #2
x
Sol #...
8.12 Solution #1: Standalone Application user consent management function
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.2.1 General
| This solution relates to KI #1 on the architecture of application user consent management. The open issues to be studied from this KI are described in clause 7.1.2.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.2.2 Architecture impacts
| This solution proposes a standalone application user consent function. The following aspects, indicated in the use cases analysis in clauses 4.2.2, 4.3.2 and 4.4.2 and in the business relationships, are covered in this solution for the architecture of the application user consent management function:
- The exposure of... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.2.3 Solution description
| An example of interaction between the consumer of APCOT-1 interface (an Exposure platform) and the application user consent management function is described below.
Figure 8.1.3-1: Application user consent check over APCOT-1
1. The Consumer (Exposure platform) requests the application user consent check for the spec... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.2.4 Solution evaluation
| This section provides solution evaluation based on the open issues specified in the related key issue(s).
8.3 Solution #2: End to end consent for applications
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.3.1 General
| This solution relates to KI #2. on the E2E clarifications on user consent for applications. The open issues to be studied from this KI are described in clause 7.2.2.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.3.2 Architecture impacts
| There are no additional architecture impacts for this solution.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.3.3 Solution description
| As indicated in the end-to-end use case described in clause 4.2 and in KI#2, the overall consent needs for an application request may involve two different types of checks on user consent. This solution addresses clarifications of the end-to-end aspects related to what application user consent and user consent checks a... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.3.4 Solution evaluation
| This section provides solution evaluation based on the open issues specified in the related key issue(s).
8.x Solution #x: <Solution Title>
8.x.1 General
This solution relates to KI #N.
This section describes the high-level principle of the solution.
8.x.2 Architecture requirements and impacts
This section descr... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 9 Overall evaluation
| 9.x Evaluation of key issue #x
This section evaluates all solutions related to key issue #x.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 10 Conclusions
| |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 10.1 Architectural conclusions
| This section provides conclusion and suggestion for normative work for the architecture options studied in this TR.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 10.2 Key issues conclusions
| 10.2.x Conclusions of key issue #x
This section provides conclusion and suggestion for normative work for the solutions related to key issue #x.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 11 Recommended requirements
| |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 11.1 General
| Subject to applicable regional regulations, different type of data is required to be obtained from the user as part of user’s agreement provided to a data controller (e.g., PLMN operator) to share his/her data to applications.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 11.2 Description
| [APCOT-11.2-1] The Application user consent management shall expose an interface to support the application user consent check requests.
[APCOT-11.2-2] The Application user consent management shall expose an interface to support the subscription requests for application user consent data changes and shall send the due... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 4.5.12 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... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 4.5.23 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.
Editor's Note: The consent in UDM is s... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.12.1 General
| This solution relates to KI #1 on the architecture of application user consent management. The open issues to be studied from this KI are described in clause 7.1.2.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.12.2 Architecture impacts
| This solution proposes a standalone application user consent function. The following aspects, indicated in the use cases analysis in clauses 4.2.2, 4.3.2 and 4.4.2 and in the business relationships, are covered in this solution for the architecture of the application user consent management function:
- The exposure of... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.12.3 Solution description
| An example of interaction between the consumer of APCOT-1 interface (an Exposure platform) and the application user consent management function is described below.
Figure 8.1.3-1: Application user consent check over APCOT-1
1. The Consumer (Exposure platform) requests the application user consent check for the spec... |
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.12.4 Solution evaluation
| This section provides solution evaluation based on the open issues specified in the related key issue(s).
8.23 Solution #2: End to end consent for applications
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.23.1 General
| This solution relates to KI #2. on the E2E clarifications on user consent for applications. The open issues to be studied from this KI are described in clause 7.2.2.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.23.2 Architecture impacts
| There are no additional architecture impacts for this solution.
|
263d42674c1a3a0559086815e5da4aa3 | 23.700-42 | 8.23.3 Solution description
| As indicated in the end-to-end use case described in clause 4.2 and in KI#2, the overall consent needs for an application request may involve two different types of checks on user consent. This solution addresses clarifications of the end-to-end aspects related to what application user consent and user consent checks a... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 1 Scope
| The present document studies the potential enhancements to CAPIF (as specified in 3GPP TS 23.222 [2]) to support potential requirements addressing e.g. handling of AEF unavailability, location granularity, use cases related to CAPIF administrator emerging from practical field experiences e.g. in management of API provi... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 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.
-... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 3 Definitions of terms, symbols and abbreviations
| |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 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].
Definition format (Normal)
<defined term>: <definition>.
example: text used to clarify abstract r... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 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].
Abbreviation format (EW)
<ABBREVIATION> <Expansion>
BSS Business Support... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4 Key issues
| 4.1 Key issue #1: Enhancements to API provider function to handle API invoker status change
|
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.1.1 Description
| Background: As specified in the clause 6.1 of 3GPP TS 33.122 [3], the API invoker obtains onboarding enrolment information from the API provider domain. Without onboarding enrolment information provided by the API provider domain, the API invoker would not be able to perform onboarding to CCF. The API provider domain (... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.1.2 Open issues
| The following open issues are required to study:
1) whether and how to handle the scenario where API invoker whose status has changed in the API provider domain, e.g. the API invoker has unsubscribed the services from the API provider domain or being rogue?
4.2 Key issue #2: Enhancements to API administrationprovider... |
ab60f309d592db459e2be3eea4e94a12 | 23.700-43 | 4.2.1 Description
| 3GPP SA1 has specified the service requirements for exposure in 3GPP TS 22.261 [5] including service exposure, information exposure, etc. And 3GPP SA6 has already specified many APIs in various SEAL specifications, EDGEAPP specification etc. And 3GPP SA6 has defined CAPIF as a framework to support the management of suc... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.