Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 38.838
Word version: 17.0.0
1…
5…
7…
8…
9…
A…
A
Evaluation methodology
A.1
Evaluation methodology for capacity
A.2
Evaluation methodology for power
A.3
Evaluation methodology for coverage
A.4
Evaluation methodology for mobility
B
Source specific capacity performance evaluation results
B.1
FR1 DL
B.2
FR1 UL
B.3
FR2 DL
B.4
FR2 UL
C
Source specific mobility evaluation results
C.1
Consecutive XR packets lost due to a HO event, N
C.2
Minimum target time interval between HO events, T
$
Change history
A
Evaluation methodology
p. 194
A.1
Evaluation methodology for capacity
p. 194
A.2
Evaluation methodology for power
p. 197
A.3
Evaluation methodology for coverage
p. 199
A.4
Evaluation methodology for mobility
p. 200
B
Source specific capacity performance evaluation results
p. 202
B.1
FR1 DL
p. 202
B.1.1
DU scenario
p. 202
B.1.1.1
VR/AR
p. 202
B.1.1.1.1
Single stream traffic model
p. 202
B.1.1.1.2
Multi-stream traffic model
p. 208
B.1.1.2
CG
p. 213
B.1.2
InH scenario
p. 215
B.1.2.1
VR/AR
p. 215
B.1.2.1.1
Single stream traffic model
p. 215
B.1.2.1.2
Multi-stream traffic model
p. 218
B.1.2.2
CG
p. 219
B.1.3
Uma scenario
p. 220
B.1.3.1
VR/AR
p. 220
B.1.3.1.1
Single stream traffic model
p. 220
B.1.3.1.2
Multi-stream traffic model
p. 222
B.1.3.2
CG
p. 223
B.2
FR1 UL
p. 224
B.2.1
DU scenario
p. 224
B.2.1.1
VR/CG (Pose/control-stream)
p. 224
B.2.1.2
AR (1 stream: Scene/video/data/voice-stream)
p. 225
B.2.1.3
AR (2 streams: Pose/control-stream + scene/video/data/voice-stream)
p. 226
B.2.1.4
AR (3 streams: Video stream+Data/audio stream+Pose/control stream)
p. 227
B.2.1.5
AR (3 streams: Pose/control-stream + I/P-stream)
p. 227
B.2.2
InH scenario
p. 228
B.2.2.1
VR/CG (Pose/control-stream)
p. 228
B.2.2.2
AR (1 stream: Scene/video/data/voice-stream)
p. 228
B.2.2.3
AR (2 streams: Pose/control-stream + scene/video/data/voice-stream)
p. 229
B.2.2.4
AR (3 streams: Video stream+Data/audio stream+Pose/control stream)
p. 230
B.2.3
Uma scenario
p. 230
B.2.3.1
VR/CG (Pose/control-stream)
p. 230
B.2.3.2
AR (1 stream: Scene/video/data/voice-stream)
p. 231
B.2.3.3
AR (2 streams: Pose/control-stream + scene/video/data/voice-stream)
p. 231
B.3
FR2 DL
p. 232
B.3.1
DU scenario
p. 232
B.3.1.1
VR/AR
p. 232
B.3.1.1.1
Single stream traffic model
p. 232
B.3.1.1.2
Multi-stream traffic model
p. 234
B.3.1.2
CG
p. 235
B.3.2
InH scenario
p. 235
B.3.2.1
VR/AR
p. 235
B.3.2.1.1
Single stream traffic model
p. 235
B.3.2.1.2
Multi-stream traffic model
p. 237
B.3.2.2
CG
p. 239
B.4
FR2 UL
p. 240
B.4.1
DU scenario
p. 240
B.4.1.1
VR/CG (pose/control-stream)
p. 240
B.4.1.2
AR (1 stream: scene/video/data/voice-stream)
p. 241
B.4.1.3
AR (2 streams: pose/control-stream + scene/video/data/voice-stream)
p. 241
B.4.2
InH scenario
p. 242
B.4.2.1
VR/CG (Pose/control-stream)
p. 242
B.4.2.2
AR (1 stream: Scene/video/data/voice-stream)
p. 243
B.4.2.3
AR (2 streams: Pose/control-stream + scene/video/data/voice-stream)
p. 243
C
Source specific mobility evaluation results
p. 245
C.1
Consecutive XR packets lost due to a HO event, N
p. 245
C.2
Minimum target time interval between HO events, T
p. 252
$
Change history
p. 272