NONRTRIC-944 - Getting issue details... STATUS NONRTRIC - Service Exposure Manager
Service Manager builds on CAPIF and depends on the Kong API Gateway.
CAPIF stands for common API framework and it was developed by 3GPP to enable a unified Northbound API framework across 3GPP network functions, and to ensure that there is a single and harmonized approach for API development.
Among CAPIF's key features are the following.
- Onboarding/offboarding API invoker
- Discovery APIs
- Register/deregister APIs
- CAPIF events subscription/notification
- Entity authentication/authorization
- Support for 3rd party domains i.e., allow 3rd party API providers to leverage the CAPIF framework
- Support interconnection between two CAPIF providers
CAPIF implements 3GPP TS 29.222 V17.5.0 Common API Framework for 3GPP Northbound APIs.
Service Manager also implements 3GPP TS 29.222 V17.5.0 Common API Framework for 3GPP Northbound APIs. Service Manager uses CAPIF to provide the following APIs.
- Register/deregister APIs
- Publishing APIs
- Onboarding/offboarding API invoker
- Discovery APIs
If you only need the above APIs, then Service Manager is a plugin-in replacement for CAPIF.
In addition to CAPIF, Service Manager depends
When you call the Publish Service API of Service Manager, the requests body contains the IPv4 address and port of the API Publishing Function. In the response body, these values are replaced by the IP v4 Address and port of the Kong data plane. This allows us to use Kong as a reverse proxy.