Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 23.700-23 Word version: 19.0.0

0… 4… 5… 6…

6.1 Application enablement architecture 7.0 Mapping of solutions to key issues 7.1 Solution #1: SEALDD Policy Configuration for multi-modal flows 7.2 Solution #2: Policy based Multi-modal SEALDD flow establishment 7.3 Solution #3: Support of Multi-Modal traffic indication in SEALDD layer 7.4 Solution #4: Support of QoS measurement for Multi-Modal traffic in SEALDD layer 7.5 Solution #5: Multi-flow synchronization for multi-modal XR application 7.6 Solution #6: Multi-modal flows alignment and monitoring 7.7 Solution #7: Support multi-modal service in SEALDD 7.8 Solution #8: EAS instantiation enhancement to satisfy E2E KPI requirements for XR application 7.9 Solution #9: Support performance analytics for tethered UEs 7.10 Solution #10: EDN selection based on predicted network connectivity 7.11 Solution #11: Support the tethered UE based on PINAPP 7.12 Solution #12: XR application server deployment enhancement 7.13 Solution #13: XR EAS selection based on N6 delay measurement 7.14 Solution #14: Support UE to UE communication in different modes via SEALDD 7.15 Solution #15: Application enablement layer capabilities usage to support the user group level QoS guarantee 7.16 Solution #16: XR Application enablement client capability information procedure 8.1 General 9.1 General 9.2 Architecture evaluation 9.3 Solution evaluation 10.1 General conclusions 10.2 Conclusions of key issue #1 10.3 Conclusions of key issue #2 10.4 Conclusions of key issue #3 10.5 Conclusions of key issue #4 10.6 Conclusions of key issue #5 10.7 Conclusions of key issue #6 10.8 Conclusions of key issue #7 10.9 Conclusions of key issue #8

6 Application enablement architecture for XR services p. 15

6.1 Application enablement architecture p. 15

6.1.1 General p. 15

6.1.2 Option1: Application enablement architecture for XRAPP function p. 15

6.1.3 Option2: Application enablement architecture based on existing application enablement capabilities p. 15

6.1.4 Option3: CAPIF architecture to support the service discovery and invocation for XR application p. 19

7 Solutions p. 20

7.0 Mapping of solutions to key issues p. 20

7.1 Solution #1: SEALDD Policy Configuration for multi-modal flows p. 20

7.1.1 Architecture Impacts p. 20

7.1.2 Solution description p. 20

7.1.3 Information flows p. 21

7.1.4 Solution evaluation p. 21

7.2 Solution #2: Policy based Multi-modal SEALDD flow establishment p. 21

7.2.1 Architecture Impacts p. 21

7.2.2 Solution description p. 21

7.2.3 Solution evaluation p. 23

7.3 Solution #3: Support of Multi-Modal traffic indication in SEALDD layer p. 23

7.3.1 Architecture Impacts p. 23

7.3.2 Solution description p. 23

7.3.3 Solution evaluation p. 27

7.4 Solution #4: Support of QoS measurement for Multi-Modal traffic in SEALDD layer p. 28

7.4.1 Architecture Impacts p. 28

7.4.2 Solution description p. 28

7.4.3 Solution evaluation p. 37

7.5 Solution #5: Multi-flow synchronization for multi-modal XR application p. 37

7.5.1 Architecture Impacts p. 37

7.5.2 Solution description p. 37

7.5.3 Solution evaluation p. 39

7.6 Solution #6: Multi-modal flows alignment and monitoring p. 39

7.6.1 Architecture Impacts p. 39

7.6.2 Solution description p. 39

7.6.3 Solution evaluation p. 42

7.7 Solution #7: Support multi-modal service in SEALDD p. 43

7.7.1 Architecture Impacts p. 43

7.7.2 Solution description p. 43

7.7.3 Solution evaluation p. 50

7.8 Solution #8: EAS instantiation enhancement to satisfy E2E KPI requirements for XR application p. 50

7.8.1 Architecture Impacts p. 50

7.8.2 Solution description p. 50

7.8.3 Solution evaluation p. 52

7.9 Solution #9: Support performance analytics for tethered UEs p. 52

7.9.1 Architecture Impacts p. 52

7.9.2 Solution description p. 52

7.9.3 Solution evaluation p. 54

7.10 Solution #10: EDN selection based on predicted network connectivity p. 54

7.10.1 Architecture Impacts p. 54

7.10.2 Solution description p. 54

7.10.3 Solution evaluation p. 55

7.11 Solution #11: Support the tethered UE based on PINAPP p. 55

7.11.1 Architecture Impacts p. 55

7.11.2 Solution description p. 58

7.11.3 Solution evaluation p. 61

7.12 Solution #12: XR application server deployment enhancement p. 61

7.12.1 Architecture Impacts p. 61

7.12.2 Solution description p. 61

7.12.3 Solution evaluation p. 64

7.13 Solution #13: XR EAS selection based on N6 delay measurement p. 64

7.13.1 Architecture Impacts p. 64

7.13.2 Solution description p. 64

7.13.3 Solution evaluation p. 65

7.14 Solution #14: Support UE to UE communication in different modes via SEALDD p. 66

7.14.1 Architecture Impacts p. 66

7.14.2 Solution description p. 66

7.14.3 Information flows p. 68

7.14.4 Solution evaluation p. 68

7.15 Solution #15: Application enablement layer capabilities usage to support the user group level QoS guarantee p. 69

7.15.1 Architecture Impacts p. 69

7.15.2 Solution description p. 69

7.15.3 Solution evaluation p. 70

7.16 Solution #16: XR Application enablement client capability information procedure p. 70

7.16.1 Architecture Impacts p. 70

7.16.2 Solution description p. 71

8 Business Relationships p. 74

8.1 General p. 74

9 Overall evaluation p. 74

9.1 General p. 74

9.2 Architecture evaluation p. 76

9.3 Solution evaluation p. 76

9.3.1 Key Issue #1 solutions evaluation p. 76

9.3.2 Key issue #2 solutions evaluation p. 76

9.3.3 Key issue #3 solutions evaluation p. 77

9.3.4 Key Issue #4 solutions evaluation p. 77

9.3.5 Key Issue #5 solutions evaluation p. 78

9.3.6 Key Issue #6 solutions evaluation p. 78

9.3.7 Key Issue #7 solutions evaluation p. 78

9.3.8 Key issue #8 solutions evaluation p. 78

10 Conclusions p. 79

10.1 General conclusions p. 79

10.2 Conclusions of key issue #1 p. 79

10.3 Conclusions of key issue #2 p. 79

10.4 Conclusions of key issue #3 p. 79

10.5 Conclusions of key issue #4 p. 80

10.6 Conclusions of key issue #5 p. 80

10.7 Conclusions of key issue #6 p. 80

10.8 Conclusions of key issue #7 p. 80

10.9 Conclusions of key issue #8 p. 80

$ Change history p. 81