hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2.4 Key issue #4: Spatial mapping | Solution #8 addresses the key issue 4 by enhancing SEAL LM server.
Solution #8 resolves open issue 1) and 2) by enhancing SEAL-LM client and server functionalities, and provides procedures to produce, update, get and subscribe spatial maps.
Solution #8 can be adopted in the normative work by defining new SEAL server fo... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2.1 Key issue #5: Support for avatar discovery and QoS control | Solution #9, Solution #10 and Solution #11 address the key issue 5.
Solution #9 resolves open issue 1) and supports discovering avatars using mobile metaverse enablement service.
Solution #10 provides digital asset synchronization services to mobile metaverse VAL applications. The procedure allows for QoS coordination ... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2.6 Key issue #6: Support device discovery to offload task for metaverse services | Solution #12 addresses the key issue 6.
The solution uses PINAPP architecture and provides procedure to discover other PIN elements to offload the task. |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2.7 Key issue #7: Support for metaverse services requiring multiple devices | Solution #13 addresses the key issue 7 and can be considered for normative work.
Solution #13 resolves open issue 1 of KI #7 by enhancing existing EDGEAPP architecture and procedures.
NOTE: Whether application specific mechanisms are sufficient or enable enhancements are required needs further discussion in the normati... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2.8 Key issue #8 solutions evaluation | The open issue of KI#8 includes:
1) How to combine one or more mobile metaverse services associated with spatial anchors?
2) How to provide the exposure of the spatial anchor analytics to the consumers?
For open issue#1, there are two ways in solution#1 to find a group of spatial anchors:
- Way#1: preconfiguring the hi... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 10.2.9 Key issue #9 solutions evaluation | Key issue#9 is addressed by solution #x. In the solution#x, VAL user uses VAL server to upload a digital asset to A-DACM function. DAPM is to publish digital assets and provide subscription digital assets service. DACM and DAPM work together to achieve permission distribution and meet the needs for sharing and widespre... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 11 Conclusions | |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 11.1 Architecture conclusions | The study concludes with following architectural considerations for the normative work:
1. For Key issue #1 Enabler support for managing spatial anchors, it is concluded to define new SEAL server to support spatial anchor management. The new SEAL server will consider to re-use the architecture as specified in option#1.... |
1ad30994e0ec99bee8dc5b93e80a1724 | 23.700-21 | 11.2 Conclusions of key issues | The study concludes with following solution considerations for the normative work: 1. Following individual solutions, corresponding to the key issues, will be considered as candidate solutions: i. for Key issue #1 (Enabler support for managing spatial anchors): Solution #1, Solution#2 and Solution #3 can be consider fo... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 1 Scope | The present document studies the potential enhancements to CAPIF (as specified in 3GPP TS 23.222[2]) to support: a) authentication and authorization interactions between Resource Owner and Authorization Functionality, b) UE-deployed API invoker accessing resources not owned by that UE, c) more granular access control (... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 3 Definitions of terms, symbols and abbreviations | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 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 invoker frontend: An API invoker incapable of maintaining the confidentiality of their credentia... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 3.2 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].
ASP Application Service Provider
BFF Backend For Frontend
GMS Group Managem... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 4 Gap analysis and requirements | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 4.1 CAPIF impacts due to charging considerations | The gaps and impacts on CAPIF architecture due to charging considerations are studied by SA5 in 3GPP TR 28.849 [7].
NOTE: Any impact on CAPIF architecture due to the study conclusions in SA5 can be handled during normative work. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 4.2 Requirements for RNAA | [AR-4.2-a] The CAPIF shall provide mechanisms to manage (provide, obtain, revoke) user consents for API invoker(s) to access the resources owned by resource owners.
[AR-4.2-b] The CAPIF shall provide mechanisms to enable API invoker on a UE to access resources owned by the resource owner(s) of another UE or group of UE... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 4.3 Requirements for CAPIF interconnection | [AR-4.3-a] The CAPIF shall provide mechanisms for authentication and authorization for access to the service API(s) exposed by a 3rd party CAPIF provider.
NOTE: Additional CAPIF interconnection security requirements will be coordinated with SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5 Key issues | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.1 Key issue #1: Managing resource owner consent | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.1.1 Description | With the introduction of support for Subscriber-aware Northbound API access in 3GPP Rel-18 a number of requirements were added at stage 1, one of which was motivated by the desire for a UE to be able to control whether or not to provide information considered private to a 3rd party entity. Specifically, the requirement... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.1.2 Open issues | The CAPIF does not address management of resource owner consent in the context of supporting RNAA. The open issues are:
1. How consent of the resource owner can be managed through communication between the resource owner and authorization function in the CAPIF core function
2. Whether (and how) “purpose of data process... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.2 Key issue #2: Supporting Single Sign-On | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.2.1 Description | For the Authorization code flow in RNAA, CAPIF-8 reference point (between User Agent/ROF and Authorization Server/CCF) is used to support end-user interactions with the resource owner e.g., obtaining permission from resource owner (also known as consent) and user authentication. According to 3GPP TS 23.222 clause 6.4.1... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.2.2 Open issues | 1. Whether and how to enhance CAPIF architecture and procedures considering Single sign-on (SSO)?
NOTE: The detailed security aspects related to address Single sign-on (SSO)should be provided by SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.3 Key issue #3: RNAA architecture enhancements | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.3.1 Description | Clause 6.2.3 of 3GPP TS 23.222 [2] specifies the high-level functional architecture for CAPIF supporting Resource owner-aware northbound API access (RNAA). The security procedures for CAPIF supporting RNAA are specified in 3GPP TS 33.122 [3]. As per the architecture and security procedures the role and responsibilities... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.3.2 Open issues | Open issues to study:
1. Further enhancements to CAPIF architecture considering Resource Owner Function functionalities and its interactions with CAPIF entities (e.g., CAPIF-8 related interactions).
NOTE: The security aspects for the architecture enhancements need to be coordinated with SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.4 Key issue #4: CAPIF interconnection | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.4.1 Description | Service federation between different service providers is important in application enabler to support service sharing. Two organizations with a business relationship that have each deployed CAPIF may need to interoperate to allow API invokers in each trust domain to utilize service APIs from both CAPIFs as illustrated ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.4.2 Open issues | Solutions to this key issue will address the following aspects in CAPIF interconnection:
- How to authenticate and authorize service API access for the AEF service API(s) exposed via CAPIF-6/6e;
NOTE: Coordination with SA3 is needed for security details.
- Investigate applicable events and new events (if any) for CAPIF... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.5 Key issue #5: Enhancing support to API Invoker on-boarding | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.5.1 Description | 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 sufficient API information to make decision of making an on-boarding request to CCF. However, in reality the API Provider exposes limited or only information that can be shared commonly ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.5.2 Open issues | This key issue will study the following aspects:
1. How to enhance the support of API Invoker on-boarding to reduce unnecessary on-boarding and wastage of resources?
2. Any enhancements required to other CAPIF procedures e.g. Registering the API provider domain functions, Publish Service APIs to CCF? |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.6 Key issue #6: UE-deployed API invoker accessing resources not owned by that UE | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.6.1 Description | An API invoker may be either an application on a server or an application on a UE. According to clause 7.5 in 3GPP TS 23.222 [2], the API invoker may be deployed in any of the following ways:
a. API invoker may be deployed as AF on the UE (i.e. 3rd party application).
b. API invoker may be deployed as AF on the UE supp... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.6.2 Open issues | This key issue will study:
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 for PDU sessions of another UE)
... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.7 Key issue #7: CAPIF enhancement for AEF status and service API status | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.7.1 Description | For the previous CAPIF procedure specified in 3GPP TS 23.222 [2], the status of AEF instance is assumed to be instantiated. The service API can be published through service API publish procedure by APF, and dicovered by API invoker by using the service API discovery procedure. However, the AEF instance may have multipl... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.7.2 Open issues | This key issue includes the following aspects:
- Whether and what kinds of AEF availability status and service API status should be considered for service discovery.
- Whether and how to enhance the current CAPIF mechnisms considering AFF status and service API status.
NOTE: Coordination and alignment with SA5 are requ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6 Solutions | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 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
Sol #6
X
Sol #7
X
Sol #8
X
Sol #9
X
Sol #10
X
Sol #11
X
Sol #12
X
Sol #13
X
Sol #14
X
Sol #15
X
Sol #16
X
Sol #17
X
Sol #18
X
Sol #19
X
Sol #20
X
Sol #21
X
Sol #22
X
Sol #23
X
Sol #24
X
... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.2 Solution #1: Backend For Frontend | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.2.1 Solution description | This solution relates to KI#3 on RNAA architecture enhancements. Specifically, it proposes the Backend For Frontend (BFF) pattern (as described, for example, in clause 6.1 of IETF draft-ietf-oauth-browser-based-apps-17 [5]) to be included as an architectural option.
In 3GPP TS 23.222 [2] clause 7.5, the RNAA deployment... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.2.2 Architecture Impacts | In relation to the OAuth 2.0 Authorization Framework [6] the CAPIF resource owner function is responsible for interactions with the resource owner, which is anticipated to be in a similar manner to the way in which interactions between the resource owner’s user agent are described by the OAuth framework.
With OAuth the... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.2.3 Corresponding APIs | The following API calls are described in the context of those described in the BFF IETF RFC draft, draft-ietf-oauth-browser-based-apps-17 [5].
CAPIF-X (API invoker frontend – API invoker backend)
- Initiate authorization request, from API invoker frontend to API invoker backend (step 1, clause 6.2.2)
NOTE: API invoker ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.2.4 Solution evaluation | This solution addresses KI#3 on RNAA architecture enhancements, specifically proposing the BFF patten as decribed for instance in IETF RFC draft, draft-ietf-oauth-browser-based-apps-17 [5]. That IEFT RFC draft focuses on browser-based applications, i.e., application clients run from within the browser, typically JavaSc... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.3 Solution #2: User consent for nested API invocation | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.3.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.3.1.1 General | This solution maps to KI#1 on managing resource owner consent, specifically on how consent of the resource owner can be managed through communication between the resource owner (through the resource owner function) and authorization function in the CAPIF core function. This solution proposes to extend the existing text... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.3.1.2 Enhancement to clause 8.32.3 of 3GPP TS 23.222 | With this solution the procedure to reducing authorization information inquiry in a nested API invocation in clause 8.32.3 is enhanced with the following:
New pre-condition added:
Optionally, AEF-1 is configured with policy for user consent checking before making nested API service invocation requests.
New descriptive ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.3.2 Architecture Impacts | None. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.3.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.3.4 Solution evaluation | This solution addresses KI#1 on managing resource owner consent by proposing that the AEF supports the ability use a configured policy to enforce user consent checking during service API invocation. Then when such policy is applied to the AEF, it will check that received service API invocation requests are not in breac... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.4 Solution #3: Finer granularity of access control for service API | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.4.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.4.1.0 General | This solution addresses the KI#1 and enables the finer granularity of the access control for service API, i.e.:
1. Service operation level access, the API invoker may request and the CAPIF may grant the access for the given service operation(s) of the service API.
2. Resource level access, the API invoker may request a... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.4.1.1 Impact to existing CAPIF procedures | The CAPIF procedure in 3GPP TS 23.222 [2] can be enhanced (highlighted in bold italics) as follows. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 8.3.2.1 Service API publish request | Table 8.3.2.1-1 describes the information flow service API publish request from the API publishing function to the CAPIF core function.
Table 8.3.2.1-1: Service API publish request
Information element
Status
Description
API publisher information
M
The information of the API publisher may include identity, authenticatio... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 8.7.2.1 Service API discover request | Table 8.7.2.1-1 describes the information flow service API discover request from the API invoker to the CAPIF core function.
Table 8.7.2.1-1: Service API discover request
Information element
Status
Description
API invoker identity information
M
Identity information of the API invoker discovering service APIs
Query info... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 8.11.3 Procedure | Figure 8.11.3-1 illustrates the procedure for obtaining authorization to access the service API.
Pre-condition:
1. The API invoker is onboarded and has received an API invoker identity.
Figure 8.11.3-1: Procedure for the API invoker obtaining authorization for service API access
1. The API invoker sends an obtain servi... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.4.2 Architecture Impacts | This solution is based on architecture of CAPIF as described in 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.4.3 Corresponding APIs | This solution impacts the CAPIF_Security API defined in clause 10.6 of 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.4.4 Solution evaluation | The coordination with SA3 is needed to align the information flows and procedures in 3GPP TS 33.122 [3].
This solution addresses KI#1 and enables the finer granularity of the access control for service API. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5 Solution #4: CAPIF interconnection | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.1.1 General | This solution enables authorization for service API access in CAPIF interconnection for CCFs in different CAPIF provider domains. The proposed change is also applicable for CAPIF interconnection within a CAPIF provider domain where different CCFs of the same CAPIF provider are involved.
In addition, since the API invok... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.1.3 Procedures to support CAPIF interconnection | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.1.3.1 API invoker obtaining authorization for service API access in CAPIF interconnection | Pre-condition:
1. The API invoker has discovered service APIs provided by an AEF via procedure defined in step 1 and 2 of clause 8.25.3.2 of 3GPP TS 23.222 [2].
2. The API invoker and the CCF-B are in the same trusted domain.
3. The AEF and the CCF-A are in the same trusted domain.
4. The CCF-A and the CCF-B are connec... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.1.3.2 Procedure for CAPIF revoking API invoker authorization in CAPIF interconnection | Pre-conditions:
1. The CCF-A is triggered to revoke API invoker authorization for service API access.
Figure 6.5.1.3.2-1: Procedure for revoking API invoker authorization in CAPIF interconnection
1. If the CCF-B was delegated with service API authorization, the CCF-A sends revoke API invoker authorization request to th... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.1.3.3 Procedure for obtaining access control policy in CAPIF interconnection | Pre-condition:
1. The AEF is hosting the service API but the policy to perform access control is not available with AEF.
2. The CCF-B has available access control policies corresponding to one or more service APIs.
3. The AEF and the CCF-A are in the same trusted domain.
Figure 6.5.1.3.3-1: Procedure for obtaining acce... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.1.3.4 Procedure for obtaining security information in CAPIF interconnection | Pre-condition:
1. The AEF has no security information available for authentication and/or authorization
2. The CCF-B has security information available for authentication and/or authorization corresponding to one or more service APIs.
3. The AEF and the CCF-A are in the same trusted domain.
Figure 6.5.1.3.4-1: Procedur... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.2 Architecture Impacts | Existing CAPIF architecture in 3GPP TS 23.222 [2] is used to accommodate new interactions between CCFs in this solution. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.3 Corresponding APIs | This solution impacts the CAPIF-6/6e interface with new or updated APIs. Security related API(s) will be addressed by SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.5.4 Solution evaluation | This solution addresses KI#4 regarding CAPIF interconnection including authorization, authentication and access control aspects.
NOTE: Security details will be addressed by SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.6 Solution #5: Enhancing API Invoker onboarding | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.6.1 Solution description | This solution is related to Key issue #5: Enhancing support to API Invoker onboarding, proposing to enhance the API invoker onboarding procedure specified in 3GPP TS 23.222. The enhanced procedure enables the CCF to onboard an API Invoker to CAPIF, based on meeting the criteria information from the API invoker. The API... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.6.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. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.6.3 Corresponding APIs | This solution impacts the CAPIF_API_Invoker_Management API as specified in clause 10.5 of 3GPP TS 23.222 [2] |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.6.4 Solution evaluation | This solution addresses the key issue #5 by enabling the CCF to onboard an API Invoker to CAPIF based on meeting the criteria information from the API Invoker. Initial on-boarding of API Invoker is avoided when the CCF does not meet the criteria information, if provided by API invoker. Potentially, this results in API ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.7 Solution #6: API instantiation based on service discovery | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.7.1 Solution description | Figure 6.7.1-1 illustrates the procedure for Service API discovery procedure.
Figure 6.7.1-1: Procedure to trigger service API instantiation
1-2. Same as step 1 and 2 in clause 8.7.3 of 3GPP TS 23.222 [2].
3. If the CCF determines that the service API being discovered is not instantiated, then the CCF invokes AMF to pe... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.7.2 Architecture Impacts | Existing CAPIF architecture in 3GPP TS 23.222 [2] is used to accommodate new interactions between CCF and AMF in this solution. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.7.3 Corresponding APIs | This solution impacts the CAPIF-5/5e interface with a new AMF API for triggering service instantiation. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.7.4 Solution evaluation | This solution provides a proposal to address the open issues listed in key issue#7 by enhancing the service API discover mechanism to enable service API level instantation where CAPIF's AMF will interact with the OAM system specified by SA5 for such service API level or AEF level instantiation. Coordination with SA5 is... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.8 Solution #7: API based activation for service API discover | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.8.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.8.1.1 General | This paper proposes a solution for key issue #7 on CAPIF enhancement for service API status, to introduce the API based activation in service API discover procedure.
The API can be activated during the service API discover, if the required servcie API is inactive without API interface details, and the related AEF is al... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.8.1.2 Procedure | The following text captures the solution by describing the neccesary changes in bold font compared with 3GPP TS 23.222 v18.3.0 as shown below:
* * * Enhancement based on TS 23.222 v18.3.0 * * * *
8.3.2.1 Service API publish request
Table 8.3.2.1-1 describes the information flow service API publish request from the API ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 8.7.3 Procedure | Figure 8.7.3-1 illustrates the procedure for discover service APIs.
The service API discover mechanism is supported by the CAPIF core function.
Pre-conditions:
1. The API invoker is onboarded and has received an API invoker identity.
2. The CAPIF core function is configured with a discover policy information (e.g. to r... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.8.2 Architecture Impacts | This solution is presented based on the existing CAPIF architecture in 3GPP TS 23.222. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.8.3 Corresponding APIs | This solution is based on service API publish and service API discover, no new APIs are introduced. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.8.4 Solution evaluation | This solution proposes the API-based service API activation as part of the service API discover procedure. For situations where the AEF instance is already instantiated but the required service API is not active, the CAPIF core function can request the API management function to trigger the activation of the required s... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.9 Solution #8: AEF based instantiation for service API discover | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.9.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.9.1.1 General | This paper proposes a solution for key issue #7 on CAPIF enhancement for AEF status, to introduce the API based instantiation in service API discover procedure.
For the current CAPIF specificiation, the status of AEF instance is assumed to be instantiated. However, the AEF instance may be instantiable but not yet insta... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.9.1.2 Procedure | The following text captures the solution by describing the neccesary changes in bold font compared with 3GPP TS 23.222 v18.3.0 as shown below:
* * * Enhancement based on 3GPP TS 23.222 v18.3.0 * * * *
8.7.3 Procedure
Figure 8.7.3-1 illustrates the procedure for discover service APIs.
The service API discover mechanism ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.9.2 Architecture Impacts | This solution is presented based on the existing CAPIF architecture in 3GPP TS 23.222. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.9.3 Corresponding APIs | This solution is based on service API publish and service API discover, no new APIs are introduced. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.9.4 Solution evaluation | This solution proposes the AEF based instantiation in service API discover procedure. For the AEF instance is instantiable but not be instantiated, the CAPIF core function can request the management function to make service API available. This solution solves the two open issues in key issue#7. The feasibility of this ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.