Tech-
invite
3GPP
space
IETF
RFCs
SIP
Quick
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 23.722
Word version: 15.1.0
1…
4…
4
Analysis of external API frameworks
5
Key issues
6
Architectural requirements
7
Solutions
8
Overall evaluation
9
Conclusions
A
API work done by other 3GPP WGs
B
OMA API Program
C
ETSI MEC API framework
$
Change History
4
Analysis of external API frameworks
Word‑p. 10
4.1
Introduction
4.2
OMA API framework
Word‑p. 11
4.2.1
Description
4.2.2
Detailed analysis
5
Key issues
Word‑p. 12
5.1
Publish and discover service API information
5.2
Topology hiding of the service
5.3
API invoker authentication to access service APIs
5.4
API invoker authorization to access service APIs
Word‑p. 13
5.5
Charging on invocation of service APIs
5.6
Lifecycle management of service APIs
5.7
Monitoring service API invocations
5.8
Logging API invoker onboarding and service API invocations
5.9
Auditing service API invocations
5.10
Onboarding API invoker to CAPIF
5.11
CAPIF authentication towards API invokers
5.12
Service API access control
Word‑p. 14
5.13
Secure API communication
5.14
Policy configuration
5.15
API protocol stack model
5.16
API security protocol
5.17
CAPIF support for service APIs from multiple providers
6
Architectural requirements
Word‑p. 15
6.1
General requirements
6.2
Service API publish and discover requirements
6.2.1
General
6.2.2
Requirements
6.3
Security requirements
6.3.1
General
6.3.2
Requirements
6.4
Charging requirements
Word‑p. 16
6.4.1
General
6.4.2
Requirements
6.5
Lifecycle management requirements
6.5.1
General
6.5.2
Requirements
6.6
Monitoring service API invocation requirements
Word‑p. 17
6.6.1
General
6.6.2
Requirements
6.7
Logging service API invocation requirements
6.7.1
General
6.7.2
Requirements
6.8
Auditing service API invocation requirements
6.8.1
General
6.8.2
Requirements
6.9
Onboarding API invoker requirements
Word‑p. 18
6.9.1
General
6.9.2
Requirements
6.10
Policy configuration requirements
6.10.1
General
6.10.2
Requirements
6.11
Protocol design requirements
6.11.1
General
6.11.2
Requirements
6.12
Logging API invoker onboarding requirements
6.12.1
General
6.12.2
Requirements
Word‑p. 19
6.13
CAPIF interaction logging requirements
6.13.1
General
6.13.2
Requirements
7
Solutions
7.1
High level architecture
7.1.1
Solution 1 - High level functional architecture for the CAPIF
7.1.1.1
Solution description
7.1.1.1.1
General
7.1.1.1.2
Architectural Model
7.1.1.1.3
Reference points
Word‑p. 21
7.1.1.1.4
Deployment options
Word‑p. 22
7.1.1.1.4.1
General
7.1.1.1.4.2
Option 1 - Centralized deployment
7.1.1.1.4.3
Option 2 - Distributed deployment
7.1.1.2
Solution evaluation
Word‑p. 25
7.1.2
Solution 2 - CAPIF architecture for service APIs from 3rd party service provider
Word‑p. 26
7.1.2.1
Solution description
7.1.2.1.1
General
7.1.2.1.2
Architectural Model
7.1.2.1.3
Reference points
Word‑p. 27
7.1.2.1.4
Deployment options
7.1.2.1.4.1
Option 1 - PLMN operator hosted service APIs and CAPIF core functions
7.1.2.1.4.2
Option 2 - 3rd party service provider hosted service APIs and CAPIF core functions
Word‑p. 28
7.1.2.1.4.3
Option 3 - PLMN operator-assisted service capability APIs and CAPIF core functions for a 3rd party service provider
7.1.2.2
Solution evaluation
Word‑p. 29
7.1.3
Solution 3 - High level functional architecture to support service APIs from 3rd party API providers via CAPIF interconnection
Word‑p. 30
7.1.3.1
Solution description
7.1.3.1.1
General
7.1.3.1.2
Architectural Model
7.1.3.1.3
Reference points
Word‑p. 31
7.1.3.2
Solution evaluation
7.2
Solutions to key issues
Word‑p. 32
7.2.1
Solution 1: Publish service APIs
7.2.1.1
Solution description
7.2.1.2
Solution evaluation
7.2.2
Solution 2: Discover service APIs
Word‑p. 33
7.2.2.1
Solution description
7.2.2.2
Solution evaluation
7.2.3
Solution 3: Subscription and notifications for the CAPIF events related to service APIs
Word‑p. 34
7.2.3.1
Solution description
7.2.3.1.1
General
7.2.3.1.2
Procedure
7.2.3.2
Solution evaluation
Word‑p. 35
7.2.4
Solution 4: CAPIF topology hiding
7.2.4.1
Solution description
7.2.4.1.1
General
7.2.4.1.2
Procedure
7.2.4.2
Solution evaluation
Word‑p. 36
7.2.5
Solution 5: Onboarding API invoker to the CAPIF
7.2.5.1
Solution description
7.2.5.1.1
General
7.2.5.1.2
Procedure
7.2.5.2
Solution evaluation
Word‑p. 37
7.2.6
Solution 6: Authentication between the API invoker and the CAPIF core functions
Word‑p. 38
7.2.6.1
Solution description
7.2.6.1.1
General
7.2.6.1.2
Procedure
7.2.6.2
Solution evaluation
7.2.7
Solution 7: Obtaining authorization to access service API
Word‑p. 39
7.2.7.1
Solution description
7.2.7.1.1
General
7.2.7.1.2
Procedure
7.2.7.2
Solution evaluation
7.2.8
Solution 8: Authentication between the API invoker and the AEF as separate procedure
Word‑p. 40
7.2.8.1
Solution description
7.2.8.1.1
General
7.2.8.1.2
Procedure
7.2.8.2
Solution evaluation
7.2.9
Solution 9: Secure communication
Word‑p. 41
7.2.9.1
Solution description
7.2.9.2
Solution evaluation
7.2.10
Solution 10: API invoker authorization to access service APIs
7.2.10.1
Solution description
7.2.10.1.1
General
7.2.10.1.2
Procedure
7.2.10.2
Solution evaluation
Word‑p. 42
7.2.11
Solution 11: Logging service API invocations
7.2.11.1
Solution description
7.2.11.1.1
General
7.2.11.1.2
Procedure
Word‑p. 43
7.2.11.2
Solution evaluation
7.2.12
Solution 12: Auditing service API invocation
7.2.12.1
Solution description
7.2.12.1.1
General
7.2.12.1.2
Procedure
Word‑p. 44
7.2.12.2
Solution evaluation
7.2.13
Solution 13: Charging the invocation of service APIs
7.2.13.1
Solution description
7.2.13.1.1
General
7.2.13.1.2
Procedure
7.2.13.2
Solution evaluation
Word‑p. 45
7.2.14
Solution 14: Monitoring service API invocation
7.2.14.1
Solution description
7.2.14.1.1
General
7.2.14.1.2
Procedure
7.2.14.2
Solution evaluation
Word‑p. 46
7.2.15
Solution 15: CAPIF access control
7.2.15.1
Solution description
7.2.15.1.1
General
7.2.15.1.2
Procedure
7.2.15.2
Solution evaluation
Word‑p. 47
7.2.16
Solution 16: CAPIF access control with cascaded AEFs
7.2.16.1
Solution description
7.2.16.1.1
General
7.2.16.1.2
Procedure
7.2.16.2
Solution evaluation
Word‑p. 48
7.2.17
Solution 17: Authentication between the API invoker and the AEF as part of the API invocation
7.2.17.1
Solution description
7.2.17.1.1
General
7.2.17.1.2
Procedure
Word‑p. 49
7.2.17.2
Solution evaluation
8
Overall evaluation
8.1
General
8.2
Architecture evaluation
Word‑p. 50
8.3
Solution evaluation
9
Conclusions
Word‑p. 51
A
API work done by other 3GPP WGs
Word‑p. 53
A.1
General
A.2
Discussion
A.2.1
SA4: API for the interface between MBMS service provider and BM-SC (xMB)
A.2.2
SA2, CT3: SCEF to expose the services and capabilities provided by 3GPP network interfaces and protocols
Word‑p. 54
A.2.3
CT3: Representational State Transfer (REST) protocol-based St reference point
A.2.4
CT3: Representational State Transfer (REST) reference point between the Application Function (AF) and the Protocol Converter (PC)
A.3
Summary
Word‑p. 55
B
OMA API Program
Word‑p. 57
B.1
General
B.2
OMA API Architecture
Word‑p. 58
B.2.1
General
B.2.2
OMA Next Generation Service Interfaces (NGSI) for Abstract APIs
B.2.2.1
OMA reference architecture of Abstract APIs
B.2.2.2
Service Registration and Discovery
B.2.2.3
Identity Control
B.2.2.4
Data Configuration and Management
Word‑p. 59
B.2.3
OMA RESTful APIs
B.2.3.1
Authorization Framework for Network APIs
B.2.3.2
RESTful Network API for Capability Discovery
B.3
API consistency within OMA APIs
C
ETSI MEC API framework
Word‑p. 61
C.1
General
C.2
MEC Application Enablement
Word‑p. 62
C.3
Design aspects of ETSI MEC APIs
Word‑p. 63
C.3.1
General
C.3.2
Entry point of a Mobile Edge service API
C.3.3
API security and privacy considerations
Word‑p. 64
C.3.4
API template
C.3.5
Patterns of the API
$
Change History
Word‑p. 65