Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.222  Word version:  19.3.0

Top   Top   Up   Prev   Next
0…   4…   5…   6…   6.3…   6.4…   7…   8…   8.5…   8.8…   8.9…   8.13…   8.17…   8.21…   8.25…   8.26…   8.28…   8.30…   9…   10…   10.4…   10.7…   11…   A   B…   B.2…   B.3…   C…   D… 
B.2 CAPIF relationship with 3GPP 5GS network exposure  B.2.1 General  B.2.2 Deployment models  B.2.2.1 General  B.2.2.2 NEF implements the CAPIF architecture  B.2.2.3 NEF implements the service specific aspect compliant with the CAPIF architecture  B.2.2.4 Distributed deployment of the NEF compliant with the CAPIF architecture 
...

 

B.2  CAPIF relationship with 3GPP 5GS network exposure  p. 122

B.2.1  General  p. 122

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 TS 23.501 and the details of NEF service operations are specified in TS 23.502.
Aspects CAPIF 5GS network exposure
Entity providing the APIs to external or 3rd partyapplicationsAEFNEF
Entity providing framework related services to the applications (discovery, authentication, authorization, etc)CAPIF core functionNEF (Not specified yet)
Entity representing the external or 3rd party applicationsAPI invokerAF
Entity providing framework related services to support the APIs operation and management (publish, policy enforcements, charging)CAPIF core functionNEF (Not specified yet)
Interface/Reference point for exposing network capabilities as APIsCAPIF-2 and CAPIF-2e (Do not include the service specific aspects)Nnef
Interface/Reference point for exposing framework services as APIs to the applicationsCAPIF-1 and CAPIF-1eNnef (Not specified yet)
Interface/Reference point for framework services to support the APIs operation and managementCAPIF-3, CAPIF-4 and CAPIF-5Internal to NEF
Up

B.2.2  Deployment models  p. 123

B.2.2.1  General  p. 123

Based on the relationship captured in Table B.2.1-1, the following deployment models for CAPIF are possible to enable 5GS network exposure.

B.2.2.2  NEF implements the CAPIF architecture  p. 123

Figure B.2.2.2-1 illustrates the deployment model where the NEF implements the CAPIF architecture.
Reproduction of 3GPP TS 23.222, Fig. B.2.2.2-1: NEF implements the CAPIF architecture
Figure B.2.2.2-1: 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 architecture  p. 124

Figure B.2.2.3-1 illustrates the deployment model where the NEF implements the service specific aspect compliant with the CAPIF architecture.
Reproduction of 3GPP TS 23.222, Fig. B.2.2.3-1: NEF implements the service specific aspect compliant with the CAPIF architecture
Figure B.2.2.3-1: 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 architecture  p. 125

Figure B.2.2.4-1 illustrates the distributed deployment model where the NEF implements the service specific aspect compliant with the CAPIF architecture.
Reproduction of 3GPP TS 23.222, Fig. B.2.2.4-1: Distributed deployment of NEF compliant with the CAPIF architecture
Figure B.2.2.4-1: Distributed deployment of NEF 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.
Up

Up   Top   ToC