Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 23.722  Word version:  15.1.0

Top   Top   Up   Prev   None
0…   4…

 

4  Analysis of external API frameworksp. 10

5  Key issuesp. 12

6  Architectural requirementsp. 15

7  Solutionsp. 19

7.1  High level architecturep. 19

7.2  Solutions to key issuesp. 32

7.2.1  Solution 1: Publish service APIsp. 32

7.2.2  Solution 2: Discover service APIsp. 33

7.2.3  Solution 3: Subscription and notifications for the CAPIF events related to service APIsp. 34

7.2.4  Solution 4: CAPIF topology hidingp. 35

7.2.5  Solution 5: Onboarding API invoker to the CAPIFp. 36

7.2.6  Solution 6: Authentication between the API invoker and the CAPIF core functionsp. 38

7.2.7  Solution 7: Obtaining authorization to access service APIp. 39

7.2.8  Solution 8: Authentication between the API invoker and the AEF as separate procedurep. 40

7.2.9  Solution 9: Secure communicationp. 41

7.2.10  Solution 10: API invoker authorization to access service APIsp. 41

7.2.11  Solution 11: Logging service API invocationsp. 42

7.2.12  Solution 12: Auditing service API invocationp. 43

7.2.13  Solution 13: Charging the invocation of service APIsp. 44

7.2.14  Solution 14: Monitoring service API invocationp. 45

7.2.15  Solution 15: CAPIF access controlp. 46

7.2.16  Solution 16: CAPIF access control with cascaded AEFsp. 47

7.2.17  Solution 17: Authentication between the API invoker and the AEF as part of the API invocationp. 48

8  Overall evaluationp. 49

9  Conclusionsp. 51

A  API work done by other 3GPP WGsp. 53

B  OMA API Programp. 57

C  ETSI MEC API frameworkp. 61

$  Change Historyp. 65


Up   Top