tech-invite   World Map
3GPP     Specs     Glossaries     UICC       IETF     RFCs     Groups     SIP     ABNFs       T+       Search     Home
 


 

Here        Top        Up        Prev        None
part:    1     2     3

 

 

7   Solutions
7.1   High level architecture
7.2   Solutions to key issues   Word-p. 32
7.2.1   Solution 1: Publish service APIs
7.2.2   Solution 2: Discover service APIs   Word-p. 33
7.2.3   Solution 3: Subscription and notifications for the CAPIF events related to service APIs   Word-p. 34
7.2.4   Solution 4: CAPIF topology hiding
7.2.5   Solution 5: Onboarding API invoker to the CAPIF
7.2.6   Solution 6: Authentication between the API invoker and the CAPIF core functions   Word-p. 38
7.2.7   Solution 7: Obtaining authorization to access service API   Word-p. 39
7.2.8   Solution 8: Authentication between the API invoker and the AEF as separate procedure   Word-p. 40
7.2.9   Solution 9: Secure communication   Word-p. 41
7.2.10   Solution 10: API invoker authorization to access service APIs
7.2.11   Solution 11: Logging service API invocations
7.2.12   Solution 12: Auditing service API invocation
7.2.13   Solution 13: Charging the invocation of service APIs
7.2.14   Solution 14: Monitoring service API invocation
7.2.15   Solution 15: CAPIF access control
7.2.16   Solution 16: CAPIF access control with cascaded AEFs
7.2.17   Solution 17: Authentication between the API invoker and the AEF as part of the API invocation
8   Overall evaluation
9   Conclusions   Word-p. 51
A   API work done by other 3GPP WGs   Word-p. 53
B   OMA API Program   Word-p. 57
C   ETSI MEC API framework   Word-p. 61      Up
D   Change history   Word-p. 65

Up        Top