PowSav Rel-17

 RAN1#102-e

8.7       UE Power Saving Enhancements

Please refer to RP-200938 for detailed scope of the WI

Note: although for now this WI has its own separate agenda, it is expected to be managed jointly under a single agenda with 8.6 when RedCap becomes a WI.

R1-2005614         Work plan for UE power saving enhancements           MediaTek Inc.

8.7.1        Enhancements for idle/inactive-mode UE power saving

8.7.1.1       Potential paging enhancements

Focusing on potential evaluation methodology updates and high-level concepts

R1-2005388        Discussion on paging enhancements for idle/inactive mode UE power saving vivo

·        Proposal 1: Adopt power model in Table 1 (except the power of PDCCH-only of cross-slot scheduling) for power saving evaluation in idle/inactive mode.

·        Proposal 2: The evaluation should assume the number of SSBs for IDLE mode loop convergence / time-frequency tracking can be 1 or 3.

·        Proposal 3: Paging assumptions in Table 2 in R1-2005388 should be adopted.

·        Proposal 4: UE grouping indication for sequence based WUS and PDCCH based WUS should be studied and evaluated.

·        Proposal 5: Sequence based WUS before PO reception should be supported for paging enhancement.

Decision: The document is noted.

R1-2005615        Evaluation methodology and paging enhancement for idle/inactive mode UE power saving      MediaTek

·        Proposal 1: Power consumption evaluation for idle/inactive mode should base on calculation for ease of utilization by RAN1 and RAN2 work groups.

·        Proposal 2: Power consumption evaluation for idle/inactive mode should at least include different SINR conditions and different group paging rates.

·        Proposal 3: Power consumption evaluation for idle/inactive mode should be able to cover both normal capability and reduced capability UEs in order to develop unified paging enhancement scheme(s) for both type of UEs in the same network.

·        Proposal 4: FR1 with SCS 30 KHz is prioritized

·        Proposal 5: For idle/inactive mode power consumption analysis, the power consumption values in Table 1 are utilized, which covers both normal capability and reduced capability UEs.

·        Proposal 6: For paging related settings, consider

o   1.28 second idle-mode paging DRX cycle

o   Group paging rates of 10% and 60%, corresponding to around 10 and 100 UEs sharing the same PO

·        Proposal 7: For measurement related settings, assume

o   SS burst periodicity of 20 ms

o   SMTC periodicity of 20 ms

o   SMTC window duration: 2 ms for intra-band measurement and 5 ms for inter-band measurement

o   No neighbour cell measurement in high SINR condition

·        Proposal 8: For UE paging monitoring/reception within a paging cycle, the following operations should be specified for different SINR conditions:

o   SS burst processing before PO for synchronization as well as measurement of serving cell and, if needed, intra-band neighbour cell(s)

o   PO processing, including Paging PDCCH monitoring, and paging PDSCH processing (subject to group paging rate)

o   SS burst processing after PO for inter-band neighbour cell measurement

·        Proposal 9: When SINR is not high, or for reduced capability UE, the processing timeline in Figure 1 is assumed,
where

o   Three SS bursts before PO are utilized for synchronization; one is also used for serving cell and intra-band neighbour cell measurement

o   4-ms PO processing is assumed for paging monitoring/reception across multiple beams

o   One  5-ms SMTC window after PO is utilized for inter-band neighbour cell measurement

Figure 1: UE processing timeline for paging monitoring/reception when SINR is not high

·        Proposal 10: For high SINR condition, the processing timeline in Figure 2 is assumed, where

o   One SS burst before PO is sufficient for synchronization and serving cell measurement.

o   1-ms PO processing is assumed for paging monitoring/reception only over the best beam(s)

o   No neighbour cell measurement after PO

o   Note that, due to potential SINR change for each paging DRX cycle, an early SS burst is assumed so that UE can process the following SS bursts if identifying lower SINR condition from the first SS burst

Figure 2: UE processing timeline for paging monitoring/reception in high SINR

·        Proposal 11: Rel-17 paging enhancements should aim for minimizing UE wake-up energy overhead, particularly when there is no paging to the UE.

·        Proposal 12: Introduce paging early indication (PEI) before PO for idle/inactive mode power saving.

o   PEI indicates UE whether to decode paging PDCCH/PDSCH in the PO

o   PEI should be located near SS bursts to reduce UE wakeup overhead

o   FFS PEI with UE subgrouping

·        Proposal 13: Due to the limited time of WI and large specification efforts, new signal/channel design for paging early indication(s) is not supported in Rel-17.

·        Proposal 14: FFS the following existing signal/channel for paging early indication.

o   PDCCH channel

o   Existing RS, e.g., SSS and TRS/CSI-RS

·        Proposal 15: RAN1 should follow the physical requirements of PEI from RAN2 if any. RAN1 can additionally take the following performance metrics into consideration.

o   Network resource overhead

o   Detection complexity and power consumption

o   Detection performance requirement

o   Specification effort

Decision: The document is noted.

R1-2005262         Paging enhancement(s) for UE power saving in IDLE/inactive mode     Huawei, HiSilicon

R1-2005520         Discussion on power saving enhancements for paging ZTE

R1-2005582         Considerations on paging enhancements       Sony

R1-2005719         Paging enhancement for UE power saving    CATT

R1-2005738         Paging enhancement for power saving          Beijing Xiaomi Software Tech

R1-2005773         Potential paging enhancements       TCL Communication Ltd.

R1-2005884         On paging enhancements for UE power saving           Intel Corporation

R1-2005935         Power efficient paging      Lenovo, Motorola Mobility

R1-2006041         Paging enhancements for power saving         OPPO

R1-2006157         On potential paging enhancements  Samsung

R1-2006221         Discussion on paging enhancement CMCC

R1-2006291         Discussion on potential paging enhancements             Spreadtrum Communications

R1-2006311         Discussion on potential paging enhancements             LG Electronics

R1-2006385         Potential paging enhancements for idle/inactive-mode UE power saving               Panasonic

R1-2006527         Potential paging enhancements for idle/inactive-mode UE power saving               Apple

R1-2006544         Paging enhancements for UE power saving  InterDigital, Inc.

R1-2006665         Discussion on potential paging enhancements for UE power savings      Ericsson

R1-2006736         Discussion on paging enhancements              NTT DOCOMO, INC.

R1-2006815         Paging enhancements and evaluation methodology     Qualcomm Incorporated

R1-2006896         On paging enhancements for UE power saving           Nokia, Nokia Shanghai Bell

[102-e-NR-UE_pow_sav_enh-01] – Weide (MTK)

Email discussiona/approval

·        By 8/21 – high priority

·        By 8/27 – medium

R1-2007063        Summary for potential paging enhancements         MediaTek

Agreements:

For study of Rel-17 paging enhancement, the following are assumed as a baseline for FR1 and FR2:

·        Reference configuration for FR1/FR2 as specified in Section 8.1.1/8.1.2 of TR 38.840

o   Note: the setting for some PDSCH parameters may not be applicable for RedCap UEs

·        Baseline paging cycle length: [1.28] second

·        SS burst related assumptions:

o   20 ms periodicity

o   2 ms duration for serving cell RRM measurement, which can overlap with the one for synchronization before PO

o   FFS time/frequency tracking

·        Measurement related assumptions:

o   20 ms SMTC periodicity

o   2 ms SMTC window for intra-frequency RRM measurement, assuming synchronized deployment

o   [5 ms SMTC window and 6 ms measurement gap for inter-frequency RRM measurement]

§  Note: RAN4 requirement assumes one frequency layer per measurement gap, and 0.5 ms is assumed for switch in/out a frequency layer

·        Note: the inclusion of potential TRS/CSI-RS occasions can be considered

From GTW session on August 24^th,

Agreements:

The following power consumption model for FR1 is utilized for the evaluations of Rel-17 UE power saving enhancements in idle/inactive mode.

·        FFS: FR2 power consumption model for idle/inactive mode operations

Agreements:

Group paging rate of 10% is assumed for the evaluation of Rel-17 paging enhancement

·        FFS: Another group paging rate > 10%

·        Note: If UE sub-grouping is applied, the sub-group paging rate can be reduced w.r.t. the total sub-group number for a PO

Agreements:

For the study on paging enhancements to reduce unnecessary paging reception, the following metrics are considered:

·        UE power saving gain (relative to a given feature or overall)

·        Impact to UE paging detection probability

o   FFS: Link level simulation assumptions

·        System impact, including

o   Additional resource overhead and its implications

o   Impact to Rel-15/Rel-16 idle/inactive-mode UEs and connected-mode UEs

o   Impact to other legacy functionalities, including SI change and ETWS indication

o   [Note: NW energy consumption evaluation is not precluded]

Agreements:

·        For the study of paging enhancement, 1, 2, or 3 SS burst processing is assumed before PO

o   Note: in choosing one or more values (1, 2, or 3) for the evaluations, companies to provide justification

From GTW session on August 28^th,

Agreement

Send a LS with for evaluation methodology updates related to paging enhancement(s) to RAN2

R1-2007355        Draft LS on evaluation methodology for UE power saving enhancements               MediaTek

Decision: The draft LS is endorsed. Final LS is approved in R1-2007425.

Agreements:

For the study on paging enhancements, the following LLS assumptions are considered.

·        For investigating the residual frequency error after one or multiple SS burst processing, at least -6 dB SNR should be considered

Agreements:

For potential paging enhancements, RAN1 to study the following candidate schemes:

• Paging early indication before a target PO to indicate UE whether to monitor PDCCH scrambled with P-RNTI at the PO. Potential candidate indication methods include
• DCI-based indication, e.g., based on
• Extending existing DCI format 1_0 or 2_6
• New DCI format
• RS-based or sequence-based indication, e.g., based on TRS/CSI-RS or SSS
• Sub-grouping for paging, based on
• Legacy paging DCI
• Paging early indication
• Additional reception occasions in time/frequency domain

o   Multiple P-RNTIs

• Cross-slot scheduling for paging PDSCH
• Other proposal is not precluded

8.7.1.2       TRS/CSI-RS occasion(s) for idle/inactive UEs

Focusing on high-level concepts

R1-2006158        On TRS/CSI-RS occasion(s) for idle/inactive Ues   Samsung

·        Proposal #1: Support functionalities of TRS/CSI-RS for idle/inactive UEs, including

o   Synchronization

o   FFS: RRM measurement or indication for paging reception

·        Proposal #2: Support configuration of cell-specific TRS/CSI-RS resources included in SIB1.

·        Proposal #3: Support time alignment between TRS/CSI-RS reception occasion and PO.

·        Proposal # 4: Support activation or deactivation of TRS/CSI-RS reception for idle/inactive mode UEs based on physical layer signal/channel.

·        Proposal #5: Support relative power for TRS/CSI-RS reception, , such that , where x is occupied symbols of TRS/CSI-RS per slot, and  is relative power for micro-sleep.

Decision: The document is noted.

R1-2006386        Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive Ues               Panasonic

·        Proposal 1: For RRC INACTIVE/IDLE mode UE, new TRS/CSI-RS occasions can be studied to enhance the synchronization and beam tracking before paging monitoring.

·        Proposal 2: To shorten the UE active time for paging monitoring, the additional TRS/CSI-RS location in time and frequency domain and how to configure should be studied.

·        Proposal 3: The influence/interaction with UE's periodic frequency/time tracking should be checked for additional TRS/CSI-RS.

Decision: The document is noted.

R1-2005263         Assistance RS occasions for IDLE/inactive mode       Huawei, HiSilicon

R1-2005389         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  vivo

R1-2005521         Reference signal for RRC idle and inactive UEs         ZTE

R1-2005583         On the usage of TRS/CSI-RS for the UE in Idle Mode              Sony

R1-2005616         On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving    MediaTek Inc.

R1-2005720         Configuration of TRS/CSI-RS for paging enhancement            CATT

R1-2005739         Discussion on TRS CSI-RS occasions for idle/inactive UEs     Beijing Xiaomi Software Tech

R1-2005885         Discussion on TRS/CSI-RS reception during idle/inactive mode             Intel Corporation

R1-2006042         RS occasion for idle/inactive UEs   OPPO

R1-2006222         Discussion on potential TRS CSI-RS occasion(s) for idle/inactive UEs  CMCC

R1-2006269         Consideration on TRS/CSI-RS occasion(s) for idle/inactive UEs            Spreadtrum Communications

R1-2006312         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  LG Electronics

R1-2006528         Indication of TRS/CSI-RS for idle/inactive-mode UE power saving       Apple

R1-2006666         Provisioning of potential TRS/CSI-RS occasion(s) for Idle/Inactive UEs               Ericsson

R1-2006737         Discussion on TRS/CSI-RS occasion for idle/inactive UEs       NTT DOCOMO, INC.

R1-2006816         TRS/CSI-RS for idle/inactive UE power saving          Qualcomm Incorporated

R1-2006897         On RS information to IDLE/Inactive mode Ues          Nokia, Nokia Shanghai Bell

[102-e-NR-UE_pow_sav_enh-02] – Taehyoung (Samsung)

Email discussiona/approval

·        By 8/21 – high priority

·        By 8/27 – medium

R1-2007475        Summary for TRS/CSI-RS occasion(s) for idle/inactive Ues Moderator (Samsung)

From GTW session on August 25^th,

Agreement:

·        New types/patterns of TRS/CSI-RS are not introduced specifically for idle/inactive mode UE.

Decision: As per email decision posted on August 28^th,

Agreements:

The TRS/CSI-RS occasion(s) that may be for connected mode UEs can be shared to idle/inactive mode UEs.

·        Note: It is understood that gNB can potentially share the occasions to idle/inactive (which would just mean it up to NW whether to share or not share).

·        Note: It is understood that TRS/CSI-RS in the TRS/CSI-RS occasion(s) may or may not be transmitted.

·        Note: Always-on TRS/CSI-RS transmission by gNodeB is not required

·        At least TRS/CSI-RS occasion(s) corresponding to periodic TRS is supported

o   FFS for other RS types

·        FFS: Whether UE blind detection is required or not.

Agreements:

Idle/inactive UE may use the TRS/CSI-RS occasion(s) that are shared to it for functionalities such as:

·        AGC, time/frequency tracking

·        FFS: RRM measurement for serving cell, RRM measurement for neighbor cell, paging reception indication

Observation:

It is up to gNB implementation whether or not to transmit a TRS/CSI-RS to idle/inactive UEs even when the TRS/CSI-RS is not needed by connected UEs (e.g., when there is a connected mode UE in a cell but the UE is no longer using the TRS/CSI-RS, or when there is no longer connected mode UE in a cell, etc.)

Agreements:

The configuration of TRS/CSI-RS occasion(s) for idle/inactive mode UE(s) is provided by higher layer signalling

·        FFS higher layer signalling candidates (e.g., SIB, dedicated RRC, RRC release message, etc.)

·        FFS for other signalling candidates (e.g., pre-configuration, etc.)

·        FFS for detailed configuration parameters (e.g., whether and how to reduce the signalling overhead for configuration, etc.)

Decision: As per email decision posted on August 28^th,

Agreement:

Further study whether and how to inform the availability of TRS/CSI-RS to idle/inactive mode UE (implicitly or explicitly).

·       Note: Availability corresponds to the information for whether TRS/CSI-RS is actually transmitted or not.

8.7.1.3       Other

R1-2005390         Discussion on paging grouping       vivo

R1-2005522         Additional simulation results of UE power consumption in RRC idle and inactive state       ZTE

R1-2006412         Initial analysis on power consumption for IDLE mode UE        Huawei, HiSilicon

R1-2006667         High-level UE energy consumption profiling              Ericsson

8.7.2        Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime

Focusing on potential evaluation methodology updates and high-level concepts

R1-2006738        Discussion on extension to DCI-based power saving adaptation        NTT DOCOMO, INC.

·        Proposal 1: It should be discussed first on what Rel-16 DCI-based power saving adaptation(s) the enhancements will be considered.

·        Proposal 2: Consider following Rel-16 DCI-based power saving adaptation(s) as the candidates for enhancements to reduce PDCCH monitoring.

o   Rel-16 cross-slot scheduling enhancements, i.e., minimum scheduling offset of K0/K2

o   Search space set group switching

Decision: The document is noted.

R1-2005264         Extension(s) to Rel-16 DCI-based power saving adaptation for an active BWP               Huawei, HiSilicon

R1-2005391         Discussion on DCI-based power saving adaptation     vivo

R1-2005523         Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time               ZTE

R1-2007032         Evaluation methodology and enhancement for connected mode UE power saving               MediaTek Inc.     (rev of R1-2005617)

R1-2005721         PDCCH monitoring adaptation       CATT

R1-2005886         On PDCCH monitoring reduction techniques during active time             Intel Corporation

R1-2005936         Potential enhancement to DCI based power saving adaptation  Lenovo, Motorola Mobility

R1-2006043         DCI-based adaptation for PDCCH  OPPO

R1-2006159         On enhancements of power saving techniques during DRX active time  Samsung

R1-2006223         Discussion on PDCCH monitoring reduction during DRX active time   CMCC

R1-2006271         Discussion on power saving techniques for connected-mode UE             Spreadtrum Communications

R1-2006313         Discussion on DCI-based power saving adaptation during DRX ActiveTime       LG Electronics

R1-2006387         Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime         Panasonic

R1-2006529         PDCCH based power saving enhancements for connected-mode Ues     Apple

R1-2006548         PDCCH-based power saving signal design considerations        InterDigital, Inc.

R1-2006668         Discussion on potential enhancements for power savings during active time               Ericsson

R1-2006755         Power saving adaptation during Active Time ASUSTEK COMPUTER (SHANGHAI)

R1-2006817         DCI-based power saving adaptation during DRX ActiveTime  Qualcomm Incorporated

R1-2006898         UE power saving enhancements for Active Time        Nokia, Nokia Shanghai Bell

R1-2006946         Power saving enhancements for connected mode UEs Sony

[102-e-NR-UE_pow_sav_enh-03] Email discussiona/approval – Xiaodong (vivo)

·        By 8/21 – high priority

·        By 8/27 – medium

R1-2007065        FL summary of potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime          Moderator (vivo)

R1-2007117        FL summary#2 of potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime          Moderator (vivo)

From GTW session on August 24^th,

Agreements:

·        Reusing power model in TR38.840 for evaluation of DCI-based power saving adaptation schemes.

o   Note: company reporting additional power model for missing state or update is not precluded.

Agreements:

• Company should report assumptions used for periodic measurement activities for the Rel-17 DCI-based power saving adaptation evaluation.
• The periodic activities defined in TR38.840 can be reused.
• Measurement for RLM/BFD every C-DRX cycle can be optionally modelled

R1-2007225        FL summary#3 of potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime          Moderator (vivo)

From GTW session on August 28^th,

Agreements:

·        The performance metrics described in TR38.840 section 8.2 is reused for power saving evaluation of Rel-17 DCI-based power saving adaptation during ActiveTime.

·        The following Rel-15 / 16 features is recommended of the power consumption as reference for baseline. Company can report the feature(s) being used in the baseline.

o   DRX

§  C-DRX cycle 40msec for VoIP

·        10ms IAT, 8ms On-duration

·        Assume max two packets bundled

§  C-DRX cycle 160msec for FTP

·        Alt 1: 20 msec IAT, 8ms On-duration

·        Alt 2: short DRX

o   20 ms [or 40ms as optional] IAT, 8ms On-duration

o   20 ms for short DRX cycle, 4 cycles

·        Note: 100 msec IAT, 8ms On-duration can also be used with sufficient justifications that available Rel-15/16 Techniques being used to reduce UE power saving

• DCP for DRX adaptation,
• DCP offset  to DRX ON = 2 ms, other values are not precluded
• Cross-slot scheduling adaptation
• Minimum K0 can be adapted from 0 to 1 for FR1, 0 to [4] for FR2
• BWP switching, including
• MIMO layer adaptation,
• Max # of MIMO layer can be adapted from 4 layer to 2 layer for FR1, 2 layer to 1 layer for FR2
• PDCCH monitoring period adaptation
• PDCCH monitoring period can be adapted from per slot monitoring to X slot monitoring
• X = [2] for FR1 and [8] for FR2
• Bandwidth adaptation
• Bandwidth can be adapted from 100MHz to 20MHz for FR1,FFS for FR2
• Note:
• BWP transition time type 2 is assumed, BWP transition duration is
• 5 slot @ 30kHz SCS for FR1,
• 18 slot@120kHz SCS for FR2
• the slot-average power level for BWP transition duration is according to TR38.840
• BWP transition time type 1 can be optional modelled
• BWP switching is Y (ms) after last packet/data burst.
• Y = [8], other values are not precluded
• Whether BWP switching is modeled depends on the assumed UE capability and evaluated schemes.
• Scell dormancy assumption for CA capable UEs
• FR1 & FR2: SCell dormancy with [160 ms] periodic CSI measurement and reporting
• Other settings
• CA assumption if configured for CA capable UEs
• For FR1, FFS
• For FR2, 4*100MHz can be considered.
• Assumptions for scheduler
• For FR1, no restriction on the beam assumptions being used in each slot
• For FR2, up to each company, e.g., gNB equally schedule the slots for UEs targeting to different beams.
• Note: the assumptions does not necessary mean to restrict or precluded any implementation. Other assumptions are not precluded and can be reported by companies.
• Company to report the used assumption for the interruption and also power savings impact due to presence/absence of interruptions .

Agreements:

Legacy traffic models in TR38.840 can be considered for Rel-17 DCI-based power saving adaptation evaluation, other traffic models can be optionally modelled and company report which traffic model(s) is used.

R1-2007419        LS on evaluation methodology for connected mode UE power saving enhancement      RAN1, vivo, MediaTek

Decision: The LS is approved.

Final summary in:

R1-2007400        FL summary#4 of potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime          Moderator (vivo)

8.7.33        Other

R1-2005392         Discussion on RLM/BFD relaxation              vivo

R1-2005524         Further discussion on potential power saving schemes for RRC connected UEs   ZTE

R1-2006044         Discussion on RLM Relaxation       OPPO

R1-2006404         Other considerations on power saving in Rel-17         Huawei, HiSilicon

R1-2006669         Evaluation of UE power saving schemes       Ericsson

 RAN1#103-e

8.7       UE Power Saving Enhancements

Please refer to RP-200938 for detailed scope of the WI

Note: although for now this WI has its own separate agenda, it is expected to be managed jointly under a single agenda with 8.6 when RedCap becomes a WI.

8.7.1        Enhancements for idle/inactive-mode UE power saving

8.7.1.1       Potential paging enhancements

R1-2008964        Paging enhancements for idle/inactive-mode UE power saving         MediaTek Inc.

·        Proposal 1: For paging enhancement study, consider at least UE processing timelines using 3 SS bursts and 1 SS burst for synchronization.

·        Proposal 2: For UE processing timelines, it should be assumed that one early SS burst is processed to check channel condition so that sufficient number of SS bursts can be utilized if poor channel condition is identified.

·        Proposal 3: For Rel-17 paging enhancement study, RAN1 to prioritize (UE-Group) paging early indication scheme, where UE is notified before paging occasion whether UE (sub)group is paged or not.

o   LS to RAN2 for inquiring the potential subgroup number if UE grouping is considered

·        Proposal 4: To avoid paging early indication to content resource with existing channels, UE is required to monitor legacy PO if PEI is not detected.

·        Proposal 5: Decide whether to include SI change and ETWS indications in paging early indication after the physical layer design is decided.

·        Proposal 6: For Rel-17 paging enhancement, UE-group paging early indication is supported.

o   UE is required to monitor legacy PO if paging early indication is not detected.

o   FFS: PDCCH/DCI-based or sequence-based physical layer design

Decision: The document is noted.

R1-2007600         Paging enhancement(s) for UE power saving in IDLE/inactive mode     Huawei, HiSilicon

R1-2007673         Paging enhancements for idle/inactive mode UE power saving vivo

R1-2007867         Paging enhancement for UE power saving    CATT

R1-2007890         Potential paging enhancements       TCL Communication Ltd.

R1-2007898         Paging enhancement for power saving          Beijing Xiaomi Software Tech

R1-2007971         Discussion on power saving enhancements for paging ZTE

R1-2008021         Discussion on paging enhancement CMCC

R1-2008053         Discussion on potential paging enhancements             LG Electronics

R1-2008103         Discussion on potential paging enhancements             Spreadtrum Communications

R1-2008175         Discussion on paging enhancements              Samsung

R1-2008265         Further discussion on Paging enhancements for power saving  OPPO

R1-2008287         Potential paging enhancements for idle/inactive-mode UE power saving               Panasonic

R1-2008368         Paging enhancement for idle/inactive mode UE          Sony

R1-2008474         Paging enhancements for idle/inactive-mode UE power saving Apple

R1-2008689         Paging enhancements for UE power saving  InterDigital, Inc.

R1-2008933         On paging enhancements for UE power saving           Nokia, Nokia Shanghai Bell

R1-2009488         On paging enhancements for UE power saving           Intel Corporation (rev of R1-2008992)

R1-2009105         Paging enhancement for UE power saving    Lenovo, Motorola Mobility

R1-2009187         Discussion on paging enhancements              NTT DOCOMO, INC.

R1-2009200         Discussion on potential paging enhancements for UE power savings      Ericsson

R1-2009266         Paging enhancements and evaluation methodology     Qualcomm Incorporated

[103-e-NR-PowSav-Enh-01] – Weide (MediaTek)

Email discussion/approval for potential paging enhancements

• 1^st check point: 11/5
• 2^nd check point: 11/10
• 3^rd check point: 11/12

R1-2009753        Summary for Potential Paging Enhancements        Moderator (MediaTek)

Decision: As per email decision posted on Nov. 10^th,

Agreements:

Observation: For NR idle/inactive-mode UEs, UE sub-grouping indication within a PO can provide the following power saving gains w.r.t. Rel-16:

• If the original group paging rate is 10%:
• [0.3%] - [1.1%] where the baseline assumes 1 SS burst for synchronization before PO reception
• [0.4%] - [0.8%] where the baseline assumes 2 SS bursts for synchronization before PO reception
• [0.3%] - [1.0%] where the baseline assumes 3 SS bursts for synchronization before PO reception
• Some sources also evaluated performance if the original group paging rate is in the range between 20% and 80% and showed following results: 
• [0.7%] - [7.6%] where the baseline assumes 1 SS burst for synchronization before PO reception
• [0.8%] - [3.0%] where the baseline assumes 2 SS bursts for synchronization before PO reception
• [0.5%] - [4.7%] where the baseline assumes 3 SS bursts for synchronization before PO reception

The number of UE sub-groups evaluated ranges from 2 to 16.

Some companies show concern on assuming group paging rate larger than 60%.

Note: It is FFS in RAN1 another group paging rate > 10% for the evaluation of Rel-17 paging enhancement.

Agreements:

Observation: For NR idle/inactive-mode UEs, UE sub-grouping indication carried in paging early indication can provide the following power saving gains w.r.t Rel-16:

• If the original group paging rate is 10%:
• [10.6%] –[19.1%] where the baseline assumes 1 SS burst for synchronization before PO reception
• [16.0%] –[36.0%] where the baseline assumes 2 SS bursts for synchronization before PO reception
• [14.3%] –[46.0%] where the baseline assumes 3 SS bursts for synchronization before PO reception
• Some sources also evaluated performance if the original group paging rate is in the range between 20% and 60% and showed following results: 
• [8.0%] –[19.1%] where the baseline assumes 1 SS burst for synchronization before PO reception
• [18.1%] –[34.0%] where the baseline assumes 2 SS bursts for synchronization before PO reception
• [20.6%] –[42.0%] where the baseline assumes 3 SS bursts for synchronization before PO reception

The additional power saving gains w.r.t. paging early indication without UE sub-grouping are given as follows:

• If the original group paging rate is 10%:
• [0.6%] –[2.7%] where the baseline assumes 1 SS burst for synchronization before PO reception
• [0.6%] –[4.0%] where the baseline assumes 2 SS bursts for synchronization before PO reception
• [0.6%] –[4.7%] where the baseline assumes 3 SS bursts for synchronization before PO reception
• Some sources also evaluated performance if the original group paging rate is in the range between 20% and 60% and showed following results: 
• [1.3%] –[8.0%] where the baseline assumes 1 SS burst for synchronization before PO reception
• [2.1%] –[13.0%] where the baseline assumes 2 SS bursts for synchronization before PO reception
• [3.3%] –[16.1%] where the baseline assumes 3 SS bursts for synchronization before PO reception

The number of UE sub-groups evaluated ranges from 2 to 16.

The power saving gains are dependent on the assumptions about placement of PEI and PO relative to SSB.

Note: It is FFS in RAN1 another group paging rate > 10% for the evaluation of Rel-17 paging enhancement.

Note: Not all sources providing results for paging early indication without UE sub-grouping also provide results for paging early indication with UE sub-grouping.

Agreements:

Observation: For NR idle/inactive-mode UEs with 10% group paging rate, cross-slot scheduling with K0 = 1, which can be supported by Rel-15/Rel-16 for Type 2 CSS, can provide the following power saving gains w.r.t. same-slot scheduling (K0 = 0):

• [<1%] –[2.5%] where the baseline assumes 1 SS burst for synchronization before PO reception
• [<1%] -[1.6%] where the baseline assumes 2 SS bursts for synchronization before PO reception
• [<1%] -[1.44%] where the baseline assumes 3 SS bursts for synchronization before PO reception

One source shows that cross-slot scheduling with K0 = 32, which cannot be supported by Rel-15/Rel-16 for Type 2 CSS, can provide the following power saving gains w.r.t. same-slot scheduling (K0 = 0):

• [0%] where the baseline assumes 1 SS burst for synchronization before PO reception
• [6.3%] where the baseline assumes 3 SS bursts for synchronization before PO reception

The power saving gain will become lower with higher group paging rate.

Agreements: For NR idle/inactive-mode paging enhancement, paging early indication before paging occasion is supported from RAN1 perspective

• FFS: Physical layer design based on DCI, SSS or TRS/CSI-RS
• Send LS to inform RAN2 and kindly ask RAN2 to inform RAN1 if there is anything that RAN1 should take into consideration in the physical layer design for this feature, including any other progress RAN2 has made in this WI which may has RAN1 impact

Decision: As per email decision posted on Nov. 12^th,

Agreements:

Observation: For NR idle/inactive-mode UEs with 10% group paging rate, paging early indication without UE sub-grouping can achieve the following power saving gains w.r.t. Rel-16:

• [0%] - [22.8%] where the baseline assumes 1 SS burst for synchronization before PO reception
• Note: [0%] means UE can apply the baseline behavior if the time offset between the utilized SS burst and PO is small.
• [5.0%] - [32.0%]  where the baseline assumes 2 SS bursts for synchronization before PO reception
• [10.2%] - [67.7%]  where the baseline assumes 3 SS bursts for synchronization before PO reception

The power saving gains will become lower for higher group paging rate.

The power saving gains are dependent on the assumptions about placement of PEI and PO relative to SSB.

The power saving gains may vary with different paging early indication design.

R1-2009754        Draft LS on Paging Enhancement              MediaTek Inc.

Decision: As per email decision posted on Nov. 13^th,  the draft LS is endorsed. Final LS is approved in R1-2009801.

8.7.1.2       TRS/CSI-RS occasion(s) for idle/inactive UEs

R1-2008934        On RS information to IDLE/Inactive mode Ues      Nokia, Nokia Shanghai Bell

·        Proposal: Do not consider the potential TRS/CSI-RS occasions(s) for RRM measurements of serving cell mobility evaluations.

·        Proposal: Do not consider the potential TRS/CSI-RS occasions(s) for RRM measurements of neighbour cell mobility evaluations.

·        Proposal: Do not consider the potential TRS/CSI-RS occasion(s) for IDLE/INACTIVE mode UEs as early paging indication.

·        Proposal: Focus the RAN1 work on WID objective 1b on designing the mechanism to provide IDLE/INACTIVE mode UEs the information on potential periodic TRS occasions. Do not support additional RS types.

·        Proposal: Prior agreeing to support of presence indication, RAN1 should discuss and conclude the side conditions associated with the presence indication.

·        In section 3 we discussed the mechanism to singal the TRS configuration for the IDLE/INACTIVE mode UEs and also look that the parameters needed for the configuration:-

·        Proposal: Once RAN1 has concluded on principles on the desired main functionality and extend of the signaling, RAN1 should send a LS to RAN2 asking RAN2 to design the higher layer signaling mechanism to deliver the TRS configuration to IDLE/INACTIVE mode UEs.

·        Proposal: Configuration of TRS occasion related parameters informed to the IDLE/INACTIVE mode UE(s) should be assumed to support similar flexibility as required by Connected Mode UE(s).

·        Proposal: The configuration of TRS to the IDLE/INACTIVE mode UEs needs to support independent configuration for each broadcast/SSB beam.

Decision: The document is noted.

R1-2007601         Assistance RS occasions for IDLE/inactive mode       Huawei, HiSilicon

R1-2007674         TRS/CSI-RS occasion(s) for idle/inactive UEs            vivo

R1-2007868         Configuration of TRS/CSI-RS for paging enhancement            CATT

R1-2007891         TRS/CSI-RS occasion(s) for idle/inactive UEs            TCL Communication Ltd.

R1-2007899         TRS CSI-RS occasion(s) for idle inactive UEs            Beijing Xiaomi Software Tech

R1-2007972         Reference signal for RRC idle and inactive UEs         ZTE

R1-2008022         Discussion on TRS/CSI-RS occasion(s) for idle/inactive-mode UEs       CMCC

R1-2008054         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  LG Electronics

R1-2008176         Discussion on TRS/CSI-RS occasion(s) for idle/inactive Ues   Samsung

R1-2008266         Further discussion on RS occasion for idle/inactive UEs           OPPO

R1-2008288         Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive Ues               Panasonic

R1-2008369         Considerations on TRS/CSI-RS occasion(s) for idle/inactive mode UE  Sony

R1-2008475         Indication of TRS/CSI-RS for idle/inactive-mode UE power saving       Apple

R1-2008690         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  InterDigital, Inc.

R1-2008965         On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving    MediaTek Inc.

R1-2008993         Discussion on TRS/CSI-RS reception during idle/inactive mode             Intel Corporation

R1-2009106         Provision of TRS/CSI-RS for idle/inactive UEs          Lenovo, Motorola Mobility

R1-2009151         Consideration on TRS/CSI-RS occasion(s) for idle/inactive UEs            Spreadtrum Communications

R1-2009188         Discussion on TRS/CSI-RS occasion for idle/inactive UEs       NTT DOCOMO, INC.

R1-2009201         Provisioning of potential TRS/CSI-RS occasion(s) for Idle/Inactive UEs               Ericsson

R1-2009267         TRS CSI-RS for idle and inactive UE power saving   Qualcomm Incorporated

[103-e-NR-PowSav-Enh-02] – Taehyoung (Samsung)

Email discussion/approval for TRS/CSI-RS occasion(s) for idle/inactive UEs

• 1^st check point: 11/5
• 2^nd check point: 11/10
• 3^rd check point: 11/12

R1-2008178        Moderator summary for TRS/CSI-RS occasion(s) for idle/inactive UEs               Moderator (Samsung)

Decision: As per email decision posted on Nov. 10^th,

Agreement:

·        Functionality of RRM measurement for neighbour cell is not supported for TRS/CSI-RS for idle/inactive UE(s).

Agreements:

·        SIB signalling provides the configuration of TRS/CSI-RS occasion(s) for idle/inactive UE(s).

o   Up to RAN2 to decide which SIB is to be used.

o   Whether or not to additionally support other high-layer signalling methods (e.g., dedicated RRC, RRC release message, etc.) is up to RAN2

Send an LS to RAN2 informing the above agreements, and

·        To further add that RAN1 is working on the detailed physical layer design

R1-2009791        [draft] LS on signalling method for TRS/CSI-RS occasion(s) for idle/inactive UE(s)     Samsung

Decision: As per email decision posted on Nov. 13^th,  the draft LS is endorsed. Final LS is approved in R1-2009848.

Agreement:

·        Aperiodic TRS and semi-persistent/aperiodic CSI-RS are not used as TRS/CSI-RS occasion(s) for idle/inactive UEs.

Agreements:

·        Target sending an LS to RAN2 and RAN4 to ask whether it is feasible to allow a UE to use the potential TRS/CSI-RS occasion to enhance the SSB based IDLE/Inactive mode evaluations of the serving cell. (to also include agreements from last meeting)

·        Further discussion whether any additional information needs to be included in the LS or not, including potential re-wording of the leading sentence

Decision: As per email decision posted on Nov. 13^th,

Agreements:

• Discuss further based on the following alternatives and down-select at RAN1#104-e:
• Alt 1: The availability of TRS/CSI-RS at the configured occasion(s) is NOT informed to the UE.
• Alt 2: The availability of TRS/CSI-RS at the configured occasion(s) is informed to the UE.
• Alt 3. The conditional availability of TRS/CSI-RS at the configured occasion(s) is informed to the UE.
•  The condition can be, e.g., existence of paging.
• Alt 4. Combination of the above alternatives.
• FFS for details
• FFS for UE behavior when the availability is not informed.
• Other techniques are not precluded.
• Companies encourage to provide sufficient information for the proposal, e.g.,
• how to achieve power saving gain
• how to minimize impact on NW

how to minimize extra UE implementation complexity

• feasibility check on sharing the TRS/CSI-RS between connected UEs and idle/inactive UEs
• Proposals should be consistent with the WID objective.

Conclusion:

·        TRS/CSI-RS based PEI is discussed in AI 8.7.1.1.

·        PEI functionality is not further discussed under AI 8.7.1.2.

·        Note: This does not prevent to potentially use PEI to carry the indication for TRS/CSI-RS presence.

8.7.1.3       Other

R1-2007675         Discussion on paging grouping       vivo

R1-2007869         Link level performance of IDLE UE for UE power saving        CATT

R1-2007973         Additional simulation results of UE power consumption in RRC idle and inactive state       ZTE

R1-2008335         Analysis on power consumption for IDLE mode UE   Huawei, HiSilicon

R1-2009202         High-level UE energy consumption profiling              Ericsson

R1-2009300         On network power consumption model         Nokia, Nokia Shanghai Bell

8.7.2        Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime

R1-2008267        Discussion on DCI-based power saving adaptation OPPO

·        Proposal 1: The new FTP models 3 for Gaming and Short Video IM could use 0.05 Mbytes packet size and 15ms mean inter-arrival time. Smaller Packet size like 0.01Mbytes can be also considered.

·        Proposal 2: Power saving enhancement consider the PDCCH monitoring adaptation schemes including:

o   Indicating Search Space group adaptation.

o   Indicating skipping of PDCCH monitoring occasions.

o   Autonomous PDCCH monitoring adaptation.

·        Proposal 3: In power saving mode with cross-slot minimum k0, The UE specific PDCCH search space monitoring periodicity can be matched to the current applicable minimum K0 values.

o   Considering the (min(K0)+1) as the monitoring periodicity.

Decision: The document is noted.

R1-2007602         Extension(s) to Rel-16 DCI-based power saving adaptation for an active BWP               Huawei, HiSilicon

R1-2007676         Discussion on DCI-based power saving adaptation in connected mode  vivo

R1-2007701         Extension to Rel-16 DCI-based power sabing adaptation during DRX Active Time               GDCNI

R1-2007870         PDCCH monitoring adaptation       CATT

R1-2007974         Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time               ZTE

R1-2008023         Discussion on PDCCH monitoring reduction during DRX active time   CMCC

R1-2008055         Discussion on DCI-based power saving adaptation during DRX ActiveTime       LG Electronics

R1-2008177         Discussion on DCI-based power saving techniques    Samsung

R1-2008289         Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime         Panasonic

R1-2008476         Enhanced DCI-based power saving adapation             Apple

R1-2008691         PDCCH-based power saving signal design considerations        InterDigital, Inc.

R1-2008711         DCI-based Power Saving Enhancements       Fraunhofer HHI, Fraunhofer IIS

R1-2008714         Power saving adaptation during Active Time ASUSTeK

R1-2008935         UE power saving enhancements for Active Time        Nokia, Nokia Shanghai Bell

R1-2008966         Discussion on DCI-based power saving adaptation during DRX active time               MediaTek Inc.

R1-2008994         On PDCCH monitoring reduction techniques during active time             Intel Corporation

R1-2009056         Discussion on extension(s) to Rel-16 DCI-based power saving adaptation            Asia Pacific Telecom co. Ltd

R1-2009107         Enhanced DCI based power saving adaptation            Lenovo, Motorola Mobility

R1-2009150         Discussion on power saving techniques for connected-mode UE             Spreadtrum Communications

R1-2009189         Discussion on extension to DCI-based power saving adaptation              NTT DOCOMO, INC.

R1-2009203         Discussion on potential enhancements for power savings during active time               Ericsson

R1-2009268         DCI-based power saving adaptation during DRX ActiveTime  Qualcomm Incorporated

R1-2009299         On power saving adaptation during the DRX active time          Sony

R1-2009501        FL summary#1 of power saving for Active Time    Moderator (vivo)

[103-e-NR-PowSav-Enh-03] – Xiaodong (vivo)

Email discussion/approval for potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime

• 1^st check point: 11/5
• 2^nd check point: 11/10
• 3^rd check point: 11/12

R1-2009655         FL summary#2 of power saving for Active Time        Moderator (vivo)

R1-2009656         FL summary#3 of power saving for Active Time        Moderator (vivo)

Agreements:

Observation:

·        Each of the following schemes is individually shown to be beneficial for UE power saving compared to the baseline.

o   Dynamically switching search space set

o   Dynamically skipping PDCCH monitoring for a certain duration or until next DRX ON

·        At least the following Rel-15 and/or Rel-16 power saving solutions have been utilized for baseline,

o   For eMBB traffic,

§  DRX setting(including using short DRX or long DRX with a short IAT or long IAT), Wake-up signal, Cross-slot scheduling, CA/Scell dormancy, MAC-CE skipping, BWP switching

o   For VoIP traffic,

§  DRX setting(only long DRX cycle with a short IAT), Wake-up signal,  Cross-slot scheduling, MAC-CE skipping

o   For IM traffic,

§  DRX setting(long DRX cycle [with a short IAT]), Wake-up signal

o   For intensive eMBB traffic,

§  DRX setting(including using short DRX or long DRX with a short IAT), Wake-up signal, Cross-slot scheduling, [CA/Scell dormancy], MAC-CE skipping, BWP switching

§  Note: intensive eMBB traffic is optional and companies may use FTP model 3 with different packet size and mean data arrival time, e.g., 15ms, 30ms, 50ms or 100ms.

·        Note 1: For Search space switching, switching from 1slot monitoring to 2, 4, 8, 10, 16 or 32 slot with 30kHz SCS (FR1) and 120kHz (FR2) is utilized.

·        Note 2: For PDCCH skipping , skipping 2ms, 4ms, 5ms, 8ms, 15ms, 16ms, 32ms,  64ms or to next DRX cycle is utilized

·        Note 3: the baseline assumed may vary across companies

Decision: As per email decision posted on Nov. 13^th,

Agreements:

·        Specify at least one of the following options for Rel-17 dynamic PDCCH adaptation in time-domain for active time,

o   Option 1: Search space set group switching,e.g., potential adjustments/enhancements forincluding explicit and implicit search spaceset group switching specified in R16 for NR-U

o   Option 2: PDCCH skipping for a certain duration / DRX cycle

·        FFS: which option(s)(e.g. taking into account additional gain of option 1 over option 2, or vice-versa)

·        Candidate DCI formats for dynamic PDCCH adaptation include DCI formats 1_1(including scheduling and non-scheduling DCI), 0_1, 1_2, 0_2, 2_0, 2_6.

·        Note:

o   Companies are encouraged to provide analysis on specification impact, power saving benefit and system impact (e.g., packet latency, system overhead)

·        FFS: other schemes are not precluded for further study

Final summary in:

R1-2009804        FL summary#4 of power saving for Active Time    Moderator (vivo)

8.7.33        Other

R1-2007677         Discussion on RAN2 and RAN4 related power saving relaxation           vivo

R1-2007871         Feature interaction between Secondary DRX group and DCP/SCell dormancy               CATT

R1-2007975         Further discussion on potential power saving schemes for RRC connected UEs   ZTE

R1-2008268         Discussion on RLM relaxation        OPPO

R1-2008330         Other considerations on power saving in Rel-17         Huawei, HiSilicon

R1-2008477         Power saving evaluation for RLM/BFD relaxation     Apple

R1-2009204         Evaluation of additional UE power saving schemes    Ericsson

 RAN1#104-e

8.7       UE Power Saving Enhancements

Please refer to RP-200938 for detailed scope of the WI

From AI5

[104-e-NR-R17-PowSav-LS-01] – Weide (MediaTek)

Email discussion regarding LS in R1-2100020, including a possible reply LS till 2/1

R1-2101940        [Draft] Reply LS on Paging Enhancement MediaTek

Decision: As per email decision posted on Feb 4^th, the draft LS is endorsed. Final LS is approved in R1-2102136.

8.7.1        Enhancements for idle/inactive-mode UE power saving

8.7.1.1       Potential paging enhancements

R1-2100392        Paging enhancement for UE power saving CATT

·        Proposal 1:  The sequence-based PEI should be adopted in Rel-17 for UE in IDLE/Inactive mode for UE power saving.

·        Proposal 2:  The sequence-based PEI with sub-grouping does not provide much power saving gain over that without sub-grouping and require large additional overhead.  Supporting sub-grouping should be further study.

·        Proposal 3:  For the sequence-based PEI with sub-grouping, the number of sub-groups should be up to 8 sub-groups considering the trade-off between power saving gain and system overhead.

·        Proposal 4: The sequence-based PEI configuration and procedure could be calculated by reference signal/channel, e.g., reusing the procedure of paging occasion computation for 38.304.

·        Proposal 5: For Idle/Inactive mode, multiple beams of PEI should be supported.

·        Proposal 6: For Idle/Inactive mode, the spatial channel property of PEI is QCLed with the beams of SSB corresponding to paging PDCCH/PDSCH.

·        Proposal 7: The PEI design should consider a trade-off between the ratio of the number of PEI to PO and resource collision.

Decision: The document is noted.

R1-2100523        Discussion on power saving enhancements for paging          ZTE , Sanechips

·        Proposal 1: The combination of PEI and sub-grouping indication should be supported.

·        Proposal 2: The system information change and availability indication of periodic TRS can be conveyed by PEI.

·        Proposal 3: Adopt DCI-based PEI to reduce the paging reception for RRC idle/inactive state UE.

Decision: The document is noted.

R1-2100168         Further discussion on Paging enhancements for power saving  OPPO

R1-2100216         Paging enhancement(s) for UE power saving in IDLE/inactive mode     Huawei, HiSilicon

R1-2100452         Paging enhancements for idle/inactive mode UE power saving vivo

R1-2100544         Potential paging enhancements       TCL Communication Ltd.

R1-2100591         Design of paging early indication for idle/inactive-mode UE power saving               MediaTek Inc.

R1-2100662         On paging enhancements for UE power saving           Intel Corporation

R1-2100824         Discussion on potential paging enhancements             Spreadtrum Communications

R1-2100866         Paging enhancement in Idle/Inactive state     Sony

R1-2100903         Discussion on potential paging enhancements             LG Electronics

R1-2100998         Paging enhancement for UE power saving    Lenovo, Motorola Mobility

R1-2101052         Discussion on paging early indication design              CMCC

R1-2101125         Paging enhancement for power saving          Xiaomi

R1-2101217         Discussion on paging enhancements              Samsung

R1-2101300         On paging enhancement    Panasonic

R1-2101392         Paging early indication for idle/inactive-mode UE      Apple

R1-2101474         Paging enhancements for idle/inactive UE power saving           Qualcomm Incorporated

R1-2101787         Paging enhancements for UE power saving  InterDigital, Inc.  (rev of R1-2101503)

R1-2101555         Design of Paging Enhancements     Ericsson

R1-2101622         Discussion on paging enhancements              NTT DOCOMO, INC.

R1-2101664         On paging enhancements for UE power saving           Nokia, Nokia Shanghai Bell

[104-e-NR-R17-PowSav-01] – Weide (MediaTek)

Email discussion on potential paging enhancements

-        1^st check point: Jan 28

-        2^nd check point: Feb 2

-        3^rd check point: Feb 4

R1-2101948        Summary for Paging Enhancements          Moderator (MediaTek)

Agreement:

·        Carrying UE subgroups information is considered in physical layer design for paging enhancement 

Agreements:

For the evaluation and comparison of PEI candidate designs based on PDCCH, TRS/CSI-RS and SSS, the following are assumed:

• Behv-A:
• PEI indicates UE should monitor a PO if UE’s group/subgroup is paged
• UE is not required to monitor a PO if UE does not detect PEI at all PEI occasion(s) for the PO
• Behv-B:
• PEI indicates whether or not UE should monitor a PO 
• UE is required to monitor a PO if UE does not detect PEI at all PEI occasion(s) for the PO

Agreements:

For the evaluation and comparison of PEI candidate designs, companies to report

·        Description of how PEI design can co-exist with existing channels/signals, and impact to legacy UEs.

o   Rel-15 designs for multiplexing PEI with legacy channels/signals are assumed as baseline

o   Other multiplexing method with legacy channels/signals can be additionally reported with justification

Agreements:

• Take Alt 1 as mandatory, and Alt 2 as optional

Alt 1: For the performance evaluations of PEI candidate designs based on PDCCH, TRS/CSI-RS and SSS,

1.      The following are assumed, at the SNR where the Miss-Detection Rate (MDR) of paging PDSCH is 1%,

a.      When Behv-A is assumed:

                                                    i.     The joint miss-detection rate (MDR) of PEI and paging PDCCH defined below should be no worse than 1%: MDR_Joint_A = MDR_PEI + (1 – MDR_PEI) MDR_PagingPDCCH

                                                   ii.     The False-Alarm Rate (FAR) of PEI should be no larger than [1%]

b.      When Behv-B is assumed:

                                                    i.     The joint miss-detection rate (MDR) of PEI and paging PDCCH defined below should be no worse than 1%: MDR_Joint_B = FAR_PEI + (1 – FAR_PEI) MDR_PagingPDCCH

                                                   ii.     The MDR of PEI should be no larger than [1%]

c.      Note: The CFO is modeled at the input of PEI detection and based on LLS assumptions agreed in RAN1 #102-e. Companies should justify the applied random range for the CFO.

2.      Companies to provide:

a.      Information on the utilized detection method for each PEI candidate design (e.g., non-coherent detection or coherent detection)

b.      The required #REs to comply with the performance assumptions

c.      The maximum number of subgroups that can be carried in PEI, subject to the performance assumptions

Alt 2: For the performance evaluations of PEI candidate designs based on PDCCH, TRS/CSI-RS and SSS,

1.      The following are assumed, at the SNR where the Miss-Detection Rate (MDR) of paging DCI is 1%,

a.      When Behv-A is assumed:

                                                    i.     The MDR of PEI should be no larger than 0.1%

                                                   ii.     The False-Alarm Rate (FAR) of PEI should be no larger than 1%

b.      When Behv-B is assumed:

                                                    i.     The FAR of PEI should be no larger than 0.1%

                                                   ii.     The MDR of PEI should be no larger than 1%

c.      Note: The CFO is modeled at the input of PEI detection and based on LLS assumptions agreed in RAN1 #102-e. Companies should justify the applied random range for the CFO.

2.      Companies to provide:

a.      Information on the utilized detection method for each PEI candidate design (e.g., non-coherent detection or coherent detection)

b.      The required #REs to comply with the performance assumptions

c.      The maximum number of subgroups that can be carried in PEI, subject to the performance assumptions

Agreements:

For the evaluation of resource overhead with PEI candidate designs based on PDCCH, TRS/CSI-RS and SSS, companies to provide estimated overheads for PEI candidate designs based on the following factors:

a.      Assumption of Behv-A/B

b.      Required #REs from performance evaluations

c.      10% group paging rate per PO as baseline; other group paging rates can be optionally considered

and based on the following assumptions with justification (up to each company)

d.      Whether and how coexistence with legacy UEs is considered

e.      Whether and how indication(s) to multiple POs and/or UE subgroups by one PEI is considered

f.       Whether and how multi-beam transmission is considered

Decision: As per email posted on Feb 5^th,

Agreements:

Further study the design on how to provide the indications for UE subgroups over PEI and/or paging PDCCH, subject to the metrics agreed in RAN1 102e.

8.7.1.2       TRS/CSI-RS occasion(s) for idle/inactive UEs

R1-2100169         Further discussion on RS occasion for idle/inactive UEs           OPPO

R1-2100217         Assistance RS occasions for IDLE/inactive mode       Huawei, HiSilicon

R1-2100393         Configuration of TRS/CSI-RS for paging enhancement            CATT

R1-2100453         TRS/CSI-RS occasion(s) for idle/inactive UEs            vivo

R1-2100524         TRS for RRC idle and inactive UEs ZTE , Sanechips

R1-2100545         TRS/CSI-RS occasion(s) for idle/inactive UEs            TCL Communication Ltd.

R1-2100592         On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving    MediaTek Inc.

R1-2100663         TRS/CSI-RS functionality during idle/inactive mode Intel Corporation

R1-2100814         Consideration on TRS/CSI-RS occasion(s) for idle/inactive UEs            Spreadtrum Communications

R1-2100867         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  Sony

R1-2100904         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  LG Electronics

R1-2100999         Provision of TRS/CSI-RS for idle/inactive UEs          Lenovo, Motorola Mobility

R1-2101053         Discussion on TRS/CSI-RS occasion(s) for IDLE/INACTIVE-mode UEs               CMCC

R1-2101126         On TRS/CSI-RS occasion(s) for idle/inactive UEs      Xiaomi

R1-2101219         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  Samsung

R1-2101301         Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs               Panasonic

R1-2101393         Indication of TRS/CSI-RS for idle/inactive-mode UE power saving       Apple

R1-2101475         TRS/CSI-RS for idle/inactive UE power saving          Qualcomm Incorporated

R1-2101504         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  InterDigital, Inc.

R1-2101544         On TRS/CSI-RS occasions for idle/inactive UEs         Sharp

R1-2101556         Provisioning of TRS occasions to Idle/Inactive UEs   Ericsson

R1-2101623         Discussion on TRS/CSI-RS occasion for idle/inactive UEs       NTT DOCOMO, INC.

R1-2101665         On RS information to IDLE/Inactive mode Ues          Nokia, Nokia Shanghai Bell

[104-e-NR-R17-PowSav-02] – Qiongjie (Samsung)

Email discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs

-        1^st check point: Jan 28

-        2^nd check point: Feb 2

-        3^rd check point: Feb 4

R1-2101218        Moderator summary for TRS/CSI-RS occasion(s) for idle/inactive UEs               Moderator (Samsung)

Decision: As per email posted on Jan 29^th,

Agreements:

Configuration of TRS/CSI-RS occasion(s) for idle/inactive Ues include at least:

·        powerControlOffsetSS,

·        scramblingID

·        firstOFDMSymbolInTimeDomain,

·        startingRB.

·        nrofRBs,

·        FFS other parameters

·        FFS applicable values

Agreements:

The SCS configuration of TRS/CSI-RS occasion(s) for idle/inactive UEs can be discussed and down-selected from following alternatives at RAN1#104b-e:

·        Alt1: same as initial BWP

·        Alt2: configurable parameter

Agreements:

Multiple RS resources can be configured for TRS/CSI-RS occasion(s) for idle/inactive UEs.

·        FFS details (including whether or not to restrict the RS to be TRS only)

Decision: As per email posted on Jan 31^st,

Agreements:

For a cell with TRS/CSI-RS occasions configured for IDLE/Inactive UEs, IDLE/Inactive UE’s assumption on the availability of TRS/CSI-RS at the configured occasion(s) is informed to the idle/inactive UE based on explicit indication.

·        FFS details (e.g., the signalling, detailed information for the TRS/CSI-RS, etc.)

·        There is no intended blind detection of the presence/absence of TRS/CSI-RS at the UE side in this feature. That is, the UE assumes TRS/CSI-RS is not present if the network does not indicate it is available (or indicates it is unavailable).

Conclusion

From RAN1 perspective, there is no consensus on supporting RRM measurement for serving cell functionality for TRS/CSI-RS occasion(s) for idles/inactive UEs.

Agreements:

The configuration of the frequency location of TRS/CSI-RS occasion(s) for idle/inactive UEs are discussed and down-selected from following alternatives at RAN1#104bis-e:

• Alt-1: within initial DL BWP
• Alt-2: is not restricted by initial BWP
• IDLE/INACTIVE mode UE is not expected to receive TRS/CSI-RS outside the initial DL BWP.

Decision: As per email posted on Feb 4^th,

Agreements:

To study QCL information of TRS/CSI-RS occasion(s) for idle/inactive UEs from following alternatives:

• Alt-1: From higher layer configuration, e.g. qcl-InfoPeriodicCSI-RS
• Alt-2: QCL assumptions associated with transmitted SSBs implicitly, e.g. similar to PDCCH monitoring in PO
• FFS details
• Other alternatives are not precluded

Conclusion:

Decide at RAN1#104b-e, whether or not to support periodic CSI-RS in addition to periodic TRS for TRS/CSI-RS occasion(s) for idle/inactive UEs.

8.7.1.3       Other

R1-2100394         Details of PEI configuration            CATT

R1-2100454         Discussion on paging grouping       vivo

R1-2100525         Additional simulation results of UE power consumption in RRC idle and inactive state       ZTE , Sanechips

R1-2101557         Modeling of Network Power Consumption   Ericsson

R1-2101740         Analysis on power consumption for IDLE mode UE   Huawei, HiSilicon

8.7.2        Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime

R1-2100170         DCI-based power saving adaptation solutions             OPPO

R1-2100218         Extension(s) to Rel-16 DCI-based power saving adaptation for an active BWP               Huawei, HiSilicon

R1-2100395         PDCCH monitoring adaptation       CATT

R1-2100455         Discussion on DCI-based power saving adaptation in connected mode  vivo

R1-2100498         Extension to Rel-16 DCI-based power sabing adaptation during DRX Active Time               GDCNI

R1-2100526         Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time               ZTE , Sanechips

R1-2100593         On enhancements to DCI-based UE power saving during DRX active time               MediaTek Inc.

R1-2100664         Discussion on PDCCH monitoring reduction techniques during active time         Intel Corporation

R1-2100815         Discussion on power saving techniques for connected-mode UEs           Spreadtrum Communications

R1-2100905         Discussion on DCI-based power saving adaptation during DRX ActiveTime       LG Electronics

R1-2100980         Discussion on extension(s) to Rel-16 DCI-based power saving adaptation            Asia Pacific Telecom, FGI

R1-2101000         Enhanced DCI based power saving adaptation            Lenovo, Motorola Mobility

R1-2101054         Discussion on PDCCH monitoring reduction during DRX active time   CMCC

R1-2101220         Discussion on DCI-based power saving techniques    Samsung

R1-2101285         DCI-based Power Saving Enhancements       Fraunhofer HHI, Fraunhofer IIS

R1-2101302         Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime         Panasonic

R1-2101394         Enhanced DCI-based power saving adaptation            Apple

R1-2101476         DCI-based power saving adaptation during DRX ActiveTime  Qualcomm Incorporated

R1-2101505         PDCCH monitoring reduction in Active Time             InterDigital, Inc.

R1-2101558         Design of active time power savings mechanisms       Ericsson

R1-2101567         Power saving adaptation during Active Time ASUSTeK

R1-2101624         Discussion on extension to DCI-based power saving adaptation              NTT DOCOMO, INC.

R1-2101666         UE power saving enhancements for Active Time        Nokia, Nokia Shanghai Bell

[104-e-NR-R17-PowSav-03] – Xiaodong (vivo)

Email discussion on potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime

-        1^st check point: Jan 28

-        2^nd check point: Feb 2

-        3^rd check point: Feb 4

R1-2101893        FL summary#1 of power saving for Active Time    Moderator (vivo)

Agreements:

·        Strive for a common design for DCI based PDCCH monitoring adaptation in active time for an active BWP to support functionalities inclusive of both SSSG switching and PDCCH skipping for a duration.

o   Details FFS

Agreements:

·        Further study whether and how to minimize the impact to data scheduling for new transmissions and retransmissions.

o   FFS details

·        Further study the application delay for PDCCH adaptation indication

Agreements:

·        For DCI based PDCCH skipping in active time for an active BWP (if supported), the following can be further considered,

o   Explicit indication of PDCCH adaptation

§  Scheduling DCI

·        Format 1_1

·        Format 0_1

·        Format 0_2/1_2

§  Non-scheduling DCI

·        Format 2_6 in active time

·        Format 2_0

·        Format 1_1 (SCell dormancy case 2)

§  additional indication mechanism

·        By reusing Rel-16 SCell dormancy indication when CA is configured, FFS details

·        By reusing Rel-16 cross-slot scheduling indication when R16 cross-slot scheduling is configured, FFS details

o   DCI dynamically indicates a duration/periodic interval for skipping

§  FFS: how to indicate the duration/period interval, e.g., number of slots or skipping current DRX

o   PDCCH skipping for a duration indicated by minimum scheduling offset

o   Others are not precluded

Agreements

·        For DCI based SSSG switching in active time for an active BWP (if supported), the following can be further considered,

o   Explicit indication of PDCCH adaptation

§  Scheduling DCI based

·        Format 1_1,

·        Format 0_1,

·        Format 0_2/1_2

·        Format 1_0

§  Non-scheduling DCI

·        Format 2_6 in active time

·        Format 2_0

·        Format 1_0

·        Format 1_1 (SCell dormancy case 2)

§  additional indication mechanism

·        By reusing Rel-16 SCell dormancy indication when CA is configured, FFS details

·        By associating Rel-16 cross-slot scheduling indication when R16 cross-slot scheduling is configured, FFS details

§  DCI dynamically indicates a duration for the switched SSSG, UE switch back to previous/default SSSG after duration ends

o   Timer-based SSSG switching, including RRC configured a timer, UE switch back after timer expired.

o   SSSG activation/deactivation

o   FFS: Implicit SSSG switching

§  SSSG switching triggered by SR

§  SSSG switching triggered by RACH

§  Default SSSG that a UE monitors when coming out of DRX to monitor an ON duration.

·        FFS: whether/how to support SSSG switching for multiple groups of cell(s).

·        FFS: whether/how to support SSSG switching in active time with DCP outside active time

·        FFS: whether / how to support more than 2 SSSGs,

o   FFS: number of SSSGs

·        FFS: a search space set group to emulate PDCCH skipping

·        Others are not precluded

Decision: As per email posted on Feb 5^th,

Agreements:

• The following alternatives can be considered for DCI based PDCCH monitoring adaptation in active time for an active BWP for power saving
• Alt 1: Enhancement of Rel-16 SSSG switching to support PDCCH monitoring adaptation including skipping for a duration
• Alt 2a: Enhancement of DCI(s) utilized for Rel-16 power saving adaptation for supporting both skipping PDCCH monitoring for a duration and SSSG switching
• Alt 2b: Enhancement of DCI(s) utilized for Rel-16 power saving adaptation for supporting both skipping PDCCH monitoring for a duration and PDCCH monitoring periodicity adaptation
• Others not precluded

Final summary in R1-2101894.

8.7.33        Other

R1-2100171         Discussion on RLM relaxation        OPPO

R1-2100396         System overhead analysis of PEI and TRS/CSI-RS for IDLE mode UE  CATT

R1-2100456         Discussion on RLM/BFD/RRM relaxation   vivo

R1-2100527         Further discussion on potential power saving schemes for RRC connected UEs   ZTE , Sanechips

R1-2100816         Discussion on other power saving techniques              Spreadtrum Communications

R1-2101257         Other considerations on power saving in Rel-17         Huawei, HiSilicon

R1-2101559         Evaluation results for UE power saving schemes        Ericsson

R1-2101720         Paging indication based on sub-time units    InterDigital, Inc.

 RAN1#104-bis-e

8.7       UE Power Saving Enhancements

Please refer to RP-200938 for detailed scope of the WI

8.7.1        Enhancements for idle/inactive-mode UE power saving

8.7.1.1       Potential paging enhancements

//Handled under NWM – See RAN1-104b-e-NWM-NR-R17-PowSav-01 as the document name

R1-2102316         Paging enhancements for UE power saving in IDLE/inactive mode        Huawei, HiSilicon

R1-2102405         Further discussion on Paging enhancements for power saving  OPPO

R1-2102463         Discussion on potential paging enhancements             Spreadtrum Communications

R1-2102532         Paging enhancements for idle/inactive mode UE power saving vivo

R1-2102565         Discussion on power saving enhancements for paging ZTE,Sanechips

R1-2102641         Paging enhancement for UE power saving    CATT

R1-2102681         On paging enhancements for idle/inactive mode UE power saving         MediaTek Inc.

R1-2102805         On paging enhancement    Panasonic

R1-2102892         Discussion on paging early indication design              CMCC

R1-2103768         Paging enhancement for power saving          Xiaomi  (rev of R1-2102991)

R1-2103041         On Paging Enhancements for UE Power Saving          Intel Corporation

R1-2103115         Paging early indication for idle/inactive-mode UE      Apple

R1-2103177         Paging enhancements for idle/inactive UE power saving           Qualcomm Incorporated

R1-2103249         Discussion on paging enhancements              Samsung

R1-2103310         Discussion on potential paging enhancements             Sony

R1-2103355         Discussion on potential paging enhancements             LG Electronics

R1-2103405         On paging enhancements for UE power saving           Nokia, Nokia Shanghai Bell

R1-2103424         Paging enhancements for UE power saving  InterDigital, Inc.

R1-2103586         Discussion on paging enhancements              NTT DOCOMO, INC.

R1-2103614         Paging enhancement for UE power saving    Lenovo, Motorola Mobility

R1-2103642         Design of Paging Enhancements     Ericsson

R1-2103653         On  paging early indication              Nordic Semiconductor ASA

[104b-e-NR-R17-PowSav-01] – Weide (MediaTek)

Email discussion on potential paging enhancements

-        1^st check point: 4/15

-        2^nd check point: 4/19

-        3^rd check point: 4/20

R1-2103848        Summary of paging enhancements             Moderator (MediaTek)

Agreement:

Observation 1a:

For the evaluation and comparison of PEI candidate designs, the following observations for coexistence with legacy PDSCH are identified:

a)      For coexistence with legacy PDSCH, semi-static resouce sharing by configuring RB-symbol-level or RE-level rate-matching patterns covering PEI REs is supported for all PEI candidate designs.

b)      For coexistence with legacy PDSCH, dynamic resource sharing can be realized for all PEI candidates if PDSCH is scheduled by DCI format 1_1

o   For PDCCH based PEI, CORESET-level rate matching can be realized for the PDSCH as per mandatory capability  

o   For SSS-based PEI, CORESET-level rate matching may be realized for the PDSCH as per mandatory capability, depending on the design of SSS-based PEI and UE capability regarding number of supported CORESETs  

o   For TRS/CSI-RS based PEI, RE-level rate matching can be realized for the PDSCH as per mandatory capability

o   When PDSCH is not scheduled by DCI format 1_1, it is up to gNB implementation whether and how PEI is transmitted in PDSCH resource

Observation 2a:

For the evaluation and comparison of PEI candidate designs, the following summarize the identified configurations of PEI candidate designs, including pairs of the minimum required resource and maximum UE (sub)group indication capacity per PEI, that can comply with the mandatory performance metrics agreed in RAN1 #104-e:

·        If Behv-A is assumed,

·        If Behv-B is assumed,

Observation 3a:

For the evaluation and comparison of PEI candidate designs, the following summarize average resource overheads per PO for PEI candidate designs, considering the configurations identified from performance observation.

·        The average overhead results are based on PO settings without impact from UE sub-grouping indication within the PO.

·        Note: For comparison purpose, single-beam transmission for PEI is assumed, and results with multi-beam transmission for PEI is scaled. This doesn’t preclude any beam-forming related design for PEI.

·        If Behv-A is assumed:

·        If Behv-B is assumed:

8.7.1.2       TRS/CSI-RS occasion(s) for idle/inactive UEs

R1-2102317         Assistance RS occasions for IDLE/inactive mode       Huawei, HiSilicon

R1-2102406         Further discussion on RS occasion for idle/inactive UEs           OPPO

R1-2102464         Consideration on TRS/CSI-RS occasion(s) for idle/inactive UEs            Spreadtrum Communications

R1-2102478         TRS/CSI-RS occasions for idle/inactive UE TCL Communication Ltd.

R1-2102533         TRS/CSI-RS occasion(s) for idle/inactive UEs            vivo

R1-2102566         TRS for RRC idle and inactive UEs ZTE,Sanechips

R1-2102642         Configuration of TRS/CSI-RS for paging enhancement            CATT

R1-2102682         On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving    MediaTek Inc.

R1-2102806         Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs               Panasonic

R1-2102893         Discussion on TRS/CSI-RS occasion(s) for IDLE/INACTIVE-mode UEs               CMCC

R1-2102992         On TRS/CSI-RS configuration and indication for idle/inactive UEs       Xiaomi

R1-2103042         TRS/CSI-RS functionality during idle/inactive mode Intel Corporation

R1-2103116         Indication of TRS/CSI-RS for idle/inactive-mode UE power saving       Apple

R1-2103178         TRS/CSI-RS for idle/inactive UE power saving          Qualcomm Incorporated

R1-2103250         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  Samsung

R1-2103311         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  Sony

R1-2103356         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  LG Electronics

R1-2103406         On RS information to IDLE/Inactive mode Ues          Nokia, Nokia Shanghai Bell

R1-2103425         Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs  InterDigital, Inc.

R1-2103479         On TRS/CSI-RS occasions for idle/inactive UEs         Sharp

R1-2103587         Discussion on TRS/CSI-RS occasion for idle/inactive Ues       NTT DOCOMO, INC.

R1-2103615         Provision of TRS/CSI-RS for idle/inactive UEs          Lenovo, Motorola Mobility

R1-2103643         Provisioning of TRS occasions to Idle/Inactive UEs   Ericsson

R1-2103654         On TRS design for idle/inactive UEs             Nordic Semiconductor ASA

[104b-e-NR-R17-PowSav-02] – Qiongjie (Samsung)

Email discussion on TRS/CSI-RS occasions(s) for idle/inactive UEs

-        1^st check point: 4/15

-        2^nd check point: 4/19

-        3^rd check point: 4/20

R1-2103251        Moderator summary for TRS/CSI-RS occasion(s) for idle/inactive Ues               Moderator (Samsung)

Agreement:

SCS of TRS/CSI-RS occasion(s) for idle/inactive UEs is same as SCS of CORESET#0.

Agreement:

Support higher layer configuration of the QCL information of TRS/CSI-RS occasion(s) for idle/inactive UEs.

·        FFS details of the QCL information, e.g. associated SSB index

Agreement:

IDLE/INACTIVE mode UE is not expected to receive TRS/CSI-RS outside the initial DL BWP.

·        Configuration of the frequency location of TRS/CSI-RS occasion(s) for idle/inactive UEs is not restricted by initial BWP.

Working assumption:

Support at least L1 based signaling for the availability indication of TRS/CSI-RS at the configured occasion(s) to the idle/inactive UEs.

·        FFS details, including paging DCI and/or PEI for L1 based signaling

·        FFS SIB-based signaling/configuration

• Note: It is RAN1 understanding that existing SI update procedure is used for SIB based signaling

Agreement:

Configuration for TRS/CSI-RS occasion(s) for idle/inactive UEs is based on periodic TRS only, including following limitations

·        Configuration parameters that are necessary to provide configuration of periodic TRS for idle/inactive UEs

·        Applicable values that are necessary to provide configuration of periodic TRS for idle/inactive UEs

·        If the configuration is provided, idle/inactive UEs can always implicitly assume that trs-info is configured.

o   The parameter trs-info does not need to be provided in the configuration

Agreement:

For the information provided by a physical layer availability indication of TRS/CSI-RS at the configured occasion(s) to the idle/inactive UEs, one or more alternatives from the following can be supported:

• Alt1: Availability/unavailability information for all or some of configured RS resources using a bitmap or codepoint
• e.g. using bitmap, where each bit from a bitmap or a codepoint is associated with at least one resource/configuration or a set/group of resources
• e.g. a codepoint to indicate a state of availability/unavailability for all or some of configured RS resources 
• Alt2: value or codepoint to indicate one or more resource/configuration indices that correspond to the available RS resources
• FFS whether and how to indicate the ‘availability’ in beam selective manner.
• Other alternatives are not precluded

R1-2104115        Final summary for TRS/CSI-RS occasion(s) for idle/inactive Ues     Moderator (Samsung)

8.7.1.3       Other

R1-2102407         Paging and TRS indication in idle/inactive modes      OPPO

R1-2102534         Discussion on paging grouping       vivo

R1-2102567         Additional simulation results of UE power consumption in RRC idle and inactive state       ZTE,Sanechips

R1-2102643         Details of PEI configuration            CATT

R1-2103389         Analysis on power consumption for IDLE mode and RedCap  Huawei, HiSilicon

R1-2103426         Paging indication based on sub-time units    InterDigital, Inc.

R1-2103644         Modeling of Network Power Consumption   Ericsson

8.7.2        Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime

Void (not be handled during this e-meeting). No contributions please.

The following is withdrawn.

R1-2103634         Discussion on DCI-based power saving adaptation     ITRI

8.7.33        Other

Void (not be handled during this e-meeting). No contributions please.

 RAN1#105-e

8.7       UE Power Saving Enhancements

Please refer to RP-200938 for detailed scope of the WI

8.7.1        Enhancements for idle/inactive-mode UE power saving

8.7.1.1       Potential paging enhancements

R1-2104221         Discussion on power saving enhancements for paging ZTE, Sanechips

R1-2104251         Paging enhancements for UE power saving in IDLE/inactive mode        Huawei, HiSilicon

R1-2106011         Paging enhancements for idle/inactive mode UE power saving vivo       (rev of R1-2104371)

R1-2104432         Discussion on potential paging enhancements for UE Power Saving      Spreadtrum Communications

R1-2104532         Paging enhancement for UE power saving    CATT

R1-2104622         Discussion on paging early indication design              CMCC

R1-2104682         Paging enhancements for idle/inactive UE power saving           Qualcomm Incorporated

R1-2104787         Further discussion on Paging enhancements for power saving  OPPO

R1-2104916         On Paging Enhancements for UE Power Saving          Intel Corporation

R1-2105116         Paging early indication for idle/inactive-mode UE      Apple

R1-2105174         Considerations on potential paging enhancements      Sony

R1-2105321         Discussion on paging enhancements              Samsung

R1-2105386         On Paging Enhancements for Idle/Inactive Mode UE Power Saving       MediaTek Inc.

R1-2105434         Discussion on potential paging enhancements             LG Electronics

R1-2105474         On paging enhancement    Panasonic

R1-2105504         On paging enhancements for UE power saving           Nokia, Nokia Shanghai Bell

R1-2105573         Paging enhancements for power saving         Xiaomi

R1-2105708         Discussion on paging enhancements              NTT DOCOMO, INC.

R1-2105742         Paging enhancements for UE power saving  InterDigital, Inc.

R1-2105770         Paging enhancement for UE power saving    Lenovo, Motorola Mobility

R1-2105791         Design of Paging Enhancements     Ericsson

R1-2105886         On  paging early indication              Nordic Semiconductor ASA

[105-e-NR-R17-PowSav-01] – Weide (MediaTek)

Email discussion regarding potential paging enhancements

• 1^st check point: 5/21
• 2^nd check point: 5/25
• Final check: 5/27

R1-2106076        Summary of paging enhancements             Moderator (MediaTek)

Agreement:

For UE subgroups indication in physical layer, maximum of 8 subgroups per PO is supported.

Conclusion:

To down-select one solution for PEI physical-layer channel/signal in RAN1 #106-e, using below as a starting point:

·        PDCCH-based PEI

·        SSS-based PEI

·        TRS/CSI-RS-based PEI

Note: Additional details for each of the above 3 solutions are encouraged for more informed down-selection

Note: further refinement of the above list is possible, e.g., by merging/further splitting, depending on significance of the commonality and/or differences

Agreement:

Observation:

Dynamically sharing PDCCH resources of Rel-15 UEs (whether or not this is an important aspect to consider for PEI is FFS)

Ÿ  For PDCCH-based PEI,

o   PEI can dynamically share resources with PDCCH for Rel-15 UEs within a PDCCH CORESET at granularity of one or more candidates

§  Exact number of multiplexed/impacted Rel-15 PDCCH candidates depends on AL used for PDCCH-based PEI and relative size of PDCCH CORESET, etc.

Ÿ  For SSS-based PEI and for the case of partial overlap of CORESET and PEI

o   For interleaved CORESET (such as CORESET#0), SSS-based PEI can dynamically share resources with PDCCH for Rel-15 UEs only at CORESET-level granularity

o   For non-interleaved CORESET, SSS-based PEI can dynamically share resources with PDCCH for Rel-15 UEs within a PDCCH CORESET at granularity of one or more candidates

§  Exact number of impacted Rel-15 PDCCH candidates depends on relative size and location of PDCCH CORESET, etc.

Ÿ  For TRS/CSI-RS-based PEI and for the case of partial overlap of CORESET and PEI

o   For interleaved CORESET (such as CORESET#0), TRS/CSI-RS-based PEI can dynamically share resources with PDCCH for Rel-15 UEs only at CORESET-level granularity

o   For non-interleaved CORESET, TRS/CSI-RS-based can dynamically share resources with PDCCH for Rel-15 UEs within a PDCCH CORESET at candidate level granularity

§  Exact number of impacted Rel-15 PDCCH candidates depends on CSI-RS mapping pattern, relative size and location of PDCCH CORESET, etc.)

Agreement:

For paging indication to the subgroups in a PO,

Ÿ  For PDCCH-based PEI, subgroups in a PO are indicated by one PEI

o   One bit in the DCI payload indicating one UE subgroup is supported

§  FFS: Whether code-point based mapping is utilized, and, if so, how to map to the subgroups in a PO

Ÿ  For SSS-based PEI, subgroups in a PO are indicated by a set of sequence realizations

o   FFS: Sequence mapping design for supporting up to 8 subgroups per PO

o   Physical-layer configuration(s) and sequence generation design are subject to no impact to initial access and RRM measurements of legacy UEs

Ÿ  For TRS/CSI-RS-based PEI, subgroups in a PO can be indicated by the following alternatives

o   Alt 1: One TRS sequence with orthogonal cover as PEI transmitted in the PEI monitoring occasion where one orthogonal cover of the PEI indicates one subgroup or combination of subgroups

§  FFS: Design details for the orthogonal cover

o   Alt 2: A set of TRS sequences indicating the subgroups with one selected sequence transmitting in one TRS resource

§  FFS: Sequence mapping design for supporting up to 8 subgroups per PO and combination of subgroups

o   Alt 3: Multiple TRS/CSI-RS resources FDMed/TDMed /CDMed in the same monitoring occasion where one TRS/CSI-RS resource indicates one subgroup

§  Reuse Rel-15/16 CSI-RS FDM/TDM/CDM patterns for supporting up to 8 subgroups per PO

Ÿ  Note : It is RAN1 understanding that Physical-layer configuration(s) for paging early indication to the subgroups is subject to the same idle-mode reception bandwidth as CORESET-0 frequency span

Agreement

Observation:

For the comparison of PEI candidate designs, the following table summarizes average power saving gains based on companies contributions: