Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.222  Word version:   17.0.0

Top   Up   Prev   Next
0…   4…   5   6…   6.3…   7…   8…   8.5…   8.9…   8.13…   8.17…   8.21…   8.25…   9…   10…   11…   A   B…   B.2   B.3   C…   D…

 

B.2  CAPIF relationship with 3GPP 5GS network exposureWord-p. 102
B.2.1  General
The table B.2.1-1 shows the relationship between CAPIF and 5GS network exposure aspects. The details of NEF and its role in exposing network capabilities of 5GS to 3rd party applications are specified in 3GPP TS 23.501 and the details of NEF service operations are specified in 3GPP TS 23.502.
Aspects
CAPIF
5GS network exposure

Entity providing the APIs to external or 3rd partyapplications
AEF
NEF
Entity providing framework related services to the applications (discovery, authentication, authorization, etc)
CAPIF core function
NEF (Not specified yet)
Entity representing the external or 3rd party applications
API invoker
AF
Entity providing framework related services to support the APIs operation and management (publish, policy enforcements, charging)
CAPIF core function
NEF (Not specified yet)
Interface/Reference point for exposing network capabilities as APIs
CAPIF‑2 and CAPIF‑2e (Do not include the service specific aspects)
Nnef
Interface/Reference point for exposing framework services as APIs to the applications
CAPIF‑1 and CAPIF‑1e
Nnef (Not specified yet)
Interface/Reference point for framework services to support the APIs operation and management
CAPIF‑3, CAPIF‑4 and CAPIF‑5
Internal to NEF

Up
B.2.2  Deployment modelsWord-p. 103
B.2.2.1  General
Based on the relationship captured in table B.2.1-1, the following deployment models for CAPIF are possible to enable 5GS network exposure.
NOTE:
The deployment models captured in subclause 7 are possible for the NEF deployment compliant with CAPIF. Not all deployment models are illustrated in this subclause.
B.2.2.2  NEF implements the CAPIF architecture
Figure B.2.2.2-1 illustrates the deployment model where the NEF implements the CAPIF architecture.
Up
The NEF can implement the functionalities of the CAPIF core function, the API exposing function, the API publishing function and the API management function.
According to the CAPIF architecture, CAPIF‑2 and CAPIF‑2e consist of framework aspects and service specific aspects. The service specific aspects are out of scope of CAPIF. Nnef can implement the service specific aspects of CAPIF‑2 and CAPIF‑2e, and can provide the service APIs exposed by the NEF (AEF) to the AF (API invoker).
The NEF can additionally provide CAPIF‑1 and CAPIF‑1e (CAPIF APIs) to the AF (API invokers).
Up
B.2.2.3  NEF implements the service specific aspect compliant with the CAPIF architectureWord-p. 104
Figure B.2.2.3-1 illustrates the deployment model where the NEF implements the service specific aspect compliant with the CAPIF architecture.
Up
3GPP 5GS can deploy the CAPIF core function along with the NEF.
The NEF can implement the functionalities of the API provider domain functions.
According to the CAPIF architecture, CAPIF‑2 and CAPIF‑2e consist of framework aspects and service specific aspects. The service specific aspects are out of scope of CAPIF. Nnef can implement the service specific aspects of CAPIF‑2 and CAPIF‑2e, and can provide the service APIs exposed by NEF (AEF) to the AF (API invoker).
The NEF can implement the CAPIF‑3 reference point/interface to the CAPIF core function.
Up
B.2.2.4  Distributed deployment of the NEF compliant with the CAPIF architectureWord-p. 105
Figure B.2.2.4-1 illustrates the distributed deployment model where the NEF implements the service specific aspect compliant with the CAPIF architecture.
Up
The 3GPP 5GS can deploy the CAPIF core function, the NEF-2 (API exposing function as a gateway) along with the NEF-1 as illustrated in subclause 7.3.
The NEF can implement the functionalities of API provider domain functions.
According to the CAPIF architecture, CAPIF‑2 or CAPIF‑2e consists of framework aspects and service specific aspects. The service specific aspects are out of scope of the CAPIF. Nnef can implement the service specific aspects of CAPIF‑2 and CAPIF‑2 or CAPIF‑2e can provide the service APIs exposed by the NEF-2 (AEF as a gateway) to the AF (API invoker).
The NEF-2 (AEF) can implement the CAPIF‑3 reference point to the CAPIF core function and the NEF-1 can implement the CAPIF‑4 and CAPIF‑5 reference points to the CAPIF core function.
Editor's Note: The illustration of this deployment model requires further study.
Up

Up   Top   ToC