Content for TR 23.700-22 Word version: 19.0.0
5 Key issues
6 Solutions
7 Deployment scenarios
8 Business Relationships
9 Overall evaluation
10 Conclusions
$ Change history
5 Key issues p. 12
5.1 Key issue #1: Managing resource owner consent p. 12
5.1.1 Description p. 12
5.1.2 Open issues p. 12
5.2 Key issue #2: Supporting Single Sign-On p. 12
5.2.1 Description p. 12
5.2.2 Open issues p. 13
5.3 Key issue #3: RNAA architecture enhancements p. 13
5.3.1 Description p. 13
5.3.2 Open issues p. 13
5.4 Key issue #4: CAPIF interconnection p. 13
5.4.1 Description p. 13
5.4.2 Open issues p. 14
5.5 Key issue #5: Enhancing support to API Invoker on-boarding p. 14
5.5.1 Description p. 14
5.5.2 Open issues p. 15
5.6 Key issue #6: UE-deployed API invoker accessing resources not owned by that UE p. 15
5.6.1 Description p. 15
5.6.2 Open issues p. 15
5.7 Key issue #7: CAPIF enhancement for AEF status and service API status p. 16
5.7.1 Description p. 16
5.7.2 Open issues p. 16
6 Solutions p. 16
6.1 Mapping of solutions to key issues p. 16
6.2 Solution #1: Backend For Frontend p. 17
6.2.1 Solution description p. 17
6.2.2 Architecture Impacts p. 17
6.2.3 Corresponding APIs p. 20
6.2.4 Solution evaluation p. 20
6.3 Solution #2: User consent for nested API invocation p. 21
6.3.1 Solution description p. 21
6.3.2 Architecture Impacts p. 22
6.3.3 Corresponding APIs p. 22
6.3.4 Solution evaluation p. 22
6.4 Solution #3: Finer granularity of access control for service API p. 23
6.4.1 Solution description p. 23
6.4.2 Architecture Impacts p. 26
6.4.3 Corresponding APIs p. 26
6.4.4 Solution evaluation p. 26
6.5 Solution #4: CAPIF interconnection p. 26
6.5.1 Solution description p. 26
6.5.2 Architecture Impacts p. 29
6.5.3 Corresponding APIs p. 29
6.5.4 Solution evaluation p. 29
6.6 Solution #5: Enhancing API Invoker onboarding p. 29
6.6.1 Solution description p. 29
6.6.2 Architecture Impacts p. 31
6.6.3 Corresponding APIs p. 31
6.6.4 Solution evaluation p. 31
6.7 Solution #6: API instantiation based on service discovery p. 31
6.7.1 Solution description p. 31
6.7.2 Architecture Impacts p. 32
6.7.3 Corresponding APIs p. 32
6.7.4 Solution evaluation p. 32
6.8 Solution #7: API based activation for service API discover p. 32
6.8.1 Solution description p. 32
6.8.2 Architecture Impacts p. 34
6.8.3 Corresponding APIs p. 34
6.8.4 Solution evaluation p. 34
6.9 Solution #8: AEF based instantiation for service API discover p. 35
6.9.1 Solution description p. 35
6.9.2 Architecture Impacts p. 36
6.9.3 Corresponding APIs p. 36
6.9.4 Solution evaluation p. 36
6.10 Solution #9: Support more API invoker info in RNAA p. 37
6.10.1 Solution description p. 37
6.10.2 Architecture Impacts p. 37
6.10.3 Corresponding APIs p. 37
6.10.4 Solution evaluation p. 37
6.11 Solution #10: Access Control Management of Service API p. 38
6.11.1 Solution description p. 38
6.11.2 Architecture Impacts p. 38
6.11.3 Corresponding APIs p. 38
6.11.4 Solution evaluation p. 38
6.12 Solution #11: Resource Owner Consent Revocation p. 38
6.12.1 Solution description p. 38
6.12.2 Architecture Impacts p. 39
6.12.3 Corresponding APIs p. 39
6.12.4 Solution evaluation p. 39
6.13 Solution #12: Capturing resource owner consent p. 39
6.13.1 Solution description p. 39
6.13.2 Architecture Impacts p. 41
6.13.3 Corresponding APIs p. 41
6.13.4 Solution evaluation p. 41
6.15 Solution #14: Enhancement to API invoker authorization with the Purpose of Data Processing p. 43
6.15.1 Solution description p. 43
6.15.2 Architecture Impacts p. 44
6.15.3 Corresponding APIs p. 44
6.15.4 Solution evaluation p. 45
6.16 Solution #15: Enhancing the description of authorization function capabilities p. 45
6.16.1 Solution description p. 45
6.16.2 Architecture Impacts p. 45
6.16.3 Corresponding APIs p. 45
6.16.4 Solution evaluation p. 45
6.17 Solution #16: Obtaining Resource Owner Consent p. 45
6.18 Solution #17: Enhanced CAPIF events for onboarded API invoker p. 47
6.18.1 Solution description p. 47
6.18.2 Architecture Impacts p. 47
6.18.3 Corresponding APIs p. 47
6.18.4 Solution evaluation p. 47
6.19 Solution #18: Enabling resource owner's consent in the context of group p. 48
6.19.1 Solution description p. 48
6.19.2 Architecture Impacts p. 49
6.19.3 Corresponding APIs p. 50
6.19.4 Solution evaluation p. 50
6.20 Solution #19: UE-deployed API invoker accessing resources not owned by that UE p. 50
6.20.1 Solution description p. 50
6.20.2 Architecture Impacts p. 51
6.20.3 Corresponding APIs p. 51
6.20.4 Solution evaluation p. 52
6.21 Solution #20: User consent upon nested service API invocation p. 52
6.21.1 Solution description p. 52
6.21.2 Architecture Impacts p. 54
6.21.3 Corresponding APIs p. 54
6.21.4 Solution evaluation p. 54
6.22 Solution #21: Resource Owner Authentication p. 54
6.22.1 Solution description p. 54
6.22.2 Architecture Impacts p. 55
6.22.3 Corresponding APIs p. 55
6.22.4 Solution evaluation p. 55
6.23 Solution #22: Enhancing discover service APIs for API Invoker on-boarding p. 55
6.23.1 Solution description p. 55
6.23.2 Architecture Impacts p. 57
6.23.3 Corresponding APIs p. 57
6.23.4 Solution evaluation p. 57
6.24 Solution #23: Resource Owner Authentication p. 57
6.24.1 Solution description p. 57
6.24.2 Architecture Impacts p. 58
6.24.3 Corresponding APIs p. 58
6.24.4 Solution evaluation p. 58
6.25 Solution #24: UE-deployed API invoker accessing resources not owned by that UE p. 59
6.25.1 Solution description p. 59
6.25.2 Architecture Impacts p. 60
6.25.3 Corresponding APIs p. 60
6.25.4 Solution evaluation p. 60
6.26 Solution #25: Discovery without onboarding service operation for enhanced API Invoker p. 61
6.26.1 Solution description p. 61
6.26.2 Architecture Impacts p. 63
6.26.3 Corresponding APIs p. 63
6.26.4 Solution evaluation p. 63
7 Deployment scenarios p. 63
7.1 General p. 63
7.2 Deployment model #1: Updates to RNAA deployments p. 63
7.5 RNAA deployments p. 64
8 Business Relationships p. 64
9 Overall evaluation p. 65
9.1 Evaluation of key issue#1 p. 65
9.2 Evaluation of key issue#2 p. 67
9.3 Evaluation of key issue#3 p. 67
9.4 Evaluation of key issue#4 p. 67
9.5 Evaluation of key issue#5 p. 67
9.6 Evaluation of key issue#6 p. 68
9.7 Evaluation of key issue#7 p. 68
10 Conclusions p. 69
10.1 General conclusions p. 69
10.2 Conclusions of key issue #1 p. 69
10.3 Conclusions of key issue #2 p. 70
10.4 Conclusions of key issue #3 p. 70
10.5 Conclusions of key issue #4 p. 70
10.6 Conclusions of key issue #5 p. 70
10.7 Conclusions of key issue #6 p. 70
10.8 Conclusions of key issue #7 p. 70
$ Change history p. 72
