Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 23.700-23
Study on Application enabler for XR Services

V19.2.0 (Wzip)  2025/03  85 p.
Rapporteur:
Ms. Zheng, Shaowen
China Mobile Com. Corporation

full Table of Contents for  TR 23.700-23  Word version:  19.2.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
0Introduction  p. 7
1Scope  p. 8
2References  p. 8
3Definitions of terms, symbols and abbreviations  p. 9
3.1Terms  p. 9
3.2Symbols  p. 9
3.3Abbreviations  p. 9
4Key issues  p. 10
4.1Key issue #1: KPI measurement and exposure  p. 10
4.2Key issue #2: E2E Multi-Modal Communication Flows  p. 10
4.3Key Issue #3: Coordination between direct UE connection and network based connection for AR/VR services  p. 11
4.4Key issue #4: Application enablement layer capabilities usage to supporting the XR services  p. 11
4.5Key issue #5: Support the tethered UE  p. 11
4.6Key issue #6: XR application server selection enhancement  p. 12
4.7Key issue #7: E2E KPI optimization for XR service  p. 13
4.8Key issue #8: PDU set handling for XR traffic  p. 13
5Application enablement architecture requirements  p. 14
5.1General requirements  p. 14
5.2Support for direct UE connection  p. 14
5.2.1Description  p. 14
5.2.2Requirements  p. 15
5.3Multi-modal flows alignment and monitoring requirements  p. 15
5.3.1Description  p. 15
5.3.2Requirements  p. 15
5.4Tethered device discovery and monitoring requirements  p. 15
5.4.1Description  p. 15
5.4.2Requirements  p. 15
6Application enablement architecture for XR services  p. 15
6.1Application enablement architecture  p. 15
6.1.1General  p. 15
6.1.2Option1: Application enablement architecture for XRAPP function  p. 15
6.1.3Option2: Application enablement architecture based on existing application enablement capabilities  p. 16
6.1.4Option3: CAPIF architecture to support the service discovery and invocation for XR application  p. 20
7Solutions  p. 21
7.0Mapping of solutions to key issues  p. 21
7.1Solution #1: SEALDD Policy Configuration for multi-modal flows  p. 21
7.1.1Architecture Impacts  p. 21
7.1.2Solution description  p. 21
7.1.3Information flows  p. 22
7.1.4Solution evaluation  p. 22
7.2Solution #2: Policy based Multi-modal SEALDD flow establishment  p. 22
7.2.1Architecture Impacts  p. 22
7.2.2Solution description  p. 22
7.2.3Solution evaluation  p. 24
7.3Solution #3: Support of Multi-Modal traffic indication in SEALDD layer  p. 24
7.3.1Architecture Impacts  p. 24
7.3.2Solution description  p. 24
7.3.3Solution evaluation  p. 28
7.4Solution #4: Support of QoS measurement for Multi-Modal traffic in SEALDD layer  p. 29
7.4.1Architecture Impacts  p. 29
7.4.2Solution description  p. 29
7.4.3Solution evaluation  p. 38
7.5Solution #5: Multi-flow synchronization for multi-modal XR application  p. 38
7.5.1Architecture Impacts  p. 38
7.5.2Solution description  p. 38
7.5.3Solution evaluation  p. 40
7.6Solution #6: Multi-modal flows alignment and monitoring  p. 40
7.6.1Architecture Impacts  p. 40
7.6.2Solution description  p. 40
7.6.3Solution evaluation  p. 43
7.7Solution #7: Support multi-modal service in SEALDD  p. 44
7.7.1Architecture Impacts  p. 44
7.7.2Solution description  p. 44
7.7.3Solution evaluation  p. 51
7.8Solution #8: EAS instantiation enhancement to satisfy E2E KPI requirements for XR application  p. 51
7.8.1Architecture Impacts  p. 51
7.8.2Solution description  p. 51
7.8.3Solution evaluation  p. 53
7.9Solution #9: Support performance analytics for tethered UEs  p. 53
7.9.1Architecture Impacts  p. 53
7.9.2Solution description  p. 53
7.9.3Solution evaluation  p. 55
7.10Solution #10: EDN selection based on predicted network connectivity  p. 55
7.10.1Architecture Impacts  p. 55
7.10.2Solution description  p. 55
7.10.3Solution evaluation  p. 56
7.11Solution #11: Support the tethered UE based on PINAPP  p. 56
7.11.1Architecture Impacts  p. 56
7.11.2Solution description  p. 59
7.11.3Solution evaluation  p. 62
7.12Solution #12: XR application server deployment enhancement  p. 62
7.12.1Architecture Impacts  p. 62
7.12.2Solution description  p. 62
7.12.3Solution evaluation  p. 65
7.13Solution #13: XR EAS selection based on N6 delay measurement  p. 65
7.13.1Architecture Impacts  p. 65
7.13.2Solution description  p. 65
7.13.3Solution evaluation  p. 66
7.14Solution #14: Support UE to UE communication in different modes via SEALDD  p. 67
7.14.1Architecture Impacts  p. 67
7.14.2Solution description  p. 67
7.14.3Information flows  p. 69
7.14.4Solution evaluation  p. 69
7.15Solution #15: Application enablement layer capabilities usage to support the user group level QoS guarantee  p. 70
7.15.1Architecture Impacts  p. 70
7.15.2Solution description  p. 70
7.15.3Solution evaluation  p. 71
7.16Solution #16: XR Application enablement client capability information procedure  p. 71
7.16.1Architecture Impacts  p. 71
7.16.2Solution description  p. 72
7.17Solution #17: Application Enablement Layer AIML Capabilities for Supporting XR Services  p. 75
7.17.2Procedure  p. 75
7.17.3Information flows  p. 77
7.17.4Solution evaluation  p. 78
8Business Relationships  p. 78
8.1General  p. 78
9Overall evaluation  p. 78
9.1General  p. 78
9.2Architecture evaluation  p. 79
9.3Solution evaluation  p. 80
9.3.1Key Issue #1 solutions evaluation  p. 80
9.3.2Key issue #2 solutions evaluation  p. 80
9.3.3Key issue #3 solutions evaluation  p. 81
9.3.4Key Issue #4 solutions evaluation  p. 81
9.3.5Key Issue #5 solutions evaluation  p. 81
9.3.6Key Issue #6 solutions evaluation  p. 82
9.3.7Key Issue #7 solutions evaluation  p. 82
9.3.8Key issue #8 solutions evaluation  p. 82
10Conclusions  p. 83
10.1General conclusions  p. 83
10.2Conclusions of key issue #1  p. 83
10.3Conclusions of key issue #2  p. 83
10.4Conclusions of key issue #3  p. 83
10.5Conclusions of key issue #4  p. 83
10.6Conclusions of key issue #5  p. 84
10.7Conclusions of key issue #6  p. 84
10.8Conclusions of key issue #7  p. 84
10.9Conclusions of key issue #8  p. 84
$Change history  p. 85

Up   Top