Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 23.722  Word version:  15.1.0

Top   Top   Up   Prev   None
1…   4…

 

4  Analysis of external API frameworksWord‑p. 10

5  Key issuesWord‑p. 12

6  Architectural requirementsWord‑p. 15

7  Solutions

7.1  High level architecture

7.2  Solutions to key issuesWord‑p. 32

7.2.1  Solution 1: Publish service APIs

7.2.2  Solution 2: Discover service APIsWord‑p. 33

7.2.3  Solution 3: Subscription and notifications for the CAPIF events related to service APIsWord‑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 functionsWord‑p. 38

7.2.7  Solution 7: Obtaining authorization to access service APIWord‑p. 39

7.2.8  Solution 8: Authentication between the API invoker and the AEF as separate procedureWord‑p. 40

7.2.9  Solution 9: Secure communicationWord‑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  ConclusionsWord‑p. 51

A  API work done by other 3GPP WGsWord‑p. 53

B  OMA API ProgramWord‑p. 57

C  ETSI MEC API frameworkWord‑p. 61

$  Change HistoryWord‑p. 65


Up   Top