hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.10 Solution #9: Support more API invoker info in RNAA | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.10.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.10.1.1 General | This solution provides more API invoker info related to RNAA so that the resource owner can know better about which user and/or which service (and its provider) is asking for sensitive information (e.g. location) of the resource owner. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.10.1.3 Procedures | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.10.1.3.1 Authorization | Figure 6.10.1.3.1-1: Procedure for the API invoker obtaining authorization for service API access
The procedure is similar to clause 8.11.3 of 3GPP TS 23.222 [2] with the following difference:
- In step 1, more information about API invoker (application service info like ASP id, application id) and purpose of data proc... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.10.2 Architecture Impacts | Existing CAPIF architecture in 3GPP TS 23.222 [2] is used to accommodate new impact to CAPIF-1/1e reference point.
The CAPIF architecture shall support CAPIF-8 reference point between CCF and resource owner. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.10.3 Corresponding APIs | Existing CAPIF service API authorization API is enhanced. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.10.4 Solution evaluation | This solution addresses KI#1 with more granular information about API invoker in the context of RNAA. It also addresses the purpose of data processing in KI#1. The impacted CAPIF procedure includes service API authorization. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.11 Solution #10: Access Control Management of Service API | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.11.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.11.1.1 General | This solution is for Key issue #1 to give a description of the service API invocation procedure based on authorization for granular service access.
The API invoker performs the authorization based on granular service access (e.g., per service API or per service operation or per service resource). The subsequent service... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.11.2 Architecture Impacts | This solution is based on the existing CAPIF architecture in 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.11.3 Corresponding APIs | The security APIs specified in clause 10.6 of 3GPP TS 23.222 [2] is to be used. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.11.4 Solution evaluation | This solution addresses the Key issue#1 by emphasizing the need for authorization based on granular service access. The authorization solution itself is in the scope of SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.12 Solution #11: Resource Owner Consent Revocation | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.12.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.12.1.1 General | This solution is for Key issue #1 to manage the resource owner consent.
In current specification, the consent of resource access will only be requested by API invoker before service API invocation procedure. However, the scenario where the resource owner's consent is revoked after the API invoker obtains it has not bee... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.12.1.2 Procedure for resource owner consent revocation | Pre-condition:
1. The resource owner can communicate with the API invoker.
2. The service API access requires obtaining consent from resource owner.
3. The resource owner function has provided the user consent for the API invoker.
Figure 6.12.1.2-1: Procedure for resource owner consent revocation
1. The resource owner ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.12.2 Architecture Impacts | This solution is based on architecture of CAPIF as described in 3GPP TS 23.222 [2].
The CAPIF architecture shall support resource owner consent revocation procedure over CAPIF-8 reference point. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.12.3 Corresponding APIs | NOTE: APIs corresponding to this solution will be specified during normative phase based on SA3 outcome. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.12.4 Solution evaluation | This technical solution addresses KI#1 and is a technically feasible solution for resource owner consent revocation to be considered for consent management. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.13 Solution #12: Capturing resource owner consent | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.13.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.13.1.1 General | Even though consent can be captured through a variety of methods and techniques (e.g., ticking a box on a website or writing/accepting a letter confirming the grant for processing personal data), having the consent captured during runtime is a well-established approach for some scenarios in which the resource owner gra... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.13.1.2 Procedure for capturing resource owner consent | Figure 6.13.1.2-1 presents the procedure for capturing and storing the consent using RNAA.
Pre-condition:
1. The API invoker is onboarded as in clause 8.1 in 3GPP TS 23.222 [2] and has received an API invoker identity.
2. The notification criteria (e.g. allowed timeslot for notification) towards ROF is available at CCF... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.13.1.3 Enhancement to clauses in 3GPP TS 23.222 | Potential changes to clauses 8.8.1, 8.8.6, 10.4.1 (among others) in 3GPP TS 23.222 will be based on SA3 solution for procedures on CAPIF-8 ad further elaborated during the normative phase. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.13.2 Architecture Impacts | None. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.13.3 Corresponding APIs | NOTE: Whether new or enhanced APIs are required in support of this solution is in scope of SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.13.4 Solution evaluation | This solution addresses the following open issue in KI#1:
1. How consent of the resource owner can be managed through communication between the resource owner and authorization function in the CAPIF core function
This solution provides a feasible solution for managing user consent where the CCF can combine one or more ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.15 Solution #14: Enhancement to API invoker authorization with the Purpose of Data Processing | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.15.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.15.1.1 General | This paper is for KI #1 to manage the purpose of data processing.
According to clause Annex V.2 and V.3 in 3GPP TS 33.501, the user consent parameters shall be bound to the purpose of data processing. The AEF shall determine the purpose of data processing prior to the data processing. If the purpose of data processing ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.15.1.2 Impact to existing CAPIF procedures | The CAPIF procedure in 3GPP TS 23.222 can be enhanced (highlighted in bold italics) as follows. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 8.31.3 Procedure | Figure 8.31.3-1 illustrates the procedure for API invoker obtaining authorization from resource owner.
Pre-conditions:
1. The resource owner function can communicate with the API invoker.
2. The service API access requires obtaining authorization from resource owner.
Figure 8.31.3-1: Procedure for API invoker obtaining... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.15.2 Architecture Impacts | This solution is based on architecture of CAPIF as described in 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.15.3 Corresponding APIs | No new APIs are introduced. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.15.4 Solution evaluation | This solution addresses the open issue of purpose of data processing in KI #1, the impacted CAPIF procedure is the procedure of API invoker obtaining authorization from resource owner. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.16 Solution #15: Enhancing the description of authorization function capabilities | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.16.1 Solution description | This solution adds the relevant capabilities for storing the resource owner consent information to authorization function’s functionality description in 3GPP TS 23.222 (highlighted in bold italics) as follows. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.3.7 Authorization function | The authorization function consists of the following capabilities:
- Receiving and storing authorization from the resource owner; and
- Providing the API invoker with the authorization information which is needed to access the resource owner’s resources.
NOTE1: In the current release, the authorization function is an i... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.16.2 Architecture Impacts | This solution is based on architecture of CAPIF as described in 3GPP TS 23.222. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.16.3 Corresponding APIs | No new APIs are introduced. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.16.4 Solution evaluation | This solution addresses KI #1, by adding relevant capabilities to the authorization function’s functionality description for resource owner consent management. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.17 Solution #16: Obtaining Resource Owner Consent | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.17.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.17.1.1 General | This solution is for Key issue #1 to manage the resource owner consent.
From the description of authorization mechanism in 3GPP TS 33.122, CCF will check and store the resource owner consent information. However, there is no relevant statements about how to get the authorization from resource owner. This solution enabl... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.17.1.2 Procedure for obtaining resource owner consent | Pre-condition:
1. The service API access requires obtaining consent from resource owner.
2. The CCF has received service API authorization request from API invoker.
Figure 6.17.1.2-1: Procedure for obtaining resource owner consent
1. The CAPIF core function sends a resource owner consent request to the resource owner f... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.17.2 Architecture Impacts | This solution is based on the existing architecture of CAPIF as described in 3GPP TS 23.222 [2] and relates to the CAPIF-8 reference point. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.17.3 Corresponding APIs | This solution impacts the CAPIF-8 interface with new APIs. The APIs will be specified in normative work.
6.17.4 Solution evaluation
This solution addresses open issue 1 of KI#1 and provides a mechanism for the CCF to obtain resource owner consents which are used to authorize subsequent service API invocation. This solu... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.18 Solution #17: Enhanced CAPIF events for onboarded API invoker | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.18.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.18.1.1 General | This solution is related to key issue#5. Due to various considerations at CCF (e.g. expiry of credentials) more events can be notified to the API invoker. New CAPIF events for onboarded API invoker are introduced based on the procedures in clause 8.8 of 3GPP TS 23.222 [2].
NOTE: The considerations related to security f... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.18.1.2 CAPIF events to support onboarded API invoker | The following updates (in bold) to clause 8.8.6 of 3GPP TS 23.222 [2] are proposed for supporting new events for onboarded API invoker. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 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 invocations
... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.18.2 Architecture Impacts | It is based on existing CAPIF architecture specified in 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.18.3 Corresponding APIs | The CAPIF_Events API specified in clause 10.4 of 3GPP TS 23.222 [2] will be enhanced to accommodate the new events related to onboarded API invoker. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.18.4 Solution evaluation | This solution addresses the key issue#5 and proposes a viable technical solution for addressing new events for onboarded API invoker. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.19 Solution #18: Enabling resource owner’s consent in the context of group | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.19.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.19.1.1 General | This paper is for KI #1 to enable resource owner’s consent in the context of group.
To address the open issue enabling CAPIF resource owner’s consent in the context of group, the solution proposes to consider the group context information during provisioning of user consent on CCF. The group context information is comp... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.19.1.2 Impact to existing CAPIF procedures | The CAPIF procedure in 3GPP TS 23.222 can be enhanced (highlighted in bold italics) as follows.
8.31.3 Procedure
Figure 8.31.3-1 illustrates the procedure for API invoker obtaining authorization from resource owner.
Pre-conditions:
1. The resource owner function can communicate with the API invoker.
2. The service API ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.19.2 Architecture Impacts | This solution is based on architecture of CAPIF as described in 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.19.3 Corresponding APIs | No new APIs are introduced. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.19.4 Solution evaluation | This solution addresses the open issue of group user consent in KI #1, the impacted CAPIF procedure is the API invoker obtaining authorization from the resource owner based on the group context information. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.20 Solution #19: UE-deployed API invoker accessing resources not owned by that UE | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.20.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.20.1.1 General | As from clause 4.17.1 in 3GPP TS 23.222 [2], the scope of an API invoker on a UE in Resource owner-aware northbound API access (RNAA) is limited to accessing its own resources only, i.e., resource owner is a user of the UE hosting the API invoker that can authorize the API access. This is also acknowledged by SA3 in cl... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.20.1.2 UE-deployed API invoker accessing other UEs’ resources | Figure 6.20.1.2-1 presents the procedure for enabling a UE-hosted API invoker accessing network-hosted resources owned by other UEs.
Pre-condition:
1. The network hosts personal resources for a group of UEs which can be accessed via AEF provided the right security conditions are met.
2. UE 1 and UE 2 belong to a same g... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.20.2 Architecture Impacts | Communication between CCF and SEAL-GMS is expected to take place, so an instance of GM-S reference point shall be present. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.20.3 Corresponding APIs | NOTE: Whether new or enhanced APIs are required in support of this solution is in scope of SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.20.4 Solution evaluation | This solution addresses the following open issue in KI#6:
1. Whether (and how) RNAA can support the scenario where API invoker(s) which are deployed on the UE can access resources (hosted in the network) of other resource owners (users) (e.g., application client on UE is fetching location of another UE or setting QoS f... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.21 Solution #20: User consent upon nested service API invocation | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.21.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.21.1.1 General | This solution maps to KI#1 on managing the resource owner consent in nested API invocations scenarios. The solution addresses the scenario of obtaining authorization information with resource owner / user consent upon nested service API invocations. The solution proposed for obtaining authorization information with res... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.21.1.2 Obtain authorization with user consent upon service API invocation | This solution is an enhancement to clause 8.16, TS 23.222 [2] (Service API invocation with AEF authorization) or the solution can be new a procedure alternative to clause 8.16, TS 23.222 [2] to handle the case of obtaining authorization with resource owner consent upon service API invocation. The solution mainly propos... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.21.2 Architecture Impacts | The existing CAPIF architecture as specified in 3GPP TS 23.222 [2], is used for the interactions between API Invoker and CCF defined in this solution. No new functional entities or interfaces are proposed in this solution. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.21.3 Corresponding APIs | The solutions proposed impact the procedures and the related APIs, specified in clause 8.16 of 3GPP TS 23.222 [2]. During normative phase, if new procedures are agreed as way forward than updating the existing APIs and procedures, then correspondingly new APIs may need to be specified. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.21.4 Solution evaluation | This solution addresses the open issue #1 of key issue #1 by enabling for obtaining authorization with resource owner consent upon service API invocation, which is applicable for both nested API invocations and generically when API invoker invokes service API directly on AEF. This solution handles the scenario when an ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.22 Solution #21: Resource Owner Authentication | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.22.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.22.1.1 General | This paper provides a new solution related to the authentication of resource owner consent.
To manage resource owner consent effectively, the resource owner must first be authenticated by the CAPIF core function. Therefore, this paper proposes a resource owner authentication procedure. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.22.1.2 Procedure for resource owner authentication | Pre-condition:
1. The resource owners are subscribers which are registered at the MNO, and CCF can utilize MNO’s subscriber information.
Figure 6.22.1.2-1: Procedure for resource owner authentication
1. CAPIF core function triggers the authentication of resource owner function.
2. CAPIF core function verifies the ident... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.22.2 Architecture Impacts | This solution is based on the existing architecture of CAPIF as described in 3GPP TS 23.222 [2] and relates to the CAPIF-8 reference point. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.22.3 Corresponding APIs | NOTE: Whether new or enhanced APIs are required in support of this solution is in scope of SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.22.4 Solution evaluation | This solution addresses KI#1 on resource owner authentication to the CAPIF core function. The coordination with SA3 is needed to align the authentication information flows and procedures in 3GPP TS 33.122[3]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.23 Solution #22: Enhancing discover service APIs for API Invoker on-boarding | This solution is related to Key issue #5: Enhancing support to API Invoker on-boarding.
Currently in 3GPP TS 23.222 clause 8.1 On-boarding of API Invoker to the CAPIF procedure, there is an assumption that API Invoker has appropriate API information to make decision of making an on-boarding request to CCF. Also, there ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.23.1 Solution description | This solution is related to Key issue #5, enhancing discover service APIs for better API Invoker on-boarding experience. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.23.1.1 Enhancing Discover service APIs | The Service API discover request and Service API discover response information flows in TS 23.222 clause 8.7 Table 8.7.2.1-1 and Table 8.7.2.2-1 respectively are enhanced (bold text) as proposed below.
Table 8.7.2.1-1: Service API discover request
Information element
Status
Description
API invoker identity information ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.23.2 Architecture Impacts | This solution is based on architecture of CAPIF as described in 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.23.3 Corresponding APIs | This solution impacts the CAPIF_Discover_Service_API API as specified in clause 10.2 of 3GPP TS 23.222 [2].
NOTE: During normative phase, to enable the API invoker has visibility to APIs information (e.g., API catalogue) with appropriate information to make decision about onboarding, a new API may be introduced instead... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.23.4 Solution evaluation | This solution addresses the open issue of enhancing the support to API Invoker on-boarding in KI #5, the impacted CAPIF procedure is the procedure of discover service APIs for limiting the information to be provided to the API Invoker prior to on-boarding. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.24 Solution #23: Resource Owner Authentication | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.24.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.24.1.1 General | This solution is related to Key issue #1, open issue #5, Resource Owner authentication via CAPIF-8.
Currently, 3GPP TS 23.222 [2] clause 4.17.1, the scope of an API invoker on a UE in RNAA is limited to accessing its own resources only, i.e., the resource owner is a user of the UE hosting the API invoker that can autho... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.24.1.2 Procedure for Resource Owner Authentication | Precondition:
1. The resource owner ID is the GPSI of the corresponding UE if the resource is related to a UE.
2. The CCF is the Authorization server that holds the RO account and provides access grants for accessing RO resources,
3. The ROF interacts with the CCF (Authentication and Authorization server) using CAPIF-8... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.24.2 Architecture Impacts | This solution is based on the existing architecture of CAPIF as described in 3GPP TS 23.222 [2] and relates to the CAPIF-8 reference point. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.24.3 Corresponding APIs | Whether new or enhanced APIs are required to support this solution is in the scope of SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.24.4 Solution evaluation | This solution addresses KI#1 on resource owner authentication via CAPIF-8. Coordination with SA3 is needed to align the framework with the authentication and authorization procedures in 3GPP TS 33.122[3]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.25 Solution #24: UE-deployed API invoker accessing resources not owned by that UE | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.25.1 Solution description |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.