hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ab31f7079a8a111d16643c592a155fe0 | 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 ... |
ab31f7079a8a111d16643c592a155fe0 | 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... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 7 Key issues
| 7.1 Key issue #1: Application user consent management
|
ab31f7079a8a111d16643c592a155fe0 | 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... |
ab31f7079a8a111d16643c592a155fe0 | 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... |
ab31f7079a8a111d16643c592a155fe0 | 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... |
ab31f7079a8a111d16643c592a155fe0 | 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... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 8 Solutions
| |
ab31f7079a8a111d16643c592a155fe0 | 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.2 Solution #1: Standalone Application user consent management function
|
ab31f7079a8a111d16643c592a155fe0 | 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.
|
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 8.2.2 Architecture impacts
| This solution proposes a standalone application user consent function. The standalone Application user consent management function covers use cases requiring handling of application user consent for exposure of user data to applications.
The following aspects, indicated in the use cases analysis in clauses 4.2.2, 4.3.... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 8.2.3 Solution description
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 8.2.3.1 Application User Consent check
| The example of interaction between the consent consumer of APCOT-1 interface (an Exposure platform) and the application user consent management function for the consent check functionality is described in figure 8.2.3.1-1 below.
Figure 8.2.3.1-1: Application user consent check over APCOT-1
1. The Consent Consumer (... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 8.2.3.2 Application User Consent Subscription and Notification
| The interaction between the Consent Consumer of APCOT-1 interface (an Exposure platform) and the application user consent management function for the subscriptions to application user consent data changes is in figure 8.2.3.2-1 below.
Figure 8.2.3.2-1: Application user consent subscription over APCOT-1
1. The Conse... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 8.2.3.3 Application User Consent Data Management
| The interaction between the consumer of APCOT-2 interface (Consent Capture solutions) and the Application user consent management function for the management operations of the application user consent data collected from the user is in figure 8.2.3.3-1 below.
Figure 8.2.3.3-1: Application user consent management ove... |
ab31f7079a8a111d16643c592a155fe0 | 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
|
ab31f7079a8a111d16643c592a155fe0 | 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.
|
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 8.3.2 Architecture impacts
| There are no additional architecture impacts for this solution.
|
ab31f7079a8a111d16643c592a155fe0 | 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... |
ab31f7079a8a111d16643c592a155fe0 | 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... |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 9 Overall evaluation
| 9.x Evaluation of key issue #x
This section evaluates all solutions related to key issue #x.
|
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 10 Conclusions
| |
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 10.1 Architectural conclusions
| This section provides conclusion and suggestion for normative work for the architecture options studied in this TR.
|
ab31f7079a8a111d16643c592a155fe0 | 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.
|
ab31f7079a8a111d16643c592a155fe0 | 23.700-42 | 11 Recommended requirements
| |
ab31f7079a8a111d16643c592a155fe0 | 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.
|
ab31f7079a8a111d16643c592a155fe0 | 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... |
2493bf882622f4ae27da4d44c4bc73b2 | 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... |
2493bf882622f4ae27da4d44c4bc73b2 | 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.
-... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 3 Definitions of terms, symbols and abbreviations
| |
2493bf882622f4ae27da4d44c4bc73b2 | 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].
API provider administrator: An authorized user with special permissions for API provider domain ope... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
2493bf882622f4ae27da4d44c4bc73b2 | 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].
BSS Business Support System
CA Certificate Authority
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4 Key issues
| 4.1 Key issue #1: Enhancements to API provider function to handle API invoker status change
|
2493bf882622f4ae27da4d44c4bc73b2 | 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 (... |
2493bf882622f4ae27da4d44c4bc73b2 | 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 administration in CAPI... |
2493bf882622f4ae27da4d44c4bc73b2 | 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... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.2.2 Multiple API provider domains service API information
| As per 3GPP TS 23.222, using Logging server API invocations procedure, the AEF logs the service API invocations information at the CCF. CCF has service API invocation logs related to AEFs from multiple API provider domains.
The service API invocation logs at CCF belongs to the respective API provider domain. In servic... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.2.3 Open issues
| To support the enhancements to API administrator role, the following aspects need to be studied:
- What are the key types of API analytics that would be useful for an API provider administrator?
- How to provide API analytics for the CAPIF entities in the API provider domain?
- whether and what are the key types of... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.3.1 Description
| As described in clause 6.1 of 3GPP TS 33.122 [3], a prerequisite to onboarding an API invoker to CAPIF, an API invoker is required to obtain onboarding enrolment information from the API provider domain (see step 1 of the referenced clause). This information is necessary to enable the API invoker to authenticate with t... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.3.2 Open issues
| This key issue will study approaches to managing entities (i.e., API Invoker or API Provider) without a valid CCF issued and signed certificate, specifically how such entities can be deleted from the CCF including associated resources to the entities like Security_Context associated to API Invokers and API resources pu... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.4.1 Description
| Currently, the CCF obtains the service API status (e.g., active, inactive) via the API management function as described in clause 6.3.6 and 6.4.8 of 3GPP TS 23.222, or via the APF publish and publish updated procedure.
However, in some scenarios the API Provider Domain is unable to provide the status of Service APIs a... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.4.2 Open issues
| - This key issue will study approaches to address scenarios in which the API Provider Domain is unable to provide the status of its AEFs with associated Service APIs and whether and how to enhance the architecture and related functions to handle the scenarios in which the connection between the CAPIF core function and ... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.5.1 Description
| One existing gap in current deployments, detected by field experiences, is how to avoid in a controlled way that a service API invocation is served when, e.g., the UE is roaming and no exposure related roaming agreements with the visiting network exists in the home network or indicates that the service should not be de... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.5.2 Open issues
| To support the control of service API invocations when the UE is roaming, the following aspects need to be studied:
- How to determine and ensure correct handling on Service API invocations, based on:
- whether roaming agreements and policies between CSPs needed for exposure; and
- whether application preferences re... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.6.1 Description
| One existing challenge is how to ensure that a service API is only invoked when the UE is within a designated service area aligned e.g. with the application preferences. Some services are only valid or cost-effective when the UE is physically inside a predefined service area or meets application-specific location prefe... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.6.2 Open issues
| To support the control of service API invocations when the UE is within or outside a designated service area, the following aspects need to be studied:
- How to determine and ensure correct handling on Service API invocations based on location of API invoker.
4.7 Key issue #7: Open Discovery Policies
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.7.1 Description
| One existing gap in current deployments, is how the CAPIF Core Function can become aware of the Service API information that can be disseminated when a requester (not identified in the CAPIF Core Function) invokes the Open Discovery service API.
To ensure a controlled handling of Open Discovery API, knowledge of the s... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 4.7.2 Open issues
| To support the control of the service API information that can be disseminated when a requester invokes the Open Discovery API the following aspects need to be studied:
- How to enhance the existing handling of Open Discovery API in CCF to support the provisioning of API Provider domain preferences about the dissemina... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 5 Architecture enhancements
| 5.x General
The architecture enhancements as required by specific solutions are captured as part of the respective solutions.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6 Solutions
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.1 Mapping of solutions to key issues
| Table 6.1-1 Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
KI #5
KI #6
KI #7
…
Sol #1
X
Sol #2
X
Sol #3
X
Sol #4
X
Sol #5
X
X
Sol #6
X
Sol #7
X
Sol #8
X
Sol #9
X
... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.2.1 General
| This solution relates to KI #1.
KI#1 identifies several use cases where the API invoker may have changed its status in the API provider domain after onboarding in the CAPIF provider domain. E.g., the API invoker decides to terminate the service agreement with the API provider, or the API Provider decides to terminate... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.2.2 Architecture Impacts
| There are no architecture impacts.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.2.3 Solution description
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.2.3.0 General
| The following changes are proposed to 3GPP TS 23.222 [2]:
- Update of Annex E to include the CAPIF administrator provisioning of per API provider domain and API Invoker service API enrollement information.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.2.3.0.1 Updates to TS 23.222 Annex E
| Annex E (normative):
Configuration data for CAPIF
The configuration data is stored in the CAPIF core function and provided by the CAPIF administrator.
The configuration data for CAPIF is specified in table E-1.
Table E-1: Configuration data for CAPIF
Reference
Parameter description
Subclause 4.2.2
List of pub... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.2.3.1 Information flows
| Not applicable.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.2.4 Solution evaluation
| Solution#1 is a feasible solution for KI#1, which is based on the CAPIF Administrator capability to update the API Invoker profile, e.g., to update the set of APIs authorized for enrollment.
The solution is based on the communication to the CAPIF Provider (e.g. CSP) of the termination of the service agreement between ... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.3.1 General
| This solution relates to KI #1.
KI#1 identifies several use cases where the API invoker may have changed its status in the API provider domain after onboarding in the CAPIF provider domain. E.g., the API invoker decides to terminate the service agreement with the API provider, or the API Provider decides to terminate... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.3.2 Architecture Impacts
| This solution proposes an enhancement to the CAPIF_Events API, with the definition of a new subscription filter for the Service API of interest event, and a new subscription indication to include the Identifier of the API Invoker that successfully enrolls the reported service API in the event report of enrolled service... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.3.3 Solution description
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.3.3.0 General
| Figure 6.x.3.0-1 illustrates the procedure for the API provider domain subscribing with the CCF to notification of API Invoker API Invoker enrolled service API event, and the notification from the CCF to API provider domain about changes in the list of service APIs the API invoker successfully enrolled for.
Figure 6... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.3.3.1 Information flows
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.8.6 List of CAPIF events
| Table 8.8.6-1 provides a non-exhaustive list of CAPIF events.
Table 8.8.6-1: List of CAPIF events
Events
Events Description
Availability of service APIs
Availability events of service APIs (e.g. active, inactive)
Service API updated
Events related to change in service API information
Monitoring service API invo... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.3.4 Solution evaluation
| Solution#2 is a feasible solution that completes KI#1 by enhancing the event "service API of interest". The Solution#2 enables that the CCF notifies about the API Invoker that is enrolling/disenrolling a Service API. To achieve so, the subscription to "Service API of interest" event is updated to indicate whether the s... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.4.1 General
| The API invoker receives onboarding enrolment information from the API provider domain, which is used by the API invoker to onboard to CCF. If the API invoker has unsubscribed to the services provided by the API provider domain, then the it is required remove enrolled APIs for the APIs provided by API provider domain.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.4.2 Architecture Impacts
| This solution does not impact existing CAPIF architecture.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.4.3 Solution description
| Figure 6.4.3.1 illustrates the procedure for offboarding API invoker from the CCF initiated by the AEF.
Pre-conditions:
1. The API invoker had received the onboarding enrolment information from the API provider domain and successfully onboarded to the CCF..
2. The API provider domain function (i.e. AMF) decides to r... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.4.3.1 Information Flows
| The Offboard API invoker request and Offboard API invoker response messages are same as specified in clause 8.2.2.1 and clause 8.2.2.2 respectively. Table 6.x.3.1-1 describes the information flow offboard API invoker notify from the CAPIF core function to the API invoker.
Table 6.4.3.1-1: Offboard API invoker notify
... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.4.4 Solution evaluation
| The solution is related to KI #1. The solution proposes to removed API invoker’s enrolled API if the API status is changed e.g. as specified in different use cases described in KI #1. Upon receiving the request from AMF, the CCF to invalidate the API invoker authorization corresponding to the service APIs. The solution... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.5.1 General
| This solution is related to key issue#4, specifically on introducing new CAPIF events to handle the scenarios in which the connection between the CAPIF core function and the API provider domain functions is disrupted due to network issues.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.5.2 Architecture Impacts
| It is based on existing CAPIF architecture specified in 3GPP TS 23.222 [2].
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.5.3 Solution description
| In the existing CAPIF framework, introducing a heartbeat mechanism similar to the EAS Availability Reporting Period would enable CCF (CAPIF core function) to detect whether the connection between the CAPIF core function and an AEF is disrupted or not.
When such connectivity problems arise, the AEF associated APIs may... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.5.3.1 Information flows
| The following updates (in bold) to clause 8.8.6 of 3GPP TS 23.222 [2] are proposed for supporting new events for AEF status change if option 1 is adopted.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.5.4 Solution evaluation
| This solution is related to key issue#4. The solution proposes CCF to send AEF unreachable/disconnected status via a new CAPIF event (i.e., option 1) or a existing CAPIF event (i.e., option 2). Compared with option 2, option 1 can bring more benefit. Therefore, sending AEF status via a new CAPIF event is recommended i... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.1 General
| This solution relates to KI #2 and KI #4. As per KI #2, CCF can collect data required for error tracking. This solution proposes API invoker to share the error reports to the CCF, Further, as per KI #4, CCF needs to know when AEF is unavailable. As stated in the key issue - the API Provider Domain is unable to provide ... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.2 Architecture Impacts
| This solution does not impact existing CAPIF architecture.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.3 Solution description
| In this solution, if CCF requires the status report from the API invoker, the CCF provides the indication about the same in the discovery response (as specified in clause 6.6.3.1.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.3.1 Enhancements to Service API discover response
| The service API discovery response is enhanced with new information element as described below:
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 8.7.2.2 Service API discover response
| Table 8.7.2.2-1 describes the information flow service API discover response from the CAPIF core function to the API invoker.
Table 8.7.2.2-1: Service API discover response
Information element
Status
Description
Result
M
Indicates the success or failure of the discovery of the service API information
Service AP... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.3.2 AEF Status reporting
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.3.2.1 General
| The procedure API invoker to report AEF status. The procedure may be invoked when service API invocation towards the AEF fails.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.3.2.2 Information flows
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.3.2.2.1 AEF status reporting request
| Table 6.6.3.2.2.1-1 describes the information flow AEF status reporting request from the API invoker to the CAPIF core function.
Table 6.6.3.2.2.1-1: AEF status reporting request
Information element
Status
Description
API invoker identity information
M
Identity information of the API invoker
Service API inform... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.3.2.2.2 AEF status reporting response
| Table 6.6.3.2.2.2-1 describes the information flow AEF status reporting response from the CAPIF core function to the API invoker.
Table 6.6.3.2.2.2-1: AEF status reporting response
Information element
Status
Description
Result
M
Indicates the availability check is in-progress and result will be notified later, s... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.3.2.3 Procedure
| Figure 6.6.3.2.3-1 illustrates the procedure for AEF status reporting.
Pre-conditions:
1. The API invoker is onboarded, discovered the service APIs and received service authorization to invoke the service APIs.
Figure 6.6.3.2.3-1: AEF Status reporting
1. The API invoker (on the UE) sends the AEF status reporting ... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.6.4 Solution evaluation
| This solution relates to KI #2 and KI #4.
As per KI #2, Error tracking is one of the analytics required by CAPIF administrator. The solution supports API invoker to share error reports to the CCF which can be used for providing the Error tracking analytics This solution proposes API invoker share the error reports wi... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.7.0 General description
| Here are some key types of API analytics that would be useful for an API provider administrator and their applications:
1. Usage Metrics
- Requests per Second (RPS): Monitor the number of API requests to identify peak usage times and ensure the system can handle the load.
- Total Requests: Track the overall number o... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.7.1 Solution description
| Figure 6.7.1-1 illustrates the procedure for support of API provider administrator in CAPIF.
Pre-conditions:
1. Authorization details of the API analytics consumer e.g. AMF are available with the CAPIF core function.
Figure 6.7.1-1: Procedure for support of API provider administrator in CAPIF
1. For querying serv... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.7.2 Architecture Impacts
| Supporting API analytics functionality is required.
The API analytics function has the following capabilities:
1. Requests per Second (RPS), Total Requests, Response Times
2. Error Rates
3. Most Used Endpoints, Usage patterns
4. Unauthorized Access Attempts, Rate Limiting Violations, Anomaly detection
5. Latency... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.7.3 Corresponding APIs
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.7.3.1 CAPIF_Service_API_Analytics API
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.7.3.1.1 General
| API description: This API enables the API analytics consumer (e.g., API management function) to communicate with the CAPIF core function to request the service API analytics over CAPIF-5/5e reference point. If the analytics functionality is not internal to CCF, then the reference point over which the API is supported w... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.7.3.1.2 Query_Service_API_Analytics operation
| API operation name: Query_Service_API_Analytics
Description: Request for Service API analytics.
Known Consumers: API management function.
Inputs: Refer clause 6.7.1, Table 6.7.1-1.
Outputs: Refer clause 6.7.1, Table 6.7.1-2.
See clause 6.7.1 for the details of usage of this API operation.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.7.4 Solution evaluation
| This solution is related to KI#2 and proposes a CAPIF procedure and API for enabling the API provider administration entity (e.g., AMF) with service API analytics. Some key types of API analytics that would be useful for an API provider administrator and their applications are usage metrics, error tracking, user patter... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.1 General
| This solution relates to KI #7.
KI#7 describes one existing gap in current deployments, about how the CAPIF Core Function can become aware of the Service API information that can be disseminated when a requester (not identified in the CAPIF Core Function) invokes the Open Discovery service API.
This solution propose... |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.2 Architecture Impacts
| This solution does not have arhictectural impacts.
|
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.3 Solution description
| |
2493bf882622f4ae27da4d44c4bc73b2 | 23.700-43 | 6.8.3.0 General
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.