Content for TR 23.700-21 Word version: 19.0.0
6 Application enablement architecture for metaverse services
7 Solutions
8 Deployment scenarios
9 Business Relationships
10 Overall evaluation
11 Conclusions
$ Change history
6 Application enablement architecture for metaverse services p. 18
6.1 Option #1: On-network mobile metaverse application layer architecture p. 18
6.1.1 Application enablement architecture p. 18
6.1.2 Functional Elements p. 19
6.1.3 Reference Points p. 19
6.2 Option #2: A-DACM architecture to support Metaverse services p. 20
6.2.1 Application enablement architecture p. 20
6.2.2 Functional Elements p. 22
6.2.2.1 A-DACM function p. 22
6.2.3 Reference Points p. 22
6.2.3.1 SEAL-S p. 22
6.2.4 Service-based interface p. 22
6.2.4.1 Sdacm p. 22
6.3 Option #3: Reuse existing SEAL architecture for metaverse services p. 22
6.4 Option #4: Architecture to support Metaverse services with permission control p. 22
6.4.1 Application enablement architecture p. 22
6.4.2 Functional Elements p. 23
6.4.2.1 DAPM function p. 23
6.4.2.2 UE DAPM function p. 23
6.4.3 Reference Points p. 23
7 Solutions p. 24
7.0 Mapping of solutions to key issues p. 24
7.1 Solution #1: Spatial anchor discovery p. 25
7.1.1 Solution description p. 25
7.1.1.1 General p. 25
7.1.1.2 Procedure p. 25
7.1.1.3 Creating spatial anchor group p. 26
7.1.1.3.1 General p. 26
7.1.1.3.2 Procedure p. 26
7.1.2 Architecture Impacts p. 27
7.1.3 Corresponding APIs p. 27
7.1.3.1 Overview p. 27
7.1.3.2 Information flows p. 27
7.1.4 Solution evaluation p. 28
7.2 Solution #2: Support for spatial anchor management p. 28
7.2.1 Solution description p. 28
7.2.2 Architecture Impacts p. 29
7.2.3 Procedures p. 29
7.2.3.1 Creating spatial anchor p. 29
7.2.3.2 Updating spatial anchor p. 30
7.2.3.3 Get spatial anchor p. 30
7.2.3.4 Spatial anchor information subscription p. 31
7.2.4 Solution evaluation p. 31
7.3 Solution #3: Spatial anchor subscription p. 32
7.3.1 Solution description p. 32
7.3.1.1 General p. 32
7.3.1.2 VAL server subscription procedure for information about UE with spatial anchor interest p. 32
7.3.1.3 VAL client subscription procedure for spatial anchors in range p. 33
7.3.2 Architecture Impacts p. 34
7.3.3 Corresponding APIs p. 34
7.3.3.1 Overview p. 34
7.3.3.2 Information flows p. 35
7.3.4 Solution evaluation p. 36
7.4 Solution #4: Support for spatial anchor analytics information p. 37
7.4.1 Solution description p. 37
7.4.2 Procedures p. 37
7.4.3 Architecture Impacts p. 38
7.4.4 Corresponding APIs p. 38
7.4.4.1 Overview p. 38
7.4.5 Solution evaluation p. 38
7.5 Solution #5: Support for digital avatars p. 38
7.5.1 Solution description p. 38
7.5.2 Architecture Impacts p. 38
7.5.3 Procedures p. 39
7.5.3.1 Create application specific avatar profile p. 39
7.5.3.2 Update application specific avatar profile p. 41
7.5.3.3 Get application specific avatar profile p. 42
7.5.3.4 Delete application specific avatar profile p. 42
7.5.3.5 Application specific avatar profile(s) subscription p. 43
7.5.4 Solution evaluation p. 43
7.7 Solution #7: Digital avatar support by A-DACM p. 46
7.7.1 Solution description p. 46
7.7.1.1 General p. 46
7.7.1.2 Avatar profile creation p. 46
7.7.1.3 Avatar profile upload p. 47
7.7.1.4 Avatar linking to user/subscriber p. 47
7.7.1.5 Avatar download p. 48
7.7.2 Architecture Impacts p. 48
7.7.3 Corresponding APIs p. 48
7.7.4 Solution evaluation p. 49
7.8 Solution #8: Support for spatial map management p. 49
7.8.1 Solution description p. 49
7.8.2 Architecture Impacts p. 49
7.8.3 Procedures p. 49
7.8.3.1 Producing spatial map p. 49
7.8.3.2 Update spatial map p. 50
7.8.3.3 Get spatial map p. 51
7.8.3.4 Subscribe/unsubscribe spatial map p. 51
7.8.3.5 Spatial localization services p. 52
7.8.3.6 Delete spatial map p. 53
7.8.4 Corresponding APIs p. 54
7.8.4.1 Produce spatial map p. 54
7.8.4.2 Update spatial map p. 54
7.8.4.3 Get spatial map p. 55
7.8.4.4 Subscribe/unsubscribe spatial map p. 55
7.8.4.5 Delete spatial map p. 57
7.8.5 Solution evaluation p. 58
7.9 Solution #9: Avatar discovery procedure p. 58
7.9.1 Solution description p. 58
7.9.2 Architecture Impacts p. 59
7.9.3 Corresponding APIs p. 59
7.9.4 Solution evaluation p. 60
7.10 Solution #10: Metaverse digital asset synchronization QoS control p. 60
7.10.1 Solution description p. 60
7.10.2 Architecture Impacts p. 62
7.10.3 Corresponding APIs p. 62
7.10.4 Solution evaluation p. 62
7.11 Solution #11: Application QoS coordination for Mobile Metaverse Sessions p. 62
7.11.1 Solution description p. 62
7.11.2 Architecture Impacts p. 65
7.11.3 Corresponding APIs p. 65
7.11.4 Solution evaluation p. 65
7.12 Solution #12: Support device discovery to offload task for metaverse services p. 65
7.12.1 Solution description p. 65
7.12.2 Architecture Impacts p. 66
7.12.3 Corresponding APIs p. 66
7.12.4 Solution evaluation p. 67
7.13 Solution #13: Support for metaverse services requiring multiple devices p. 67
7.13.1 Solution description p. 67
7.13.1.1 Enhancement to EAS profile p. 67
7.13.1.2 Enhancement to EAS discovery request (between AC to EEC) p. 68
7.13.1.3 Enhancement to EAS discovery procedure (between EEC to EES) p. 68
7.13.2 Architecture Impacts p. 68
7.13.3 Corresponding APIs p. 68
7.13.4 Solution evaluation p. 69
7.15 Solution #15: Support for VAL UEs in spatial map p. 70
7.15.1 Solution description p. 70
7.15.2 Architecture Impacts p. 71
7.15.3 Procedures p. 71
7.15.3.1 Create spatial map augmented with VAL UE p. 71
7.15.3.2 Update spatial map augmented with VAL UEs p. 72
7.15.4 Corresponding APIs p. 73
7.15.4.1 Overview p. 73
7.15.4.2 Information Flows p. 73
7.15.5 Solution evaluation p. 74
7.16 Solution #16: Spatial mapping service exposure and discovery p. 74
7.16.1 Solution description p. 74
7.16.1.1 General p. 74
7.16.1.2 Exposing a spatial mapping service p. 75
7.16.1.3 Discovering a spatial mapping service p. 75
7.16.1.4 Service exposure via CAPIF p. 76
7.16.2 Architecture Impacts p. 77
7.16.3 Corresponding APIs p. 77
7.16.3.1 Overview p. 77
7.16.3.2 Information flows p. 77
7.16.4 Solution evaluation p. 78
7.17 Solution #17: Discovery of UEs consenting and capable of providing spatial mapping information p. 78
7.17.1 Solution description p. 78
7.17.1.1 General p. 78
7.17.1.2 Registering a spatial mapping information provider p. 79
7.17.1.3 Discovering and triggering a spatial mapping information provider p. 79
7.17.2 Architecture Impacts p. 80
7.17.3 Corresponding APIs p. 81
7.17.3.1 Overview p. 81
7.17.3.2 Information flows p. 81
7.17.4 Solution evaluation p. 82
7.18 Solution #18: Discovery and requirements translation for 5G-enabled Traffic Flow Simulation and Situational Awareness p. 83
7.18.1 Solution description p. 83
7.18.2 Architecture Impacts p. 85
7.18.3 Corresponding APIs p. 85
7.18.4 Solution evaluation p. 85
8 Deployment scenarios p. 85
8.1 General p. 85
8.2 Deployment model #1: Deployment of enabler for Metaverse Services as SEAL server(s) p. 86
9 Business Relationships p. 86
10 Overall evaluation p. 86
10.1 Architecture evaluations p. 86
10.1.1 On-network mobile metaverse application layer architecture p. 86
10.1.2 SEAL architecture to support metaverse applications p. 86
10.2 Key issue evaluations p. 87
10.2.1 Key issue #1: Enabler support for managing spatial anchors p. 87
10.2.2 Key issue #2: Exposure of user sensitive information p. 87
10.2.3 Key issue #3: Avatar and digital asset support p. 87
10.2.4 Key issue #4: Spatial mapping p. 87
10.2.5 Key issue #5: Support for avatar discovery and QoS control p. 88
10.2.6 Key issue #6: Support device discovery to offload task for metaverse services p. 88
10.2.7 Key issue #7: Support for metaverse services requiring multiple devices p. 89
10.2.8 Key issue #8 solutions evaluation p. 89
11 Conclusions p. 89
$ Change history p. 91
