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 38.835  Word version:  18.0.1

Top   Top   Up   Prev   Next
1…   4…   5…   6   A   B…   B.1.2   B.1.3   B.1.4   B.1.5   B.1.6   B.1.7   B.1.8   B.1.9   B.1.10   B.2…   B.2.2   B.2.3   B.2.4   B.2.5   B.2.6   B.2.7   B.2.8   B.2.9   B.2.10   B.2.11   B.2.12   B.2.13   B.2.14   B.2.15   B.2.16   B.2.17   B.2.18   C… 
B.2.5 Jitter handling by LP-WUS 
...

 

B.2.5  Jitter handling by LP-WUS  p. 72

This clause captures evaluation results for LP-WUS based jitter handling
  • vivo and Xiaomi evaluated LP-WUS based wakeup mechanism for XR traffic in presence of jitter, i.e., UE wakes up after a LP-WUS is detected. LP-WUS evaluation methodologies such as power modelling of WUS detection and gap between detected LP-WUS and UE wakeup are based on their own assumptions.
sourcedata row indexTdoc sourcePower saving schemeCDRX cycle (ms)ODT (ms)IAT (ms)Load H/L#UE /cellfloor (Capa­city)% of satis­fied UECapa­city gain (%)Mean PSG of all UEs (%)Mean PSG of satis­fied UEs (%)Addi­tional Assump­tions
Xiaomi1R1-2211341Always On---H3396.61%0.0%-0.0%
Xiaomi2R1-2211341Rel-17 PDCCH skipping---H3395%-1.7%-41.74%Note 1
Xiaomi4R1-2211341LP-WUS---H3395%-1.7%-54.92%Note 1, 2, 3
NOTE 1:
PDCCH skipping with 2 candidate durations(8/10ms)
NOTE 2:
the relative power of LP WUS monitoring is assumed to be 1
NOTE 3:
the resource overhead for LP WUS is not considered
Based on the evaluation results in Table B.2.5-1, the following observations can be made:
  • For FR1, DL only, DU, high load, VR 45Mbps traffic at 60fps and 10ms PDB, it is observed from Xiaomi that:
    • LP-WUS based jitter handling provides:
      • power saving gain of 54.92% for satisfied UEs
      • mean capacity gain of -1.7%
sourcedata row indexTdoc sourcePower saving schemeCDRX cycle (ms)ODT (ms)IAT (ms)Load H/L#UE /cellfloor (Capa­city)% of satis­fied UECapa­city gain (%)Mean PSG of all UEs (%)Mean PSG of satis­fied UEs (%)Addi­tional Assump­tions
vivoR1-2211024Always On---L510100%0.0%--Note1
vivoR1-2211024Always On---L510100%0.0%--Note2
vivoR1-2211024Always On---L510100%0.0%--Note3
vivoR1-2211024Always On---L510100%0.0%--Note4
vivoR1-2211024R17 PDCCH monitoring adaptation16.6784L510100%0.0%23.36%-Note1,5,6
vivoR1-2211024R17 PDCCH monitoring adaptation16.67124L510100%0.0%18.73%-Note2,5,6
vivoR1-2211024R17 PDCCH monitoring adaptation16.67164L510100%0.0%15.79%-Note3,5,6
vivoR1-2211024R17 PDCCH monitoring adaptation16.67164L510100%0.0%13.91%-Note4,5,6
vivoR1-2211024LP-WUS scheme16.6784L510100%0.0%29.71%-Note1,5,7,10
vivoR1-2211024LP-WUS scheme16.67124L510100%0.0%28.26%-Note2,5,7,10
vivoR1-2211024LP-WUS scheme16.67164L510100%0.0%29.36%-Note3,5,7,10
vivoR1-2211024LP-WUS scheme16.67164L510100%0.0%29.28%-Note4,5,7,10
vivoR1-2211024LP-WUS scheme16.6784L51089.44%-10.6%34.10%-Note1,5,8,10
vivoR1-2211024LP-WUS scheme16.67124L51087.22%-12.8%34.83%-Note2,5,8,10
vivoR1-2211024LP-WUS scheme16.67164L51087.60%-12.4%37.87%-Note3,5,8,10
vivoR1-2211024LP-WUS scheme16.6784L51099.44%-0.6%34.10%-Note1,5,8,9,10
vivoR1-2211024LP-WUS scheme16.67124L51099.44%-0.6%34.83%-Note2,5,8,9,10
vivoR1-2211024LP-WUS scheme16.67164L51099.33%-0.7%37.87%-Note3,5,8,9,10
vivoR1-2211024Always On---H101092.50%0.0%--Note1
vivoR1-2211024Always On---H101092.33%0.0%--Note2
vivoR1-2211024Always On---H101091.83%0.0%--Note3
vivoR1-2211024Always On---H101090.94%0.0%--Note4
vivoR1-2211024R17 PDCCH monitoring adaptation16.6784H101092.22%-0.3%19.28%-Note1,5,6
vivoR1-2211024R17 PDCCH monitoring adaptation16.67124H101092.16%-0.2%14.96%-Note2,5,6
vivoR1-2211024R17 PDCCH monitoring adaptation16.67164H101091.05%-0.8%12.26%-Note3,5,6
vivoR1-2211024R17 PDCCH monitoring adaptation16.67164H101091.01%0.1%11.17%-Note4,5,6
vivoR1-2211024LP-WUS scheme16.6784H101092.22%-0.3%25.10%-Note1,5,7,10
vivoR1-2211024LP-WUS scheme16.67124H101092.20%-0.1%24.08%-Note2,5,7,10
vivoR1-2211024LP-WUS scheme16.67164H101091.08%-0.8%24.68%-Note3,5,7,10
vivoR1-2211024LP-WUS scheme16.67164H101091.11%0.2%25.90%-Note4,5,7,10
vivoR1-2211024LP-WUS scheme16.6784H101054.17%-41.4%29.22%-Note1,5,8,10
vivoR1-2211024LP-WUS scheme16.67124H101053.61%-41.9%30.26%-Note2,5,8,10
vivoR1-2211024LP-WUS scheme16.67164H101054.86%-40.3%33.18%-Note3,5,8,10
vivoR1-2211024LP-WUS scheme16.6784H101082.78%-10.5%29.22%-Note1,5,8,9,10
vivoR1-2211024LP-WUS scheme16.67124H101082.25%-10.9%30.26%-Note2,5,8,9,10
vivoR1-2211024LP-WUS scheme16.67164H101082.51%-10.1%33.18%-Note3,5,8,9,10
NOTE 1:
jitter range = [-4, +4]ms, STD=2ms
NOTE 2:
jitter range = [-6, +6]ms, STD=2ms
NOTE 3:
jitter range = [-8, +8]ms, STD=5ms
NOTE 4:
jitter range = [-10, +10]ms, STD=5ms
NOTE 5:
PDCCH skipping is indicated in the DCI that schedules a dummy PDSCH after all the HARQ-ACK processes of transmissions have been completed
NOTE 6:
applying R17 sparse SSSG with PDCCH monitoring every 2 slots when DRX Onduration starts and switch to dense SSSG with PDCCH monitoring every 1 slot after detecting DCI scheduling XR traffic burst
NOTE 7:
the total relative power (including the power of both LP-WUR and main radio) for LP-WUS monitoring is 45 units with no wake-up latency
NOTE 8:
the total relative power (including the power of both LP-WUR and main radio) for LP-WUS monitoring is 20 units with 3ms wake-up latency
NOTE 9:
UE satisfaction metric as 95% packet successful rate
NOTE 10:
the resource overhead for LP WUS is not considered
Based on the evaluation results in Table B.2.5-2, the following observations can be made:
  • For FR1, DL only, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from vivo that:
    • LP-WUS jitter handling provides:
      • mean power saving gain of 28.51% in the range of 24.08% to 33.18% for all UEs
      • mean capacity gain of -15.61% in the range of -41.90% to -0.10%
    • sparse PDDCH monitoring followed by SSSG switching to dense PDCCH monitoring as the performance reference provides:
      • mean power saving gain of 14.42% in the range of 11.17% to 19.28% for all UEs
      • mean capacity gain of -0.30% in the range of -0.80% to -0.10%%%
  • For FR1, DL only, InH, low load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from vivo that:
    • LP-WUS jitter handling provides:
      • mean power saving gain of 33.02% in the range of 29.71% to 37.87% for all UEs
      • mean capacity gain of -3.77% in the range of -12.80% to 0.0%
    • sparse PDDCH monitoring followed by SSSG switching to dense PDCCH monitoring as the performance reference provides:
      • mean power saving gain of 17.95% in the range of 13.91% to 23.36% for all UEs
      • mean capacity gain of 0%
Up

Up   Top   ToC