Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.222  Word version:   17.0.0

Top   Up   Prev   None
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…

 

D  CAPIF relationship with external API frameworksWord-p. 110
This annex provides the relationship of CAPIF with the OMA Network APIs and the ETSI MEC API framework. The relationship of CAPIF with these external API frameworks is illustrated in the table D-1. "Yes" means that the external API framework supports the CAPIF functionality, "No" means that the API framework does not support the CAPIF functionality, and "Partial" means that it provides a mechanism that partially supports the CAPIF functionality.
CAPIF functionalities
OMA Network APIs
Supported
Reference
ETSI MEC API framework
Supported
Reference

Publish and discover service API information
Partial (see NOTE)
OMA-TS-NGSI_Registration_and_Discovery [11]
Yes
ETSI GS MEC 011 [7]
Topology hiding of the service
Yes
Individual API exposing function
Yes
Individual API exposing function
API invoker authentication to access service APIs
Partial
OMA-ER_Autho4API [9]
Partial
ETSI GS MEC 009 [8]
API invoker authorization to access service APIs
Partial
OMA-ER_Autho4API [9]
Partial
ETSI GS MEC 009 [8]
Charging on invocation of service APIs
No
No
Lifecycle management of service APIs
No
No
Monitoring service API invocations
No
No
Logging API invoker onboarding and service API invocations
No
No
Auditing service API invocations
No
No
Onboarding API invoker to CAPIF
No
No
CAPIF authentication of API invokers
No
No
Service API access control
Partial
OMA-ER_Autho4API [9]
Partial
ETSI GS MEC 009 [8]
Secure API communication
Yes
OMA-ER_Autho4API [9]
Yes
ETSI GS MEC 009 [8]
Policy configuration
No
No
API protocol stack model
Partial
for REST: OMA-TS_REST_NetAPI_Common [10]
Partial
for REST: ETSI GS MEC 009 [8]
API security protocol
Partial
OMA-ER_Autho4API [9]
Partial
ETSI GS MEC 009 [8]
CAPIF support for service APIs from multiple providers
No
No

NOTE:
OMA-TS-NGSI_Registration_and_Discovery [11] is only applicable to a specific type of web services (OWSER using UDDI and WSDL).

Up
E (Normative)  Configuration data for CAPIFWord-p. 111
The configuration data is stored in the CAPIF core function and provided by the CAPIF administrator.
The configuration data for CAPIF is specified in table E-1.
Reference
Parameter description

Subclause 4.2.2
List of published service API discovery restrictions
> Service API identification
> API invoker identity information
Subclause 4.7.2
List of service API log storage durations
> Service API identification
> Service API log storage duration (in hours) (see NOTE)
Subclause 4.7.4
List of API invoker interactions log storage durations
> Service API identification
API invoker interactions log storage duration (in hours) (see NOTE)
Subclause 4.10
List of access control policy per API invoker
> Volume limit on service API invocations (total number of invocations allowed)
> Time limit on service API invocations (The time range of the day during which the service API invocations are allowed)
> Rate limit on service API invocations (allowed service API invocations per second)
> Service API identification
> API invoker identity information

NOTE:
If no value is set for the duration, the duration is assumed to be unlimited.

Up
F  Change historyWord-p. 112

Up   Top